A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2002-July/026354.html below:

Type Names in the types Module

[Python-Dev] PEP 294: Type Names in the types Module [Python-Dev] PEP 294: Type Names in the types ModuleGuido van Rossum guido@python.org
Fri, 12 Jul 2002 12:15:02 -0400
> from new import function
> 
> # ...
> 
> if isinstance(obj, function):
>     # ...
> 
> It didn't look odd at all.  And I don't care much where I import
> function from.  I wouldn't mind if all the type objects defined in new
> where available in types.  IOW, the names exported by new could also
> be exported by types.

No, the docs for types.py promises that it only exports names ending
in 'Type'.  That's not a promise I want to break lightly.

> This means types would fall into two categories: types with builtin
> names and types available in the types module.  I expect the current
> set of types with builtin names is sufficient.

This is already the case, but the names exported by types.py don't
match the __name__ attribute of those types.  Is that a problem?

--Guido van Rossum (home page: http://www.python.org/~guido/)




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4