Posts made by ltddev

Yes, @coltonboyd, I too cannot access this link but I would very much like to use your Python 3 Pythonista 3 template for Xcode. Could you please post a corrected link?

I routinely use Ole's "ftp server" sample code here to copy and move files back and forth from Pythonista on my iPad to PC and PC to iPad and I never had any issues with it prior to updating to Pythonista 3.3. While running this code in 3.3 I can open folders, I can view directories without problem, using various ftp clients. However, when I try to either copy files FROM my iPad (a purely read operation) or copy files TO my iPad (a write operation), I completely crash Pythonista and the files are not copied. I have tried various clients such as web browsers, file managers and every time I try to do anything other than just viewing directories, I crash Pythonista 3.3 If you look at the code you see that it will try to install the ftp lib if it does not find it. Because it finds a copy already present it does not try to install it again. I recently upgraded my iPadOS and ios on my iPhone so that could be a factor. I have not tried the same scenario on my iPhone I have only tried on my iPad.

Has anyone seen this on their Pythonista 3.3 device?

Well, I've just had the pleasure of updating my iPhone 11 Pro and my iPad Pro to Pythonista 3.3 Final! See the Release Notes and Preview video here .

The last sentence in the Release Notes is:been
"Thanks for reading, and thanks for your patience with this release. It's not everything I'd like it to be (hello, Shortcuts app!), but there are still many new things to discover, and I hope you have a lot of fun with it!."

I know I will, for sure! Thank you Ole, @omz, for all your hard work, under extreme health circumstances. I know only too well how difficult that must have been for you. Please know that Pythonista's faithful users appreciate all you've done and continue to do to guide this App, to keep it alive, to keep it relevant - especially when there have been some naysayers (and not just a few) that were habitually posting that Pythonista was dead, that it was "abandonware" (a term I must confess I've never come across in all my years in software development until I saw it on this forum by trollers no doubt) and that it was time to start discussing what comes after Pythonista.

@Zoot can you clarify the meaning of, "...a new Test Flight version also being available at that time too!"?

My understanding would be once the code goes golden in the app store, it means the release is no longer "in beta" and if that is the case, beta testing for this release is effectively wrapped up and Ole does not need beta testing any more and a beta build would cease. If that is the case, what is the purpose of a "new Testflight version"?

Any news?

@Guest ,
It is apparent to anyone following omz on Twitter that Ole has been away for quite some time at least in part to heal from some sort of mental illness combined with intentionally holding back on the updates and new features of a new product while he thinks about/tries out various types of offerings and updates such as free and pro versions of the next version of Pythonista and Editorial In any case, it would appear that the stress of managing and updating these apps in a way that both suits his needs to draw an income and pay bills with revenue from these apps and be a good thing for all the current and future users of Pythonista and Editorial, may be factor in the mental illness he has been dealing with for the past two years. If so, your constant baiting and taunting him (you and some others) with remarks such as ( I paraphrase) "la la Pythonista is falling down, falling down, falling down la lala..." make it abundantly clear that you (and some others) firstly fail to realize that there is actually a real human being named Ole who produced/produces Pythonista and Editorial , who has feelings, who uses revenue from these two apps to pay real bills, who did not create them just for your benefit and of some of the people out there who think and strongly believe that because they slapped down ten bucks a couple of years ago to purchase a LICENSE to USE Pythonista, that this, in itself, grants you some ownership of them and their author and that you somehow DESERVE future updates/new features (as opposed to bug fixes to correct defective code you licensed). As others in this thread have remarked, Pythonista 3,x is a FINISHED, versioned, product and grants you usage of it, as is, as it was at the time you installed it. Any further enhancements or improvements are COMPLETELY at the discretion of their author, though any good author with a dedicated group of users will want ro take their opinions on such things into consideration.

The point I am trying to make is,that there is really no room here on this forum for any negative remarks about Ole and this app that are not constructive and only serve to annoy the users of this forum and probably Ole as well.

@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.

@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?

@ccc, I don't want to come off as rude, but the question was a legitimate one and your reply states the obvious. Do you work in some means on this product to give a more specific answer than "it will be released when it's ready to be released? I would certainly hope it will not be released if it's not ready so this begs the question:
When will Pythonista 3.3 be ready? Please don't answer "it will be ready when it's ready" lol.

@Blanchot
Yes, I can indeed imagine such a scenario. I am actually an IBM developer who had a stroke in 2011 and currently on long term disability leave, hence my handle ltd - LTD
dev - developer
(developer on LTD).
Life events often necessitate removing yourself from the world just as you describe and I can easily imagine Ole (a real person, just like you and me with real life events) dropping out of the world/communication for a while and that this does not mean that he has given up on his projects.

"...and seeing that Ole has recently begun again to publicly reply to tweets"

is very good to hear and encouraging.about the future of Pythonista.

@ccc, are you confirming that because there is an update to the beta that means there is indeed active development to Pythonista?I If true, my question is how long is Pyrthonista going to remain in bera? It seems like the beta program has been going on forever. When will we see a significant update or new product in rhe App store? For those of us that don't really suit beta testing, why has development effectively going on in secret with no mention here in THIS forum of a public statement of any kind as to what we can expect in the update and WHEN can we expect to see it in the App store? Will it be an entirely different application altogether or will it be delivered as in in app purchase, I don't mind paying for it either way but I would like and think the developer would say SOMETHING about these things here in HIS forum.

@dgelessus - are you saying flat out that as of IOS 11 there is no way to get Pythonista (or any other IOS app ) to talk to Twitter? Since there is no native apis, there can be no straightforward way tor any IOS app ( other than presumably the Twitter app itself) to code ro Twitter?

@Drizzel, I am looking at your replies over and over again and feel I must be missing something. In both replies you suggest changing code to what @richexperiences has actually already presented.

It seems to me that in both cases the code ALREADY states what you are suggesting it should be changed to,

@Drizzel, could you please clarify what the differences are between the code as already written and the code you suggest it be changed to?

@omz, thanks, I thought of that workaround as well but wondered if there was anything a little more elegant such as "Open with" to choose the editor to use rather than try to trick it that the .pyui file is either a text file outright or one to be treated as a text file.

I may have forgot but I checked through the forum posts and I don't see an answer to the following: What is the suggested way to view a .pyui file (without changing the default ui editor)as plain text rather than use the ui editor?

@omz forgive my ignorance but where is the bug tracker for STASH?

I agree this seems to be a bug in STASH and some of the other errors I am seeing here (like issues with git) may be related.

I can reproduce with the following steps:

1. Run launch_stash.py
2. Run the command again to create a second instance.
3. Go back to the first and enter what seems to be any character.

RESULT: Pythonista crashes.

If STASH does not support this scenario perhaps it should only allow a single instance?

Actually, I'm having some trouble reproducing this. I have to go back and see the exact steps I took when I was able to crash the app but I can create multiple STASH instances and have no problem switching between instances. I definitely was able to crash the app multiple times with two STASH instances.

I don't recall this to be a problem before but when I run Launch STASH a second time to have a second STASH instance, when i go back to the first STASH instance andI run a command such as "ls" Pythonista crashes.

Using the ui editor, is there a way to add a separator line such as you see on many settings pages in iOS (including, I believe, Pythonista's own settings page) ? I am creating a custom view which contains a number of settings with check boxes and toggle switches and other controls. I would like to add a separator line between various settings to break the ui into meaningful groups. As a hack I am using a label whose text attribute is a continuous underline character.