Add pyproject.toml to resolve build dependency on NumPy #806
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
When trying to install ProDy into a clean environment using pip and
requirements.txt
, sometimes pip tries to install ProDy before NumPy, and it causesNo files/directories in /tmp/pip-build-xxxxxxx/prody/pip-egg-info (from PKG-INFO)
error (which is not very helpful).Here's a
Dockerfile
to reproduce (same on 18.04):Doing
pip install
in two-step (first, install NumPy and SciPy, and only afterward install ProDy) works, but is rather inconvenient.ProDy is far from the first project that encountered this problem, and it seems the way to solve it is by using
pyproject.toml
.Unfortunately, it is supported only by recent versions of pip>=10.0. However, if one is using VirtualEnv, that should be okay.
I haven't tested the proposed solution extensively, but it solves the issue for me at least.