Am 18.11.2015 um 19:19 schrieb D'Arcy J.M. Cain:
I realize that we couldn't change this before but for 5.0 I would like to consider changing the result of bool type to be an actual True or False (or None) rather than 't' or 'f'. Anyone see any issue with that?
There should be no problem if we do it on ingress, but on egress it should be configurable - I have a lot of legacy code that assumes 't' and 'f' and I would rather not want to change that. Maybe we can make the whole type system more configurable. We would need to add our own type, since boolean is not standardized in DB API 2.
Anyway, we should only start to make changes *after* the conversion to Python 3 is done and all tests are running. Otherwise it will be a mess, we will not know whether issues are caused by Py 3 or by the new things and changes we introduced.
-- Christoph _______________________________________________ PyGreSQL mailing list [email protected] https://mail.vex.net/mailman/listinfo.cgi/pygresql
