From: Yitzchak Scott-Thoennes <sthoenna@efn.org>
To: cygwin@cygwin.com
Subject: Re: python and cygwin
Date: Sun, 22 Feb 2004 19:29:00 -0000 [thread overview]
Message-ID: <20040222183030.GB1208@efn.org> (raw)
In-Reply-To: <c16d7u$2ck$1@sea.gmane.org>
On Fri, Feb 20, 2004 at 05:45:33PM -0800, Totte Karlsson <tkarlsson@qm.com> 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 have to
> duplicate things. I only want one "repository".
You can use your already innstalled python. You just may need to do a
little work to make sure paths are correctly translated. I'm not sure
exactly what you were doing to feed python a /cygdrive... path; you may
just need to replace the #! line in your script to point to a wrapper
that does a cygpath -w translation on its first argument.
Does anyone know if there is any particular reason that PATH translation
ends up with /cygdrive/x/... rather than x:/...?
> It sounds as if you are talking about cygwin as an operating system, on
> which you can run cygwin applications.
That's a good way to think of it.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2004-02-22 18:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 22:33 Totte Karlsson
2004-02-20 22:53 ` Totte Karlsson
2004-02-20 23:20 ` Brian Dessent
2004-02-20 23:39 ` Totte Karlsson
2004-02-21 0:00 ` Brian Dessent
2004-02-21 1:25 ` Thorsten Kampe
2004-02-21 2:29 ` Totte Karlsson
2004-02-21 2:36 ` Norman Vine
2004-02-21 2:38 ` Thorsten Kampe
2004-02-21 3:10 ` Larry Hall
2004-02-22 19:29 ` Yitzchak Scott-Thoennes [this message]
2004-02-22 20:09 ` Larry Hall
2004-02-22 22:15 ` Yitzchak Scott-Thoennes
2004-02-20 23:54 DePriest, Jason R.
2004-02-21 0:01 ` Igor Pechtchanski
2004-02-21 0:26 ` Christopher Faylor
2004-02-21 18:45 Totte Karlsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040222183030.GB1208@efn.org \
--to=sthoenna@efn.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).