Re: use of setuptools in SetupTools.py
Tavis Rudd <[email protected]>
| Newsgroups | gmane.comp.python.cheetah |
|---|---|
| Message-ID | <[email protected]> |
Tyler, I'd like to maintain some way to turn off the use of setup tools, other than removing it from the PYTHONPATH. Perhaps an env var 'CHEETAH_INSTALL_WITHOUT_SETUPTOOLS'? Tavis On Tue, 9 Jun 2009, R. Tyler Ballance wrote: > On Fri, Jun 05, 2009 at 02:04:53PM -0400, Mike Bonnet wrote: >> I was curious about this comment in SetupTools.py >> >> if 'CHEETAH_USE_SETUPTOOLS' in os.environ: >> # @@TR: Please note that this is for testing purposes only! PEAK setuptools >> # is not required or recommended for installing Cheetah. Downstream >> # package managers (linux distros, etc.) should *not* enable this. >> >> Several python frameworks (TurboGears for one) that use Cheetah require the egg-info metadata that setuptools generates, so we define CHEETAH_USE_SETUPTOOLS in the Fedora package for Cheetah. I just wanted to verify that this is a supported installation method, and that future upgrades aren't likely to break it. >> >> Thoughts? > > In the next branch, what will become v2.2.2 I went ahead and removed > that cnoditional and have the try/except defaulted such that setup.py > will use setuptools if available, otherwise fall back to distutil (see: > b9bfe53). > > The maintainer of the Debian Cheetah package also mentioned some bits to > me about setuptools off-list so I think it's safe to say that most Linux > package maintainers are fine with setuptools these days :) > > > Cheers > -- > -R. Tyler Ballance > Slide, Inc. > ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects