Could you please expand on which specific badges you're referring to (e.g. version vs. license vs. downloads vs. etc.)? Shields always has to reach out to some upstream API to get the required data needed for building a badge, and various badges, even those under the same "umbrella", use different APIs and sometimes even different API providers.

Thanks for you reply. For now the version badge is most used, it would be good if sheild can support self-hosted pypi repo!

I think it would be possible to do this for all the pypi badges except for downloads in a similar way to how we allow a registry_uri param for NPM.
One thing to note: If we added this feature to shields.io it would only be possible for the alternate pypi registry to be a public registry that does not require authentication. For a non-public registry you would have to host your own instance of shields in order to address it.

certainly, non-public registry cannot be reached from shields.io