Configuration is not saved

[vict0rsch]

Whenever I start ptipython and change something in the menu (say, syntax highlighting, but anything, really), it is forgotten at next startup. Is this expected?

ipython: 7.12.0
python: 4.7.4
ptipython: 1.0.1
ptpython: 3.0.0

[SongRb]

You should edit $HOME/.config/ptpython/config.py to reflect your configuration.

[treatmesubj]

https://github.com/prompt-toolkit/ptpython/blob/master/examples/ptpython_config/config.py looks easy enough to use, but how would I implement this in Windows? Just drop it in AppData\Local\Programs\Python\Python38-32\Lib\site-packages\ptpython and add a function to init.py or main.py to use it or something?

[treatmesubj]

Not sure if this is the best way to do this, but I just went into ptpython/python_input.py and changed self.insert_blank_line_after_output's bool to False, show_signature to True, and show_docstring to True. Probably have to pay attention to which things aren't compatible in menu if you do this.

[mgd722]

i get this message:

~/.ptpython/config.py is deprecated, move your configuration to /Users/mike/Library/Application Support/ptpython/config.py

on macOS 10.15.2, so it would seem that the preferred config location has changed again?

[Aeron]

@mgd722 looks like you’re correct. I’ve faced a similar problem. Probably, those are appdirs changes rather than ptpython’s.

I solved it by sym-linking ~/.config/ptpython/config.py to ~/Library/Application Support/ptpython/config.py. It should work for any modern $XDG_CONFIG_HOME definition.

Thanks for pointing it out; it helped a lot.

[skrat]

I don't think having users editing the config.py is the way to go. If there's GUI for that, then all I need is a Save command, as opposed to going and studying ptpython's configuration types. That kind of negates the point of having the GUI there, doesn't it?