<p><br>
On Jan 14, 2012 5:56 PM, "Georg Brandl" <<a href="mailto:g.brandl@gmx.net">g.brandl@gmx.net</a>> wrote:<br>
><br>
> On 01/14/2012 07:53 AM, Nick Coghlan wrote:</p>
<p>> > I agree, but it's one of the challenges of a long-lived branch like<br>
> > the PEP 380 one (I believe some of these cosmetic changes started life<br>
> > in Greg's original patch and separating them out would have been quite<br>
> > a pain). Anyone that wants to see the gory details of the branch<br>
> > history can take a look at my bitbucket repo:<br>
> ><br>
> > <a href="https://bitbucket.org/ncoghlan/cpython_sandbox/changesets/tip/branch%28%22pep380%22%29">https://bitbucket.org/ncoghlan/cpython_sandbox/changesets/tip/branch%28%22pep380%22%29</a><br>
><br>
> I see. I hadn't followed the development of PEP 380 closely before.<br>
><br>
> In any case, it is probably a good idea to mention this branch URL in the<br>
> commit message in case it is meant to be kept permanently (it would also be<br>
> possible to put only that branch of your sandbox into another clone at<br>
> <a href="http://hg.python.org">hg.python.org</a>).</p>
<p>You're right we should have a PSF-controlled copy of the entire branch history in cases like this. I actually still keep an irregularly updated clone of my entire sandbox repo on <a href="http://hg.python.org">hg.python.org</a> (that's actually where it started), so I'll refresh that and add a link to the pep380 branch history into the tracker item that covered the PEP 380 integration into 3.3.</p>
<p>> > (Vaguely related tangent: the new code added by the patch probably has<br>
> > a few parts that could benefit from the new GetAttrId private API)<br>
><br>
> Maybe another candidate for an issue, so that we don't forget?</p>
<p>I just added a note about it to the C API cleanup tracker item.</p>