Welcome!
This is the community forum for my apps Pythonista and Editorial.
For individual support questions, you can also send an email. If you have a very short question or just want to say hello — I'm @olemoritz on Twitter.
Python 3.x Progress Update
-
Bug: when running a script via the url scheme (
pythonista3://
) it ignores the default interpreter setting and runs the script as 3.5. It also ignores the shebang -#!python2
-
@omz, sorry another question about colliding betas so to speak. I seen yesterday we got a new thing (well for me it was new, a renew on the 2.x beta for 7 days , instead of an update in TestFlight). Great idea btw. Not sure if that's a new thing apple opened up to you or if it's been there all the time.
But if at anytime the 2.x beta is expired or not, if I delete it and install the App Store version will it just take the place of the beta leaving all my files intact?
Just want to make sure what will happen -
@Phuket2 If you delete the app (tap and hold, then tap the delete icon) then your files will be deleted. If you install the App Store version over the beta, the data will probably stay in place, I don't think there were any major changes to Pythonista's data structure in the beta.
-
@dgelessus , ok thanks for that. I would have done it the wrong way and lost my data 😱 I should know better, but it appears I don't. Thanks again, makes sense
-
@omz - Just signed up for the beta, hope its not to late to test it out and provide feedback!
-
Hey, this topic just hit 20k views!
-
Seem to me the split-screen toggle is broken in the beta.
I had a full screen console and I could swipe left and right between it and the editor, then I pushed the split screen button and now swiping left/right transitions between either the editor with the file browser on the left or the editor with the (narrow) console on the right. Problem is, the split screen button seems to have disappeared now and I can't for the life of me figure out how to get the full screen console back.
Just went and checked in version 2 and the toggle remains after switching to split-screen. In the beta it disappears and only the help button remains at the top left of the console pane.
-
see https://forum.omz-software.com/topic/2747/python-3-x-progress-update/289
from objc_util import ObjCClass ObjCClass('NSUserDefaults').standardUserDefaults().setBool_forKey_(False, 'DockedAccessoriesPanel')
then restart the app
-
Any idea when the next beta will be, or better yet a release?
-
@JonB Thanks. I missed that post.
-
New beta literally fixes all the worst bugs, I'm so happy :D
- Improved console prompt: the text input area now expands automatically for multi-line statements
- Improved auto-indentation (also works when splitting a line now)
And also it also has most of my most-wanted editor features!
- Some improvements for external keyboard users 😍
- Experimental Today widget for running scripts in notification center
- Code completions can now be suggested based on fuzzy-matching
Thanks a lot, @omz, this is great work 👍
-
@omz Nice update! Excited to mess around with the today widget, and look forward to integration into the Xcode template.
-
Is there a way to print out how much memory your script is using?
-
@omz Will you use a bundle to give a discount to existing users? (A bundle including Pythonista 2 and 3 allows customers who purchased 2 at full price to subtract $10 from the bundle price.)
-
I just messed around with the new beta, and the today widget is great! I also love the new icon, I wasn't a fan of using the python logo, and really like that you switched back to the old style. As a quick test I changed the calculator example to run from the today widget and it worked fine, so that's nice :) one suggestion I have is the ability to remove the play button from the widget. It takes up the entire column, and makes the view not be centered.
-
@Tizzy said:
Is there a way to print out how much memory your script is using?
You might want to take a look at the resource module
-
I noticed that running a script after running it in the today widget gives the notimplementederror if the script has a non supported module (the interpreter thinks you are still in the widget)
-
@filippocld I can't reproduce that, and I'm not even sure how that would be possible at all, given that the widget runs in an entirely different process. Do you have a short example perhaps? Maybe there's something wrong with the way I check if the widget is running in some cases, but not others...
-
Maybe it is only the notification module...
-
@filippocld I see... It actually looks like the notification module doesn't work at all in Python 2 mode (I assume that's what you've selected as the default interpreter). Thanks for noticing, I'll look into it.