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.

Sign up for GitHub

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

Jump to bottom

Prepare release of Cython 3.1 #6536

Open
scoder opened this issue Dec 5, 2024 · 6 comments
Open

Prepare release of Cython 3.1 #6536

scoder opened this issue Dec 5, 2024 · 6 comments
Labels
Planning Release planning and general project goal discussions
Milestone
3.1

Comments

@scoder
Copy link
Contributor

scoder commented Dec 5, 2024

Describe your issue

This is to collect and discuss remaining work for the Cython 3.1 release.

Planned features for this milestone are:

  • Remove code for Python 2 and Python < 3.8.
  • Integrate better with Python 3.
  • Improve support for the Limited API.
  • Start supporting GIL-free Python 3.13.
  • Support the Py3.13 sys.monitoring API.
  • Support and use am_send for coroutines.

All done. The non-measurable goals in this list do not block a release.

Please link issues and PRs in comments below that you want to see considered or discussed for inclusion.
@scoder scoder added the Planning Release planning and general project goal discussions label Dec 5, 2024
@scoder scoder added this to the 3.1 milestone Dec 5, 2024
@da-woods
Copy link
Contributor

da-woods commented Dec 5, 2024

I'm in favour of 3.1 sooner rather than later.

Ideally there's one more limited API bit I'd like to get in:
https://github.com/cython/cython/pull/6479/files (or possibly #5871, but I'd live with the first one).

There's a couple of sys.monitoring bugs that might be worth a look (#6503 #6399) but I don't really think they should block it.

@matusvalo
Copy link
Contributor

From my side if we can include:

@matusvalo
Copy link
Contributor

Yes and this one - most likely you already know about it: #5479 since user waits for it but I am not sure if it is ready to go ...

@da-woods
Copy link
Contributor

da-woods commented Dec 5, 2024

Yes and this one - most likely you already know about it: #5479 since user waits for it but I am not sure if it is ready to go ...

I'm quickly trying another approach...

@da-woods
Copy link
Contributor

da-woods commented Dec 5, 2024

I'm quickly trying another approach...

which I've convinced myself doesn't easily work...

@matusvalo
Copy link
Contributor

I have created a new PR for const global variables: #6542. I hope it is ready to go to 3.1...

@h-vetinari h-vetinari mentioned this issue Dec 9, 2024
Merged
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Planning Release planning and general project goal discussions
Projects
None yet
Milestone
3.1
Development

No branches or pull requests
3 participants
@scoder @matusvalo @da-woods