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 nnorwitz
Recipients brett.cannon, christian.heimes, nnorwitz
Date 2008-04-02.02:31:15
SpamBayes Score 0.3635102
Marked as misclassified No
Message-id <ee2a432c0804011931kd17a109ie500930c52d8d070@mail.gmail.com>
In-reply-to <1207055676.43.0.961222308102.issue1631171@psf.upfronthosting.co.za>
Content
On Tue, Apr 1, 2008 at 6:14 AM, Brett Cannon <report@bugs.python.org> wrote:
>
>  Brett Cannon <brett@python.org> added the comment:
>
>  Neal's issues are addressed in this patch. I also finally filled out
>  warnings.h. The only thing that I didn't deal with is Neal's worry of
>  exposing _PyWarnings_Init(). It is not explicitly exported anywhere as
>  part of the API so I am not sure what he is worrying about.

I wasn't so worried about exposing it, I didn't like the name
pollution (we're talking about init_warnings, right?).  I know that we
have other modules that use init*, but those are broken too.  I'm not
sure we should fix those in 2.6, but 3.0 we should.
History
Date User Action Args
2008-04-02 02:31:18nnorwitzsetspambayes_score: 0.36351 -> 0.3635102
recipients: + nnorwitz, brett.cannon, christian.heimes
2008-04-02 02:31:16nnorwitzlinkissue1631171 messages
2008-04-02 02:31:15nnorwitzcreate