REL: new release needed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- build-system, release
Research direction
Review the build matrix changes in #589 and the proposed approach in #511, then inspect the repository's release process for publishing CPython 3.15 wheels. Done means a new release is published with the required wheels, with the support decision for Python 3.10 and #511 resolved first.
Written by the indexing model from the issue text.
Description
A new release is needed in order to publish wheels for CPython 3.15.
I already merged #589 which added it to our build matrix.
I also want to note that #511 would help make this a non-problem for GIL-enabled builds as well as vastly reduce the number of artifacts we need to publish to support all current versions of CPython as well as future ones. I also plan to explore the recently standardised abi3t to also fix this yearly point of friction for free-threaded builds, though the ecosystem (setuptools in particular) isn't ready yet.
If for any reason we didn't include #511 in our next release, I would also love feedback on wether we could/should drop support for 3.10, which will be EOL in a little less than a month. I don't know of a motivation to do so right now, other than reducing the number of wheels, which #511 would be much more effecient at.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 123
- Avg merge
- 45m
- Merged PRs (30d)
- 7
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pydata/bottleneck
-
BUFFER_NEW macro: unchecked malloc inside GIL-released regionMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pydata/bottleneck#529 ·
Maintainers usually reply within 1 day
-
mm_new/mm_new_nan: three unchecked malloc calls — segfault on OOMPossibly taken @neutrinoceros claimed this 231 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pydata/bottleneck#526 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pydata/bottleneck#519 · 6 comments ·
Maintainers usually reply within 1 day
-
[PERF] bn.nammax/nanmin is ~70% slower on latest conda-forge buildMay be free again @AtharvRG claimed this 20 days ago, and no pull request is open. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
pydata/bottleneck#600 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
pydata/bottleneck#574 · 1 comment ·
Maintainers usually reply within 1 day
All issues in pydata/bottleneck
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
abetlen/llama-cpp-python#2424 ·
Maintainers usually reply within 1 day
-
Bug IronPython Python 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pyrevitlabs/pyRevit#4184 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
jqueryscript/awesome-claude-code#1009 ·
-
tests
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day