Does PEP 440 cover this any better for you?
I actually think the example in PEP 440 are part of what caused my confusion, because all of them are also for *pip*: ``` pip @ file:///localbuilds/pip-1.3.1.zip pip @ file:///localbuilds/pip-1.3.1-py33-none-any.whl pip @ https://github.com/pypa/pip/archive/1.3.1.zip#sha1=da9234ee9982d4bbb3c72346a... pip @ git+https://github.com/pypa/pip.git@7921be1537eac1e97bc40179a57f0349c2aee67d pip @ git+https://github.com/pypa/pip.git@1.3.1#7921be1537eac1e97bc40179a57f0349c2aee6... ```
We could add further clarifying examples
Yes please!
I don't think anyone had considered that by using pip as the example of the project name, readers might assume that was the installer rather than the project, so changing that example may be reasonable.
This about sums up the roadblock I hit.
but the PEPs are intended to be definitions rather than tutorials
(I think) I understand that PEPs are meant for a technical discussion, but they should be also verbose enough to allow the proposal to be implemented. I read the PEP and tried to implement it, but failed. My hope if that those that follow after me will be more successful.
more explanatory information may be better handled as part of the packaging user guide at https://packaging.python.org/.
I think this is a good idea as well, as I could find any part of the documentation there that dealt with this. I would offer to write that myself, but I feel like I'm operating just at (or past!) the limits of my understanding here. Thanks for you help thus far.