- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 33.3k
gh-100925: Move array methods under class in array doc #101485
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
gh-100925: Move array methods under class in array doc #101485
Conversation
| @ezio-melotti @JelleZijlstra thanks for the reviews here; would one of you be able to help merge the prior backports to unblock this? Thanks! | 
| Looks like this is ready @JelleZijlstra and @ezio-melotti Thanks for your help here! | 
| Thanks @CAM-Gerlach for the PR, and @ezio-melotti for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.11. | 
| GH-101527 is a backport of this pull request to the 3.11 branch. | 
| GH-101528 is a backport of this pull request to the 3.10 branch. | 
This fixes the issue reported in #100925 , where the attributes and methods of the
array.arrayclass are listed under the module rather than the class, and not clearly indicated as such, which is confusing to readers. This supersedes #101239 , which didn't quite solve the right problem; thanks @theWiseAman for your original PR that prompted this.Also a followup to #98657 , which just fixed this for the one module-level attribute. As both of these are a fix to a docs defect that applies to all supported versions, ensures the stable version will be updated to avoid more reports like the one that prompted this one, and allows future PRs to be cleanly backported, I've queued up backports for both that PR, #98729 and this one, the latter of which should be merged first before this PR is, so that miss-islington can do the backports of this one cleanly:
array.typecodesis a module-level attribute (GH-98729) #101483array.typecodesis a module-level attribute (GH-98729) #101484To note, since the class name was included in the existing
method/attributedirectives, this change doesn't break any internal or Intersphinx links, and also maintains the same fragment ids, so external links will continue to work exactly the same as before. Therefore, I've confirmed it is fully backward-compatible.Closes #101239