This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author brett.cannon
Recipients barry, benjamin.peterson, brett.cannon, exarkun, ncoghlan, pitrou
Date 2008-09-10.02:35:49
SpamBayes Score 1.1769068e-05
Marked as misclassified No
Message-id <bbaeab100809091935m5bb0c5c6v292cf71903f11086@mail.gmail.com>
In-reply-to <1220998419.01.0.404839265269.issue3781@psf.upfronthosting.co.za>
Content
On Tue, Sep 9, 2008 at 3:13 PM, Nick Coghlan <report@bugs.python.org> wrote:
>
> Nick Coghlan <ncoghlan@gmail.com> added the comment:
>
> No worries - the only reason I suggested full reversion at all is
> because I had temporarily forgotten why the relocation had become so
> necessary (i.e. we needed the feature ourselves in the main part of the
> standard library to avoid emitting spurious warnings).
>
> J.P.'s suggestion (basic functionality in warnings, with each group of
> users providing their own convenience API tailored to their own use
> cases) makes an awful lot of sense, which is why it is the model I am
> going to adopt.
>

Adopt how? As in just provide a context manager that copies and
restores the filter? That might be enough and then let test.support
have a subclass or another context manager that plugs in the whole
showwarning() implementation. Then everyone should be happy.
History
Date User Action Args
2008-09-10 02:35:50brett.cannonsetrecipients: + brett.cannon, barry, exarkun, ncoghlan, pitrou, benjamin.peterson
2008-09-10 02:35:49brett.cannonlinkissue3781 messages
2008-09-10 02:35:49brett.cannoncreate