On 2020-01-10 07:29, Steffen Hoffmann wrote:
Am 10. Januar 2020 00:20:03 MEZ schrieb Rick van der Zwet
<i...@rickvanderzwet.nl>:
Hi Folks,
Since python2 is EOL and scheduled to be removed from software
repositories like Debian and FreeBSD, trac is also in danger of
getting removed, since no Python 3 support is working yet.
I could spend my time trying to change all my Trac instances to a
alternative, how-ever I decided to give a blunt-axe approach in
converting the trunk code to be python 3 compatible (dropping support
for python 2 all together). After 6 hours hacking on the codebase I
got myself a 'hello world' version of Trac on Python3.
...
I be happy to spend some more time on it, ironing out most issues and
making sure all test cases are working again. How-ever I do like to
make sure this is the right way forward and/or I am not duplicating
work.
IIRC Trac 1.5 dev releases shall prepare Trac 1.6 that will work with
Phython3.
Which branch is this work based on? I was basing my work of @trunk,
which did not have any Python3 support at all.
Pushing Trac-hacks Trac plugin code in a broad sense is rather weak
yet.
To be honest I do not worry about the track-hacks trac plugin code yet,
I first like to see the core work with Python 3.
Anyway, more developer ressources will help to make it happen in a
convenient time. So please pick up corresponding discussions here
Where will this be?
review Trac dev code and join collaborativ effort for Track plugins as
much as you can. Thanks for asking!
Thanks for your answers, I am not a trac developer, so still finding my
way around the project. More pointers welcome :-)
Kind regards,
Rick
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to trac-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/trac-dev/5b72253d30c9ba0b3700a031014fe35e%40rickvanderzwet.nl.
