pkginfo vs. twine version conflict by downgrading pkginfo 1.12-->1.10#8
Open
mengsig wants to merge 1 commit into
Open
pkginfo vs. twine version conflict by downgrading pkginfo 1.12-->1.10#8mengsig wants to merge 1 commit into
mengsig wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In the [dev] install of pyretechnics there is a version incompatibility between
pkginfoandtwine. Running onpython3.11the following:Yields the following error message:
ERROR: Cannot install pyretechnics and pyretechnics[dev]==2025.6.13 because these package versions have conflicting dependencies. The conflict is caused by: pyretechnics[dev] 2025.6.13 depends on pkginfo~=1.12.1.2; extra == "dev" twine 5.1.1 depends on pkginfo>=1.8.1 twine 5.1.1 depends on pkginfo<1.11 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip to attempt to solve the dependency conflict ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflict.Personally, I felt more comfortable downgrading pkginfo 1.12 --> 1.10 than upgrading twine (I do not even know if there is a twine release that supports pkginfo 1.12).
Tests passed ✔️