Change in paths to packages on PyPI

Rainer Müller raimue at
Tue Apr 26 10:28:23 PDT 2016

On 2016-04-23 13:04, Davide Liessi wrote:
> There has been a recent update in the way PyPI handles paths to
> packages [1] that will require to manually update master_sites for
> every update (fortunately old paths seem to be still valid).
> There's already an issue at PyPA's tracker [2], but I don't know if
> they'll be willing to revert the change.
> (Maybe voting the issue on the tracker would help...)

According to the upstream issue tracker, they now provide a translator
from the old URL scheme to the new at their pre-release version at

I did not do much testing, so I would be glad if someone could give the
attached patch some more testing, especially if this breaks fetching any
of the old ports.

Also a quick grep returned quite a lot of ports not using the pypi:
mirror sites, but instead hardcode Although it still
works, they should probably all be changed to allow control of the
mirrors at a single place.

-------------- next part --------------
Index: _resources/port1.0/fetch/mirror_sites.tcl
--- _resources/port1.0/fetch/mirror_sites.tcl	(revision 148039)
+++ _resources/port1.0/fetch/mirror_sites.tcl	(working copy)
@@ -401,7 +401,7 @@
 # port name) so just use a basic form here and fake it in ports that need
 # to use this.
 set portfetch::mirror_sites::sites(pypi) {
 set portfetch::mirror_sites::sites(ruby) {

More information about the macports-dev mailing list