Skip to content

MPLRC environment variable to set rcparams #6884

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

Closed
anntzer opened this issue Aug 2, 2016 · 3 comments · Fixed by #9570
Closed

MPLRC environment variable to set rcparams #6884

anntzer opened this issue Aug 2, 2016 · 3 comments · Fixed by #9570
Milestone

Comments

@anntzer
Copy link
Contributor

anntzer commented Aug 2, 2016

I'd like to suggest a MPLRC environment variable which could be set to a JSON encoded dict, that would be merged into the rcparams read from the matplotlibrc.
Typical use case would be similar to MPLBACKEND -- temporarily set some rcparams without having to edit the source or the matplotlibrc.

@tacaswell tacaswell added this to the 2.1 (next point release) milestone Aug 2, 2016
@tacaswell
Copy link
Member

Interesting idea. Do other programs use this sort of thing?

@anntzer
Copy link
Contributor Author

anntzer commented Aug 3, 2016

Using environment variables for "simple" configuration of "base libraries" is pretty standard in the Unix world, right? Using JSON not so much (probably because most of them predate JSON) but that sounds better than introducing one new variable per rcparam.

@anntzer
Copy link
Contributor Author

anntzer commented Oct 5, 2016

Actually, a better idea would be to either have MPLRC contain the contents of the rcparams file itself, or have it point to a filename that contains the desired rcparams (in which case process substitution can come in handy) -- thus avoiding the need to invent yet another encoding.

@tacaswell tacaswell modified the milestones: 2.1 (next point release), 2.2 (next next feature release) Oct 3, 2017
@QuLogic QuLogic modified the milestones: needs sorting, v2.2.0 Feb 12, 2018
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 a pull request may close this issue.

3 participants