This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Add download_url to setup()
Type: Stage:
Components: Distutils Versions: Python 2.3
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: akuchling Nosy List: akuchling, richard, theller
Priority: normal Keywords: patch

Created on 2003-02-10 14:58 by akuchling, last changed 2022-04-10 16:06 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
download_url.patch akuchling, 2003-02-10 15:00
Messages (8)
msg42790 - (view) Author: A.M. Kuchling (akuchling) * (Python committer) Date: 2003-02-10 14:58
For a Python package installer, it would be a good idea to provide a "download URL" metadata keyword in the next release of Python. 
msg42791 - (view) Author: A.M. Kuchling (akuchling) * (Python committer) Date: 2003-02-10 15:00
Logged In: YES 
user_id=11375

The attached patch implements the new metadata keyword.

Open question: if a value isn't provided, the PKG-INFO file 
will contain the line "Download-URL: UNKNOWN".  Should the line 
simply be omitted in this case?

There should be an updated metadata PEP; I'm not sure if PEP 241 should be edited or what, but will ask the relevant people.
msg42792 - (view) Author: Thomas Heller (theller) * (Python committer) Date: 2003-02-10 15:34
Logged In: YES 
user_id=11105

What will this line contain, if there are several download
URLs possible (zip, tar.gz, multiple exe fir different
Python versions?)

Will it work with redirects a la Sourceforge?
msg42793 - (view) Author: Richard Jones (richard) * (Python committer) Date: 2003-02-10 22:56
Logged In: YES 
user_id=6405

IMO The line should be omitted. 
 
The patch doesn't touch the register command source - could that be done 
too? Perhaps the dict generation should be moved off to the 
DistributionMetadata class instead? 
 
msg42794 - (view) Author: Richard Jones (richard) * (Python committer) Date: 2003-02-11 00:03
Logged In: YES 
user_id=6405

Sorry, I was responding to the question "Should 
the line simply be omitted in this case"? 
 
I was also entirely vague about the "dict generation" bit too. I was referring 
to the build_post_data method in the register command source. 
 
In response to the multiple downloads question, I believe this is an open 
question still (as to whether multiple download sources are to be allowed). 
PyPI currently allows a single download URL, but since it's still in "test" 
mode, I could easily change that. 
 
Sourceforge doesn't auto-redirect if there's no session cookie present. 
 
msg42795 - (view) Author: A.M. Kuchling (akuchling) * (Python committer) Date: 2003-02-19 14:10
Logged In: YES 
user_id=11375

So should download_url be omitted from the POST data, or included with a value of UNKNOWN?
msg42796 - (view) Author: A.M. Kuchling (akuchling) * (Python committer) Date: 2003-02-19 14:28
Logged In: YES 
user_id=11375

The changes to core.py and dist.py are checked in, but register.py still needs to be updated.
msg42797 - (view) Author: A.M. Kuchling (akuchling) * (Python committer) Date: 2003-02-19 14:37
Logged In: YES 
user_id=11375

Rev. 1.4 of register.py includes the download_url data in the POST; it will be UNKNOWN if not supplied.  Richard, just re-open this bug if you want it to be different (suppressing it completely or whatever).
History
Date User Action Args
2022-04-10 16:06:42adminsetgithub: 37955
2003-02-10 14:58:32akuchlingcreate