Using --target with --editable results in "internal" error
See original GitHub issueIt seems like --target
is not supported when using --editable
at the same time. It would be nice to have it working. Meanwhile there should be some better diagnostic as
c:\>pip install -t z:\1 -e git+https://github.com/kennethreitz/requests.git#egg=requests
results in
Obtaining requests from git+https://github.com/kennethreitz/requests.git#egg=requests
Updating c:\python\virtualenv\test\src\requests clone
Running setup.py egg_info for package requests
Downloading/unpacking certifi>=0.0.7 (from requests)
Running setup.py egg_info for package certifi
Downloading/unpacking oauthlib>=0.1.0,<0.2.0 (from requests)
Running setup.py egg_info for package oauthlib
Downloading/unpacking chardet>=1.0.0 (from requests)
Running setup.py egg_info for package chardet
Downloading/unpacking rsa (from oauthlib>=0.1.0,<0.2.0->requests)
Running setup.py egg_info for package rsa
warning: no files found matching 'README'
Downloading/unpacking pyasn1>=0.0.13 (from rsa->oauthlib>=0.1.0,<0.2.0->requests)
Running setup.py egg_info for package pyasn1
Installing collected packages: requests, certifi, oauthlib, chardet, rsa, pyasn1
Running setup.py develop for requests
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: option --home not recognized
Complete output from command c:\python\virtualenv\test\Scripts\python.exe -c "import setuptools; __file__='c:\\python\\virtualenv\\test\\src\\requests\\setup.py'; exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" develop --no-deps --home=c:\users\piotr\appdata\local\temp\tmp3abskl:
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: option --home not recognized
----------------------------------------
Command c:\python\virtualenv\test\Scripts\python.exe -c "import setuptools; __file__='c:\\python\\virtualenv\\test\\src\\requests\\setup.py'; exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" develop --no-deps --home=c:\users\piotr\appdata\local\temp\tmp3abskl failed with error code 1 in c:\python\virtualenv\test\src\requests
Storing complete log in C:\Users\Piotr\AppData\Roaming\pip\pip.log
Issue Analytics
- State:
- Created 11 years ago
- Reactions:2
- Comments:22 (3 by maintainers)
Top Results From Across the Web
Why can't I call pip with --target and --editable? - Stack Overflow
"pip install -e ." works but if I add the -t option I get the same error. Any workarounds? Can I just copy...
Read more >Remote desktop connection: An internal error has occurred
Go to the Start Menu, search for Local Group Policy and open up 'Edit group policy'. ... On the right-hand side, locate the...
Read more >large API call fails: Invalid target object in edit handler
Solved: When trying to send an rather large API call (atomic) to Panorama I receive this error message What I found out so...
Read more >Fix common Google Ads Editor errors
When using Editor, you may encounter error messages. This article shows you what the most common error messages mean, how to fix them,...
Read more >How to Fix the 500 Internal Server Error on Your WordPress ...
We go through why you may be getting this error and how to troubleshoot a 500 internal server error on WordPress and via...
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’d add that this is an issue for Google Appengine developers who need to install their dependencies in a directory in the app root but also need to deploy an editable dependency in a local checkout as part of a QA process. As it sits, the editable would need to be manually symlinked which is cumbersome.
I just experienced the same issue. As suggested by @jezdez you can work around this by doing the following (without using --editable that is):