incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <bloodhound-...@incubator.apache.org>
Subject Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Date Tue, 27 Nov 2012 15:54:45 GMT
#161: Install fails when trac-hacks is down
------------------------+-----------------------
  Reporter:  jdreimann  |      Owner:  gjm
      Type:  defect     |     Status:  closed
  Priority:  critical   |  Milestone:  Release 3
 Component:  installer  |    Version:
Resolution:  fixed      |   Keywords:
------------------------+-----------------------

Comment (by olemis):

 jftr

 Replying to [comment:14 rjollos]:
 [...]
 > This had me thinking as to whether the older eggs would be retained on
 PyPI, and even if they aren't, setuptools will probably just go out and
 grab the latest version from PyPI, right? I wasn't sure if this had been
 given much thought already, and whether we might want more explicit
 control over the version being installed.

 Files uploaded to PyPI will remain there for a while ;) . There should be
 a way in requirements file to make pip install a particular version from
 PyPI.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:16>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

Mime
View raw message