Re: [SQLObject] Proposed Plan for Porting to Python 3
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: Oleg B. <ph...@ph...> - 2014-12-08 13:13:35
|
The new maintainers of FormEncode promised compatibility of version 1.3 with Py3: http://www.formencode.org/en/latest/whatsnew-1.3.html They released the first alpha a year ago: https://pypi.python.org/pypi/FormEncode and it seems there are commits in the repository since that: https://github.com/formencode/formencode On Mon, Dec 08, 2014 at 11:54:00AM +0100, "Fetchinson ." <fet...@go...> wrote: > Hi all, I've started a python 3 branch of formencde in 2011 but didn't > have time to finish a complete port, you might still find it useful: > > https://bitbucket.org/fetchinson/formencode-py3k > > To be precise, this is still a python 2 branch, the goal was to have > something which can be fed into 2to3, at the current point there are > still 2 errors and 3 failures though when the output of 2to3 is > tested. This was my working cycle: > > > > #!/bin/bash > > rm -rf formencode-py3k-2to3.hg > cp -r formencode-py3k.hg formencode-py3k-2to3.hg > find formencode-py3k-2to3.hg -name .*.swp -exec rm {} ';' > /path/to/2to3 formencode-py3k-2to3.hg -w > cd formencode-py3k-2to3.hg > python3.2 -c "import nose;nose.run_exit()" > ../out 2>&1 > cd .. > vim out > > If I remember correctly all the errors are unicode related. In any > case I also think the best way is to have a single code base which > works with python 2 but which also translates smoothly by 2to3. So the > python 3 version can always be obtained by running 2to3 on the single > code base. > > Hope you find it useful! > Daniel Oleg. -- Oleg Broytman http://phdru.name/ ph...@ph... Programmers don't die, they just GOSUB without RETURN. |