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
-
@omz Thanks
-
@omz When in doubt, blame daylight saving time.
;)
(Explanation for non-Europeans: Our DST just began last weekend.)
-
@dgelessus My DST started about 2-3 weeks ago I think. I can't remember. Just remember being tired :)
-
I have no DST!
#whyisthesunupat4am -
@omz Update looks really good! First things I noticed:
- Great new icon!
- The "Run with Python 2.7" option has to be selected every time. My idea on this is:
- Have a small number 2 or 3 shown in the bottom right of the "Run" icon to show whether Python 2 or 3 is selected to run
- If a user selects the "Run with Python 2.7" option manually, change the indicator to say 2.
- The interpreter would run with Python 2.7 until the user long-pressed the run button and selected a "Run with Python 3.5" option.
- This toggling behavior would make using Python 2 vs 3 easier if a user prefers one over the other but still wants to switch quickly. I think a user wants to use the same interpreter they just did a second ago more often than a user wants to switch interpreters.
- If I long-press the "Run" button and hold on an option, it becomes highlighted and changes color. If I slide up and down the options, they all become highlighted without the ones I've moved my finger off of becoming un-highlighted.
-
I love the new icon, nonetheless after the app has been installed I still have the old icon from the previous beta. I tried removing and re-installing again, the same thing, still the old icon
-
Hello. Is there any way to understand whether my beta request was abandoned or not?
-
The icon is good! Now it's downloading :-)
-
-
In the Task Manager (double click home button) the correct icon is displayed on my iPad Pro, but on my iPhone 6 Plus the task manager will show the old icon, it's weird because they are using the same iOS version.
-
@Webmaster4o Did you see the option to change the default Python version in the settings?
@OI That is probably the issue mentioned in the release notes, that the new icon is missing for some resolutions (probably the non-Retina ones) so the old one is displayed instead. And to be honest I like the old logo better... possibly because every other Python app uses the Python logo in the icon. The "prompt" icon is different and more recognizable IMHO.
@filippocld Agreed, though it would be good to have separate site-packages folders for the two versions (I think currently Python 2 uses the Pythonista 2 site-packages). Not all modules have a single codebase for Python 2 and 3, I think some projects just run
2to3
or3to2
on their source code. -
@alexquot It wasn't. He probably just hasn't gotten to it yet.
-
@dgelessus Yeah, I saw that. I just think my solution would be smoother
@omz Thanks so much for speeding up
print
! -
@Webmaster4o Honestly your solution does not make sense to me. If you really want to switch versions fast just put the
#!/usr/bin/env python3
line at line 1 of the script
-
@Webmaster4o I do like the idea with the small number showing what Python version will be used, even if there is no toggle in the run menu. (Then you could also see if Pythonista recognizes the script's shebang line correctly.) In the patchnotes omz said that the interactive console's version switching behavior might be changed in the future.
@omz Any chance that we could have interactive Python 2 and 3 in separate tabs, so we can use them in parallel and switch between them? I like @ccc's ideas for how that could be used to run two scripts at the same time.
-
@OMZ: Great new beta. Nice icon but to much "Python" and to less "Pythonista". Maybe an icon with both symbols (big old symbol and small python icon within) could do it.
-
@omz how do you plan to handle different versions of modules for Python 2 and 3? We may need two site-packages directories. Note that on desktop,
pip
will only install for Python 2 andpip3
will install for Python 3, keeping them separate… -
Yeah, like "site-packages" and "site-packages3" that's a simple and fast way
-
@omz
console.write_link
seems to be broken in this build. For example,print("foo", end=""); console.write_link("title", "http://example.com/")
prints titlefoo instead of footitle.PS:
Looks like a threading issue.
print("foo", end=""); time.sleep(0.1); console.write_link("title", "http://example.com/")
works as expected.PPS:
And
console.set_color
doesn't work properly either in combination withconsole.write_link
.(Ignore the use of
multiprocessing
, that was just to generate a long traceback. I'm testing a customsys.excepthook
.) -
I'd like if you could add breakpoints by simply tapping on the line number ( like in Xcode)