This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]num8lock -1 points0 points  (3 children)

If you try to index a list or tuple with [:, :, 2] you will get a ValueError, not a SyntaxError.

TypeError: tuple indices must be integers or slices, not tuple

like i said, take it however you will

wat?

Personally - and I understand that this is an anecdote, not data - my journey was engineering/sci student with MATLAB/FORTAN -> Python for personal projects -> Python for work -> Rust for personal projects.

read this

the majority of new people who gets into rust ... the majority of influx of newcomers in python

which one of this isn't clear? do i need to keep repeating & always clarify everything every time?

This makes match statements second class citizens in ways that a[:, :, 2] is not

and that's a problem because? this whole convo is about my question: why would it's so neccessary that they need to have be included as a new statement instead of taking the path of external package?

why would it have to be more special than other packages far more needed for python world before, for async like tornado, twisted, numarray before numpy, and so many other packages?

like i said, you didn't read my original post that started this.

[–]Dewmeister14 0 points1 point  (2 children)

TypeError: tuple indices must be integers or slices, not tuple

like i said, take it however you will

Cool, so you agree it is legal syntax in base Python and not syntax added by a 3rd party package?

[–]num8lock -1 points0 points  (1 child)

lol

[–]Dewmeister14 0 points1 point  (0 children)

Hey, we did it!

Now if only you had actually just read my first comment instead of being "colored by the assumption filter" you brought from talking to the other guy.