Thank you!

But, there is.

I have a special case, because I suffer with a low space storage device. I know, this is my fault, but anyway, it IS a problem (although I regularly free up space, something eats it very quickly, and I cannot guess what it is). I also kwo that Black Friday is coming... But the problem is currently existing.

So I realized that pwb.py wants to log soemthing even if I use -nolog. It also wants to cache something or read some cache, not that I wuld have said to it to do so. And if pwb. py is unhappy with this, it

* writes many kilometers of error messages, that I cannot read, becuase 90% ran out of screen (I don't think any developer wants to read this in the life)

* generates additional errors during writing the previous errors, so the message gets pretty long

* the witing itself last half a minute or a minute (yes, so long!), and takes my time unless I use ctrl C.

* I cannot find he useful writing on screen, if it exists at all

* the task is often not completed or partially completed, even if it has nothing to do with the storage device.

I think it does not take seriously the -nolog.

Example 1:

I wrote a script which generates lists in memory, compares with the existing lists on Wikipedia and uploads if there is a difference.

This script ran 10 minutes before it found the first list to upload. It wrote all the titles on screen, so I know, it has just created the appropriate list.

But INSTEAD of saving it to wiki, it began to write this long looped error message, and did not execute the put command, rather it terminated.

After I freed up soma space, it ran properly.

Example 2:

I run  python pwb.py -version -nolog because I know you would ask for it.

For the first time it generated a mile long error message again, and did not writ the config which it should have done. Then I freed up some space, and itt worked. So -nolog is useless if I want to avoid troubles. Here goes the VERY tail of the first run, and the result of the second run below.