Okay, created http://trac.edgewall.org/ticket/12130
I'll direct all future discussion there unless there's a reason to come back to the mailing list. So that we don't need to rework a bunch of imports, it would be great to have a decision ASAP about whether to add six as a dependency or to vendor a copy of it. Currently I have it as a dependency. On Sunday, July 19, 2015 at 2:06:41 PM UTC-4, RjOllos wrote: > > On Sun, Jul 19, 2015 at 10:56 AM, Tim Graham <timog...@gmail.com > <javascript:>> wrote: > >> I put together a few initial patches (some is rebased from Jun's work) >> which should be fine to merge now, even if Python 2.6 is still supported. >> <https://github.com/timgraham/trac/pull/1> >> >> Is attaching patches to Trac tickets the best way to submit this work? >> That workflow seems painful from a code review perspective. >> >> I created a pull request to my own fork which seems like it would at >> least make review easier: https://github.com/timgraham/trac/pull/1 >> > > Providing a link to Git repository in a ticket is good. Looks like you > have a good granularity to those changesets, which should make them easy to > review. Thanks! > > I think it would be good to just create another ticket for Python3 > compatibility, one that we can close at the end of this development > iteration even if we haven't obtained full Python3 compatibility. You can > then post comments about your work to that ticket, and we can integrate it > to the trunk. > > When we finally have full Python3 compatibility we can close out #10083. > > - 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 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.
