A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-November/049724.html below:

[Python-Dev] Tests broken on Windows

[Python-Dev] Tests broken on Windows [Python-Dev] Tests broken on WindowsTim Peters tim.peters at gmail.com
Mon Nov 1 06:52:03 CET 2004
[Raymond Hettinger]
> Run fine on WinME.
>
> Am still getting a failure for test_traceback.py's test_bug737473.

Fixed that already for WinXP.  No current failures in the -uall test
suite.  Is there a bug report for this ME problem?  Exactly how does
it fail?  Does it work if you force the test to take the time.sleep()
path instead of the os.utime() path?  Is posixmodule.c's posix_utime()
taking the utime() or _wutime() path on ME?  If the latter, does it
work if you force it to take the utime() path instead?  MS docs claim
utime() and _wutime() work "under Windows 98/Me and Windows
NT/2000/XP", but they could be lying:

<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt__utime.2c_._wutime.asp>

That link has a wonderful C example:  if you study the sample output,
it shows that the sample code they ran had no visible effect <wink>.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4