Message407195
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 ... |
|
Date |
User |
Action |
Args |
2021-11-28 09:39:33 | mark.dickinson | set | recipients:
+ mark.dickinson, rhettinger, facundobatista, eric.smith, serhiy.storchaka |
2021-11-28 09:39:33 | mark.dickinson | set | messageid: <1638092373.95.0.0680559646671.issue45739@roundup.psfhosted.org> |
2021-11-28 09:39:33 | mark.dickinson | link | issue45739 messages |
2021-11-28 09:39:33 | mark.dickinson | create | |
|