If it's meant to be user visible, it should go in "Documents" then. Personally I dislike this, but I live inside AppData (unlike most people).

No strong opinion about putting it in Documents (but I don't think it's something in the appdirs model?), I can't say I have a good idea of what the average Windows user expects. But if we move it to AppData you get to field the questions on the issue tracker about how to get there :-)

It's just as hard to get to the user profile directory as the AppData directory, and the AppData directory is specifically for these kinds of files.

Well, C:/Users/<user>/.matplotlib is not hidden by default on Windows, so I don't understand what you mean by "as hard"?

And AppData/Local and AppData/Roaming have different behaviours on some systems, as they are designed specifically for different types of app settings, so using them is actually the feature, rather than a misfeature. (The documents folder will also roam when configured, which gives the user better control over their settings.)

Actually I'd rather have matplotlibrc follow $PYTHONPATH (to have it per-venv), but that's a side issue...

Another helpful thing is to offer a command line option/equivalent to open the file wherever it is located and/or in the user's default text editor (a big advantage of using a ".txt" or ".ini" file for configuration, rather than a "hidden" dotfile).

If it was matplotlibrc.txt then we could do something like webbrowser.open(matplotlib.matplotlibrc_fname()) (which would open the text editor, despite what the module name says) but in the absence of extension this indeed gets opened by, well, the webbrowser.
I don't particularly care about the extension, to be honest (I guess .conf would be the normal thing).

Uh oh!

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions