Release new version of plugin on PyPI

[Ryan J Ollos]

I hope you don't mind if I create a ticket to trac the release of the latest version on ​PyPI, whenever that may happen.

I also wanted a way to communicate this change to you, and see if you had any suggestions. I haven't seen any links on trac-hacks that point to PyPI pages, but it seems like a valuable thing to have when such pages exist.

[ejucovy]

Thanks -- I'll hopefully be able to get around to it sometime this week.

I like the idea of putting PyPI links on trac-hacks. I think I've linked to PyPI for one or two of my plugins, but certainly with no consistency. Do you think some text about PyPI should even become part of the wiki page template? Or even a "PyPI Package Name" prompt in the New Hack form? Anything to encourage more people to register their plugins on PyPI, and upload new releases there regularly, seems like it would be a good thing for the whole Trac community.

(Of course there would have to be some good documentation somewhere about the PyPI registration/upload/release process. Pointing to Python community documentation would be important, but probably insufficient -- I suspect there are enough specifics and gotchas about Trac plugins, like i18n preparation, that would merit a dedicated packaging-how-to for plugin authors/maintainers. Does anything like this exist yet? I'd be happy to help write it if not.)

[Ryan J Ollos]

Replying to ejucovy:

Thanks -- I'll hopefully be able to get around to it sometime this week.

I lost track of this ticket. Sorry for the long delayed reply.

I like the idea of putting PyPI links on trac-hacks. I think I've linked to PyPI for one or two of my plugins, but certainly with no consistency. Do you think some text about PyPI should even become part of the wiki page template? Or even a "PyPI Package Name" prompt in the New Hack form?

Yeah, I like this idea of making it part of the New Hack form.

Anything to encourage more people to register their plugins on PyPI, and upload new releases there regularly, seems like it would be a good thing for the whole Trac community.

I'm open to these ideas, as well as the possibility of a PyPI macro with an image - essentially just a fancy way of promoting the PyPI links. Would it be possible to automate the upload of the archives to PyPI? I imagine that would be complex to setup, but the payoff would be big.

(Of course there would have to be some good documentation somewhere about the PyPI registration/upload/release process. Pointing to Python community documentation would be important, but probably insufficient -- I suspect there are enough specifics and gotchas about Trac plugins, like i18n preparation, that would merit a dedicated packaging-how-to for plugin authors/maintainers. Does anything like this exist yet? I'd be happy to help write it if not.)

I don't think anything like that exists at the moment. You know so much more than I do about this subject, so I'll look to you for the best way forward ;)

[ejucovy]

Sorry I didn't get to this sooner -- had a busy couple of months. I've just tagged and released a 3.0: ​https://pypi.python.org/pypi/TracPermRedirect/3.0

[Ryan J Ollos]

Oh, great, thanks. I'm connecting the dots now ... I had previously opened #10709, which you kindly fixed, but I guess we were still pulling in the old version from PyPI to Bloodhound. I opened ​bh:#432 today thinking the problem looked familiar, so I can check if it's fixed now.

[Ryan J Ollos]

I posted some ideas from the comment:1 - comment:2 discussion here.