from types import NoneType in orm fails for python3.1.1
Issue #1584
resolved
in the orm module, properties.py there is an import and two instances of NoneType in the code. This makes python3.1.1 bomb. Simply removing the import and changing both instances of NoneType with
type(None)
yields positive results and is backwards compatible with python2.6 atleast. Though maybe this should be something done by the python3 conversion script.
Comments (5)
-
Account Deleted -
repo owner - changed milestone to py3k
-
Account Deleted Ah! I've almost filed another ticket because of this. Please fix it, or at least mention it in README.py3k.
Thanks for taking py3k compatibility seriously unlike lots of libs.
-
repo owner - changed status to resolved
-
repo owner - removed milestone
Removing milestone: py3k (automated comment)
- Log in to comment
I forgot to say Im using trunk as of yesterday