-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
3.1.0 API changes page #13870
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
3.1.0 API changes page #13870
Conversation
@dstansby Hope you do not mind I pushed some commits, should have asked first 😞 |
No problem at all! |
Reorganising this into something coherent is done now, if anyone has the energy to proof read it please do... @matplotlib/developers |
|
||
This will only affect cases where that parameter has been set | ||
as a keyword argument. The common usage pattern as a positional argument | ||
``matplotlib.use('Qt5Agg')`` is not affected. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this paragraph need to be indented to match the enumeration pattern?
|
||
This has never been used internally, there is no equivalent method exists on | ||
the 2D Axis classes, and despite the similar name, it has a completely | ||
different behavior from the 2D Axis' `axis.Axis.get_ticks_position` method. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indentation (s.a.)?
- Converted many class/method names to references - tweaked some wording - broke deprecations section up into sub-sections
If this builds cleanly I am going to merge this, we can continue to work on it during the RC cycle. Again, thank you @dstansby ! |
…870-on-v3.1.x Backport PR #13870 on branch v3.1.x (3.1.0 API changes page)
This will hopefully turn into the final 3.1.0 API changes page.
In addition to merging the API changes I have slightly changed how they are shown. Instead of putting all the text at the bottom of
/api/api_changes.html
, I have created a separate3.1.0
page with the rest of the version changes, and just included it in the/api/api_changes.html
page. This means/api/api_changes_old.html
contains a complete (including latest version) list of changes