Skip to content

Conversation

zware
Copy link
Contributor

@zware zware commented Sep 18, 2025

This is effectively a replacement for --skip-existing with non-PyPI
repositories. It is not allowed when using [Test]PyPI, and is instead a
way for users of other repositories to choose which status(es) can be
ignored.

This commit also rewords the UnsupportedConfiguration message a bit;
instead of asserting that the configured repository does not support a
particular feature (which is not actually checked), instead assert that
Twine does not support using the feature(s) with the configured
repository.


This option is technically complementary to #1270; the two don't really have anything to do with each other other than offering a way to get around the non-PyPI --skip-existing issue, but this one seems less prone to being a slippery slope and offers a solution for users of repositories that don't act enough like PyPI. Overall I think I prefer this approach, and if accepted I would abandon #1270.

This is effectively a replacement for --skip-existing with non-PyPI
repositories.  It is not allowed when using [Test]PyPI, and is instead a
way for users of other repositories to choose which status(es) can be
ignored.

This commit also rewords the UnsupportedConfiguration message a bit;
instead of asserting that the configured repository does not support a
particular feature (which is not actually checked), instead assert that
Twine does not support using the feature(s) with the configured
repository.
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.

1 participant