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 minim
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?
At 06:48 AM 10/4/2006 -0400, Jim Fulton wrote:
>Phillip J. Eby wrote:
>>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).
>
>This see
On Wed, Oct 04, 2006 at 09:23:28AM +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
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 ea
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.p
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 "easy
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 particu
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 "easy_install-win.exe" under
"easy_install" in App Paths. This ver
Phillip J. Eby wrote:
> Windows
> ===
>
> Install setuptools using the provided ``.exe`` installer. If you've
> previously installed older versions of setuptools, please delete all
> ``setuptools*.egg`` files from your system FIRST.
>
> If you are upgrading a previous version of setuptools t
On 10/3/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> >IMHO, no. Your particular suggestions would annoy me immensely,
>
> Are you sure? Two points here, that I think you're not noticing:
>
> 1. Registering an "App Paths" entry for easy_install would simply make it
> *possible* to type "easy_ins
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 p
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 ha
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
On 10/3/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> I'm looking for any feedback people might have, on the installation process
> itself or on the directions. Some particular areas of question/concern:
Looks fine for Windows.
> * Should we make more effort to create a usable command-line exp
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 setupto
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
instructions,
17 matches
Mail list logo
