-
-
Notifications
You must be signed in to change notification settings - Fork 555
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
Running "pip install ." fails on Windows #755
Comments
@sschuberth Thanks! It should definitely work. Weirdly enough this seems to be related to the new test files added for #688 that git can handle ok on Windows but pip chokes on. The other weird stuff is that the So a possible cause could be the version of pip and setuptools you have: can you try with pip 9.0.1? |
Just tried, same problem with pip 9.0.1:
|
@sschuberth Thanks. The fix is easy: I will tar the test files so they are not "visible" in a checkout and only extracted at test run time and this should likely fix this. |
@sschuberth which version of Python do you run btw? |
I'm using Python 2.7.12, Confirmed that after manually deleting Any idea why the Windows CI did not also break? |
@sschuberth good. No idea why the Ci works OK. They may have something special in their env. |
The package that failed to install due to the missing compiler is called just |
* this ensures that the repo can be cloned on Windows Signed-off-by: Philippe Ombredanne <[email protected]>
I fixed the pip install issue from a clone. As for the installation of packages that have native code that needs to be compiled there is no easy way out on Windows short of installing a compiler (or point pip to use the pre-built packages in thirdparty/ which is exactly the same as running configure ...) |
* this ensures that the repo can be cloned on Windows Signed-off-by: Philippe Ombredanne <[email protected]>
Signed-off-by: Philippe Ombredanne <[email protected]>
Signed-off-by: Philippe Ombredanne <[email protected]>
Signed-off-by: Philippe Ombredanne <[email protected]>
* do not map the legacy "url" to anything #755 * allow to build a Package from data and not only from a file * do not return full location for the metafile but only filename #782 * ensure only one download_urls is created #779 * improve the mapping of "parties" * other misc code improvement and TODOs * add new tests for #755 and other samples Signed-off-by: Philippe Ombredanne <[email protected]>
Signed-off-by: Philippe Ombredanne <[email protected]>
* do not map the legacy "url" to anything #755 * allow to build a Package from data and not only from a file * do not return full location for the metafile but only filename #782 * ensure only one download_urls is created #779 * improve the mapping of "parties" * other misc code improvement and TODOs * add new tests for #755 and other samples Signed-off-by: Philippe Ombredanne <[email protected]>
@sschuberth this should be all set now, right? |
Unfortunately, it still does not seem to work with the current
|
Thank you! I now hate windows :D but we will fix this eventually ! |
So this should work nicely now... but as explained in #1214 this requires you to have a proper C/C++ compiler installed. |
Unfortunately, I'm still getting (almost) the same error with latest
|
@sschuberth you are cheating! 😆 But that may not be at all the issue here. Is this from a fresh checkout or download? have you created your own virtualenv? or not? it may be that there is some mixing up between various things there. |
Indeed I am using Git Bash, but since the Python I'm calling is a native Windows one and I'm not passing any paths as arguments, using
Sorry 😉 |
so the thing is that you have not "activated" the local virtualenv... |
After running
in
|
Thank you for testing! I will find a fix. |
Here is the skinny: this is a bug in pip that I would need to report and might never be fixed in Python 2. It gets confused by having specific unicode paths (that are in the test files). pip is trying to move these around when doing a If you use a I will report this to pypa/pip |
I was able to create a minimum package that shows the error. And I submitted a pip bug pypa/pip#5972 |
Thanks for this!
Speaking of it, what's the status / current plan to use Python 3 for ScanCode as I haven't seen any updates on #295 recently? |
IMHO the port could be a 3.1 right after a 3.0 release? what do you think? |
IMHO the port could be a 3.1 right after a 3.0 release--> I mean by these the scancode 3.1 right after the 3.0 release. many 3's are confusing ;) |
Well, if support of Python 3 would require any breaking changes to ScanCode, it would make more sense to me to do this with the new major 3.0 release of ScanCode rather than with a minor 3.1 release (in the spirit of semantic versioning). On the other hand, I could understand if you don't want to delay ScanCode 3.0 any further "just" because of Python 3.0 support. After all, it's all up to you 😉 |
FYI, still no update on the Pypa side. pypa/pip#5972 |
This is no longer an issue now that we only support Python 3 and dropped Python 2 support |
I'm not 100% sure this is supposed to work, but as it does on Linux, I believe it should work on Windows, too. Running
pip install .
on a fresh checkout of ScanCode givesNote that I'm deliberately not calling
configure
as I'm working on a generic way to detect Python project dependencies, and the generic way to install dependencies is to runpip install
AFAIK.The text was updated successfully, but these errors were encountered: