-
Notifications
You must be signed in to change notification settings - Fork 103
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
Github pip dependencies: InvalidRequirement: Expected end or semicolon #392
Comments
Thanks a lot for the examples and the analysis! We should definitely try and support this. |
Sounds like this might be fixed by #435 |
I tried it out in the meantime and #435 did resolve the issue with Also |
Hey @knedlsepp, thanks a lot for testing this! It seems that in the relevant code we are doing lots of really nasty manipulation of structured data as strings and with the deprecated I'm not so sure how difficult this is to fix. I made one very quick attempt in #457, but there are some substantial differences between We definitely need a bunch of tests for the various forms of URLs, and also I think this should break if the URL contain basic auth. |
@maresb Thanks for such quick actions on that topic! :)
This sounds like a good task for a first time contributor. I'll see what I can come up with. 😃 |
@knedlsepp, exactly! That would be amazing. |
Big bonus points if you can find well-established pre-existing or builtin libraries to do all this URL manipulation. Otherwise we're going to miss edge cases and increase our maintenance burden. |
I'm going to close this issue because my original bug was resolved, but filing a new one to track ongoing issues with the pip + git integration |
Checklist
What happened?
Since #4 is closed (and a feature request), I'm reopening this as a bug report:
environment.yml
conda-lock -f environment.yml
and see the following error:Seems like the issue is passing
to
weparsed_req = Requirement.parse(requirement_specifier)
I'm not 100% sure how to solve this, I think everything should move to using the new
from packaging.requirements import Requirement
interface asfrom pkg_resources import Requirement
is deprecated, but that doesn't solve the parsing issue (hacked up a WIP PR but it's non functional)Note adding a name to the requirements solves this particular issue but
but causes another one:
The text was updated successfully, but these errors were encountered: