On Mon, Jul 25, 2016 at 6:18 AM, Oleg Broytman <p...@phdru.name> wrote: > Hi! > > On Mon, Jul 25, 2016 at 01:03:33PM +0200, Neil Muller > <drnlmuller+sqlobj...@gmail.com> wrote: >> On 25 July 2016 at 12:40, Oleg Broytman <p...@phdru.name> wrote: >> > Does anybody here use SQLObject with Python 3? I started to believe it's >> > still impossible due to FormEncode not being ready for Python 3.4. But >> > our tests at Travis are passing. So I thing there is something wrong >> > significantly with the tests. Either Travis or Tox are betraying us. >> >> As far as I'm aware, no-one has reported significant issues with formencode >> 1.3.0 and python 3.4 . >> Formencode passes it's own test suite on python 3.4, and has for quite some >> time. >> https://travis-ci.org/formencode/formencode >> >> For the record, I am succesfully running a couple of programs using >> SQLObject 3 and python 3.4. >> >> The python3 Debian package build for sqlobject also runs the test suite, so >> it's not just passing the tests in the travis environment >> https://buildd.debian.org/status/fetch.php?pkg=sqlobject&arch=all&ver=3.0.0%2Bdfsg-2&stamp=1469130355 >> (although >> that's only with python 3.5) > > Thank you! Than there is something wrong with me: > > $ mkvirtualenv -p python3.4 SQLObject-py3 > Running virtualenv with interpreter /usr/bin/python3.4 > > $ pip3 install SQLObject > Collecting SQLObject > Using cached SQLObject-3.0.0-py2.py3-none-any.whl > Collecting PyDispatcher>=2.0.4 (from SQLObject) > Collecting FormEncode>=1.1.1 (from SQLObject) > Installing collected packages: PyDispatcher, FormEncode, SQLObject > Successfully installed FormEncode-1.3.0 PyDispatcher-2.0.5 SQLObject-3.0.0 > > $ python3.4 -c "from sqlobject import col" > Traceback (most recent call last): > File "<string>", line 1, in <module> > File > "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/sqlobject/__init__.py", > line 8, in <module> > from .col import * # noqa > File > "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/sqlobject/col.py", > line 31, in <module> > from formencode import compound, validators > File > "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/formencode/__init__.py", > line 3, in <module> > from formencode.api import ( > File > "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/formencode/api.py", > line 109, in <module> > class Invalid(Exception): > File > "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/formencode/api.py", > line 153, in Invalid > if unicode is not str: # Python 2 > NameError: name 'unicode' is not defined
So current master (I think) probably has this fixed: https://github.com/formencode/formencode/blob/203bb759cd21ca54dddae9772157342d477b45cd/formencode/api.py#L155 You can see what it was in 1.3.0: https://github.com/formencode/formencode/blob/1.3.0/formencode/api.py#L153 That team is likely struggling with Python 3 compatibility, but I think they probably just need to release a bug fix for 1.3.0 for people using Python 3. I asked the FormEncode team for a new release: https://github.com/formencode/formencode/issues/104#issuecomment-234927875 ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
