RetroSearch Browse

Mon Apr 25 16:01:32 CEST 2011 · https://mail.python.org/pipermail/python-dev/2011-April/110918.html

> Because there's no reason to include them, since they are already in
> the root (builtins) namespace.
>
> You'll notice that in Python 3, the "types" module only contains types
> which are not obviously accessed through easier means:

OK, makes sense, but in this case it would be handy to have some list of all 
possible built-in types. I was just creating one and I nearly missed sets. If 
an entry in 'types' module is too much, there should be some comprehensive list 
in the documentation at least.

Regards,
Bartosz Tarnowski

---------------------------------------------
Ksiegowa radzi: Jak zaÅ‚ozyc firme w 15 minut?
http://linkint.pl/f2968

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-April/110918.html below:

[Python-Dev] Why are there no 'set' and 'frozenset' types in the 'types' module?