Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How agressively should we hunt source of pypi.io -> pypi.org 301 and pypi.org -> files.pythonhosted.org 301 redirect. #176

Open
Carreau opened this issue Oct 28, 2024 · 0 comments

Comments

@Carreau
Copy link

Carreau commented Oct 28, 2024

I recently realized that many of the conda-forge recipe point to pypi.io, and that

https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/{{ name }}-{{ version }}.{{ ext}}
  1. Redirect to https://pypi.org/... which itself
  2. Redirect to https://files.pythonhosted.org/...

2 questions:

  • How much should we work on not having links to pypi.io ? That is to say how aggressively should we update recipes to point to pypi.org, or emit errors/warning message.
  • same for pypi.org, if we can directly update code to reach for https://files.pythonhosted.org/... url, how aggressively should we try to do it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant