strtod dilemma

Hi list,

When the 'pylab' module is loaded the function 'strtod' does not work well.

I suppose that this is not new: http://www.python.org/search/hypermail/python-1994q2/0750.html

and the question is: any solution?

In this linkit exists a better description of the problem:

http://mbdynsimsuite.sourceforge.net/build_mbdyn_bindings.html

regards, Luis.

Luis Saavedra wrote:

Hi list,

When the 'pylab' module is loaded the function 'strtod' does not work well.
  

Can you elaborate on how it doesn't work?

I suppose that this is not new: http://www.python.org/search/hypermail/python-1994q2/0750.html

and the question is: any solution?
  

There's a solution in that link: use one of the many alternatives that are known to be more consistent across various versions of UNIX.

In this linkit exists a better description of the problem:

http://mbdynsimsuite.sourceforge.net/build_mbdyn_bindings.html
  

I think this is not a matplotlib-specific problem, but a Python one, since Python provides its own strtod definition -- in an apparent attempt to get around its differences on different platforms. If you grep over the matplotlib source code, "strtod" isn't even there.

Cheers,
Mike

Michael Droettboom escribi�:

Luis Saavedra wrote:

Hi list,

When the 'pylab' module is loaded the function 'strtod' does not work well.
  

Can you elaborate on how it doesn't work?

I suppose that this is not new: http://www.python.org/search/hypermail/python-1994q2/0750.html

and the question is: any solution?
  

There's a solution in that link: use one of the many alternatives that are known to be more consistent across various versions of UNIX.

In this linkit exists a better description of the problem:

http://mbdynsimsuite.sourceforge.net/build_mbdyn_bindings.html
  

I think this is not a matplotlib-specific problem, but a Python one, since Python provides its own strtod definition -- in an apparent attempt to get around its differences on different platforms. If you grep over the matplotlib source code, "strtod" isn't even there.

Cheers,
Mike

Sorry for the noise, please ignore. This problem is produced due to the fact that 'pylab' load the 'gtk' module and when 'gtk' is loaded it load my 'locale'(es_CL with LC_NUMERIC=','), and it is fine! My module is the one that must not be dependent on the locale (LC_NUMERIC).

Regards,
Luis.