Well you know my preferences is for github ;). I don't mind much either way though since its a simple repo I rarely need to interact with. The main benefit would be consistency with most of the other pypa things. 

I'm +1 on adding a bug tracker link. Maybe peps should support a header for it similar to discussions-to


On Dec 23, 2014, at 6:42 AM, Nick Coghlan <ncoghlan@gmail.com> wrote:


On 23 Dec 2014 19:02, "Donald Stufft" <donald@stufft.io> wrote:
>
>
>> On Dec 23, 2014, at 1:03 AM, Marcus Smith <qwcode@gmail.com> wrote:
>>
>> oh, "A compatible release clause consists of either a version identifier without any comparison operator or else the compatible release operator ~="
>>
>> On Mon, Dec 22, 2014 at 9:57 PM, Marcus Smith <qwcode@gmail.com> wrote:
>>>
>>> the first 3 examples here are confusing.
>>> https://www.python.org/dev/peps/pep-0440/#examples
>>>
>>> there's no comparison operator?
>>
>>
>> _______________________________________________
>> Distutils-SIG maillist  -  Distutils-SIG@python.org
>> https://mail.python.org/mailman/listinfo/distutils-sig
>
> Heh, that’s actually a hold over from before we made specifiers mandatory. That needs updated.

Should we add a reference to the metadata issue tracker to the PEPs themselves? That's a better home for bug reports than the mailing list (Note I'm also happy to move the repo for metadata drafts to GitHub if folks would prefer that - it's a pretty simple repo, so git-hg bridges should handle the conversion easily. The issue migration would involve a bit more work, though).

Cheers,
Nick.

>
> ---
> Donald Stufft
> PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
>
>
> _______________________________________________
> Distutils-SIG maillist  -  Distutils-SIG@python.org
> https://mail.python.org/mailman/listinfo/distutils-sig
>