Guys, another simple idea. But unlikely unless some rules change. But if there comes a day where Pythonista files could be hosted on something file Dropbox this could provide write/edit/run workflow. I use a folder on Dropbox when I am at home playing around on different MacOS devices for coding. I generally use PyCharm, but sometimes use other simple lightweight Python UIs. Also with venv, is still fast enough for me.
This is a little dis-jointed, but a remote drive idea still gives you more options. Again, would depend on the rules and the speed you could read and write to the device. Mind you we are talking about kbs in most cases.
I could imagine, it would not suit everyone as if you are offline so are your files, although that could be handled switch a background process that mirrored your virtual remote volume so to speak. Maybe what I say is dribble. I am not sure. I was just surprised how well it worked on my various devices using MacOS.
Pass -p no:cacheprovider to fix operation not permitted for .cache directory (run unit tests script)
Documentation cleanup and rewrite to Markdown, which is easily editable in Pythonista compared to reST
Camel case enum constant deprecated, will be removed in 2.0.0
Use UPPER_CASED versions, camel case still exists as aliases
with bundle() always unloads pkg_resources.* causing issues
Launch Pythonista, run Black Mamba Analyze - works vs
Launch Pythonista, run Pythonista unit tests, run Black Mamba Analyze - fails, because of pkg_resources