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
-
Ok, just applied for the beta! Can't wait! Also, regarding a "future" setting in the 2.7 Pythonista, I think that would be great, but only for the console. The setting, if implemented, should not apply to editor scripts.
-
IMHO we should keep the Python 2 app as Python-2-esque as possible. It's for a different audience than the Python 3 app, and the people who continue to use it probably will use it because they prefer Python 2, and if they want Python 3 features they can buy the app. It's fine that future exists, I don't think an option for automatically using it will be in the spirit of Python 2
-
...and the first build is up! If you signed up, and didn't get an invite, you'll get one soon.
-
-
My one comment is that there needs to be a way to copy files between the apps, not just move. The first thing I tried to do was copy my
site-packages
to Pythonista 3, but then I found that they had all been removed from the Pythonista 2 app -
Edit: Ignore this -- user error!
First bug report:
import sympy
-
@omz can you add support for multiple documentation tabs (like in Editorial)
-
@ccc That works for me.
-
@ccc No problems here either:
>>> import sympy >>> sympy.Matrix([[1, 0], [0, 1]]).det() 1
Perhaps you have a file called
sympy.py
in your Documents folder?;)
At least the most important feature works - proper Unicode support:
>>> len("🐍") 1
-
Nice to see so many of the PyPI modules upgraded. Scroll down to the Python3 listing at https://github.com/cclauss/pythonista-module-versions
wsgiref and yaml are missing in addition to mechanize, midiutil, screenplain, and xhtml2pdf.
-
@Webmaster4o said:
IMHO we should keep the Python 2 app as Python-2-esque as possible. It's for a different audience than the Python 3 app, and the people who continue to use it probably will use it because they prefer Python 2, and if they want Python 3 features they can buy the app. It's fine that future exists, I don't think an option for automatically using it will be in the spirit of Python 2
Totally agreed! Especially since now we have 2 separate products, I don't see why you have to bend Python 2 to fake it like Python 3. If you prefer Python 3, just buy the new Pythonista 3. In the spirit of Unix (from which iOS draws its root), it's better to "Do one thing and do it well".
-
How the heck does async/await work in Python 3.5? Is the iOS going to limit us on asyncio and the like?
-
Got the beta! This is exciting.
-
@ccc Why should it?
asyncio
already existed in earlier versions of Python based on decorators and generators, theasync
andawait
keywords only integrate it into the language better. There's no kind of threading or process spawning involved as I understand it. -
This post is deleted! -
Random observations so far:
- Startup time (the delay between the editor appearing and
pythonista_startup
being run) is much shorter on Pythonista 3 than on Pythonista 2. Not sure if that might be because my Pythonista 2 contains a ton of files and my Pythonista 3 is almost empty. exit
,sys.exit
andSystemExit
exceptions actually kill Pythonista, which onlyos._exit
used to do.async
andawait
are not treated as keywords by Pythonista. It is true that they can still be used as normal identifiers (until Python 3.7) for backwards compatibility, but that doesn't mean that you should do that.- The behavior of
editor.open_file
was changed - previously it took a path relative to~/Documents
, now it expects an absolute path. (This probably changed in an earlier beta, but I only noticed it now.) - The "welcome" file seems to be missing in Pythonista 3.
- Startup time (the delay between the editor appearing and
-
You can crash P3 if you try to create a new file in the editor while you are in the P2 folder.
-
@omz What's going to happen with the template? Bake everything into one with some sort of switch/delete operation? Is it already secretly baked in? Will there be a separate one?
-
@Tizzy There will probably be a second one.
-
Hey, @omz, In some recent beta (maybe not this one) you changed the console text input to be something other than
PA2PromptTextField
. How can I find this view now, inobjc_util
? It doesn't have a distinct class name anymore.