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.
Care to share some highlights? Fifth to second sounds like a big difference!
Python 3.5.0
71–80 of 165 posts
Re: Python 3.5.0
#72I'd love to use Python 3. Alas, I work in the defense industry and am working on a new development project in Python 2.6. Why? Because that's the version that's already installed on the client's systems, and getting anything new installed is such a nightmare of Vogon-esque policies and procedures that I've learned not to even ask. I'm constantly having to hack around bugs in ancient versions of libraries that have be…
Re: Python 3.5.0
#73By far the most exciting news here, to me, is PEP 484 typing module. Typing support would eliminate one of pythons biggest weaknesses. Furthermore, having it optional means it can remain as easy play and prototype with while becoming "more professional." The other features are all well rounded, with co-routines having quite some potential, though I'd have to play around with them first to assess. Now if everything wo…
> PEP 484 typing module Looking forward to this as well. So far the only static analysis tool I'm aware of that makes use of the PEP 484 framework is mypy [1] -- does anybody happen to know of other tools in the works? [1] http://mypy-lang.org/
Re: Python 3.5.0
#74Earlier 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.
Re: Python 3.5.0
#75Earlier quoted context omitted.
Doubt it. The @ symbol isn't implemented by default. It's just available as a syntactic element primarily for NumPy to use, though other libraries are free to use it as well.
I want to see it used for an XML library, since I think node@"name" is a more succinct, and domain-appropriate equivalent for node.attrib.get("name").
Re: Python 3.5.0
#76By far the most exciting news here, to me, is PEP 484 typing module. Typing support would eliminate one of pythons biggest weaknesses. Furthermore, having it optional means it can remain as easy play and prototype with while becoming "more professional." The other features are all well rounded, with co-routines having quite some potential, though I'd have to play around with them first to assess. Now if everything wo…
Yep - can't wait until Python3 is the norm. Feels like such a step back when I have to use a Python 2.x codebase - so many little annoyances.
I made python 3 a 'production readiness requirement' at the start of this year.
My two biggest Python3 complaints have stopped being 'something doesn't work' to 1: Pyston is targeting Python 2 and 2: PyPy doesn't care enough about Python 3 ( I mean seriously... PyPy + AsyncIO = EPIC )
Re: Python 3.5.0
#77Earlier quoted context omitted.
> PEP 484 typing module Looking forward to this as well. So far the only static analysis tool I'm aware of that makes use of the PEP 484 framework is mypy [1] -- does anybody happen to know of other tools in the works? [1] http://mypy-lang.org/
I know PyCharms is working on using them for its type-hints as well as offering better auto-completion options.
Re: Python 3.5.0
#78I'd love to use Python 3. Alas, I work in the defense industry and am working on a new development project in Python 2.6. Why? Because that's the version that's already installed on the client's systems, and getting anything new installed is such a nightmare of Vogon-esque policies and procedures that I've learned not to even ask. I'm constantly having to hack around bugs in ancient versions of libraries that have be…
If you're already working around bugs you could create your own venv with a later version. Easier to ask forgiveness than permission.
Re: Python 3.5.0
#79I've recently joined a Python project, my first time working with the language. We're currently using Python 2.7. How do experienced Pythonistas decide if/when to upgrade to 3.x? I figured it was a no brainer given that it has been 7 years with a number of big releases, but Flask's warning on this topic put me off: http://flask.pocoo.org/docs/0.10/python3/
P.S. That flask warning is definitely very out of date. I used Flask with Python3 quite happily, literally this week.
Re: Python 3.5.0
#80Earlier quoted context omitted.
If you're already working around bugs you could create your own venv with a later version. Easier to ask forgiveness than permission.
Not in the defence industry.