[issue24876] distutils.errors not wildcard-import-safe

[Éric Araujo]

Éric Araujo  added the comment:

The docstring is wrong, but I don’t think there is much value in changing it 
now.  Style guides generally recommend against star imports, and not many 
people need to import from distutils.errors (setuptools and maybe numpy?).

--
nosy: +jaraco
resolution:  -> wont fix
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24876] distutils.errors not wildcard-import-safe

[Jakub Wilk]

New submission from Jakub Wilk:

Docstring of the distutils.errors module reads:

This module is safe to use in from ... import * mode; it only exports
symbols whose names start with Distutils and end with Error.

But in reality, the module exports also names that don't start with Distutils:

 ns = {}
 exec('from distutils.errors import *', {}, ns)
 [k for k in ns.keys() if not k.startswith('Distutils')]
['LibError', 'UnknownFileError', 'LinkError', 'CompileError', 'CCompilerError', 
'PreprocessError']

--
components: Distutils
messages: 248680
nosy: dstufft, eric.araujo, jwilk
priority: normal
severity: normal
status: open
title: distutils.errors not wildcard-import-safe

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24876
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com