The version I posted is Python3, it does not require a 2to3.py conversion. Perhaps the best way to integrate them would be to take a 2to3.py conversion of your branch and diff it against mine.
It seems that the sqlalchemy guys have found a solution to writing Python2 code that reliably converts to Python3. They did it by adding a wrapper around 2to3.py that acts as a sort of preprocessor. That might be worth looking into. On Jun 26, 10:17 am, Armin Ronacher <[email protected]> wrote: > Timbo wrote: > > Check the files section. As far as proper Py3k support, Jinja2 would > > have to have all the tests re-written or wait until py.test is ported. > > The tests are actually rewritten already just not in the repo yet. I > will work on that during the EuroPython sprints. > > I'm happy to accept a Jinja2 python3 port assuming it works in a way > that I just have to run it through 2to3 to get an updated version (or > the other way round). > > Maintaining two completely independent versions at the same time is > tedious and I don't have the time for it :( > > Regards, > Armin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pocoo-libs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pocoo-libs?hl=en -~----------~----~----~----~------~----~------~--~---
