On 4/5/07, Robert Kern [EMAIL PROTECTED] wrote:
Oh, you're requiring setuptools now? I didn't notice that. Cool.
I'd point them here for up-to-date instructions and downloads:
http://cheeseshop.python.org/pypi/setuptools
Thanks Robert for the insight! I updated the installation
On Thursday 05 April 2007 4:29:00 am Edin Salkovic wrote:
On 3/3/07, John Hunter [EMAIL PROTECTED] wrote:
On 2/23/07, Andrew Straw [EMAIL PROTECTED] wrote:
I figured I would be a good crash test dummy to see how easy
it was to install setuptools, so I poked around and found the ez_setup
On Thursday 05 April 2007 06:44:36 am Edin Salkovic wrote:
On 4/5/07, Darren Dale [EMAIL PROTECTED] wrote:
I considered this when setuptools became a requirement for python-2.3
installs, but decided against it. My reasoning was that the unfamiliar
user would go to install matplotlib, and
On 4/5/07, Edin Salkovic [EMAIL PROTECTED] wrote:
This would make installing setuptools even easier, since the newest
ez_setup/seuptools would be downloaded by the user/developer every
time a svn update;python setup.py install is issued.
Are the above changes OK?
I'm not sure I see the
On 4/5/07, Robert Kern [EMAIL PROTECTED] wrote:
The purpose of ez_setup.py was to give people a migration path such that they
could write project that used setuptools, but ensure that their users wouldn't
have to go install another package themselves.
It's deprecated now. Don't use it.
So
John Hunter wrote:
On 4/5/07, Robert Kern [EMAIL PROTECTED] wrote:
The purpose of ez_setup.py was to give people a migration path such that they
could write project that used setuptools, but ensure that their users
wouldn't
have to go install another package themselves.
It's deprecated
Robert Kern wrote:
Oh, you're requiring setuptools now? I didn't notice that. Cool.
Just for Python 2.3 so that we could sanitize the setup.py a little.
(Namely for the backport of the package_data field to setup().) It's not
required for Python = 2.4 since package_data is already in stock
