[Distutils] RFC: PEP243: Module Repository Upload Mechanism

[Amos Latteier]

Sean Reifschneider wrote:
> 
> Included below is the version of PEP243 after it's initial round of review.
> I welcome any feedback.

Looks good! I have a just few more comments.

>     The upload will be made to the host "modules.python.org" on port
>     80/tcp (POST http://modules.python.org:80/swalowpost.cgi).  The form
>     will consist of the following fields:
> 
>         distmd5sum -- The MD5 hash of the uploaded distribution,
>         encoded in ASCII representing the hexadecimal representation
>         of the digest ("for byte in digest: s = s + ('%02x' %
>         ord(byte))").

How necessary is this? How likely is file corruption over HTTP? 

>         protocol_version -- A string indicating the protocol version that
>         the client supports.  This document describes protocol version "1".

Couldn't this be handled by defining new endpoints for new protocols.
When we rev this protocol just change the upload URL.
 
> Return Data
> 
>     The status of the upload will be reported using HTTP non-standard
>     ("X-*)" headers.  The "X-Swalow-Status" header may have the following
>     values:
>         TRYAGAIN -- The server is unable to accept the upload at this
>         time, but the client should try again at a later time.
>         Potential causes of this are resource shortages on the server,
>         administrative down-time, etc...
 
How should the distutils handle this response? My guess is that it would
be impractical for the distutils to automatically wait a while and
retry. Probably it's better to not try and automate this. Let's keep
things simple to start with.

-Amos

--
Amos Latteier         mailto:amos@digicool.com
Digital Creations     http://www.digicool.com