Forum Archive

@omz, maybe this is not very Pythonetic of me to ask this. I am not sure. If possible could you nominate a dir that will be present in the site-packages folder in the future? I am not sure of all the normal naming conventions. But, I could be called anything. But the intention would be to have a dir that we all know, if from our apps/scripts we write data that is very important and you don't want to lose, then you write to that directory.
Simple example. I am going to start using a snippets that was shared today. I can see the SQLite db is being written in the root dir of the the script. If something goes really wrong, I will not want to lose that database. That's only one app.
So if all important information is written to that dir (you would assume apps would create sub dirs to store their important information inside the 'special' dir) but I could just regularly back up that folder to Dropbox or wherever.
Maybe it's sounds pedantic, but I don't so.

Anyway, food for thought. But if you do think it's a good idea. Then please just publish a name of the folder that will be used. Easily enough just to create it now if it does not exist.

site-packages is the location where Python looks for user-installed Python modules, so putting a backup folder there isn't really appropriate. I don't really see the problem with choosing a location for the "to be backed up" folder yourself - unless Pythonista provides some kind of built-in backup functionality (which isn't going to happen, because Apple), the user can choose a location for their backup folder whereever they want. There's no need to standardize the location because the only one who should access your backup folder is you.

@dgelessus , ok I get you about site-packages. But let's say you write something and I use it. But by nature of what you have written important information is being collected and saved. I am just saying for all the scripts I finally use that save important information, it would be nice if that the important data files were in one place. Then I don't have to remember what script/app does what when where. If I installed a lib from someone here that's has important information being saved, on install I could check to see first time if they are writing the important files to a known dir. After that as long as I have a backup strategy for that one folder and can forget about it.