-
-
Notifications
You must be signed in to change notification settings - Fork 287
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 requirement parsing is tripped up by files in the CWD with the same name as requirements' project names. #1188
Labels
Comments
This was spotted over in Pants trying to upgrade to Pex 2.1.25. Pants is notable here in that it uses the Pex PEX (a file named
|
jsirois
added a commit
to jsirois/pex
that referenced
this issue
Jan 22, 2021
Previously a file (not directory) in the CWD with the same name as the project name of a requirement being resolved would lead to an error. Modify the requirement parsing stress test to cause this error and fix parsing so the test passes. Fixes pex-tool#1188
jsirois
added a commit
that referenced
this issue
Jan 22, 2021
Previously a file (not directory) in the CWD with the same name as the project name of a requirement being resolved would lead to an error. Modify the requirement parsing stress test to cause this error and fix parsing so the test passes. Fixes #1188
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For example:
This only happens for files. Directories are handled just fine as is often exercised in the Pex repo where there is a top-level
pex
dir; yetpex pex -cpex -opex.pex
works just fine.The text was updated successfully, but these errors were encountered: