Re: Small Issue installing Extremes with pip
"P.J. Eby" <pje-Wh6+Hckhi6HFNGf7iClzIwC/[email protected]> Wed, 26 Aug 2009 22:09:36 -0400
| Newsgroups | gmane.comp.python.peak |
|---|---|
| Message-ID | <[email protected]> |
The Extremes-1.1.1.zip on PyPI contains the necessary ez_setup code, so I don't understand what the problem is. If the problem occurs with pip but not easy_install, then it's a bug in pip, not in Extremes. (Extremes is only distributed as a sdist, so both easy_install and pip would be installing from the same source.) At 06:02 PM 8/26/2009 -0600, Jorge Vargas wrote: >Hi, > >This is still present on my builds :( it's getting more annoying as >every new project I need to put a hack around it again. > >On Thu, May 21, 2009 at 2:58 PM, Jorge Vargas<[email protected]> wrote: > > Hello Again, > > > > I don't remember when exactly but this issue resurfaced on my > installations. > > > > Do you think we can implement the try/catch strategy? this is so > > annoying right now that I'm building a workaround on my deployment > > script > > > > On Thu, Feb 5, 2009 at 1:17 PM, P.J. Eby <pje-Wh6+Hckhi6HFNGf7iClzIwC/[email protected]> wrote: > >> At 02:03 AM 2/5/2009 -0400, Jorge Vargas wrote: > >>> > >>> Hello, > >>> > >>> I'm writing to ask for a little patch against the Extremes package. > >>> Apparently when building from source Extremes assumes ez_setup is on > >>> the build environment. As shown here > >>> http://svn.eby-sarna.com/Extremes/setup.py?view=markup This together > >>> with the way pip installs things (using sdist) is causing the build of > >>> TurboGears to fail as reported here > >>> http://trac.turbogears.org/ticket/2169 > >>> > >>> The solution is really simple. All we need is a try/catch block around > >>> the ez_setup of the setup.py which will allow it to continue. if > >>> setuptools is present but ez_setup isn't. > >> > >> Actually, it's even simpler; I fixed it to actually include ez_setup as an > >> SVN external, the way it was supposed to be in the first place. ;-) > >> > >> Thanks for reporting the problem. > >> > >