pip install -r requirements.txt – fails on fresh install #7
Conversation
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
because pip hasn't installed django yet, which is referenced by the django_faker/__init__.py adding setup_requires as an 'abstract' dependency in addition to install_requires, as according to the documentation: "...projects listed in setup_requires will NOT be automatically installed on the system where the setup script is being run. They are simply downloaded to the setup directory if they’re not locally available already. If you want them to be installed, as well as being available when the setup script is run, you should add them to install_requires and setup_requires..." unfortunately, I don't expect this to work because of the separation or responsibilities between pip and setuptools. We need to be able to tell pip to complete the installation of django completely, before carrying out django-faker
|
+1 also submitted a PR fixing same issue #29 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
because pip hasn't installed django yet, which is referenced by the
django_faker/__init__.pyadding setup_requires as an 'abstract' dependency in addition to install_requires, as according to the documentation:
"...projects listed in setup_requires will NOT be automatically installed on the system where the setup script is being run. They are simply downloaded to the setup directory if they’re not locally available already. If you want them to be installed, as well as being available when the setup script is run, you should add them to install_requires and setup_requires..."
unfortunately, I'm not sure this will work because of the separation or responsibilities between pip and setuptools.