Thanks for the feedback. As suggested, I'll try to work on some smaller patches at first to get familiar with contributing and wait until 1.2 is released before submitting any major changes.
Looking at Jun's work, it seems he is more or less reimplementing a subset of the functionality that six provides in `trac.util.compat`. I think adding six as a dependency or vendoring it (Django's solution) would save some work. Either approach is fine with me, just let me know what you think. As far as dependencies go, I'll take a look as I go, but I'll just mention that Django now recommends the mysqlclient fork of MySQLdb as it's maintained and supports Python 3. By the way, Django's philosophy regarding supporting both Python 2 and 3 is here: https://docs.djangoproject.com/en/dev/topics/python3/ Please give a read a let me know if you disagree with any of it so I don't head down the wrong path. I suspect there's no need to support Python 3.2, so we can probably omit the unicode_literals step, at least initially. On Tuesday, July 7, 2015 at 6:22:32 PM UTC-4, Peter Suter wrote: > > On 08.07.2015 00:06, Ryan Ollos wrote: > > I expect it will be a major effort to have Trac support Python 3. Jun > has done some work on it, so he can best comment on the effort required. > [...] > > (2) http://trac.edgewall.org/ticket/11600#comment:20 > > By the way, Jun's work was linked in there: > https://github.com/jun66j5/trac/commits/python3 > > -- 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 post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
