Option --no-use-pep517 not supported in requirement files
See original GitHub issueEnvironment
- pip version: 19.1
- Python version: 3.6.7, 2.7.15
- OS: any
Description
Specifying the option --no-use-pep517
in a requirements file results in
ERROR: Invalid requirement: --no-use-pep517 docopt pip: error: no such option: --no-use-pep517
Expected behavior Package is installed not using PEP 517
How to Reproduce
- Have this requirements file:
--no-use-pep517 docopt
- Run
pip install -r requirements.txt
(removing the option form the file and passing it directly works normal)
Output
pip install -r requirements.txt
Usage: pip [options]
ERROR: Invalid requirement: --no-use-pep517 docopt
pip: error: no such option: --no-use-pep517
This Issue regards specifying --no-use-pep517
inside a single requirement file. It is related to #6433, where it fails when we have nested requirement files and specify the option outside of them, i.e. give it directly as an argument to the pip invocation.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:11 (8 by maintainers)
Top Results From Across the Web
Using "-t" option inside a requirements.txt file - Stack Overflow
As of today (in pip version 21.2.4), the -t, --target <dir> option is not supported in requirements.txt files. The section "Requirements ...
Read more >Requirements File Format - pip documentation v22.3.1
Supported options #. Requirements files only supports certain pip install options, which are listed below. Global options#. The following options have an effect ......
Read more >Manage required Python packages with requirements.txt
Use pip freeze > requirements.txt and manage python package ... edit the file to exclude this package or to use pip's options to...
Read more >User Guide — pip 10.0.0.dev0 documentation
Their syntax and contents is nearly identical to Requirements Files. There is one key difference: Including a package in a constraints file does...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I removed the
awaiting PR
label, following the two comments above.@pradyunsg Not to derail this particular issue, but I think this is not a good first issue; it might be a good second or third issue, but a contributor who is new to Python packaging is going to have trouble understanding specifiers, PEP 517, and so on. Removing the tag.