On 2020-01-10 18:53, Peter Suter wrote:
On 10/01/2020 00:20, Rick van der Zwet wrote:
..
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.
Sounds great! Have you considered attaching your patch to a ticket so
it does not get lost?
Not allowed: "Maximum attachment size: 512.0 KB:
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?
I did not bother with any Python 2 compatibility, as such did not use
the six library. Secondly the pointed rjollos.git@t12130_python3.1
seemed rather old and outdated and using python 3.1 as base version.
Since I am no trac-developer, I 'trusted' svn@trunk
(https://svn.edgewall.org/repos/trac/trunk/) to be the latest, how-ever
this is just a lucky guess by me.
Basically I first processed all files with ``2to3'' (the python2 to
python3 converter tooling) and next I fixed issues which mainly involved
changes with python3 default representation of strings and continued
doing so until I could load the first WikiStart without errors on the
console and log file.
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/trac-dev/70b71c9bbf644119d6098ab72290fbb7%40rickvanderzwet.nl.
