DOC: release notes for the latest shape-typing improvements#31172
Merged
Conversation
Member
|
Thanks Joren. Might as well get this in although there are still some PRs outstanding. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Here's the promised release note for the recent shape-typing improvements.
AI Disclosure
I had copilot (with Claude Opus 4.6 High) write this (in "ask" mode), and made some minor changes afterwards.
prompt
For the upcoming NumPy 2.5.0 release I have contributed a lot of shape-typing improvements in the numpy stubs. Write a .rst release note in the same style as #30208 and #30480 . Mention that shape-typing is currently a work-in-progress, so shape-typing support isn't yet complete. With "shape-typing" I mostly refer to the type of ndarray.shape, i.e. some tuple[int, ...] type, usually either tuple[Any, ...] (if unknown), tuple[int] (1d), tuple[int, ...] (2d), etc.
Full list of shape-typing PRs that should be summarized (not enumerated) like I've done before in #30208.
argpartitionshape-typing #30484{lin,log,geom}spaceshape-typing #30532bincountshape-typing #30536from{buffer,string,file}shape-typing #30537fft.[r]fftfreqshape-typing and precise dtypes #30714cum{sum,prod}andcumulative_{sum,prod}shape-typing #31120clipand[a]roundshape-typing #31123transposeandmatrix_transposeshape-typing #31124sortandargsortshape-typing #31125innershape-typing and transparent dtypes #31133fromitershape-typing and more dtype overloads #31134asarrayshape-typing #31135nonzeroand single-argwhereshape-typing #31143atleast_{1,2,3}dshape-typing #31147fromregexshape-typing #31148meanandndarray.meanshape-typing and improved dtypes #31151stdandvarshape-typing and improved dtypes #31154sumandprodshape-typing and improved dtypes #31160[a]min,[a]max,ptp: shape-typing and improved dtypes #31163ndarray.cum{prod,sum}shape-typing and improved dtypes #31164diagonalandndarray.diagonalshape-typing #31165arg{min,max}shape-typing #31166allandanyshape-typing #31170Keep it concise, don't use emdashes and other classic AI stuff, and instead use my writing style. Don't oversell it, and keep it light and not too formal.