traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

ImportWarning is now silent by default

This commit is contained in:
Andrew M. Kuchling 2006-07-06 13:57:28 +00:00
parent 2d792254ae
commit beb572b50a
1 changed files with 5 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Doc/whatsnew/whatsnew25.tex
View File

@ -1170,19 +1170,12 @@ a line like this near the top of the source file:
to include an \file{__init__.py} module in a package directory. to include an \file{__init__.py} module in a package directory.
Debugging this mistake can be confusing, and usually requires running Debugging this mistake can be confusing, and usually requires running
Python with the \programopt{-v} switch to log all the paths searched. Python with the \programopt{-v} switch to log all the paths searched.
In Python 2.5, a new \exception{ImportWarning} warning is raised when In Python 2.5, a new \exception{ImportWarning} warning is triggered when
an import would have picked up a directory as a package but no an import would have picked up a directory as a package but no
\file{__init__.py} was found. (Implemented by Thomas Wouters.) \file{__init__.py} was found. This warning is silently ignored by default;
provide the \programopt{-Wd} option when running the Python executable
To suppress these warnings, you can either supply to display the warning message.
\code{\programopt{-W}'ignore:Not importing directory'} when running the Python (Implemented by Thomas Wouters.)
interpreter, or use the \module{warnings} module to suppress the
message:
\begin{verbatim}
warnings.filterwarnings('ignore', 'Not importing directory',
ImportWarning)
\end{verbatim}
\item The list of base classes in a class definition can now be empty. \item The list of base classes in a class definition can now be empty.
As an example, this is now legal: As an example, this is now legal: