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

[shoyer]

As an occasional numpy contributor, I would call this a bug.

[p1mrx → shoyer]

Yes, the expected output is xx›

[thezilch → p1mrx]

  xxx›

[teddyh → thezilch]

xxxₓ

[pluma → teddyh]

xxxv, actually.

(it makes sense if you know why Roman numerals look the way they do)

[ngoldbaum → shoyer]

Good point - I found it after it caused a really weird bug in a library I use. I'll open an issue on github...

[ngoldbaum → ngoldbaum]

Turns out it's deprecated:

    >>> import warnings
    >>> warnings.simplefilter('always')
    >>> 'x'*np.float64(3.5)
    __main__:1: DeprecationWarning: using a non-integer number instead of an integer will result in an error in the future
    'xxx'

[im3w1l → ngoldbaum]

I get no such warning with 2.7.9 on linux.

[dalke → im3w1l]

It would be a warning from numpy, not Python. That comes from numpy/core/src/multiarray/conversion_utils.c and was added 2013-04-13 , which would be for NumPy 1.8, I believe.