On Sun, Oct 27, 2013 at 10:49 PM, Chris Jerdonek <chris.jerdo...@gmail.com>wrote:
> On Sun, Oct 27, 2013 at 12:04 PM, Chris Jerdonek > <chris.jerdo...@gmail.com> wrote: > > > > On Sun, Oct 27, 2013 at 10:44 AM, Donald Stufft <don...@stufft.io> > wrote: > >> > >> Here’s the list of dependency links for the projects that still use > them in their latest releases: > >> > >> https://gist.github.com/dstufft/7185162 > >> > >> A good number of them are either bogus, are pointing directly to PyPI, > or are file:// urls that are highly unlikely to exist on anyones computer > but the author’s. All in all there are 307 total unique links in this set > of packages, and 99 of them are not reachable from my computer > (requests.get(…) raises an exception). > > > > I actually know a couple people on this list. I can ask them and see if > the list can be reduced further. :) > > So I asked the person I know, and this is what he said, "Yes, we have > to use it! It's the only way to allow a package to install other > packages that aren't on PyPI-- for instance, a custom fork of a > library." > > Is there another approach or work-around he can be using? What is the > "right" way for him to do it? > > --Chris Note that some projects also use the dependency_links to point to development packages. See for example https://github.com/tangentlabs/django-oscar/blob/master/setup.py#L63 Although this approach doesn't always work reliably in my experience
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig