4 ms·

Maybe because PyPI has a closer relationship with Python than the other package managers have with their core tech?

nerdponx 7y ago
I don't see how that's relevant. Hosting your own Python package index isn't easier than hosting any other, as far as I'm aware.
- femto113 7y ago
  Less technical and more political. Python has a bureaucracy that can take let’s say “a while” to decide things. If GitHub approached them about this it wouldn’t surprise me if they’re still debating whether to condone it.
  - femto113 7y ago
    See for example this PEP suggesting they use GitHub issues for the CPython repo hosted on GitHub, opened a year ago https://www.python.org/dev/peps/pep-0581/ https://www.python.org/dev/peps/pep-0581/
  - takeda 7y ago
    There's nothing required from PSF to create own repo. I created one myself on S3, all you need is then just update pip.conf to use it. Pip also has functionality to support primary repo and a backup, so they don't need to make their repo a pass through to PyPI, pip basically can be configured to look up first the custom repo and if package is not found then fallback to PyPI. There's no technical or political obstacle here.
- laurencerowe 7y ago
  Hosting a Python package index is much simpler, just dump the files in a web accessible directory with a directory listing and specify it with `--find-links`. https://pip.pypa.io/en/stable/reference/pip_wheel/#find-links https://pip.pypa.io/en/stable/reference/pip_wheel/#find-link... You can also link directly to a package with `--find-links` if you specify an egg fragment, e.g. 'https://github.com/project/reponame/tarball/version#egg=packagename-version' https://github.com/project/reponame/tarball/version#egg=pack.... (The version must match that in setup.py.)
takeda 7y ago
PyPI has no closer relationship to Python than the other options to their respective language. Similarly to others PyPI also runs out of an http server. There really is nothing tied to Python.

I don't see how that's relevant. Hosting your own Python package index isn't easier than hosting any other, as far as I'm aware.

femto113 7y ago
Less technical and more political. Python has a bureaucracy that can take let’s say “a while” to decide things. If GitHub approached them about this it wouldn’t surprise me if they’re still debating whether to condone it.
- femto113 7y ago
  See for example this PEP suggesting they use GitHub issues for the CPython repo hosted on GitHub, opened a year ago https://www.python.org/dev/peps/pep-0581/ https://www.python.org/dev/peps/pep-0581/
- takeda 7y ago
  There's nothing required from PSF to create own repo. I created one myself on S3, all you need is then just update pip.conf to use it. Pip also has functionality to support primary repo and a backup, so they don't need to make their repo a pass through to PyPI, pip basically can be configured to look up first the custom repo and if package is not found then fallback to PyPI. There's no technical or political obstacle here.
laurencerowe 7y ago
Hosting a Python package index is much simpler, just dump the files in a web accessible directory with a directory listing and specify it with `--find-links`. https://pip.pypa.io/en/stable/reference/pip_wheel/#find-links https://pip.pypa.io/en/stable/reference/pip_wheel/#find-link... You can also link directly to a package with `--find-links` if you specify an egg fragment, e.g. 'https://github.com/project/reponame/tarball/version#egg=packagename-version' https://github.com/project/reponame/tarball/version#egg=pack.... (The version must match that in setup.py.)

takeda 7y ago

PyPI has no closer relationship to Python than the other options to their respective language. Similarly to others PyPI also runs out of an http server. There really is nothing tied to Python.