Mark Dickinson <dicki...@gmail.com> added the comment:
Eric, Serhiy: do you have opinions on the right way forward? Here are 6 options, on a spectrum of increasing level of acceptance of "N". -2. Remove "N" support for cdecimal right now (i.e., for Python 3.11), on the basis that there's no need for deprecation warnings, because it was never officially a feature. -1. Deprecate "N" support for cdecimal, remove it in Python 3.13. 0. Do nothing (the default), leaving _pydecimal and cdecimal inconsistent. 1. Add "N" support to the Python implementation for parity with cdecimal, but don't document it - leave it as an undocumented feature. 2. Officially add "N" support to decimal formatting - add documentation, tests, and fix the Python implementation. 3. Officially add "N" support to all numeric formatting ... ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue45739> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
