"Joe Smith" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > "Joe Smith" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] >> >> Exactly the issue. >> I see the problem here is cygwin's partial POSIX complience. However, >> Windows NT had a design goal of allowing a complient implementation >> of POSIX to be implmented in a subsystem (along with userespace >> utilities). >> >> So it should be possible to get unlink() to work as like a POSIX unlink >> using raw NT kernel calls. >> Since Cygwin has dropped support for pre-NT systems, swithing to that >> seems >> to be the correct thing to do. >> >> I'll discuss this with the cygwin team. >> >> Regardless, the exact same issue will likely exist on the windows side. >> It seems likely that a fix for the Windows side may fix the cygwin issue. >> > > Looks like the fix needed for cygwin's unlink was checked in two days ago. > The problem should automatically disappear in the next cygwin release.
Sorry for misinformation. It looks like it has been changed for more than 2 days, but 2 days is the date of the most recent change. Regardless it looks like the code that does the right thing is not in the latest released DLL. _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
