Live data from Hacker News

Python 3.5.0

python.org

131–140 of 165 posts

Re: Python 3.5.0

#131

Earlier quoted context omitted.

Not in the defence industry.

Some industries will be stuck with old versions of just about any language, no matter what. GP actually said he's stuck on 2.6, which means he can't even use 2.7.

I work in defense. Software approval is for major releases, so he I don't see why he couldn't use 2.7. If he wants to go to 3, that's when he'd have to get approval.

Re: Python 3.5.0

#132
post #58

Earlier quoted context omitted.

Is Py3 ready for prime time? Do all the right libraries have support now?

Unfortunately I'm stuck on 2.7 until Google updates App Engine

Most of the time I find it pretty easy to make it compatible with both 2.7 and 3.4. Usually just a few "from __future__ import print_function" and a few other tips.

If your codebase is large, it can feel daunting, but it's not usually that bad.

Re: Python 3.5.0

#133

So far, this is my favorite 3.x release. Typing annotations, async/await, unpacking generalizations. Lots of cool new features. Too bad that PEP0498[1] didn't make it in this release, we'll have to wait for 3.6. [1] https://www.python.org/dev/peps/pep-0498/

> 'f' may not be combined with 'u'.

I thought that Python3 removed 'u' strings, was this just a bit of humour in the PEP?

Re: Python 3.5.0

#134
post #133

So far, this is my favorite 3.x release. Typing annotations, async/await, unpacking generalizations. Lots of cool new features. Too bad that PEP0498[1] didn't make it in this release, we'll have to wait for 3.6. [1] https://www.python.org/dev/peps/pep-0498/

> 'f' may not be combined with 'u'. I thought that Python3 removed 'u' strings, was this just a bit of humour in the PEP?

We added u'' formatting back in 3.3 to ease 2->3 porting. u'' is equivalent to simple ''.

Re: Python 3.5.0

#135
post #128

Earlier quoted context omitted.

I use it like es6 or haskell destructuring. Sure it's a little weak compared to both those implementations, but the tuple case covers enough to be useful.

EC6 allows you to destructure in the function definition ?

Yep. It's awesome.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

Re: Python 3.5.0

#136
post #58

Python 3 keeps getting better and better. I've been writing more code in Python 3 than 2 for about three years now, and I absolutely love it. When I have to write code in 2.7 now, it feels like shifting from fifth gear down to second.

Is Py3 ready for prime time? Do all the right libraries have support now?

Py3 has been prime time for a while now. Been using it full time since Py 3.3 for all my work and I haven't had any issues with it. There were some external libraries such as the library given by a twilio competitor that were incompatible, but easily fixed (almost exclusively, encoding issues).

Although, I still find myself running tests and cursing at the fact that I keep writing print "string" without the brackets :D

Re: Python 3.5.0

#138
post #128

Earlier quoted context omitted.

I use it like es6 or haskell destructuring. Sure it's a little weak compared to both those implementations, but the tuple case covers enough to be useful.

EC6 allows you to destructure in the function definition ?

As someone who splits his time between Python, Clojure, and Javascript (via Babel), lack of this is extremely annoying for Python since the other two languages allow it.

Re: Python 3.5.0

#139
post #71
post #59

Earlier quoted context omitted.

Care to share some highlights? Fifth to second sounds like a big difference!

It has the ability to statically check the type system , that's amazing. Moreover async/await with async resource management (which C# doesn't have yet) gives it a real edge for server development.

> Moreover async/await with async resource management (which C# doesn't have yet)

In C#, the using statement combines with async/await. It is cool that Python finally gains proper async/await, there is no need to diss other languages.

Re: Python 3.5.0

#140

Python 3 keeps getting better and better. I've been writing more code in Python 3 than 2 for about three years now, and I absolutely love it. When I have to write code in 2.7 now, it feels like shifting from fifth gear down to second.

> When I have to write code in 2.7 now, it feels like shifting from fifth gear down to second. You mean, second gear up to fifth? I tried writing some Python 3 code and the lack of parameter tuple unpacking by itself stunned me and drove me crazy, never mind other stuff. Python 3 seems very user-unfriendly compared to Python 2. Won't touch it with a ten foot pole unless my life depends on it.

At first glance, parameter tuple unpacking seems like a silly hack that was wisely removed, explained here http://legacy.python.org/dev/peps/pep-3113/

What are the cases where you use it / rely on it?

Post reply on HN