This is the mail archive of the
mailing list for the Cygwin project.
RE: difficulties with 1.4.5/cygwin
- To: "'Jan Nieuwenhuizen'" <janneke at gnu dot org>, <raybro at iname dot com>
- Subject: RE: difficulties with 1.4.5/cygwin
- From: "Norman Vine" <nhv at cape dot com>
- Date: Tue, 14 Aug 2001 10:17:34 -0400
- Cc: <lilypond-user at gnu dot org>, <cygwin at cygwin dot com>
- Reply-To: <nhv at cape dot com>
Jan Nieuwenhuizen writes:
>"William R. Brohinsky" <firstname.lastname@example.org> writes:
>> Tonight, in frustration, I upgraded python from the
>supported 1.5.2-2 in
>> the distribution to 2.2 from the full cygwin distrib.
>> And now, ly2dvi works.
>I've looked into that python supported by cygwin, but I'm not planning
>to include it, as it seems to be a rather quaint mixture of
>cygwin/unix and windows. At the core, it uses windows paths and
>I think we should wait until cygwin fixes python to use unix style
>paths. Until then, I've added your suggestion to the wiki,
The Python distributed with Cygwin fully understands POSIX paths
'exactly' the same as the Cygwin package itself.
AFAICT the only thing this is not true for is the Tkinker extension,
which depends on the Cygwin TCL libraries which also have this
If you know of any other 'quaint windowism's' in the Python distribution
please tell us.
< I realize that there might be an inherent issue with a case-preserving
case-insensitive file-naming system versus a true case-sensitive one >
2.1 is the first version of Python 'officially' ported to work with Cygwin
However if you need to support 1.52 and the path handling is the
problem contact me off list as I probably still have my 1.52 mods laying
around some where.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html