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
-
I am ready to purchase. It can't make me a worse Python programmer than I am already 😝
-
@ccc Just FYI,
unicode_literals
unfortunately doesn't always work well in Python 2. The main issue is that Python 2 allows only 8-bitstr
for identifier names, sogetattr
and such will fail withunicode_literals
enabled, unless you wrap the strings in astr
call, which is really ugly.The way I use strings in Python 2 is:
unicode
/u"..."
for normal textbytes
/b"..."
for binary datastr
/"..."
for things that are Python identifiers
This is almost fully forwards compatible with Python 3, except that you need to replace
unicode
withstr
. -
I'm looking at Anaconda now. Looks awesome. I'm installing it in my personal school-provided network drive, as it seems to allow installation to a custom directory (yay). Before I was using PortablePython at school, which also came with a lot of useful modules, but Anaconda looks like it offers much more, as well as having a much larger community around it.
-
I'm looking forward to it (even if it's only a "beta" version). Am perfectly fine to pay for it. Keep up the great work!
-
I've just submitted the first beta to Apple. The first build needs app review approval, so it'll take a couple of days until I can actually invite external beta testers. I've already addressed most of the limitations I mentioned above, i.e. app extension, URL scheme, documentation etc. should all be working in the first beta. There are probably bugs though (it's a beta after all).
@ccc Now that I think a little more about the "future mode" setting, I'm not sure anymore that it's a good idea. The problem I see is that it would potentially introduce incompatibilities when you share scripts with someone who has different settings, and it would be a hassle to switch settings when using different scripts. The current "true division" setting only applies to the console, so it's not really an issue there. I think it might be better to use explicit
__future__
imports in scripts ("explicit is better than implicit"). -
@omz Though it would be nice to allow any
__future__
option to be enabled in the console. Not havingprint
as a function bugs me when I need more than the standardrepr
.Somewhat related - since absolute imports are the default in Python 3, would it make sense to remove the root
Documents
folder fromsys.path
too? IMHO, havingDocuments
on thesys.path
is more confusing than useful. Importable modules should go intosite-packages
. -
@dgelessus
~/Documents
isn't insys.path
by default – it only is if the script you're running also happens to be there. The current directory is added to the path automatically, but it's not necessarily~/Documents
. -
Ah okay, I thought
Documents
was special-cased and was always there in addition to the current script location. -
@dgelessus It used to be that way in 1.5, I think.
-
You can now sign up for the 3.x beta here: http://goo.gl/forms/DMpM7sBHhl
-
I already signed up, thanks a lot
-
@omz Sent a request, and also retweeted on Twitter. I can run both betas at once, right?
-
@Webmaster4o Yes, they're separate apps, you can install both at once.
-
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)