Am 8. Januar 2020 19:33:16 MEZ schrieb Roger Oberholtzer <roger.oberholt...@gmail.com>: >On Wed, Jan 8, 2020 at 3:27 PM Martin <deba...@debian.org> wrote: >> >> On 2020-01-07 11:04, Roger Oberholtzer wrote: >> > Perhaps the Plugins that only work with Python 2 should be moved to >a >> > depreciated location? That might make it easier to see which >plugins >> > are effected by a move to Python 3. >> >> As a side note: In Debian we are in the process of remving Trac >> and all packaged plugins as part of the "py2removal" process. We >> would like to reintroduce the Python-3-based Trac again, when it >> is ready, of course. > >The list of Plugins for Trac 1.4 at least is much smaller than the >list of all plugins. > >Maybe it's time to enlist support in updating plugins? I'm a >programmer, but not a Python programmer. But I could consider trying >a few plugins to update. > >Is there a guide for the Trac part? Like the obvious things that need >to be changed for Trac 1.4? Something with example uses and not just >the names of the things to change?
I've been reading about Python3 before and right now scanning Trac 1.3 changes while trying to get AccountManagerPlugin Code ready for current Trac 1.4. After current Trac 1.5 releases Trac 1.6 is meant to switch to Python3. I'm willing to share and improve developer instructions as I did some years before for spread I18n support among plugins too. Let‘s do that together. How about that? Greetings Steffen Hoffmann -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/8B47C075-7A01-433B-A235-8BA5666E7BE2%40web.de.
