<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 23 March 2017 at 02:29, Thomas Güttler <span dir="ltr"><<a href="mailto:guettliml@thomas-guettler.de" target="_blank">guettliml@thomas-guettler.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> Wes Turner:<br>
> sourceURL: "git+ssh://<a href="http://git@github.com/pypa/pip@master" rel="noreferrer" target="_blank">git@github.com/pypa<wbr>/pip@master</a>"<br>
> sourceURL: "git+<a href="https://github.com/pypa/pip@master" rel="noreferrer" target="_blank">https://github.com/pypa/p<wbr>ip@master</a>"<br>
> Or, we could add "sourceURL" (pending bikeshedding on the property name) to the metadata 3.0 PEP.<br>
<br>
Why not?<br>
<br>
What is the next step to add sourceURL to the pep?<br></blockquote><div><br></div><div>I'm not adding any new metadata fields to the core metadata 3.0 proposal (I'm only removing them).<br><br>This means we're not going to be automating the process of getting an editable checkout in the core tools any time soon - there are already 100k+ published packages on PyPI, so anyone that seriously wants to do this is going to have to write their own client utility that attempts to infer it from the metadata that already exists (probably by building atop distlib, since that has all the necessary pieces to read the various metadata formats, both remote and local).<br><br></div><div>Future metadata extensions might help to make such a tool more reliable, but *requiring* metadata changes to be made first will just make it useless (since it wouldn't work at all until after publishers start publishing the new metadata, which would mean waiting years before it covered a reasonable percentage of PyPI).<br><br></div><div>Regards,<br></div><div>Nick.<br clear="all"></div></div><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Nick Coghlan | <a href="mailto:ncoghlan@gmail.com" target="_blank">ncoghlan@gmail.com</a> | Brisbane, Australia</div>
</div></div>