-
-
Notifications
You must be signed in to change notification settings - Fork 292
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
Building Pex with requirements.txt that includes local directory + Python version specifier fails #2037
Comments
@rajaie-sg Is there any way you can provide a link to your repository? I can't repro using another Poetry-using repo. My steps: The poetry-using project with a distribution name of
Setup the same Pex scenario as yours:
So that worked fine.
|
I'm going to tentatively label this as a question since Pex appears to work just fine with file:// URL requirements and markers. |
@jsirois thank you for your reply. It took me a quite a bit of trying to figure it out, and turns out it's the space before the semicolon that's causing the issue. In your repro attempt, your
however, in my file, there is a space before the semicolon. I was using the output of When I run |
Ok. Yeah, that's a bug. |
Assume I have a file,
reqs.txt
with the contents below:Let's say I generated this file running
poetry export
.If I run
pex --resolver-version pip-2020-resolver -r reqs.txt -o /tmp/testing.pex
, then run/tmp/testing.pex
, and thenimport mylibrary
in the Python interpreter, I get an errorNo module named 'mylibrary'
If I try building the Pex file using a reqs.txt as below, then I am able to properly import
mylibrary
It looks like adding Python version specifiers for the local package causes it not to get installed. Is this expected?
I am using Pex
2.1.120
The text was updated successfully, but these errors were encountered: