Thanks to visit codestin.com
Credit goes to github.com

Skip to content

File name made more understandable #17021

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

Merged

Conversation

SidharthBansal
Copy link
Contributor

PR Summary

Putting an actual version number on the next_api_changes directory may help avoiding notes going to the wrong file during long RC periods where it's not so obvious whether next_api_changes refers to the currently rc'd release, or the next one.
Closes #16588

PR Checklist

  • Has Pytest style unit tests
  • Code is Flake 8 compliant
  • New features are documented, with examples if plot related
  • Documentation is sphinx and numpydoc compliant
  • Added an entry to doc/users/next_whats_new/ if major new feature (follow instructions in README.rst there)
  • Documented in doc/api/api_changes.rst if API changed in a backward-incompatible way

@SidharthBansal
Copy link
Contributor Author

@anntzer @story645 @tacaswell kindly review this pr

Copy link
Member

@timhoffm timhoffm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we put the explicit number all over the docs, this will get outdated as I don‘t think it will be updated consistently.

I‘d go for using „the most recent api_changes_X.Y“ or a similar term.

@SidharthBansal
Copy link
Contributor Author

SidharthBansal commented Apr 4, 2020 via email

@timhoffm
Copy link
Member

timhoffm commented Apr 4, 2020

Fine by me.

@SidharthBansal
Copy link
Contributor Author

@timhoffm I think I am missing something very crucial due to which majority of CI are failing. I have pushed the changes. Trying to debug the failing CIs. Any help appreciated.
Thanks

@SidharthBansal
Copy link
Contributor Author

CircleCI shows

make: *** [Makefile:30: html] Error 1
Exited with code exit status 2
Your output is too large to display in the browser. Only the last 400000 characters are displayed.
Download the full output as a file.

Do I need to upload any output files too? Maybe for the test outputs?

@anntzer
Copy link
Contributor

anntzer commented Apr 4, 2020

You can download the log file and look for "warnings". Here you'll find

/home/circleci/project/doc/api/api_changes.rst:14: WARNING: toctree glob pattern 'next_api_changes/*' didn't match any documents
looking for now-outdated files... none found
pickling environment... done
checking consistency... /home/circleci/project/doc/api/recent_api_changes_3.3/2019-04-25-AL.rst: WARNING: document isn't included in any toctree
/home/circleci/project/doc/api/recent_api_changes_3.3/behaviour.rst: WARNING: document isn't included in any toctree
/home/circleci/project/doc/api/recent_api_changes_3.3/deprecations.rst: WARNING: document isn't included in any toctree
/home/circleci/project/doc/api/recent_api_changes_3.3/development.rst: WARNING: document isn't included in any toctree
/home/circleci/project/doc/api/recent_api_changes_3.3/removals.rst: WARNING: document isn't included in any toctree

which means that you forgot to edit doc/api/api_changes.rst, and therefore the moved files are not referenced anywhere.

@SidharthBansal
Copy link
Contributor Author

Thanks for the help.
I think it is ready for merge now. Thanks all for helping me :-)

@tacaswell
Copy link
Member

I am skeptical of this change, it may make it slightly clearer but it is going to require a whole bunch of places to be updated after we fork off v3.3.x and 3.4 becomes the "next" release.

@SidharthBansal SidharthBansal requested a review from timhoffm April 4, 2020 19:14
@timhoffm
Copy link
Member

timhoffm commented Apr 5, 2020

Ping @tacaswell this has only one explicit filename left (and it's in the toc). Do you think this is bearable?

@tacaswell
Copy link
Member

Yes, that seems OK.

@SidharthBansal
Copy link
Contributor Author

SidharthBansal commented Apr 6, 2020 via email

@SidharthBansal
Copy link
Contributor Author

There are conflicts. Resolving them now

@SidharthBansal SidharthBansal force-pushed the file_name_made_more_understandable branch from 34c6e1c to 91920e4 Compare April 6, 2020 21:06
@SidharthBansal
Copy link
Contributor Author

Resolved. Thanks!

Copy link
Member

@QuLogic QuLogic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some typos to fix.

SidharthBansal and others added 2 commits April 7, 2020 05:10
Co-Authored-By: Elliott Sales de Andrade <[email protected]>
Co-Authored-By: Elliott Sales de Andrade <[email protected]>
@SidharthBansal
Copy link
Contributor Author

Done. Thanks

@timhoffm timhoffm merged commit b85c7f4 into matplotlib:master Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rename next_api_changes to api_changes_3.x (whatever number makes sense)
5 participants