When researching about the best way to use C macros for creating a
unified Python2/3, I came across this nice tool called "py3c" which aims
to do for C extensions what "six" does for Python modules:
https://py3c.readthedocs.org/
I think this is exactly what we need and would be the most maintainable
solution, and everything would be nicely documented. Much better than
invent our own conventions and compatibility macros.
An alternative that would make PyGreSQL even more maintainable in the
long run would be to rewrite everything using CFFI or Cython. But we
should not make such a drastic move in version 5.x. That might be
something to consider for version 6.x.
What do you think? If it's ok, I would start to make the move to py3c
and get the merged tests from 4.x running again.
-- Christoph
_______________________________________________
PyGreSQL mailing list
[email protected]
https://mail.vex.net/mailman/listinfo.cgi/pygresql
