-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deeptools: init at 3.3.1 #70995
deeptools: init at 3.3.1 #70995
Conversation
deepTools have a lot of small, very useful tools for manipulating bam files etc. |
do you mind rebasing on top of master? you got conflicts now :( |
Also, to be compliant with CONTRIBUTING.md, you should have roughly 1 commit relate to one package |
}: | ||
|
||
buildPythonPackage rec { | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your help on this @jonringer.
I've removed most of the blank lines I hope. Is there any guidelines for this? I seem to always want more blank lines than necessary.
I kept the package within the biology folder. Any special reason you want to move it to science? It is a bioinformatic tool alongside samtools, bedtools etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reasoning behind moving it from python-packages, is that it's meant to be used a standalone application and not imported by other python packages. It's to avoid the situation in which someone will try to do propagatedBuildInputs = [ deeptools ];
in another python packages, which is probably not what you want.
Another reason for doing this, is that some applications have very specific package versions which may deviate greatly from what's available in python-modules, #71797 for example
7d9a50f
to
363ab82
Compare
363ab82
to
90afd74
Compare
Thanks again for helping me out with this one @jonringer . I've added python3 as a parameter, and used I also wonder if I should do something like this: { lib
, python
}:
let
py = python.pkgs;
in
py.buildPythonApplication rec {
/* .. */
} Or if that is too much? Anyways, learned a lot playing around with this :-) |
Yea, since you're only referencing pythonPackages, I would be fine with a top-level |
of course, I didn't think about that. Will do that next time :-) this have been a great journey! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To adhere to contributing guidelines, do you mind breaking each package addition into it's own commit, it should follow:
pythonPackages.deeptoolsintervals: init at 0.1.9
.....
and so on for the git log history
90afd74
to
b46d4ea
Compare
Trying again :-) I have to work on my git skill I think, this was really good practice. I also changed, so that I use Just hope I did everything correctly here! |
to help you out in the future, you can use Generally when doing multiple packages, I iterate over the whole change set in un-staged. Then when im making the commits, I'll just For editing a particular commit in a series, you should use |
Thanks again @jonringer, I've used |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nix-review
passes on NixOS
diff LGTM
deeptools seems to wokr
[15 built, 1 copied (7.8 MiB), 2.1 MiB DL]
https://github.com/NixOS/nixpkgs/pull/70995
10 package were build:
deeptools python27Packages.deeptoolsintervals python27Packages.py2bit python27Packages.pybigwig python37Packages.deeptoolsintervals python37Packages.py2bit python37Packages.pybigwig python38Packages.deeptoolsintervals python38Packages.py2bit python38Packages.pybigwig
@GrahamcOfBorg build deeptools python27Packages.deeptoolsintervals python27Packages.py2bit python27Packages.pybigwig python37Packages.deeptoolsintervals python37Packages.py2bit python37Packages.pybigwig python38Packages.deeptoolsintervals python38Packages.py2bit python38Packages.pybigwig |
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @