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

Skip to content

Backport #21429 from jklymak/doc-use-mpl-sphinx #21461

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
merged 2 commits into from
Oct 26, 2021

Conversation

jklymak
Copy link
Member

@jklymak jklymak commented Oct 25, 2021

DOC: use mpl-sphinx-theme for navbar, social, logo

PR Summary

PR Checklist

  • Has pytest style unit tests (and pytest passes).
  • Is Flake 8 compliant (run flake8 on changed files to check).
  • New features are documented, with examples if plot related.
  • Documentation is sphinx and numpydoc compliant (the docs should build without error).
  • Conforms to Matplotlib style conventions (install flake8-docstrings and run flake8 --docstring-convention=all).
  • New features have an entry in doc/users/next_whats_new/ (follow instructions in README.rst there).
  • API changes documented in doc/api/next_api_changes/ (follow instructions in README.rst there).

DOC: use mpl-sphinx-theme for navbar, social, logo
@jklymak jklymak changed the title Merge pull request #21429 from jklymak/doc-use-mpl-sphinx Backport #21429 from jklymak/doc-use-mpl-sphinx Oct 25, 2021
@@ -13,7 +13,8 @@ ipython
ipywidgets
numpydoc>=0.8
packaging>=20
pydata-sphinx-theme>=0.6.0
pyparsing<3.0.0
Copy link
Member

Choose a reason for hiding this comment

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

This is not needed anymore due to #21454.

Copy link
Member Author

@jklymak jklymak left a comment

Choose a reason for hiding this comment

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

The only "controversial" thing here is back porting environment.yml @timhoffm I think you introduced this file - is there any reason to not back port it? I admit I am back porting it due to poor cherry-picking skills, but left it in there anyway.

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.

Backporting environment.yml is not really necessary. The main use is creating a dev environement for the current master. OTOH future version branches will have their then-current environment.yml. So it's also no harm to have the backport in 3.5.

@timhoffm timhoffm added this to the v3.5.0 milestone Oct 26, 2021
@timhoffm timhoffm merged commit 13a439b into matplotlib:v3.5.x Oct 26, 2021
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.

2 participants