RetroSearch Browse

Thu Jan 6 17:08:09 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-January/107280.html

Le jeudi 06 janvier 2011 à 10:47 -0500, R. David Murray a écrit :
> On Thu, 06 Jan 2011 12:55:24 +0100, Victor Stinner <victor.stinner at haypocalc.com> wrote:
> >Le jeudi 06 janvier 2011 à 00:10 -0500, Alexander Belopolsky a écrit :
> >>  If calling specific system functions such as strftime with tm_year <
> >> 0 is deemed unsafe, we can move the check to where the system function
> >> is called.
> >
> >What do you mean by "unsafe"? Does it crash? On my Linux box,
> >strftime("%Y") is able to format integers in [-2^31-1900; 2^31-1-1900]
> >(full range of the int type).
> 
> I believe that we have had several cases where Windows "crashed" when
> out-of-range values were passed to the CRT that other platforms
> accepted.

If there are only issues on Windows, we can add a #ifdef _MSC_VER and
raise a ValueError("Stupid OS, install Linux or recompile with Cygwin")
for year < 1900.

Does Cygwin and MinGW have the same issues?

Victor

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

Showing content from https://mail.python.org/pipermail/python-dev/2011-January/107280.html below:

[Python-Dev] Checking input range in time.asctime and time.ctime