Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Ticket #25 (closed defect: wontfix)

Opened 14 years ago

Last modified 10 years ago

EasyInstall "find links" needs to be inheritable

Reported by: kevin Owned by: anonymous
Priority: normal Milestone:
Component: Installation Version:
Severity: normal Keywords:
Cc:

Description (last modified by kevin) (diff)

A couple of messages from Ian Bicking and Phillip Eby describe the problem, and the solution:

------- Original Message --------
Subject: Re: [Distutils] easy_install, find-links, etc
Date: Tue, 04 Oct 2005 12:18:19 -0400
From: Phillip J. Eby <pje@telecommunity.com>
To: Ian Bicking <ianb@colorstudy.com>,  Python Distutils
<distutils-sig@python.org>

At 11:08 AM 10/4/2005 -0500, Ian Bicking wrote:
>The whole find-links thing is getting confusing -- right now each system
>has to give its own set of find-links, and they aren't well inherited.
>So, for instance, if Paste has some custom packages on an index page,
>you can't just require Paste -- you have to require Paste plus put
>whatever find-links settings are needed.
>
>What would be mightily useful is if you could at least advise -- from
>within a package -- on places to find some of the requirements for that
>package.  E.g., .egg-info/find_links.txt.  I think it is inevitable that
>packages will require custom builds, and we can't always push those
>changes into PyPI or track those changes in aggregate package indexes.

Patches to implement this gratefully accepted. :) Please include:

  • argument handler entry point to allow them to be specified as a setup() keyword (I suggest "dependency_links")
  • documentation in setuptools.txt for the keyword
  • a metadata writer entry point to write the file (you might be able to reuse one of the existing entry points
  • code in easy_install's process_distribution() function to read and process the metadata before doing dependency processing

Thanks. :)

Change History

comment:1 Changed 14 years ago by kevin

  • Description modified (diff)

comment:2 Changed 13 years ago by ianb@…

See #421 for a more expedient solution that applies just to TurboGears

comment:3 Changed 13 years ago by max

  • Milestone set to __future__

comment:4 Changed 13 years ago by ianb

setuptools has a dependency_links argument in setup() now... does that satisfy this bug?

comment:5 Changed 11 years ago by Chris Arndt

  • Status changed from new to closed
  • Resolution set to wontfix

I don't see what TurboGears can do in this respect. I don't think patching up tgsetup.yp to work around easy_install's flaw would be a good idea.

Anyway, the workaround, which we implement is to have all the rquirements TurboGears needs on our own download page. We need to do this anyway, if we want to provide binary eggs for packages, which don't host them themselves.

comment:6 Changed 10 years ago by anonymous

  • Milestone __future__ deleted

Milestone future deleted

Note: See TracTickets for help on using tickets.