Martin v. Löwis mar...@v.loewis.de added the comment:
With PEP 384, this is now obsolete, so closing it as such. If you think that
selected features of this patch should still be added, please submit them as
separate patches.
--
nosy: +loewis
resolution: - out of date
status: open -
Changes by Reid Kleckner r...@mit.edu:
--
nosy: +rnk
versions: +Python 3.2 -Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5872
___
___
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5872
___
___
Python-bugs-list mailing list
Changes by Gerhard Häring g...@ghaering.de:
--
nosy: +ghaering
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5872
___
___
Python-bugs-list mailing
Antoine Pitrou pit...@free.fr added the comment:
This patch is huge.
Some things:
- you should provide an example of using the new API. Your description
is not very, well, descriptive :)
- all PyTypeObjects must now be *pointers* rather than static
instances: is it mandatory, or did you add
Larry Hastings la...@hastings.org added the comment:
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
Larry Hastings la...@hastings.org added the comment:
Whoops! I think I'll finish that unfinished sentence.
The patch attempts to mitigate this as much as possible with the
backwards-compatibility
header file; it minimizes as much as possible the changes you need to
perform to get your code
Antoine Pitrou pit...@free.fr added the comment:
As the patch matured I would obviously provide documentation
and examples and such.
What I meant is that it's difficult for me (and perhaps others) to
assess how much more practical your patch makes it to create C types.
This
requires that
Changes by Alexander Belopolsky belopol...@users.sourceforge.net:
--
nosy: +belopolsky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5872
___
___
Changes by Gregory P. Smith g...@krypto.org:
--
nosy: +gregory.p.smith
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5872
___
___
Python-bugs-list
Changes by Eric Smith e...@trueblade.com:
--
nosy: +eric.smith
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5872
___
___
Python-bugs-list mailing
Eric Smith e...@trueblade.com added the comment:
I think this is great stuff, Larry. It's a definite improvement.
Unfortunately with my workload of other Python issues, I'm not going to
be able to review this before the 3.1 beta. I don't use many
PyTypeObject's, so my review would be mostly
New submission from Larry Hastings la...@hastings.org:
EXECUTIVE SUMMARY
I've written a patch against py3k trunk creating a new function-based
API for creating extension types in C. This allows PyTypeObject to
become a (mostly) private structure.
THE PROBLEM
Here's how you create an
Changes by Brett Cannon br...@python.org:
--
nosy: +brett.cannon
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5872
___
___
Python-bugs-list
14 matches
Mail list logo
