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 belopolsky
Recipients amaury.forgeotdarc, belopolsky, jnferguson
Date 2008-04-09.18:31:05
SpamBayes Score 0.10877401
Marked as misclassified No
Message-id <d38f5330804091124o1ef4bedfu4ed0f281bb49e158@mail.gmail.com>
In-reply-to <1207761650.84.0.750061039779.issue2587@psf.upfronthosting.co.za>
Content
On Wed, Apr 9, 2008 at 1:20 PM, Justin Ferguson <report@bugs.python.org> wrote:
..
>  Do I need to create proof of concepts for each of these bugs, or can I
>  reference this ticket?
>

It would be best if you could provide a patch complete with additional
unit tests that fail in (or crash) unpatched python and demonstrate
the bugs.  Since the fixes are likely to be one-line changes, I would
say there is no need to create separate issues.  Just post a patch
here for а review.

From your other post, I understand that you are doing a security audit
of the python codebase.  Is this a manual effort (identifying unsafe
constructs and searching for them) or you use some kind of automation?
History
Date User Action Args
2008-04-09 18:31:08belopolskysetspambayes_score: 0.108774 -> 0.10877401
recipients: + belopolsky, amaury.forgeotdarc, jnferguson
2008-04-09 18:31:07belopolskylinkissue2587 messages
2008-04-09 18:31:05belopolskycreate