On 2023-12-28, Peter J. Holzer via Python-list <python-list@python.org> wrote: > On 2023-12-28 05:20:07 +0000, rbowman via Python-list wrote: >> On Wed, 27 Dec 2023 03:53:42 -0600, Greg Walters wrote: >> > The biggest caveat is that the shared variable MUST exist before it can >> > be examined or used (not surprising). >> >> There are a few other questions. Let's say config.py contains a variable >> like 'font' that is a user set preference or a calibration value >> calculated by A to keep with the thread title. Assuming both scripts are >> running, how does the change get propagated to B after it is set in A > > It isn't. The variable is set purely in memory. This is a mechanism to > share a value between multiple modules used by the same process, not to > share between multiple processes (whether they run the same or different > scripts) > >> and written to the shared file? > > Nothing is ever written to a file.
Then how does it help the OP to propogate clibration values from one program to another or from one program run to the next run? > You could of course write python files from a python script (in fact I > do this), but that's not what this pattern is about, AFAICS. -- https://mail.python.org/mailman/listinfo/python-list