-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
pex.resolvable.InvalidRequirement: Unknown requirement type: . #360
Comments
Worth noting: |
Things work under 2.6, but fail as described under 2.7 and 3.6 at least:
|
different results on my machine for 2.7: 2.7:
3.6
the failure appears related to the setuptools version:
|
correlated the start of the issue with 34.x.x - further tracing reveals this relates to an inner setuptools capability miss due to incompatible installed vs required versions:
which causes a the reason it seems to work in the case of
ultimately, this scenario should bomb with a clearer indication that the setuptools version is incompatible vs appearing like the dist itself is invalid - or worse, falling back to using paths as literal requirement spec strings. |
Any suggestion on how to mitigate this? Just downgrade setuptools? |
@habnabit yep, afaict a downgrade to |
It used to be possible to clone a python repository and do 'pex .' (in other words, check if path is an exploded source package) and build it. Not sure when this behavior changed -- breaks some packaging scripts I've been using for periscope.
The text was updated successfully, but these errors were encountered: