This post is deleted!last edited by
As for the # character, where would you put that? I can't really make the keys on the extra row much smaller, and I don't really see a key there that I'd remove to replace it with #.
Actually I had not really thought about it. I had something like a modifier key in mind. I like the fact that the new keyboard lost a row but the hashtag character is IMHO quite essential for python. The word character keys do look quite empty regarding modifer keys, but I do not know if you can modify them.
I personally never did care much about snippets (I think I was a bit unclear there, I actually meant shortcuts to little python scripts interacting with the editor: autopep8, autodocstring, linting etc. - I am lazzy, I use them alot), but since you mentioned them: An alternative route for shortcuts could be to allow to execute a python script instead of a snippet. Basically a command palette that would appear in the auto-complete bar. It is always a little bit of a hassle to use editor scripts atm.
@mikael This is currently iPad-only, and will probably remain that way. You can already swipe down to dismiss the keyboard on iPhone btw (swipe down on the editor, not the keyboard itself).
Yes, but only if your keyboard dismiss mode is set right (not on by default) and TextView's content is big enough so that it is scrolling. And never in TextFields.
To me it would at least make sense to provide a standard option for having a dismiss key on the keyboard, instead of everyone having to implement varying custom solutions.
And oh, no, I did not mean that a dismiss option is needed while editing code on iPhone, only during the execution of a UI script. I agree that the swipe down is quite sufficient while editing.
@omz will old packages still work if 3.6 is pushed to everyone? I need my pycrypto 🙂
@lachlantula I don't expect any packages to break with the switch to Python 3.6.
Python 3.6 is now available in the latest beta! 🎉
I've also added enhanced syntax-highlighted for f-strings – embedded expressions get a different background color, and (perhaps more importantly), code completion is available within those expressions, so it's faster to enter variable names etc. within a string.
@omz Awesome! It's great to have f-strings in Pythonista :)
I've noticed that the new beta requires iOS 10. Any idea if that will also apply to the release version? My iPad is stuck on iOS 9, and while it is getting a bit old, it still runs well enough that I don't want to buy a new one yet. I can understand that you don't want to support iOS 8 for much longer (though JonB probably wouldn't like that...) but iOS 9 isn't even two years old.
@dgelessus I'll probably support iOS 9 in the release version, I just didn't have time to test it at all yet, and I suspect that some keyboard-related things are broken right now.
Continued iOS 8 support is a lot less likely (sorry, @JonB!). The new coding keyboard depends on a particular iOS 9 API that I don't know how to replace, and while I could just disable the coding keyboard in iOS 8, at some point it's just too much of a hassle to drag it along for just about 5% of the total user base (probably even less for Pythonista in particular).
I will bite the bullet and install ios9...
- Pythonista version 3.1.1 (311008) running Python 3.6.1 on iOS 10.3.2 on a 64-bit iPad5,4 with a screen size of (1024 x 768) * 2
- Pythonista version 3.1.1 (311008) running Python 2.7.12 on iOS 10.3.2 on a 64-bit iPad5,4 with a screen size of (1024 x 768) * 2