Doug recently introduced the template publish-to-pypi-python3 and used it for all official projects. It only has a minimal python3 usage (calling setup.py sdist bdist_wheel) that should work with any repo.
Thus, I pushed a a series of changes up - see https://review.openstack.org/#/q/topic:publish-pypi - to rename publish-to-pypi-python3 back to publish-to-pypi. Thus, everybody uses again the same template and testing. Note that the template publish-to-pypi-python3 contained a test to see whether the release jobs works, this new job is now run as well. It is only run if one of the packaging files is updated - and ensures that uploading to pypi will work fine. If this new job now fails, please fix the fallout so that you can safely release next time. The first changes in this series are merging now - if this causes problems and there is a strong need for an explicit python2 version, please tell me, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev