[15:28] <OvenWerks> Eickmeyer: I can find both python3-flufl.lock and python3-lockfile in our packages. Lockfile has a ubuntu logo beside it and flufl does not. I am assuming that means lockfile is to be prefered? (is in main)
[15:31] <OvenWerks> however, this post here https://stackoverflow.com/questions/489861/locking-a-file-in-python# (fourth answer down) calls lockfile deprecated. I will note that this answer is from 2015 so maybe it has been updated since?
[15:38] <OvenWerks> Ah, there is also oslo.concurrency which suppercedes lockfile and is also in main.
[15:56] <OvenWerks> It does not give easy to use examples... I guess it is very capable and can keep track of many files but it looks hard to use to lock one file
[21:16] <OvenWerks> Eickmeyer: Scratch adding another package. I think I will use a two file system. Write to a temp using flock() so only one can write at a time. A reading method will look for the temp file and wait till it goes away before reading. If it starts reading just before the temp file shows up for writing, that should be ok as it will have to to fully read (writing may have a short delay to make 
[21:16] <OvenWerks> sure)
[21:19] <OvenWerks> s/to to/time to/
[21:21] <OvenWerks> then remove the config file which will not be a problem as the temp file still exists acting as a blocker. The mv the tempfile to the config file which an atomic process.