News for hackers. Stuff that matters.
Re:PyPy gets funding from Mozilla for Python 3.5 support by twblalock on Tuesday August 09, 2016 @06:24PM (#12258142)
It's optional. How can that possibly bother you? Don't use it if you don't like it.
Re:PyPy gets funding from Mozilla for Python 3.5 support by catdog on Tuesday August 09, 2016 @07:10PM (#12258337)
It's not only optional, it does nothing by default. What was introduced into python is a standardized way to do type annotations. It consists mostly of a new standard library module and as far as i know it doesn't even introduce changes to the language as it uses comments, additional files and the rarely used function annotations. The interpreter happily ignores them anyways but external tools like mypy don't have to invent their own incompatible syntax.
Re:PyPy gets funding from Mozilla for Python 3.5 support by twblalock on Tuesday August 09, 2016 @08:36PM (#12258706)
I was more excited about them when I believed they were actually enforced. I guess they help with static analysis in IDEs, but you can still get type errors at runtime, so Python is still missing out on the main advantage of static typing.
Re:PyPy gets funding from Mozilla for Python 3.5 support by hendzen on Tuesday August 09, 2016 @09:04PM (#12258804)
there is a type checker available: http://mypy-lang.org/
Re:PyPy gets funding from Mozilla for Python 3.5 support by viraptor on Tuesday August 09, 2016 @09:10PM (#12258824)
> as far as i know it doesn't even introduce changes to the language as it uses comments

That's not the case. See for example https://www.python.org/dev/peps/pep-0484/#type-definition-sy...

Re:PyPy gets funding from Mozilla for Python 3.5 support by xapata on Tuesday August 09, 2016 @06:37PM (#12258197)
Because I'll need to support people that use it and explain it to newbies who read it. More work to do, without much benefit (to me; I understand it has much benefit to some people).
Re:PyPy gets funding from Mozilla for Python 3.5 support by StavrosK on Tuesday August 09, 2016 @07:44PM (#12258466)
It's only without benefit if you don't write Python. Otherwise, it's like having tests that take almost no effort to write. What's not to love about it?
Re:PyPy gets funding from Mozilla for Python 3.5 support by xapata on Tuesday August 09, 2016 @09:00PM (#12258793)
Edward Tufte might call it chart junk. It reduces the information to ink ratio. I generally get by just fine by choosing good names, so I don't need extra type checking beyond the standard duck typing.
Re:PyPy gets funding from Mozilla for Python 3.5 support by yeukhon on Tuesday August 09, 2016 @10:11PM (#12259065)
Why add static typing to a language long stood for duck typing? There should really be one way to write in Python.
Re:PyPy gets funding from Mozilla for Python 3.5 support by srean on Tuesday August 09, 2016 @11:25PM (#12259323)
A few things.

i) its not a type checker. It cannot actually ensure type correctness. So may be a more appropriate description would be "a very smart linter".

ii) Its optional

iii) even when switched on it does nothing unless you are explicitly using its features

iv) The "there is only one way to do things in Python" is just vapid marketing. It is not true and has never been true.

Re:PyPy gets funding from Mozilla for Python 3.5 support by dagw on Wednesday August 10, 2016 @03:38AM (#12260087)
"there is only one way to do things in Python" is just vapid marketing.

It's not even that, the actual quote is "There should be one, and preferably only one, obvious way to do things". The whole "there is only one way to do it" was a joke response to Perl's "There's more than one way to do it" motto.

Re:PyPy gets funding from Mozilla for Python 3.5 support by antod on Wednesday August 10, 2016 @06:42AM (#12260674)
The explicit version: "There should be an obvious way to do something. Ideally only one way will be obvious."

The original version was too implicit. Unless you are Dutch.

Re:PyPy gets funding from Mozilla for Python 3.5 support by coderzach on Tuesday August 09, 2016 @10:35PM (#12259153)
I've had great experiences with optional static typing from tools like flow[1] and mypy. I've found you can gain most of the bug catching and readability benefits of static typing, while having the power of dynamic typing when come across a truly dynamic problem.