-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert _decimal C API changes #87588
Comments
Stefan Krah (who doesn't have access rights here, and is the author of the C _decimal module) asked me to transmit me this request: Additionally, I'd like to refine the API, perhaps together with the The relevant diff is here: I can turn it into a PR but first I'd like to gather reactions here. |
+1 fron me. |
+1 from me. 3.10.0 final haven't been released, so no one will be affected. |
I have a concern about the current _decimal C API: bpo-43060. I'm fine with removing it in Python 3.10, and add it back fixed in Python 3.11 or later.
Go ahead. |
skrah is still a bpo user with an CLA-signed account linked to his github account. So he can post here and, I believe, open a PR as a contributor. But if, under the current circumstances, he feels more comfortable using Antoine as a go between, then I thank Antoine for doing so. |
Terry, the list of roles in https://bugs.python.org/user11089 is empty, which I take it to mean that Stefan doesn't have any access rights on this issue tracker (except to read issues). Other users all seem to have the "User" role. |
OK. I see no structural difference between his page and yours, https://bugs.python.org/user2040. No 'Roles' field, no 'User' entry, on either page, nor on mine. So you must be an admin who sees extra info. In any case, the last part of my comment stands. |
FWIW, I have the roles "User,Developer,Coordinator" according to my user page. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: