Skip to content

MEP32: matplotlibrc/mplstyle with Python syntax. #9528

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.

Sign up for GitHub

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

Closed
wants to merge 3 commits into from
+268 −0
Closed

MEP32: matplotlibrc/mplstyle with Python syntax. #9528

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ca0825a
MEP32: matplotlibrc/mplstyle with Python syntax.
anntzer Oct 10, 2017
94cbbcb
Note lack of changes for end user.
anntzer Oct 22, 2017
ac17c1c
List issue titles; minor fixes.
anntzer Oct 23, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Note lack of changes for end user.
  • Loading branch information
@anntzer
anntzer committed Oct 22, 2017
commit 94cbbcb36ca9db42c577ae9ffe92bd34aafbc1c1
12 changes: 11 additions & 1 deletion doc/devel/MEP/MEP32.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,7 @@ considered below. In all cases, it is necessary to encode, in a way or
another, that the config file uses the new syntax, so that Matplotlib can tell
which file-parser to use.

Maintain a matplotlibrc-like layout
Maintain a matplotlibrc-like syntax
```````````````````````````````````

The config files would maintain the format
Expand Down Expand Up @@ -195,6 +195,16 @@ document how to do it using ``urllib`` if we really want to) of style sheets,
which I believe is a good enough replacement (but I am happy to hear arguments
that it is not).

(Lack of) changes for the end-user
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

For the end user, calls to ``matplotlib.style.use`` are unchanged. If
maintaining the *same* naming convention, then the lookup mechanism stays the
same and there is no ambiguity as to what file should be loaded. If the naming
convention is changed (e.g. ``.mplstyle-v2`` with the matplotlibrc-like syntax,
or ``.py``\(!) with the full Python syntax), then a simple priority policy
(such as "always prefer the newer syntax if available") can be implemented.

Implementation
--------------

Expand Down