Live data from Hacker News

Python bug: Can assign [] = (), but not () = []

bugs.python.org

51–53 of 53 posts

Re: Python bug: Can assign [] = (), but not () = []

#51

Post by adregan » Thu, May 28, 2015, 12:51 AM UTC

arjn wrote: post #50

ronbeltran wrote: post #10

I can also do this, which is harmful. >>> True = False >>> False = True

Waaa! ... I just did that using 2.7 idle and it worked. This is new for me. I got stuck for a while trying to back out. Finally figured the way to reverse is to use del(): del(True) del(False).

You could also do True = True == True. It's like Dorothy clicking her heels together three times.

Re: Python bug: Can assign [] = (), but not () = []

#52

Post by bpicolo » Thu, May 28, 2015, 3:43 AM UTC

squigs25 wrote: post #41

() is not a tuple. (a,b) is a tuple or (a,) would also be a tuple.

It's an empty tuple.

stuff = ()

print(type(stuff))

Re: Python bug: Can assign [] = (), but not () = []

#53

Post by sparaker » Thu, May 28, 2015, 6:40 AM UTC

This is what i see in javascript:

[] = (); VM105:2 Uncaught ReferenceError: Invalid left-hand side in assignment

() = []; VM114:2 Uncaught SyntaxError: Unexpected token )

Post reply on HN