public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Dockeen" <dockeen@mchsi.com>
To: <cygwin@cygwin.com>
Subject: Python Lesson Learned
Date: Sat, 08 Jun 2002 06:19:00 -0000	[thread overview]
Message-ID: <NCBBLKKJGBJOLDFMCKFPOEHLCAAA.dockeen@mchsi.com> (raw)

I noticed something interesting this evening.  I was playing
with the Cygwin version of dislin.  I got everything going for
C and Perl, but Python was complaining of an interpreter
mismatch.

I did a python -v, and saw it was reporting using a flavor of release
2.1.  Now, after flailing around a little bit with uninstalling
and reinstalling Python, I finally used my anemic brain and noticed
something important.  Somehow (probably through incompetence or
fumble fingering by me), I had ended up with two installations
of Python, one in /usr/local/bin, and the newer one in /usr/bin,
and the older one was being found first.  I deleted the older
stuff and now things are working well with dislin. (Oh yeah, 
python -v reports version 2.2 being used too).

I don't know how many folks out there use Python in Cygwin, but
I thought my misfortune might be of use to someone some day, even
if only for humor value.

Wayne Keen

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2002-06-08  5:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-08  6:19 Dockeen [this message]
2002-06-08 10:15 ` Jason Tishler
2002-06-08 16:20 Dockeen
2002-06-09 16:20 ` Nicholas Wourms

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=NCBBLKKJGBJOLDFMCKFPOEHLCAAA.dockeen@mchsi.com \
    --to=dockeen@mchsi.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).