On 10/01/2020 00:20, Rick van der Zwet wrote:
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.
To reproduce this 'hello world' Trac on Python3:
$ <<<apply patch against trunk r17226 (latest)>>>
$ mkdir ~/tracenvs
$ rm -Rf ~/tracenvs/project1; PYTHONPATH=. python3
./trac/admin/console.py ~/tracenvs/project1 initenv project1
sqlite:db/trac.db
$ PYTHONPATH=. python3 ./trac/web/standalone.py -e ~/tracenvs -p
8000
$ curl http://127.0.0.1:8000/project1
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.
Kind regards,
Rick
Hi,
Sounds great! Have you considered attaching your patch to a ticket so it
does not get lost?
Also, are you aware of this ticket:
https://trac.edgewall.org/ticket/12130#comment:51
It points to rjollos.git@t12130_python3.1 as the latest (but probably
far from up-to-date) status at porting Trac to Python3.
How does your patch compare to that?
Cheers,
Peter
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/trac-dev/bd1952b6-d85f-7378-8727-2ebff9d15b87%40gmail.com.
