A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-July/066910.html below:

[Python-Dev] ImportWarning flood

[Python-Dev] ImportWarning flood [Python-Dev] ImportWarning floodSergey A. Lipnevich sergey at optimaltec.com
Sat Jul 1 18:52:19 CEST 2006
All,

I tried to implement Jean-Paul Calderone's idea for the following patch,
plagiarizing Ralf W. Grosse-Kunstleve's error text. It delays import
warning until end of search for modules, but remembers how many
potential modules (candidates without __init__.py) it didn't import. I
didn't really try to analyze any conditions, instead I simply assumed
that wherever ImportWarning would be issued, we have a suitable
candidate, and saved it on the stack. If nothing is found, Python emits
ImportWarning right before ImportError, and explains what happened.
Please let me know if this would work and if anything needs to be done
for this patch to be accepted.
Thank you!

Sergey.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: import_warning.diff
Type: text/x-patch
Size: 1867 bytes
Desc: not available
Url : http://mail.python.org/pipermail/python-dev/attachments/20060701/94ab9c43/attachment-0001.bin 
More information about the Python-Dev mailing list

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