Matthieu Brucher wrote: > > > The 2.6 seems to use VC 2005 Express, I don't know about py3000(?), > > with associated upgrade issues. > But what if the next MS compiler has again broken libc > implementation ? > (Incidently, VS2005 was not used for python2.5 for even more > broken libc > than in 2003): > http://mail.python.org/pipermail/python-dev/2006-April/064126.html > > > I don't what he meant by a broken libc, if it is the fact that there > is a lot of deprecated standard functions, I don't call it broken > (besides, this deprecation follows a technical paper that describe the > new safe functions, although it does not deprecate these functions). If unilaterally deprecating standard functions which exist for years is not broken, I really wonder what is :)
cheers, David _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
