Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This reverts commit 96874c6. - No package depends on this version. - As a guideline we only keep one version of each package. Exceptions exist but only with a good reason. - Expressions shouldn't be in `python-packages.nix` but in `python-modules`, as explained in the docs and the header of the file. - I won't maintain these versions.
- Loading branch information
Showing
2 changed files
with
0 additions
and
111 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6f1f1a5
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.
cc @shlevy
6f1f1a5
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.
Pandas is an end-user library with changing API, we have code that depends on the old version. Sorry about the maintainer field, I should have removed that when I resurrected these from git. I'll re-add with me as a maintainer.
6f1f1a5
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.
Still, we only keep a single version. I suggest keeping the version you need in your copy of Nixpkgs or as an overlay.
6f1f1a5
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 are plenty of other packages in nixpkgs we keep multiple versions of. The point of a package repo is to provide packages users want to use. There's no reason not to add this if there's a use case for it.
6f1f1a5
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.
But are there other users that are interested in exactly this combination of two packages? You wrote
so to me it seems that you then provide that specific version there.
In any case, a (fixable) issue remaining is also that your package (pandas) depends on a specific version of another package (scipy_17). This causes problems if you create a python env and have other packages that depend on the other version of scipy. Therefore, if we would add them, they should not depend on a specific version. An example is Django. However, then you will need to override the package set at which point you may as well have your whole pandas/scipy expression there as well...
6f1f1a5
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.
I was under the impression (based on the commit I pulled this from) that pandas 0.17 required scipy 0.17. I am testing now to see if pandas 0.17 can work with our current scipy version.
I don't know if others will use this version, but I am still able to find recent questions about it on stack overflow etc. so it seems so. In any case, we do not require maintainers to prove that multiple users use the packages they maintain, and there's no reason to here. If no others use it, oh well. If others do want to use it, they get to benefit from the fact that the expression is already here and maintained.