Skip to content
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

Python package identification might throw exception on valid setup.py/setup.cfg #131

Closed
murphm8 opened this issue Nov 17, 2018 · 4 comments
Labels
question Further information is requested

Comments

@murphm8
Copy link
Contributor

murphm8 commented Nov 17, 2018

Pip is adding support for PEP 508 URL dependencies pypa/pip#5571. I believe that the code linked below will throw an exception if there is a URL in the dependencies list since it is 'not a valid version'.

requirement = parse_requirement(requirement_string)

@dirk-thomas
Copy link
Member

Can you please provide a reproducible example.

@dirk-thomas dirk-thomas added the question Further information is requested label Nov 17, 2018
@dirk-thomas
Copy link
Member

@murphm8 Friendly ping.

@murphm8
Copy link
Contributor Author

murphm8 commented Nov 29, 2018

Hey, sorry I haven't followed up. Been super busy. I will get you a reproduction as soon as I am able.

@murphm8
Copy link
Contributor Author

murphm8 commented Nov 29, 2018

I ran a quick test. I must've been using an improperly formatted string when I tried this before. I tested building a python package with a dependency of colcon-core@git+https://github.com/colcon/colcon-core.git#egg=colcon-core and colcon-core@git+https://github.com/colcon/colcon-core.git@0.3.12#egg=colcon-core-0.3.12.

The create_dependency_descriptor returned a DependencyDescriptor with name colcon-core. For the dependency with the version specified there is no version metadata, but I think that is expected.

For bundle I am installing dependencies into the bundle based on this metadata. It might be beneficial to put these PEP 508 urls in the metadata so the correct version is installed when the dependency was specified as a PEP 508 url.

Closing this since it doesn't appear that the parse requirement will fail with a correctly formatted PEP 508 url.

@murphm8 murphm8 closed this as completed Nov 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Development

No branches or pull requests

2 participants