[Catalog-sig] HTTPS now promoted on PyPI

[Donald Stufft]

On Tuesday, February 19, 2013 at 5:05 PM, PJ Eby wrote:
> On Tue, Feb 19, 2013 at 12:13 AM, Richard Jones <r1chardj0n3s at gmail.com (mailto:r1chardj0n3s at gmail.com)> wrote:
> > 2. incorporate some monkey-patching into distribute and setuptools and
> > promote those,
> > 
> 
> 
> This is actually on my radar to do for setuptools, as soon as the dust
> has settled enough on what it is the monkey-patching needs to *do*.
> ;-)
> 
> So far I know I'll be changing the default URLs and adding cert
> verification, but I haven't looked at the register or upload stuff
> yet. The part where people are saying https isn't working right now
> is a big red flag for me, however; I don't want to push out an update
> that'll just make the load situation worse.
> 
> 

This was likely just the stud being overwhelmed with all the PyPI
traffic running through it. I believe that's getting fixed soon.
> 
> In the meantime I'll be investigating and testing, of course. (One
> annoying issue presently under investigation: determining whether
> including a cacert bundle means setuptools' license terms will have to
> change. Pip used LGPL, which appears to be compatible with the MPL.
> I personally don't think certs should be copyrightable in the first
> place, but some jurisdictions have compilation copyright of otherwise
> non-copyrightable individual elements. Presumably, Mozilla's not
> going to be a jerk about things, but... bleah. Licensing issues
> *suck*.)
> _______________________________________________
> Catalog-SIG mailing list
> Catalog-SIG at python.org (mailto:Catalog-SIG at python.org)
> http://mail.python.org/mailman/listinfo/catalog-sig
> 
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/catalog-sig/attachments/20130219/a40d4190/attachment-0001.html>