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

Replace packaging with packvers #108

Open
pombredanne opened this issue Dec 24, 2022 · 1 comment
Open

Replace packaging with packvers #108

pombredanne opened this issue Dec 24, 2022 · 1 comment

Comments

@pombredanne
Copy link
Member

To avoid the issues of pypa/packaging#530
packaging should be replaced by https://github.com/nexB/packvers/

See also SCTK and aboutcode-org/univers#95

swastkk pushed a commit to swastkk/python-inspector that referenced this issue Jan 12, 2023
* Work around changes in packaging by replacing it with packvers
to avoid issues with missing packaging.version.LegacyVersion.

* Also bump the versions of dparse2 and pip-requirements-parser
with new versions that are not subject the LegcacyVersion issue.

* Adjust the code and tests accordingly.

Reference: aboutcode-org#108
Reference: pypa/packaging#530
Signed-off-by: swastik <[email protected]># Please enter the commit message for your changes. Lines starting
swastkk pushed a commit to swastkk/python-inspector that referenced this issue Jan 12, 2023
* Work around changes in packaging by replacing it with packvers
to avoid issues with missing packaging.version.LegacyVersion.

* Also bump the versions of dparse2 and pip-requirements-parser
with new versions that are not subject the LegcacyVersion issue.

* Adjust the code and tests accordingly.

Reference: aboutcode-org#108
Reference: pypa/packaging#530
Signed-off-by: swastik <[email protected]>
swastkk pushed a commit to swastkk/python-inspector that referenced this issue Jan 13, 2023
* Work around changes in packaging by replacing it with packvers
to avoid issues with missing packaging.version.LegacyVersion.

* Also bump the versions of dparse2 and pip-requirements-parser
with new versions that are not subject the LegcacyVersion issue.

* Adjust the code and tests accordingly.

Reference: aboutcode-org#108
Reference: pypa/packaging#530
Signed-off-by: swastik <[email protected]>
swastkk pushed a commit to swastkk/python-inspector that referenced this issue Jan 13, 2023
* Work around changes in packaging by replacing it with packvers
to avoid issues with missing packaging.version.LegacyVersion.

* Also bump the versions of dparse2 and pip-requirements-parser
with new versions that are not subject the LegcacyVersion issue.

* Adjust the code and tests accordingly.

Reference: aboutcode-org#108
Reference: pypa/packaging#530
Signed-off-by: swastik <[email protected]>
swastkk pushed a commit to swastkk/python-inspector that referenced this issue Jan 13, 2023
* Work around changes in packaging by replacing it with packvers
to avoid issues with missing packaging.version.LegacyVersion.

* Also bump the versions of dparse2 and pip-requirements-parser
with new versions that are not subject the LegcacyVersion issue.

* Adjust the code and tests accordingly.

Reference: aboutcode-org#108
Reference: pypa/packaging#530
Signed-off-by: swastik <[email protected]>
pombredanne added a commit that referenced this issue Jan 13, 2023
Replace packaging with packvers #108
@swastkk
Copy link
Contributor

swastkk commented Jan 13, 2023

Time to close this issue ✅

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

No branches or pull requests

2 participants