On Sun, Feb 22, 2004 at 01:43:06PM -0500, Larry Hall wrote:
> At 01:30 PM 2/22/2004, Yitzchak Scott-Thoennes you wrote:
> >Does anyone know if there is any particular reason that PATH translation
> >ends up with /cygdrive/x/... rather than x:/...?
>
> Sure. You get that when you ask 'cygpath' for
At 01:30 PM 2/22/2004, Yitzchak Scott-Thoennes you wrote:
>On Fri, Feb 20, 2004 at 05:45:33PM -0800, Totte Karlsson <[EMAIL PROTECTED]> wrote:
>> When I open up a "cygwin-bash" on windows, I just thought that I could use
>> my already installed "win-32" python. I realize now that you can't and I
>>
On Fri, Feb 20, 2004 at 05:45:33PM -0800, Totte Karlsson <[EMAIL PROTECTED]> wrote:
> When I open up a "cygwin-bash" on windows, I just thought that I could use
> my already installed "win-32" python. I realize now that you can't and I
> think that creates problems. As a programmer I don't like do
Thanks,
I appreciate your reply very much! I needed to hear something like that in
order to "stop", unfortunately..
/totte
-Original Message-
From: Larry Hall
To: Totte Karlsson; [EMAIL PROTECTED]
Sent: 2/20/2004 6:58 PM
Subject: Re: python and cygwin
At 08:45 PM 2/20/2
At 08:45 PM 2/20/2004, Totte Karlsson you wrote:
>I guess the problem is, as I see it, if cygwin was the "perfect" unix tool
>running under windows, it would integrate with existing windows tools. It
>does that to some extent, but not fully and that is the problem. If I want a
>pure unix environmen
* Totte Karlsson (2004-02-21 02:45 +0100)
> When I open up a "cygwin-bash" on windows, I just thought that I
> could use my already installed "win-32" python. I realize now that
> you can't
As I already told you in my answer: You *can* with a little effort.
Python as a multiplatform scripting lang
Totte Karlsson writes:
>
> When I open up a "cygwin-bash" on windows, I just thought that I could use
> my already installed "win-32" python.
One of the things Cygwin provides is a standard POSIX interface
to the OS. Cygwin Python is built on top of this.
If you want to use a Python that
I guess the problem is, as I see it, if cygwin was the "perfect" unix tool
running under windows, it would integrate with existing windows tools. It
does that to some extent, but not fully and that is the problem. If I want a
pure unix environment, on the other hand, then I would use the real stuff
* Totte Karlsson (2004-02-21 00:29 +0100)
> OK, I see, However, it seems as if I can execute the win32 python
> interpreter from within the cygwin bash shell, and it seems to work
> as long the cygwin path come into play, which is "unfortunate".
>
> I thought the idea with cygwin was to provide u
On Fri, Feb 20, 2004 at 06:55:19PM -0500, Igor Pechtchanski wrote:
>Actually, the main goal of Cygwin is to annoy users and to give a vent to
>the innate meanness of its developers.
>
>The secondary goal of Cygwin is to provide POSIX compatibility. The Unix
>tools are incidental. :-)
Thank you fo
indows since
> Windows 95.[/quote]
>
> > -Original Message-
> > From: cygwin-owner at cygwin dot com
> > [mailto: cygwin-owner at cygwin dot com] On Behalf Of Totte Karlsson
> > Sent: Friday, February 20, 2004 5:29 PM
> > To: cygwin at cygwin dot com
>
Totte Karlsson wrote:
> However, it seems as if I can execute the win32 python interpreter from
> within the cygwin bash shell, and it seems to work as long the cygwin path
> come into play, which is "unfortunate".
The win32 one has no idea what a posix (e.g. /cygdrive or /usr/bin) path
is, and h
-
> From: cygwin-owner at cygwin dot com
> [mailto: cygwin-owner at cygwin dot com] On Behalf Of Totte Karlsson
> Sent: Friday, February 20, 2004 5:29 PM
> To: cygwin at cygwin dot com
> Subject: Re: python and cygwin
>
>
> OK, I see,
> However, it seems as if I can exec
OK, I see,
However, it seems as if I can execute the win32 python interpreter from
within the cygwin bash shell, and it seems to work as long the cygwin path
come into play, which is "unfortunate".
I thought the idea with cygwin was to provide unix tools working under
windows, not to make windows
Totte Karlsson wrote:
>
> Seems as if I got it working by downloading python "for cygwin"?. I already
> had python for windows installed and I thought cygwin would used that one
> automatically? Guess one has to set it up somewhere?
The win32 python and the Cygwin python are completely seperate a
Seems as if I got it working by downloading python "for cygwin"?. I already
had python for windows installed and I thought cygwin would used that one
automatically? Guess one has to set it up somewhere?
/totte
"Totte Karlsson" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi, I wa
Hi, I want to run my python scripts in a cygwin bash shell, but have
problems.
It seems as if python don't understand the cygwin path.
If I'm placed in the directory in where the pythonscript is located, it
works fine, if I'm in another directory it don't work. I get the error
python.exe: can't op
17 matches
Mail list logo
