New Beta for Pythonista 3.3

caddtec

Soooooo great to have a new version! Thanks @omz for the beta! Just tried out most of my apps, scripts ans unit tests. Everything seems to work perfectly!
Will continue testing and report any error I find.

Again thanks!
D

caddtec

I was just trying the new keyboard PyKeys and notice what seems to be a problem... that whenever I enable it, I see only the small upper part of every buttons unless I show the whole keyboard (I use a physical keyboard by the way). I am on iOS 12 with the new iPad Pro 12.9.
Is it suppose to work that way? Am I the only one that it happens?

sashk

Any plans to include newer version of Python, i.e 3.6.7/8 or 3.7.1/2?

upwart

Any plans to support Pandas?

omz

@caddtec You can tap and hold the ^ button (bottom-right corner) to make the keyboard visible when an external keyboard is connected.

wnMark

@caddtec I had the problem on iOS 11 but not on iOS 12.

@omz Thank you for the beta. I am enjoying the testing

robnee

Any chance on addin a theme element for the stderr console text? The dark red is hard to read with some of the dark themes.

The modules are very very old. Will you update them?

orsharir

Thanks for the update! I've been looking forward to the Siri integration.

Is there any way to pass input to the script, or return an output from it? The potential for Pythonista as a glue between other shortcuts, and the possibility of creating a programmable voice interface is huge -- but it depends on the ability of Pythonista to process input and generate output.

Edit: I've just realized that the apparent lack (unless I missed this option) of native input / output could be mitigated by using the clipboard. I still think it would be better to have native support (less boilerplate steps in the shortcut app), but now I can finally start experimenting with the above ideas. Thanks again for the update!

@upwart For pandas. +1
@sashk And python 2.7.15

ccc

:beer: :beers:

mithrendal

Hi,
I tested the new Beta on my current projects. It run most of the time fine. I had some methods where I had to additionally annotate with @on_main_thread to make it run, which I must not in pythonista 3.2 . But I think this is more correct and I guess v3.2 was just a bit more forgiving in that regard and v3.3. a bit more strict which is fine.

I had an issue though with pythonista-gestures from @mikael :
it gives an key error upon accessing a dictionary each time you trigger a gesture

I opened an issue for this at https://github.com/mikaelho/pythonista-gestures

Due to some restructuring in the new pythonista v3.3, in the end I think it has to be repaired in Gestures.

EDIT: it has been repaired. ;-)

I hope @mikael has also access to the beta :-)

How many seats are there free ?

Now I will have a look at the funny keyboard thing ... ;-)

omz

@orsharir said:

Is there any way to pass input to the script, or return an output from it? The potential for Pythonista as a glue between other shortcuts, and the possibility of creating a programmable voice interface is huge -- but it depends on the ability of Pythonista to process input and generate output.

Unfortunately, there are no APIs from Apple for that, so it's not possible. You can use the clipboard as a crutch though (at least for text-based stuff).

omz

@lpl said:

The modules are very very old. Will you update them?

I'm aware of that. I'll look into updating some of the more important ones.

omz

@robnee said:

Any chance on addin a theme element for the stderr console text? The dark red is hard to read with some of the dark themes.

I'll consider it, thanks for your feedback!

omz

@caddtec said:

I was just trying the new keyboard PyKeys and notice what seems to be a problem... that whenever I enable it, I see only the small upper part of every buttons unless I show the whole keyboard (I use a physical keyboard by the way). I am on iOS 12 with the new iPad Pro 12.9.

Yeah, it's difficult to make it work well in combination with physical keyboards to be honest.

I had a solution that worked better than the current beta, but it was auto-rejected by Apple's App Store validation mechanism because it relied on the keyboard having an "emoji" language, and while that works fine on the device, it's apparently not standard-compliant or whatever.

In general, you can work around this by showing the keyboard manually. You can do this by holding the ^ button in the toolbar above the hidden keyboard (bottom-right corner).

ihf

This post is deleted!

@omz Openssl 1.0.2f has a serious bug. Please have a checkout and update it. https://bz.apache.org/bugzilla/show_bug.cgi?id=58956
And python3.6.8 is coming out soon. I think 3.6.1 is old. So is 2.7.12.
"To get a newer version of the typing module in Python 3.5 or later, you have to upgrade to a newer Python (bugfix) version. For example, typing in Python 3.6.0 is missing the definition of ‘Type’ – upgrading to 3.6.2 will fix this." https://pypi.org/project/typing/#description

caddtec

@omz Yeah I thought so (about the fact it is difficult with physical keyboard). I’ll just have to make do, it is not so problematic so no worries ;o). However, could be a good idea to do like the emoji keyboard however: when we select the PyKeys, it shows the keyboard by default (on screen) and then when we select another keyboard, let’s say English, then the on-screen keyboard disappear and you can then continue using the physical keyboard as always. IMHO I think I would prefer to show the on-screen keyboard by default instead of having to press the button in the toolbar above the hidden keyboard.
As for the App Store validation, I abandoned a long time ago the idea of understanding! ;o)

And thanks for the feedback!

pyios

This post is deleted!