#12710 closed enhancement (fixed)
Publish TracMercurial to PyPI
Reported by: | Ryan J Ollos | Owned by: | Ryan J Ollos |
---|---|---|---|
Priority: | normal | Milestone: | plugin - mercurial |
Component: | plugin/mercurial | Version: | |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: |
Published TracMercurial 1.0.0.7 to pypi:TracMercurial. |
||
API Changes: | |||
Internal Changes: |
Description
Mentioned in comment:8:ticket:10411. If there are no objections I'll publish the package to PyPI.
Attachments (0)
Change History (8)
comment:1 by , 8 years ago
Release Notes: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
comment:2 by , 8 years ago
Thanks!
Did you use a setuptools command to build the wheel and publish it? (e.g. bdist_wheel upload
)
comment:3 by , 8 years ago
I've been using twine to register and publish to PyPI:
$ python setup.py sdist bdist_wheel $ twine register dist/*.whl $ twine upload dist/*.tar.gz dist/*.whl
comment:4 by , 8 years ago
I've adding some documentation on publishing packages to PyPI: th:DevGuide#PublishingPackagestoPyPI. Contributions welcome.
Maybe a publish
command would be a good complement to the upload
command in the Trac Makefile, or have command switches so that upload
can push files to one or both locations (FTP and PyPI)?
comment:5 by , 6 years ago
1.0.0.8 was released in [61/mercurial-plugin]. I pushed this release to PyPI: pypi:TracMercurial/1.0.0.8.
comment:6 by , 6 years ago
Looks like it would be good to release 1.0.0.9 as well. Any reason to wait on that?
comment:8 by , 6 years ago
Thanks for confirming. Released 1.0.0.9 ([71/mercurial-plugin]): pypi:TracMercurial/1.0.0.9. Bumped version in [72/mercurial-plugin]. Edited TracMercurial@117.
1.0.0.7 published to pypi:TracMercurial. I bumped the version to 1.0.0.8dev for development. cboos and jun66j5 are also package owners. I could add Peter, but unsure of a PyPI username.
Edited TracMercurial@109.