Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Maybe Guido doesn't like it because it looks weird when compared to the rest of Python's syntax? Still, I think it's cool. Having sets availably without importing anything is one of the things I love about Python.

set = <> is still available.



set = <> is still available

Did this get misformatted? I don't know what you mean.


I believe sciencerobot is saying that "<>" could be used as the empty set literal.


Oh I see, thanks. "s=<>" is less ugly than "s={@}" but, obviously, is inconsistent with "s={1, 2, 3}".


Then fix that: s = <1,2,3>

I think that's better than using the same brace-type for sets and dicts anyway, and it can't be as confusing as () == tuple(), (x) == x, (x,) == tuple([x]).


Yes, that was the idea. I don't think it would be confusing to the parser.


set = <> looks like the other empty container literals, but it's not consistent with the literal notation for sets with one or more elements: my_set = {1,2,3}.


What about supporting <1, 2, 3> as well, and eventually deprecating the existing way? The end result would be much nicer.


you don't import sets , set() is available right away.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: