from types import NoneType in orm fails for python3.1.1

Issue #1584 resolved
Former user created an issue

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)

  1. Former user 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.

  2. Log in to comment