On 3/1/21 1:55 PM, Mark Sapiro wrote:
When Python runs or imports from a .py file, it first looks for a corresponding .pyc file and if that is as new or newer than the .py, it uses the .pyc. If not, it uses the .py and byte-compiles it and if it has permission, writes an updated .pyc
Except recent Python3 (at least I think 3.5 and newer doesn't use a .pyc in the same directory as the .py Its uses a __pycache__ directory in the same directory as the .py and within that directory a file like in this case settings_local.cpython-37.pyc (or whatever the python version is)
In any case, I would remove the existing settings_local.pyc. That can't hurt, but I'm curious what
ls -lR /usr/share/mailman3-web/
shows.
It just occurred to me what the issue is. It is almost certainly that there is a /usr/share/mailman3-web/settings_local.pyc that is as new or newer than the /usr/share/mailman3-web/settings_local.py symlink even though it is older than the target /etc/mailman3/mailman-web.py.
Just remove that .pyc, and that should fix it.
But I still wonder what python version this is since current Mailman requires python >= 3.6
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan