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 larry
Recipients belopolsky, brett.cannon, eric.smith, gregory.p.smith, larry, nnorwitz, pitrou
Date 2009-10-29.22:55:08
SpamBayes Score 5.9893966e-05
Marked as misclassified No
Message-id <1256856910.86.0.704148422535.issue5872@psf.upfronthosting.co.za>
In-reply-to
Content
Antoine: As the patch matured I would obviously provide documentation
and examples and such.  The point of submitting the patch in this form
was a) so it was alive somewhere besides my hard drive, and b) to get
some public review from the core team to ensure I was going in a valid
direction.

As for mandatory vs purity: The whole purpose of the patch was to make
PyTypeObject a private type; see "THE PROBLEM" / "THE SOLUTION".  This
requires that all the public interfaces take pointers.  So within the
context of what the patch is trying to accomplish, it's mandatory.

The patch attempts to mitigate this as much as possible with the
backwards-compatibility 

p.s. By "huge" I suspect you mean "large", though on first reading I
thought you meant "fabulous".  That's what I get for working with a big
crew of 20-somethings.

p.p.s. Did this patch get mentioned recently or something?  After months
of inactivity, there have been two nosy+ this week.

p.p.p.s. I have not touched this patch since submitting it.  The
tribulations of working at a startup.
History
Date User Action Args
2009-10-29 22:55:11larrysetrecipients: + larry, nnorwitz, brett.cannon, gregory.p.smith, belopolsky, pitrou, eric.smith
2009-10-29 22:55:10larrysetmessageid: <1256856910.86.0.704148422535.issue5872@psf.upfronthosting.co.za>
2009-10-29 22:55:09larrylinkissue5872 messages
2009-10-29 22:55:08larrycreate