Feature Request: Specify a config directory on the command line

[gb119]

I think it would be handy for the user to be able to specify a spyder configuration directory as a command line option so that, for example, if you install a new version of spyder in an environment you can also isolate any changes in the config from the new version. I personally would use this also for when I'm working off an external monitor compare to travelling and working on my laptop due to differences in screen size and scaling etc.

Looking at the code, I think one could implement this by having spyder's config manager look for an environment variable e.g. SPYDER_CONFDIR and use that in preference to the calculated directory, and then in the Spyder app's main() have it set that environment variable between the point the options get read and the configuration manager instance is imported.

But perhaps there is a reason for not doing this (or even more likely, my proposed solution sucks!)

[gb119]

I did a quick play to implement this if you were interested in seeing a pull-request...

[steff456]

Hi @gb119,

Thanks for this feature request! In fact we've discussed this multiple times and we would like to implement not only a spyder configuration directory, but also isolate configurations per project and global spyder configurations. In this way people will be able to load/save their configuration.

Right now we've added this to our roadmap that we are planning to put it public in the next month. If you are interested in helping us implement this it will be great! We can give you all the guidance you need :)

[gb119]

I can imagine that involves a much more comprehensive refactoring of the config management code. At the moment there are certain preference changes that require a Spyder restart and I guess those forced restarts need to be eliminated as you don't want the user to be told that opening a new project requires them to restart Spyder just because they have some different preferences set in the new project that are different from their current project...

If you want the user to manage a set of global and per project settings then the config manager is going to have to track the sets of preferences separately and then present some sort of merged view. There'd need to be some UI to let the user know whether they were changing global rather than project settings too.

I think I'd need to find a lot more time to study the code quite a bit more to understand how one might implement your plan - probably best not to wait for that to happen :-) !