We'd really like to see authenticated HTTP as well. In our case we have eggs which are not publicly available, but would like to distribute them to our customers.

Bryce

David Smith wrote: 
"Phillip J. Eby" <pje@telecommunity.com> writes:

  
At 03:12 PM 12/28/2006 +0900, David Smith wrote:
    
The usecase is too obvious: using setuptools for
distribution of modules that are not publically available, such
as commercial or pre-release development.
      
If they're not publically available, why use authenticated HTTP
at all?  Among the many alternatives that work with
easy_install today are:

* rsync-mirrored directories
* NFS-mounted directories
* ssh-transport SVN servers (you even get prompted for your credentials!)
* proxied HTTP
    

I believe HTTP authenticated subversion is more common than all
of the above. Additionally, the proxied HTTP support also lacks
authentication support, which the patch rectifies.

  
It seems to me that the only case where HTTP auth helps is if
you were already distributing your files that way.
    

I think you'd agree that HTTP is by far the most standard
distribution method than any of the others currently supported
by setuptools. We're really not talking about a special case.

  
In other words, you don't need to have this patch accepted in
order to integrate the functionality with the existing system.
    

I admit it's easy enough to fix locally; that's what I had been
doing. The problem I have with that is it's not a special case
and if you support ssl-encrypted HTTP, you should also support
HTTP authentication considering how the two are often used
together.

Thanks,
  

_______________________________________________
Distutils-SIG maillist  -  Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig