Re:Distributions vs. Releases: Why Python Packaging Is Hard
by alexbecker on Tuesday April 30, 2019 @08:49PM
(#19793502)
PyDist is specifically for Python packages, so it's 1) a better fit in this niche (for example, it mirrors PyPI so you can install public and private packages through a single index, and you won't be broken by packages deleted from PyPI), and 2) it's much cheaper if you don't need everything else Artifactory offers.
[ Parent
| on HN ]
Re:Distributions vs. Releases: Why Python Packaging Is Hard
by sl1ck731 on Tuesday April 30, 2019 @09:16PM
(#19793685)
I believe Artifactory proxies and caches PyPi as well via remote repos.
Re:Distributions vs. Releases: Why Python Packaging Is Hard
by alexbecker on Thursday May 02, 2019 @10:43AM
(#19808411)
Ah, looks like you can set that up. But it's not as convenient, because 1) you have to provision the remote repository and 2) instead of transparently installing from PyPI, you have to specify the remote repository each time you install from it.
Re:Distributions vs. Releases: Why Python Packaging Is Hard
by jbaruch_s on Monday May 06, 2019 @05:32PM
(#19844105)
It is exactly as convenient (if not more). You set up a set of 3 repositories (local for your modules, remove to proxy the PyPI, and virtual, which unifies them under a single URL (which solves the #2 you mentioned).
So, both points are incorrect.