No update?

It is ugly. I have to write duplicated code for this. And excute it like https://docs.python.org/3/library/functions.html#exec . TOO UGLY.

ccc

Nonsense.

upwart

@cvp
This absolutely briliant!

cvp

@upwart Thanks, but only @omz and the author of Pyto are brillant

TF will expire in 7 days. Oh, the next tf will come after 7 days, and we can wait another 90 days for another tf. Wow, 1 years = 365 days = 4 tf

cvp

@timtim said:

the next tf will come after 7 days

it makes me happy, that proves that @omz is still alive, and that is the most important

cvp

See, he is still driving Pythonista 😂

ccc

TestFlight version expires on 20 hours... Drumroll please.

Wow. Omz update the beta version every 90 days which is equal to the expiry date set by Apple. I wish Apple can extend this to 365 days because I don’t want him to overwork.

cvp

Beta expired

Let us pray

pulbrich

Louder, please.

cvp

😱 😱 😱 😱 😱 😱 😱 😱 😱

Hello？Still alive?

Please no more "No actual changes."

ltddev

@cvp I am quite intrigued at your creative solution to use Pyto as essentially another module that Pythonista can use to provide support for all the many modules that the latest Pyto has but as of this moment are not supported in Pythonista. And it brilliantly uses url schemes to provide the means for callbacks from one app to the other. I have a few questions that perhaps you could elaborate on<?

1 - Is code that is running on Pyto side running in a Pyto process or Pythonista's? that is, if in Pyto, then latest Python version for example.
2 - Can I create my front' end UI in Pythonista with support for a decent UI editor but run non-UI code on the Pyto side?
3 - Is it the case that, for example, in the case of Pandas, that the full breadth of support would be there, effectively never needing Pythonista to support any of these modules, but if installed on Pyto is fully available on the Pythonista side?

mikael

@ltddev, that would be the idea. Since both Pythonista and Pyto can see the same code in iCloud, there is no need to even pass all executable code over the url.

Would be even better if the pyto site-packages could be exposed to Pythonista...

RIP pythonista?

cvp

@ltddev

Yes, in Pyto
Why not
Yes, but not fully available on the Pythonista side, only the result of Pyto could be sent

cvp

@mikael said:

Would be even better if the pyto site-packages could be exposed to Pythonista...

I think it was possible with the last (disappeared) beta

ltddev

@cvp, thanks for clarifying. Then this is a nice way to own both apps and extend the longer term value of Pythonista by using each app for the way it excels(right now ( in my opinion, Pyto beats out Pythonista for the latest Python builds and the extensive 3rd party library support right out of the box and that it is open source, which at the very least means that there is an active community discussing and implementing new features, fixes and documentation. Pythonista currently beats out Pytro for its elaborate UI building capabilities, its documentation, an active community of users that have already produced great tooling (like the entire STASH ecosystem) and ways to extend Pythonista perhaps in ways never even imagined by its creator. I think Pythonista's Object C bridge and its support for calling native code (objc_utils) is easier and richer to use than Pyto's, although Pythonista''s is proprietary (OMZ created and owns)``while Pyto uses opensource 3rd party so it is more extensible. Even if OMZ never releases a single update for Pythonista, I think its value stretches into the future (provided that future IOS versions don't completely break the app which is very unlikely given there might not be any further development to Pythonista,

Thus it would appear to me that each app currently does some things better than the other does so we need not have to choose one or the other but can actually use both to build some really useful utilities and extensions that can extend IOS apps because the url scheme support provides some measure of inter-app support.