News for hackers. Stuff that matters.
Re:Python 3.5.0 by orf on Sunday September 13, 2015 @05:17PM (#10212813)
I've been using Python for 7+ years, and I had no idea parameter tuple unpacking was a thing. Never once seen any code that uses it, or seen anyone mention it. If you think the (rightful) removal of a hardly used feature[1] that has some big problems is a blocking issue then I feel sorry for you. Py3 is awesome.

1. https://www.python.org/dev/peps/pep-3113/

Re:Python 3.5.0 by dvlsg on Sunday September 13, 2015 @07:23PM (#10213109)
Interesting. Javascript is actually adding something very similar, calling it destructuring. It's actually quite handy - although admittedly more handy for destructuring object arguments than array arguments.
Re:Python 3.5.0 by ben336 on Sunday September 13, 2015 @07:42PM (#10213143)
Python 2 & 3 have destructuring. This is talking about having

def fxn(a, (b, c), d):

    pass
Be a valid function signature. So the destructuring is held in the function definition.

Python 3 will still allow

def fxn(a, x, d):

    (b, c) = x

    pass
Both Python and ES6 JavaScript allow destructuring arrays:

//javascript

let [x, y] = [1,2]

#python

[x, y] = [1,2]

(x, y) = (1,2)

Re:Python 3.5.0 by Arnavion on Sunday September 13, 2015 @08:09PM (#10213190)
ES6 does allow that via destructuring - https://babeljs.io/repl/#?experimental=true&evaluate=true&lo...

    function fxn(a, [b, c], d) {
      console.log(a, b, c, d);
    }
Re:Python 3.5.0 by wfunction on Monday September 14, 2015 @03:33AM (#10213973)
> If you think the (rightful) removal of a hardly used feature[1] that has some big problems is a blocking issue then I feel sorry for you.

Uh, thanks?

I would call it anything but "rightful". Making life harder for introspection tools is hardly a rightful reason for removing a core language feature. The code is what most developers are trying to develop, not the introspection tools.

Re:Python 3.5.0 by orf on Monday September 14, 2015 @04:03AM (#10214036)
> Making life harder for introspection tools is hardly a rightful reason for removing a core language feature

Well that's one reason yes, and by itself not really a good enough one. But if you read the PEP there are another 4 good reasons that you omitted from your comment, why is that?

Re:Python 3.5.0 by wfunction on Monday September 14, 2015 @04:23AM (#10214086)
> Well that's one reason yes, and by itself not really a good enough one. But if you read the PEP there are another 4 good reasons that you omitted from your comment, why is that?

Because the other reasons were twice as horrible.

"No loss of abilities"? Uh, you can't do this in lambdas anymore.

"Exception to the rule"? Who cares? It was useful and readable, that's all that matters.

"Uninformative Error Messages"? This has never been a pain point for me. If you don't like it then no one forced you to use it...

"Little Usage"? Well I guess everyone matters but me. Which is fine, but then you shouldn't wonder why it would tick me off.