On Monday, January 13, 2020 at 4:51:24 PM UTC-8, RjOllos wrote: > > > > On Saturday, January 11, 2020 at 5:57:14 AM UTC-8, Peter Suter wrote: >> >> On 11.01.2020 14:24, Rick van der Zwet wrote: >> >> 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: >> >> Maybe you could ZIP it. >> Or even better might be to link to a forked repository of >> https://github.com/edgewall/trac >> >> > I did not bother with any Python 2 compatibility, as such did not use >> > the six library. >> >> As I understand it this is fine, as Ryan had also mentioned a plan to >> move towards that. >> >> > Secondly the pointed rjollos.git@t12130_python3.1 >> > seemed rather old and outdated and using python 3.1 as base version. >> >> What Python version do you target? >> I'm not sure the branch name does refer to python3.1 or rather to >> something like "python3.x experiment branch revision .1". >> I thought Python 3.3+ was already assumed. >> Is there a big pain in supporting that? >> It seems only 3.5+ are not EOL yet. >> https://devguide.python.org/#status-of-python-branches >> Although supporting some Linux distributions would imply quite old >> versions. >> https://trac.edgewall.org/wiki/TracDev/ApiChanges/1.3#CompatibleDistros >> >> > 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. >> >> That's correct. The Git repository trunk branch is also automatically >> mirrored and up-to-date. https://github.com/edgewall/trac >> >> > 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. >> >> Have you tried the tests yet? >> >> Cheers, >> Peter >> > > Good points. > > I expect it's going to be difficult for anyone lacking experience on the > project to produce a patch that we can use. I don't want to discourage > anyone that is up to the task but trying to be realistic so that it doesn't > feel like wasted effort. > > I'm hoping to find time to work on the Python 3 port soon. Any attempts I > make will need a lot of help from the experts: you, Jun and Christian. > > I think we should target Python 3.6+ considering 3.5 is EOL in Q3 and the > most optimistic official release of a stable Trac w/ Python 3 would be > mid-year. > > - Ryan >
See #12130 for recent activity on the changes proposed by Jun. https://trac.edgewall.org/ticket/12130 - Ryan -- 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/af9f7e09-6f75-4874-b583-30664a3d0067%40googlegroups.com.
