4 ms·
I only recently realized how easy it was to run your own PyPI - it just has to handle a few HTTP GET / POSTs. If you want to run your own PyPI internally, here
by steiza 14y ago
I only recently realized how easy it was to run your own PyPI - it just has to handle a few HTTP GET / POSTs.
If you want to run your own PyPI internally, here's a very simple PyPI server (~150 lines of Python) that I wrote:
https://github.com/steiza/simplepypi https://github.com/steiza/simplepypi
- tobych 14y agoWe're trying out DjangoPyPI 2 to host our own PyPI. Seems very actively maintained, and works a treat, despite it being still early days. http://djangopypi2.readthedocs.org/en/latest/ http://djangopypi2.readthedocs.org/en/latest/ For now though we'll probably just create a new git repo with a folder full of source distros (tarballs and zips), as mentioned above.
- po 14y agoAlso of interest is http://crate.io/ http://crate.io/ What I've personally been looking for is an easy to setup caching proxy for PyPI. Something that is pip-compatible and serves files if it has them but will also fetch and then store packages if it doesn't. That way you could build up a collection of 3rd party packages over time, without having to explicitly manage it. It probably wouldn't be hard to roll my own with a reverse proxy but it never gets moved to the front burner.
- rykov 14y agoGemfury also supports private Python packages