Skip to content
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

PyBrain: Mark as broken #29198

Closed
wants to merge 1 commit into from
Closed

Conversation

vanschelven
Copy link
Contributor

It's broken on all versions of Python (I've tried 2.7, 3.4, 3.5, 3.6)

I think the root cause is that PyBrain is not working with numpy >= 1.12.0 as I reported here:
pybrain/pybrain#217

(The relevant release notes may be found here):
https://docs.scipy.org/doc/numpy-1.12.0/release.html#compatibility-notes

The PyBrain github repo does not seem very active (last commit 18 months ago, last release 3 years),
so I have some doubts as to whether this will be fixed any time soon.

I suppose an alternative solution could be to reintroduce the explicit dependency to numpy 1.11. But,
this is not entirely trivial: in c9b4a2f, the versions 1.10, 1.11, 1.12 were folded into a single version.
Also, the numpy dependency is not a direct one, but is implied via scipy

Motivation for this change
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • Linux
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

It's broken on all versions of Python (I've tried 2.7, 3.4, 3.5, 3.6)

I think the root cause is that PyBrain is not working with numpy >= 1.12.0 as I reported here:
pybrain/pybrain#217

(The relevant release notes may be found here):
https://docs.scipy.org/doc/numpy-1.12.0/release.html#compatibility-notes

The PyBrain github repo does not seem very active (last commit 18 months ago, last release 3 years),
so I have some doubts as to whether this will be fixed any time soon.

I suppose an alternative solution could be to reintroduce the explicit dependency to numpy 1.11. But,
this is not entirely trivial: in c9b4a2f, the versions 1.10, 1.11, 1.12 were folded into a single version.
Also, the numpy dependency is not a direct one, but is implied via scipy
@FRidh
Copy link
Member

FRidh commented Sep 10, 2017

I think the root cause is that PyBrain is not working with numpy >= 1.12.0 as I reported here:
pybrain/pybrain#217

Seems plausible. I have a package of mine that I need to fix for the same reason.

I suppose an alternative solution could be to reintroduce the explicit dependency to numpy 1.11. But,
this is not entirely trivial: in c9b4a2f, the versions 1.10, 1.11, 1.12 were folded into a single version.
Also, the numpy dependency is not a direct one, but is implied via scipy

In Nixpkgs we only keep a single version of a package, aside from some special cases, and therefore I am opposed to that kind of solution. In any case, even if we have multiple versions, then packages shouldn't retain a runtime-dependency on a specific version.

Also, the numpy dependency is not a direct one, but is implied via scipy

That's no problem. You can override the Python package set to point to an older version of numpy. Then, the whole package set will use that version of numpy.

@vanschelven
Copy link
Contributor Author

@FRidh given the discussion above, could you just merge & close the PR?

N.B. the branch is unfortunately off release-17.09, so closing the PR should be accompanied with a cherry-pick to master (which is the reverse of the usual workflow, sorry about that)

Thanks!

@FRidh
Copy link
Member

FRidh commented Sep 13, 2017

pushed 50d3655 and to 17.09

@FRidh FRidh closed this Sep 13, 2017
@vanschelven vanschelven deleted the pybrain branch September 13, 2017 07:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants