Re: [Distutils] Draft of new setuptools installation instructions

2006-10-04 Thread Paul Moore
On 10/4/06, Phillip J. Eby [EMAIL PROTECTED] wrote: At 11:12 PM 10/3/2006 +0100, Paul Moore wrote: Also, the automatic pause would annoy me. How would you make it *not* happen if I ran the command from a console window I already had open? The idea would be to register a separate

Re: [Distutils] Draft of new setuptools installation instructions

2006-10-04 Thread Jim Fulton
Jim Fulton wrote: ... This will probably break buildout's bootstrapping script, which uses ez_setup. I was too hasty in making this remark. The buildout bootstrap script, http://svn.zope.org/zc.buildout/trunk/bootstrap/bootstrap.py?view=markup Uses the use_setup function from ez_setup.py

Re: [Distutils] Draft of new setuptools installation instructions

2006-10-04 Thread Jorge Vargas
On 10/3/06, Phillip J. Eby [EMAIL PROTECTED] wrote: At 10:43 PM 10/3/2006 +0100, Paul Moore wrote: On 10/3/06, Phillip J. Eby [EMAIL PROTECTED] wrote: Should we make more effort to create a usable command-line experience on Windows? Perhaps use a post-install script to register easy_install

Re: [Distutils] Draft of new setuptools installation instructions

2006-10-04 Thread Phillip J. Eby
At 09:23 AM 10/4/2006 +0100, Paul Moore wrote: On 10/4/06, Phillip J. Eby [EMAIL PROTECTED] wrote: At 11:12 PM 10/3/2006 +0100, Paul Moore wrote: Also, the automatic pause would annoy me. How would you make it *not* happen if I ran the command from a console window I already had open? The idea

Re: [Distutils] Draft of new setuptools installation instructions

2006-10-04 Thread Paul Moore
On 10/4/06, Phillip J. Eby [EMAIL PROTECTED] wrote: Ah crap. I wonder if there's any way to tell whether you're the only process on a particular console? That would fix this, I guess. There's a GetConsoleProcessList() API, but it doesn't even work on Win2K as far as I can tell; a minimum of

[Distutils] Draft of new setuptools installation instructions

2006-10-03 Thread Phillip J. Eby
I'm working on new installation instructions for setuptools 0.6c4, which will no longer use ez_setup.py for end-user manual installation of setuptools (as opposed to bundled installation with another package). The basic idea is that the PyPI page for setuptools would contain these

Re: [Distutils] Draft of new setuptools installation instructions

2006-10-03 Thread Bob Ippolito
On 10/3/06, Phillip J. Eby [EMAIL PROTECTED] wrote: Cygwin, Mac OS X, Linux, Other == 1. Download the appropriate egg for your version of Python (e.g. ``setuptools-0.6c4-py2.4.egg``). Do NOT rename it. 2. Make it executable (e.g. ``chmod +x

Re: [Distutils] Draft of new setuptools installation instructions

2006-10-03 Thread Phillip J. Eby
At 02:40 PM 10/3/2006 -0700, Bob Ippolito wrote: Wouldn't it be easier to just tell them to do sh ./setuptools-0.6c4-py2.4.egg instead of marking it executable first? I found the phrasing much more awkward that way, as it led to having to explain the idea that it's got a shell script in there.

Re: [Distutils] Draft of new setuptools installation instructions

2006-10-03 Thread Bob Ippolito
On 10/3/06, Phillip J. Eby [EMAIL PROTECTED] wrote: At 02:40 PM 10/3/2006 -0700, Bob Ippolito wrote: Wouldn't it be easier to just tell them to do sh ./setuptools-0.6c4-py2.4.egg instead of marking it executable first? I found the phrasing much more awkward that way, as it led to having to

Re: [Distutils] Draft of new setuptools installation instructions

2006-10-03 Thread Phillip J. Eby
At 10:43 PM 10/3/2006 +0100, Paul Moore wrote: On 10/3/06, Phillip J. Eby [EMAIL PROTECTED] wrote: Should we make more effort to create a usable command-line experience on Windows? Perhaps use a post-install script to register easy_install so it works from Start/Run, with an automatic pause to

Re: [Distutils] Draft of new setuptools installation instructions

2006-10-03 Thread Phillip J. Eby
At 06:14 PM 10/3/2006 -0400, bear wrote: Phillip J. Eby wrote: RPM-Based Systems = Install setuptools using the provided source RPM. The included ``.spec`` file assumes you are installing using the default ``python`` executable, and is thus not specific to a particular Python