[Python-Dev] python 3 niggle: None < 1 raises TypeError

Stephen J. Turnbull stephen at xemacs.org
Thu Feb 20 06:08:44 CET 2014

Greg Ewing writes:

 > Data retrieved from a database is often passed to other code
 > that has nothing to do with databases, and data received from
 > other code is inserted into databases. Somewhere in between
 > someone is going to have to be careful to translate back and
 > forth between Nones and Nulls.

Sure.  The suggestion is to assign responsibility for such careful
translation to implementers of the DB API.

 > This is a recipe for chaos.

If it is, then chaos is already upon us because you can't be careful
even if you want to.

I don't know if fixing it is worth the work and confusion involved in
the fixing process, but fixing it will conserve (and maybe reduce)
chaos, not create it.

More information about the Python-Dev mailing list