Antoine Pitrou <pit...@free.fr> added the comment: > The second is whether we should take this opportunity to fix datetime > being a C extension module exclusively. I know PyPy has their own pure > Python version of datetime that they plan to eventually contribute. We > might as well use this as the chance to create Lib/datetime.py and have > that conditionally import _datetimemodule.c (see the heapq module on > how to handle this kind of situation).
Of we could let PyPy contribute their own version when they want, after all. I think additions to the datetime API are good in themselves, and we shouldn't make them depend on some mythical refactoring of the code into a separate pure Python module ;) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5094> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
