[Patches] [ python-Patches-1515609 ] Alternative fix for ImportWarning (fix for 1515169)

[SourceForge.net]

Patches item #1515609, was opened at 2006-07-01 11:05
Message generated for change (Settings changed) made by nnorwitz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1515609&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core (C code)
Group: Python 2.5
>Status: Closed
>Resolution: Rejected
Priority: 5
Submitted By: Sergey (sergeyli)
>Assigned to: Neal Norwitz (nnorwitz)
Summary: Alternative fix for ImportWarning (fix for 1515169)

Initial Comment:
Similarly to http://www.python.org/sf/1515361, tries to
change the way ImportWarning behaves. The difference
between tha patches is that this one does not try to
produce a full list of all possible directories that
have not been imported. Instead, this patch only
provides number of candidate directories found, and
prints the first one, which hopefully is the most
likely candidate. Full description follows.

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.

----------------------------------------------------------------------

>Comment By: Neal Norwitz (nnorwitz)
Date: 2006-07-05 21:24

Message:
Logged In: YES 
user_id=33168

Thank you for the patch.

The decision was made to simply ignore the warning by
default.  There's nothing necessarily wrong with this patch,
although I didn't review it.  I'm closing because we are
taking a different approach at this time.  We will revisit
the decision for 2.6.  I hope you continue reading
python-dev and help us fix this better for 2.6, whatever
that may be.  Perhaps this patch will be revived at that time.

I have added a link to this patch in PEP 361.

----------------------------------------------------------------------

Comment By: Sergey (sergeyli)
Date: 2006-07-01 11:11

Message:
Logged In: YES 
user_id=141494

This one also doesn't have the memory leak fix mentioned in
python.org/sf/1515361.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1515609&group_id=5470