@techteej I Did see no problems on my ipad2 ios9.1
Georg

Usually, I get the same effect as at_exit() in a more structured way by using try: ... finally: ... . Any reason why you need to have something like at_exit()?

Georg

Maybe try skyfield, which is pure Python https://github.com/skyfielders/python-skyfield .

Six active widgets...
Now that the Pythonista widget has worked once, it seems to work fine every time. Strange.
Georg

After the .10 update this evening, it stopped working again. The widget was at the lower end of my displayed widgets, and did not show the run-triangle nor the script result. It started working after moving the widget to the top of the list.
I wonder if the widget position contributes to the problem, or if the python interpreter running the widget just needs a lot of time for the first start up.
Georg

Seems to be working now. I did not see the run button during my previous attempts. Maybe I was too impatient with my slow iPad 2...
Resolved! Thanks,
Georg

I tried to create a simple today widget for the latest Pythonista Beta that just prints the time. The widget logo shows on the screen, but nothing else happens.

'''testing today widget
'''
import datetime as dt
print('Python time is %s'%dt.datetime.now())

What's needed to get this working?
Georg

@ccc async, await, asyncio etc are not really about threading or multiprocessing. It is more like co-routines, running everything in a single thread and handing control to the next routine at defined scheduling points (the await statements).
Georg

@techteej I Did see no problems on my ipad2 ios9.1
Georg

@polymerchm said:

... OMZ is probably already skating close to Apple's comfort zone so why wave another red flag at the bull. There's always swift and objective-C.

You are probably right ....

That's really a pity. I had a look at the developer documentation and review guidelines for healthkit: Apple appears to have very high requirements for applications that use healthkit. Amongst these: The app needs to be dedicated to health, you need to have a compliant privacy policy, you must not export health data, etc. . On the one hand, I like this (since my data deserves privacy), on the other hand those limitations can sometimes be annoying...

Having said that: Applications such as Workflow allow to read and write healthkit data, there are even workflows that allow to export heath data, Workflow is not health specific, and there is nothing regarding health data in Workflow's privacy policy. Actually, I think that's quite OK since those workflows don't run automatically, and since the app needs to ask for permissions beforing reading or writing to HealthKit. But how is this different from what you can do in Pythonista? I wonder why Apple might see Workflow different from Pythonista.

As a consequence, to record some health data, I now have a Workflow workflow with a few dozen elements. The same could probably be done with 20 lines of Python in Pythonista, in a much more concise way.

Just wondering,
Georg

What does it take to access Healtkit data from Pythonista? Is there some library available, or do I need to learn objc_util?
Thanks,
Georg