Test upcoming Twine release (1.10.0rc1)? #203
Comments
|
Thanks so much for reaching out!! I'm really glad to be able to collaborate to make sure that our users aren't adversely affected by updates. I just moved on Friday, so things are a bit hectic around the house, but I will make it my top priority this week to find some time both to contribute to pypa/twine#314 and to run our full test suite against the RC. And thanks for the heads up about pypi/warehouse#3123! I am personally very much looking forward to Warehouse's full rollout. From what I've seen, it's going to be a major improvement on the existing PyPI site. Anyway, I'll get on this hopefully tonight or tomorrow night at the latest, and I'll post updates both here and in pypa/twine#314. |
|
@mplanchard you may remove both our names and put yours as maintainer. |
Resolves #203 Related to pypa/twine#314 This commit adds an ``sh -c`` call, whose argument is the value of the environment variable ``PYPISERVER_SETUP_CMD``, or ``true`` if that variable is not set. This was specifically added to enable the ``pre_twine`` environment, which is provided to automatically test pre-releases of twine, both for our use (e.g. #203) and for the use of the twine maintainers (pypa/twine#314). The capacity to specify an arbitrary setup command via an environment variable may also wind up being useful in other cases in the future. In addition, the envlist is updated to include only Python versions we actually support. This commit also alphabetizes the ``dev.pip`` requirements and rmeoves specific requirements for testing using Python 2.5 (which we do not test against anymore).
Resolves #203 Related to pypa/twine#314 This commit adds an ``sh -c`` call, whose argument is the value of the environment variable ``PYPISERVER_SETUP_CMD``, or ``true`` if that variable is not set. This was specifically added to enable the ``pre_twine`` environment, which is provided to automatically test pre-releases of twine, both for our use (e.g. #203) and for the use of the twine maintainers (pypa/twine#314). The capacity to specify an arbitrary setup command via an environment variable may also wind up being useful in other cases in the future. In addition, the envlist is updated to include only Python versions we actually support. This commit also alphabetizes the ``dev.pip`` requirements and rmeoves specific requirements for testing using Python 2.5 (which we do not test against anymore).
|
@brainwane our existing test suite performs a twine upload, so I just added a tox environment in #204 that can be manually run to test with the current pre-release of twine against all supported Python runtimes with |
|
Thank you very much for the advice and the testing! https://pypi.org/project/twine/1.10.0/ is now out! |
|
And @mplanchard I hope you'll be at the PyCon sprints in May to collaborate with other packaging/distribution folks! |
|
@brainwane I wish I could be there! However, PyCon this year happens to fall right in the middle of my honeymoon, so I'm going to have to skip it 😉 Hopefully I'll be able to make another conference this year, or at least next year's PyCon! |
https://test.pypi.org/project/twine/1.10.0rc1/ is a release candidate for Twine 1.10.0 which I'm planning to release early this week. Please see the changelog for detailed notes under "Next feature release".
I believe this is how you test it out on its own:
pip install --upgrade --pre --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple twineI would to hear about any problems this new release causes in
pypiserver. And if there are some simple tests I can run before a new release to check whether a change intwinewould break core functionality for you, maybe you could mention that on pypa/twine#314.(By the way, I also work on Warehouse, the new codebase for https://pypi.org, and your list of similar projects in the
READMEhas been helpful to me! And I thought you might want to know about pypi/warehouse#3123 since it's about how your project's metadata renders on the new pypi.org.)Thanks.
The text was updated successfully, but these errors were encountered: