[Distutils] RFC: PEP243: Module Repository Upload Mechanism

[Sean Reifschneider]

On Sat, Mar 24, 2001 at 06:34:20PM -0800, Amos Latteier wrote:
>How necessary is this? How likely is file corruption over HTTP? 

It's not that necessary, but it's easy enough to implement, so why not?
It can detect corruption and incomplete uploads, the latter being my bigger
concern.

>Couldn't this be handled by defining new endpoints for new protocols.
>When we rev this protocol just change the upload URL.

Yeah, but do we want to *HAVE* to change the endpoint?  Mostly I'm thinking
more of small changes as opposed to a complete re-writing.  Sure, some of
this may be able to be auto-detected (is the new field there?), but in
general I think it's a good thing for the server and client to be sure
they're talking the same language.

>How should the distutils handle this response? My guess is that it would
>be impractical for the distutils to automatically wait a while and

The idea is to differentiate between temporary failures (disc space not
available, server shut down for maintenance) versus something that will
*NEVER* work (say, because of a client code bug).  I don't expect that
distutils will auto-retry it, because those sorts of failures are likely to
require hours to work out.  As a user it would be nice to know that no
matter how many times I retry this over the next several days, that it will
never work...

Sean
-- 
 Linux:  When you need to run like a greased weasel.
                 -- Sean Reifschneider, 1998
Sean Reifschneider, Inimitably Superfluous <jafo@tummy.com>
tummy.com - Linux Consulting since 1995. Qmail, KRUD, Firewalls, Python