Forum Archive

The current build (160016) is expiring in about 14 hours. Unfortunately, I'm running into some issues (again), trying to upload a new build – iTunes Connect (TestFlight) is complaining about supposedly missing code signatures, even though pretty much the same setup worked fine last time. I have a couple of ideas for working around this, but I'm not sure if they'll pan out, so I would strongly recommend that you make a backup of your files now, if you're in the beta, because it's more difficult to do this after the beta has expired. Here's a simple backup script if you need it: http://bit.ly/pythonistabackup

It looks like something has changed on Apple's (server) side. The problem seems similar to the one I had two(?) months ago, but I thought I had figured that out. The error message is less detailed this time, so I'm not quite sure what the exact problem is, and how to get around it. I'll keep you posted.

Hey!
Bought Pythonista like a week ago. I didn't know, that it runs 2.7 version of Python.
Will it be running 'fresh' Python in the next update? Thanks!

@Varmint, sadly no. Python 3 would be a great update/addition, but it would be a lot of work to port Pythonista and all the custom modules, and it would break many user scripts.

Just received notice that its new beta is available. Have things been corrected, or is this a red herring?

Okay, I've sorted out the problems with TestFlight, so the beta didn't expire this time. :)

I'm still working on some UI editor improvements that I couldn't include in this build, but they'll hopefully be ready for testing soon.

Just waiting for you to obsolete all the stuff I built for my UI editing tool (-______-)

So, it will never be updated?

omz hasn't said that it won't happen at all, but Python 3 probably isn't coming in the near future. If it were released as a normal app update, there would probably be an announcement/warning in advance to make users aware of the update, which will inevitably break a lot of code. There is also the possibility of a separate Pythonista app with Python 3, which would mean a second purchase, but no code breakage.

So I see "Watch" has gone. I'm hopeful that Workflow can be used to provide the UI to Pythonista on a watch.

I'm going to experiment.

Already I know I can dictate to the watch in Workflow and so hope I can pass stuff into Pythonista running on the phone. But the likely style is Pythonista invocations interspersed with Workflow UI stages in the pipeline.

I'm sorry to hear the sk module is going away. I've been having fun with it. Hope it's only temporary.

So far so good. Nice to have iTunes file access, at least temporarily.

@Varmint This is happening all over the industry. There are two "fresh" python versions, the latest 2.x and the latest 3.x. Development continues on both. This was an inevitable consequence of breaking backwards compatibility with some significant 3.0 features. This was done intentionally and for good reasons but the result is that 3.x breaks a lot of current code so many shops are trapped. Basically new work starts with 3.x and projects that are enhancements of old code stick with 2.x. If Omz was to switch Pythonista to 3.x lots of his current customers would be upset. Most places install both and let the users decide on a project by project basis. Omz could support both but that would be almost twice as much work for him with little extra revenue to pay for it. Since Pythonista is the only decent ios Python implementation not many people refuse to use it, mostly students that want to learn the latest and don't care as much about ios integration. Python pros can do either. The world is slowly switching but I wouldn't hold your breath.

Omz could support both but that would be almost twice as much work for him with little extra revenue to pay for it.

Not within the same app, because of Apple's app guidelines and the whole single-binary-no-dynamic-linking thing.