Allow testpypi runs #15
Merged
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
tmi
force-pushed
the
allowTestPypi
branch
5 times, most recently
from
68dff6a to
b052c3c
Compare
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.
Makes the
testpypioption a bit more useful -- allows to be run from any branch etc, so one can test without doing a release/tag etc. We are considering both ad hoc usage (for me as the wheelifier) and regular usage (eg whenever a PR tomainis open, autorun this) with thetestpypi: trueAdditionally, I add
twine checkstep and--verboseto the testpypi uploads. Useful in general when troubleshootinAdditionally, I install build dependencies prior to determining version -- because otherwise, for packages dependent on eg
setuptools_scm, this step fails