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.
"If we do not receive an update within forty-eight hours, your app [Pythonista] may be removed from sale"
-
It is the time to abandon Apple
-
Wait... Do you guys think Ole is also going to be forced to remove x-callback-url integration? You can use it in ways Apple probably wouldn't agree with.... Or does the rejection strictly encompass only Pythonista's ability to download executable code? Also, is anyone else having problems with the Gist downloader scripts after GitHub moved away from raw.github.com urls? Sorry if this is a stupidly obvious question, thanks in advance!
-
Okay, everyone relax! :) Pythonista 1.5 has just been approved by Apple, and I plan to release it on Monday.
Unfortunately, the whole thing was a bit rushed because of Apple's 48h deadline, so Xcode export didn't make it in this time. However, this is a feature I've considered moving out of the app for a while, because it can just as well be done on a Mac (which you need anyway). I will probably be able to prepare an Xcode template for Pythonista scripts over the weekend. It shouldn't be much harder to use than the previous in-app export.
As you might have read in my Twitter feed, the Open in... menu integration is also gone, and this one won't return. I'm sad to see it go, but I didn't have a choice. The alternative would have been to have Pythonista removed from the App Store entirely. Note that this does not affect the
console.open_in
function, it's entirely about opening files from other apps in Pythonista.Apart from these issues, there's quite a lot of cool new stuff in this update – the UI module that I've introduced in Editorial 1.1 will also be available in Pythonista 1.5 (including the visual UI Editor), so you can build custom user interfaces for your scripts. It's also possible to combine this with
scene
-based scripts (you can basically embed a scene in a UI, so you can use things like a text field for highscores in a game).In addition to that, I've integrated numpy and matplotlib, which are both very popular in the scientific Python community. There's a new
motion
module for getting more detailed information from the device's accelerometer and gyroscope (decoupled from thescene
module), and thephotos
module has received an overhaul – for example, you can get at metadata when picking an image from the library, and it's possible to retrieve images in their original format (e.g. for lossless png screenshots).For a few more details about what to expect in this update, here are the release notes from the new documentation:
-
why monday? just wondering if Apple already approved it.
-
Congratulations! I'm happy.
-
Thanks @omz!
-
Change notes show a downgrade of requests module.
-
Not possible to release earlier? Just thinking about caused by the weekend - having more time for experiments with the new UI module.
Can't wait for the release! This makes my day. -
@omz First congrats... Sad for "open in...". Happy for rest of things... Once again congrats...
-
Fantastic! Can't wait to integrate matplotlib directly into a native iOS interface. Will probably retain some of my web interface versions too so that I can still run cross-platform.
@briarfox - the release notes do not show a downgrade of requests: requests: 1.2.2 → 2.2.1
-
Awesome, looking forward to all of those things! Except of course the "Open in..." loss, that is unfortunate. We still have network integration though, so you can still donwload files from the internet. Combined with apps that allow Wi-Fi sharing of their files (GoodReader, USB Disk, ...) it should be possible to work around that.
-
@Kenbo01 Well thanks for pointing that out, It was late and I must have been seeing things :) Although it might have been a typo fixed my omz?
-
Terrific! I can't wait for the new numpy/matplotlib!
-
Great!
'Open in' seems like a small price to pay for numpy.
Congrats and looking forward to Monday -
I apologize for asking such a newb question, but I'm new to the world of ios devices. What does the loss of 'open in' imply? I have a bunch of python scripts that I wrote in other, non Apple environments (linux, MSWindows, Cygwin,...). I'm guessing that I will no longer be able to save a .py file to dropbox from another platform, and then have the option to open that file in pythonista. Is there another way to get those files into pythonista without having to retype them? Does this mean I can't share a script that I wrote on my iPad with other iPad owners, or even with my own iPhone?
I've been anxiously awaiting numpy support, but am now considering not updating if it means not having any way to import python scripts written on another machine (not a Mac - don't own a Mac). Or am I misunderstanding what the loss of 'open in' means? BTW - what if I import those other scripts before updating pythonista. Do they go away after I upgrade?
-
The Dropbox API still works in Pythonista v1.5. Upgrading the app preserves your scripts. Open In is discussed in detail in Federico Viticci's review http://www.macstories.net/reviews/pythonista-1-5-custom-interfaces-matplotlib-and-no-more-open-in
Bottom line: go ahead and do the upgrade.
-
Copy and paste works, too.
-
Thanks! I'll download it tonight.
-
Copy and paste works, too.
Only for plain text-based files though, images and other files can now only be imported via Dropbox or network modules.