From: "Totte Karlsson" <tkarlsson@qm.com>
To: cygwin@cygwin.com
Subject: Re: python and cygwin
Date: Fri, 20 Feb 2004 22:53:00 -0000 [thread overview]
Message-ID: <c162os$eni$1@sea.gmane.org> (raw)
In-Reply-To: <c160pf$ocm$1@sea.gmane.org>
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" <tkarlsson@qm.com> wrote in message
news:c160pf$ocm$1@sea.gmane.org...
> 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 open file '/cygrive ... the path to the
> script/theScript.py'
>
> Any suggestions?
> I guess it should be straightforward to just setup the paths in .bashrc,
but
> maybe not!
> regards
> /totte
>
>
>
>
--
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-20 22:46 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 [this message]
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
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='c162os$eni$1@sea.gmane.org' \
--to=tkarlsson@qm.com \
--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).