I'm still a little confused about keyword expansion for PEPs. Georg says
here:
http://mail.python.org/pipermail/python-committers/2011-March/001572.html
that he's enabled the extension "locally", but I don't quite understand if
that means he did it only in his copy of the repo, or on python.org.
Barry Warsaw wrote:
> I'm still a little confused about keyword expansion for PEPs. Georg says
> here:
>
> http://mail.python.org/pipermail/python-committers/2011-March/001572.html
>
> that he's enabled the extension "locally", but I don't quite understand if
> that means he did it only in his c
Am 05.04.2011 21:28, schrieb M.-A. Lemburg:
> Barry Warsaw wrote:
>> I'm still a little confused about keyword expansion for PEPs. Georg says
>> here:
>>
>> http://mail.python.org/pipermail/python-committers/2011-March/001572.html
>>
>> that he's enabled the extension "locally", but I don't quit
Am 05.04.2011 22:37, schrieb Georg Brandl:
> Am 05.04.2011 21:28, schrieb M.-A. Lemburg:
>> Barry Warsaw wrote:
>>> I'm still a little confused about keyword expansion for PEPs. Georg says
>>> here:
>>>
>>> http://mail.python.org/pipermail/python-committers/2011-March/001572.html
>>>
>>> that he
On Apr 05, 2011, at 10:37 PM, Georg Brandl wrote:
>>> Clearly,
>>> keywords are not getting expanded in the online version of the PEP:
>>>
>>> http://www.python.org/dev/peps/pep-0396/
>
>They seem to be now (but I don't know who or what changed).
But not correctly.
PEP:396
Title: Module V
> >Not sure why, especially not why it's like that for PEP 396, which only was
> >added after the switch and therefore the SVN link is broken.
> >
> >The website build is such a horrid twisty maze of hooks, suid binaries,
> >scripts, cronjobs and scripts again that I gave up trying to force a full