At 05:02 PM 6/26/2009 -0400, Barry Warsaw wrote:
When you build an sdist using setuptools, it includes a pre-
generated file manifest, along with a setup.cfg that forces the
right revision tag information in the project's version number (if
applicable). This is specifically designed so that the
Hi Zooko,
On Jun 23, 2009, at 11:42 AM, Zooko Wilcox-O'Hearn wrote:
What is the download cache?
It's where buildout caches packages it downloads and it's very handy
because we can tell buildout to use a pre-defined download cache and
to never download anything from the intarwebs. Except
Sorry for the delay in responding and the lack of clarity in the
original message...
On Jun 22, 2009, at 11:40 PM, P.J. Eby wrote:
I don't know what the "download cache" is, so I can't speak to
that. However, what I can say is that if you're using "sdist" for
distribution, you probably do
David Kim wrote:
I am running the OS X EPD distribution, which uses Enstaller (built on
setuptools). Could this have something to do with it?
Sorry, but yes, this is exactly the problem. EPD comes with Enstaller
instead of setuptools, and thus there is no installed project called
'setuptool
Thanks Jim, I think you are correct. The result of the script you provided
returned 'None'. Unfortunately, I commented out the "try" code...
> #try:
#import pkg_resources
#except ImportError:
and left the "except" code...
ez = {}
exec urllib2.urlopen('http://peak.telecommunity.com/dist/e
On Jun 25, 2009, at 7:20 PM, David Kim wrote:
Sorry to ask, but I'm having with the first step of the buildout
process, the bootstrap.py script. I get the following error:
Traceback (most recent call last): File "bootstrap.py", line 76,
in
ws.find(pkg_resources.Requirement.parse('
