Skip to content
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

Use PyLong_GetSign() #486

Closed
wants to merge 3 commits into from
Closed

Conversation

skirpichev
Copy link
Contributor

See python/cpython#116561 and capi-workgroup/decisions#19. I'm not happy with this API and it seems that discussion is ongoing. Maybe it's wise to wait some time...

@skirpichev skirpichev force-pushed the use-pylong-getsign branch 2 times, most recently from 724432c to 32aeb00 Compare June 4, 2024 04:03
@skirpichev
Copy link
Contributor Author

skirpichev commented Jun 13, 2024

Probably, discussion in capi-workgroup/decisions#19 is ended.
But see capi-workgroup/decisions#29

@casevh
Copy link
Collaborator

casevh commented Jun 26, 2024

Should this be merged now and then released as 2.2.0 or should this wait until 2.2.1?

@skirpichev
Copy link
Contributor Author

Should this be merged now and then released as 2.2.0

I don't think so. capi-workgroup/decisions#29 is open. We should wait, see also https://discuss.python.org/t/c-api-working-group-vacancy-again/56167

This pr shouldn't block 2.2 release. I'll just mark it as a draft.

@skirpichev skirpichev marked this pull request as draft June 26, 2024 06:59
@skirpichev
Copy link
Contributor Author

I don't like it, but probably capi-workgroup/decisions#35 API will have negative field. So, probably we can skip this.

@skirpichev skirpichev closed this Sep 13, 2024
@skirpichev skirpichev deleted the use-pylong-getsign branch September 13, 2024 02:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants