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

Use Version, VersionSpecifiers and Requirement from PEP 440 and PEP 508 parser #7

Merged
merged 2 commits into from
Mar 30, 2023

Conversation

konstin
Copy link
Member

@konstin konstin commented Mar 22, 2023

This means we actually parse version, requires, dependencies , optional_dependencies, both validating them and allowing the user to actually use these field. If we also update of maturin, this prevents bugs like mozilla/bleach#655.

Using crates.io releases is currently blocked on PyO3/pyo3#2786

…08 parser

Using crates.io releases is currently blocked on PyO3/pyo3#2786
@messense
Copy link
Member

LGTM, I guess we should merge this after PyO3/pyo3#2786 since we can't publish to crates.io and you need to use git dep anyway?

@konstin
Copy link
Member Author

konstin commented Mar 22, 2023

yes; i'm not entirely sure how to proceed though since PyO3/pyo3#2786 seems stalled but i need it for pep440_rs and i don't want to publish a fork

@messense
Copy link
Member

If the Python API surface isn't big, maybe just use wrapper types to expose to Python for now and feature gate them in a separate module instead.

It's a bit tedious, but hey it works.

@konstin
Copy link
Member Author

konstin commented Mar 29, 2023

:/ done

@messense messense merged commit b86dee0 into main Mar 30, 2023
@messense messense deleted the pep-440-and-pep-508 branch March 30, 2023 01:50
@messense
Copy link
Member

Published in v0.5.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants