[Python-3000] PEP 3123 (Was: PEP Parade) (original) (raw)

Guido van Rossum guido at python.org
Sun May 13 21:15:47 CEST 2007

I'm okay with applying to 2.6 and then merging into 3.0. ISTM though that backporting this to 2.5 would cause the release manager to throw a fit, so I think that's not worth it. What would be the benefit anyway?

--Guido

On 5/13/07, "Martin v. Löwis" <martin at v.loewis.de> wrote:

> S 3123 Making PyObjectHEAD conform to standard C von Löwis > > I like it, but who's going to make the changes? Once those chnges have > been made, will it still be reasonable to expect to merge C code from > the (2.6) trunk into the 3.0 branch?

I just created bugs.python.org/1718153, which implements this PEP. I had to add a number of additional macros (PyRefcnt, PySize, PyVarObjectHEADINIT); using these macros throughout is the bulk of the change. If the macros are backported to 2.x (omitting the "hard" changes to PyObject itself), then the code base can stay the same between 2.x and 3.x (of course, backporting changes from 2.6 to 2.5 might become harder, as the chances for conflicts increase). As for statistics: there are ca. 580 uses of PyType in the code, 410 of PySize, and 20 of PyRefcnt. How should I proceed? The next natural step would be to change 2.6, and then wait until those changes get merged into 3k. Regards, Martin

-- --Guido van Rossum (home page: http://www.python.org/~guido/)

More information about the Python-3000 mailing list