Wrong parameter value (configurable) loaded in python node

[RiccardoGiubilato]

I have a parameter defined like this in the .param file:

gen.add("heightMapGridResolution", description="...",  paramtype="double", default=0.1, configurable=True)

If I load the parameters in a C++ node, everything works as expected: the parameter is loaded either as the default or as the one specified in the .yaml file

If I load the parameter in a python node however, the parameter is loaded as:

'heightMapGridResolution': '-std::numeric_limits<double>::infinity()'

which corresponds to:

__min__.heightMapGridResolution = -std::numeric_limits<double>::infinity();

in the automatically generated paramConfig.h, instead of

__default__.heightMapGridResolution = 0.1;

any idea of what is happening there? Is that a rosparam_handler issue or a dynamic_reconfigure issue?

thanks!!

PS: This does not happen with configurable parameters of type std::string