Skip to content

Conversation

tetsuo-cpp
Copy link
Contributor

Closes #426

@tetsuo-cpp
Copy link
Contributor Author

tetsuo-cpp commented Dec 8, 2022

pip-requirements-parser just shipped 32.0 before which pins packaging. They have a more comprehensive fix in the works which involves vendoring LegacyVersion. Further context at: aboutcode-org/pip-requirements-parser#10.

Anyway, I think we can just unpin this for now.

@di
Copy link
Member

di commented Dec 8, 2022

We should increase the lower bound on pip-requirments-parser as well to make sure the new version is being resolved.

@woodruffw woodruffw added the dependencies Pull requests that update a dependency file label Dec 8, 2022
@woodruffw woodruffw merged commit 3aa951d into main Dec 8, 2022
@woodruffw woodruffw deleted the alex/unpin-packaging branch December 8, 2022 15:26
@ringohoffman
Copy link

Any chance a release can be generated including this PR?

@woodruffw
Copy link
Member

@ringohoffman Are you seeing errors with the latest release? 2.4.8 includes #427, which pins packaging so that pip-requirements-parser doesn't fetch a newer one.

@ringohoffman
Copy link

My mistake, I misinterpreted this PR. I'll be keeping an eye on aboutcode-org/pip-requirements-parser#10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incompatibility with packaging>=22.0: cannot import name 'LegacyVersion' from 'packaging.version'
4 participants