Wait, you had a device that runs a key piece of software for you, and you replaced it with one that doesn't run that key application? Why?

A very old, yet still quite true, adage is, buy the software that does the necessary task, then buy the OS that the software requires to run, then buy the hardware that the OS requires to run. (In the iOS case, of course, the latter two parts are combined.)

Since iOS is a proprietary system, an emulator of any sort for it on a PC is undoubtedly going to involve breaking a lot of license agreements. You can't buy a separate copy of iOS, it is licensed only for running on Apple hardware.

This thread, on the Pythonista forum, might be more well received if it were titled, "Pythonista alternatives for Android".

Your best bet might be an iPod touch or an iPad. If money is a concern, it doesn't have to be the latest gen to meet the requirements; secondhand or a refurb from Apple are worth considering.

FWIW, I've used Kivy quite extensively, on the Raspberry Pi. It's a good UI library, but it has nothing equivalent to Pythonista's IDE, and while you can definitely use it to write apps for Android, I'm not at all sure you can write them on Android.

I know Apple's restrictions prevent access to other syncing services from something that can run code (such as Pythonista), but does that also apply to a Pythonista-specific folder on Apple's own iCloud Drive?

Success! Thanks, guys. I was missing something obvious.

Nope, tried that already. I feel like I'm missing something obvious, but I'm pretty good at working through the the permutations.

I'm swiping left-to-right, and it hides the console on the right... and opens the file browser on the left. Losing one-third of the screen width to a sidebar either way. :-/

This is on an iPad Air (1), running iOS 9.2, in either portrait or landscape.

Im having fun poking around the v2.0 release of Pythonista... I could have sworn it initially opened on my iPad with the Welcome(dot)md file displaying in a full-width window, but halter opening the console, I can't get back to full-width now - it seems I can see "file browser & editor" or "editor & console" or just "console" but not just "editor". Am I missing something? Sorry if I've skipped over something obvious.

Also, is there a way to display a "preview" from a Markdown file? Either full-width, or in the console sidebar? I thought I remembered something like that from earlier, but perhaps I'm confusing features between Pythonista and Editorial.

(Also, while posting this, the forum helpfully decided that "Welcome(dot)md" - with an actual "." - was a url, and then proceeded to tell me that my message was spam, because hey, url. That I didn't put in.)

Hmm, signed up, haven't heard anything back.

This seems to be more of a problem on iOS 8, maybe there's more aggressive memory clearing, and it's driving me a bit batty...

When I switch away from Editorial, in the middle of a large file, to go grab some text from another app (often Safari, but not always), frequently when I switch back to Editorial I'm shown right where I left off for a split second, then I get the dark screen with the asterisk (reload screen?) - okay, I'm guessing this means Editorial got shoved out of memory. But the big problem is, Editorial then reloads, and gets me in the right file, but it puts me at the top of the file. Every single time. If you had been, say, roughly two-thirds of the way through a 500 line file, it's extremely tedious to scroll back to where you had just been. Especially the 20th time in five minutes. It's particularly frustrating because you were shown that exact right place just before the reload screen (yeah, guessing that's probably just a snapshot, but it's still like its teasing).

Would it be possible to modify Editorial so when iOS tells Editorial that it is being switched away from, it saves the current offset into the file as well as the current filename/handle/whatever, and then when switching back, if that saved-offset is set, it positions back to that offset into the file? It'd save me from tearing out any more hair.

Thanks!
Carl

I third this - I've been noticing on my iPhone 6 that the rows of keys in the keyboard are much farther apart in Editorial than in Apple's built in apps - using up a bunch of extra screen real estate needlessly.

Have to say, I happened across the versioning stuff yesterday, and was pretty thrilled - it's awesome, it'll diff any two previous/current versions of a document, kinda like Wikipedia's history.