-
Notifications
You must be signed in to change notification settings - Fork 60
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
Current release (0.3.15) doesn't build in python 3.6 ? #688
Comments
kdcount-0.3.29 fails with rainwoodman/kdcount#18 Pip then tries kdcount-0.3.28 (same error), kdcount-0.3.27 (same error), kdcount-0.3.26 (same error), and then kdcount-0.3.25 (works, from wheel). classylss-0.2.9 fails with:
... and many many more errors. Pip then tries classyls-0.2.8 (fails), classylss-0.2.7 (fails), all the way to classylss-0.2.1 (fails). Pip then says
so maybe it's backing off to a version of nbodykit that doesn't required classylss, or something like that? |
First bug report as a new maintainer! My guess is that you are correct that it is classylss that is the problem. As a quick fix you could try installing https://github.com/sbird/classylss by hand using python -m build . Medium-term we are going to port nbodykit to regular classy. |
Hi Simeon, Thanks for your reply! Building classylss succeeds, apparently despite a couple of bash complaints:
I then pip-installed the resulting dist/*.whl file, then did
So that did the trick! Thanks again! |
Glad to hear it! I will leave this open until pip install nbodykit just works without issues. |
Describe the bug
pip install nbodykit[extras]
produces a ton of error messages, and ends up installing versions:Note that it has installed
nbodykit-0.2.5
.Steps To Reproduce
Actual behaviour
Old version of nbodykit gets installed.
Expected behaviour
Newest version of nbodykit should get installed.
Version
heh,
If you suspect the problem is related to a dependency (e.g. Corrfunc, pmesh, or mcfit), then it is useful to report the version of that dependency as well (replacing
nbodykit
with the package name).Additional context
Provide any additional context about the problem here.
The text was updated successfully, but these errors were encountered: