On Nov 19, 2013, at 18:42 , Ryan Schmidt <ryandes...@macports.org> wrote:
> > On Nov 19, 2013, at 07:07, Joshua Root wrote: > >> On 2013-11-19 23:52 , Peter Danecek wrote: >>> >>> if I interpret things correctly, the `http://` requests to PyPi are (now?) >>> redirected to `https://` requests. Not sure if this was always the case, >>> but I have a weak memory, that I was advised to uses `http` instead of >>> `https`, not sure though. >>> >>> Now I am wondering if I should update to https, to avoid the redirect. >> >> Yes, that changed not so long ago. Yes, go ahead and update pypi URLs to >> https if you notice them while working on a port. It's not a big problem >> so I wouldn't go out of my way to fix it when there are more important >> things to do. > > But this kind of upstream hosting change is indeed the reason why we put > service URLs in mirror_sites.tcl instead of hardcoding them into each > portfile, and this would be a good opportunity to do that for pypi. Well, adding PyPi into `mirror_sites.tcl` should be strait forward, so I could take care of this, but cannot commit. But it would be nice to be able to just specify master_sites PyPi:obspy instead of master_sites PyPi:o/obspy which would provide an even higher level of abstraction. But I understand this is not possible with the current implementation, right? ~petr
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
