Nick Coghlan <ncogh...@gmail.com> added the comment: FWIW, I actually prefer Mark's graduated approach to the Python->C migration since we have a continuously working module that will get incrementally faster over time. As profiling finds performance bottlenecks in the Python code, those parts can be migrated to C (e.g. as has been done initially with the manipulation of the coefficient, which has been one of the main time sinks in the decimal module since the days when it was still stored as a tuple instead of a string).
Having most of the module in C should be the endpoint, not where we attempt to start (as I recall, attempts to rewrite the whole module in C in one go have already been made, and they failed miserably). _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue2486> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
