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 don't
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
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
Barry:
What is the download cache?
I have a guess. If you are installing with the setuptools install
command, then the things which are install_requires get installed
into some target location, but things which are build_requires get
installed into the PWD. (If you don't specify a
We have a suite of tools in the 'lazr' namespace that we've begun to
release as open source. All of these packages are maintained under
bzr and it's really nice to be able to add this to our setup.py:
setup_requires=['setuptools_bzr']
This extends setuptools so that we can use bzr instead
At 06:09 PM 6/22/2009 -0400, Barry Warsaw wrote:
We have a suite of tools in the 'lazr' namespace that we've begun to
release as open source. All of these packages are maintained under
bzr and it's really nice to be able to add this to our setup.py:
setup_requires=['setuptools_bzr']
This
