Pythonista for Python 3.x.

JonB

Out of curiosity, when folks complain about Py3 support, which features of Py3 are the feeling like they really use, that are not in futures ? Other than differences in how strings are handled, which can be simulated using six for programs that really need to distinguish between bytes and text, seems to me a lot of the Py3 changes are under the hood where most users won't really directly interact. I guess bugfixes might be important, but it is not like Pythonista was getting a new release for each Py version anyway.

dgelessus

Things that come to mind:

Unicode handling that is not completely messed up. Even with enough future imports you cannot completely simulate Python 3, simply because the separation is not strictly enforced in Python 2 (you can decode a unicode string, wtf?) and because half the code still uses 8-bit str. Also, proper wide Unicode support,
Cleaned up stdlib names, e. g. urllib2 becomes urllib and has a cleaner structure. Minor things, but I like consistency.
New syntax, like type annotations. (That would make writing function stubs for ctypes much cleaner.)
Less random language weirdness, like print and exec keywords, normal division on ints doing implicit flooring, etc.
Fancy metaclass features, like the metaclass kwarg on class definitions, or __prepare__.
Chained starargs! This took way too long. Finally func(*args, *moreargs) is allowed.
Keyword-only args in function definitions, which previously required ugly stararg hacks.
Proper exception chaining (I think that's new in Python 3).
nonlocal.
I'm sure some people would find the async/await stuff useful too.

Webmaster4o

How do the chained stargs work? If I have func(*args, *moreargs)
and I then put in func(1,2,3,4,5,6), how is it decided what goes into the list args and what goes into moreargs?

ccc

Yield from (see PEP 380). Like try to do curio or agent with Python2.

dgelessus

@Webmaster4o Not when defining functions, but when calling them. For example, this is how you could implement functools.partial:

def partial(callable, *frozen_args, **frozen_kwargs):
    def _partial(*new_args, **new_kwargs):
        return callable(*frozen_args, *new_args, **frozen_kwargs, **new_kwargs)
    return _partial

Webmaster4o

Ah, ok. Now I get it.

dgelessus

I'm sure @ccc would point this out soon enough ;) but Python 2.7.11 was released today/yesterday: https://www.python.org/downloads/release/python-2711/

ccc

@dgelessus LOL... Yes. And Python 3.5.1 is due tomorrow: https://www.python.org/downloads/release/python-351

ccc

Brett Cannon - Where are we in the Python 3 transition? http://www.snarky.ca/the-stages-of-the-python-3-transition

Phuket2

@ccc , thanks. I subscribed to his blog. I read through quite a few of his blog entries. Really good info for someone like me (limited info on the history of Python and the future and more...) for one, I will start to look at Unicode seriously, it's good to do while I am still a beginner. Anyway, great info from this guy (Not just the mentioned blog entry here) and he has the credentials

mfkilgore

Most of the posts here are 3 years old. More libraries are now available on Python 3 and it appears to be the clear direction forward for Python. My requirements are for Python 3.

Pythonista looks great and as soon as it is on Python 3 I will purchase it!

dgelessus

Just FYI to anyone who may have missed it - it's happening...