Welcome!
This is the community forum for my apps Pythonista and Editorial.
For individual support questions, you can also send an email. If you have a very short question or just want to say hello — I'm @olemoritz on Twitter.
Outliner with drag/drop reordering
-
@ihf said:
even after restarting Pythonista.
I get the same crashes. I can't anymore run the script twice in a Pythonista run. And I advice to wait some seconds before restarting Pythonista, it seems to still use some memory. Even if I even don't type any character. The program does not use a lot of memory with a short outline, less than some images, thus I don't understand why
-
@ihf said:
I occasionally miss undo/redo.
I have problems with the principle of undo. Assume you set a due date, thus create an event. If you want to undo, the program would have to remove the calendar event also. And if you ask a redo.....recreate the event...
-
@cvp On the one hand Pythonista (as you have shown) is a wonderful platform for creating UI rich Python scripts. On the other hand, it is not being supported and is probably a less than ideal place to run "production" programs. I imagine that Swift has reliable libraries that can duplicate those found in Pythonista but someone who knows Swift well would have to do the "translation" from Outline.py. In the meantime, I continue to use it (in production :-)
-
@ihf said:
I continue to use it (in production :-)
You say in production, is that for the fun, not for your job?
-
-
Pythonista will run on M1 Macs
It does!
-
-
-
@cvp I just downloaded v0.96 ran it and got:
Traceback (most recent call last): File "/private/var/mobile/Containers/Shared/AppGroup/05D14C00-CCAC-4E98-A3CC-96C6944B8534/Pythonista3/Documents/outline.py", line 905, in <module> PY3 = sys.version_info[0] >= 3 NameError: name 'sys' is not defined
Restarting Pythonista did not help.
P.S. I knew that undo/redo was not working so I stopped testing it as I figured it was on your list. -
-
@ihf could you tell me if you have still crashes during a run of the script,
If you process so:
- remove Pythonista
- wait 10 seconds
- restart Pythonista
- run the script
Other question : do you have Pyto, it is open source. I dare not estimate the number of days needed to convert outline.py to Pyto because its ui and its editor are a lot less rich, assuming that all features are supported. But, at least, Pyto it-self is supported and you get updates frequently. I'm always surprised by what a person alone can realize. Even if Pyto is still far from Pythonista, it is obviously a marvelous app for an unique developer.
-
@cvp yes, I have Pyto.
I just started outline on my iphone ( I was using it on my iPad yesterday). It crashed Pythonista so I followed the steps you listed and it crashed again. I also tried starting it using pythonista3:// but after I start the script Pythonista crashes. What to do? -
@ihf could you try to get the crash reasons? In fault_log folder or _obj_exception.txt file, both in root
Faultlog, see @dgelessus 's code
For me, crashes have always the same reason "segmentation fault" without any traceback. No way to identify the origin, sorry for you.
Pyto and future Swift Playground 4 would allow to develop an app on iPad...
-
@cvp, how repeatable is the crash?
You could consider adding some
logging
calls to write trace info to a file. Or could use thetrace
module to for instance log all function calls, then eventually narrow to all lines within a single function.Have you watched memory at all? For instance, the issue with processing lots of images without doing NSAutoreleasePool. If there is a leak somewhere, it will eventually crash without warning.
Or, maybe if you are opening lots of file handles without closing. -
-
@JonB said:
Have you watched memory at all? For instance, the issue with processing lots of images without doing NSAutoreleasePool. If there is a leak somewhere, it will eventually crash without warning.
Or, maybe if you are opening lots of file handles without closing.No memory used, it occurs even with a data file of some bytes.
Script uses maximum files, all using "with open(...)"
It occurs even without images, and anyway, I use sometimes maximum 3 images -
@ihf said:
run a completely different script which ran fine and then I went back to running outline and it ran
Strange...very difficult to identify if depends on what we did before 😰
-
@JonB said:
You could consider adding some logging calls to write trace info to a file
Following your advice, I've modified my script to write (without buffering) in a outline.trace file all called functions (mine).
I wanted to write inspect.stack()[1][3] but sometimes I got some index errors, thus I tried str(inspect.stack()) and seeing it contains .........function='name', I extract this name and logs it.You will laugh but as soon I did (only) that, I don't have any crash more. Wait and see
-
-
@ihf It is a long time since we last had a dialogue here.
Some questions I would like you to answer very sincerely:- Are you still using my program?
- If so, would you be (sincerely, I insist) interested in running it under Pyto? Becuse you would prefer an open source app (even if I don't see who would continue to modify it)
- The conversion to Pyto seems to me an enormous work which would certainly meet impassable walls, therefore which will take months, but which I would accept to carry out for the challenge.