[Numpy-discussion] numpy 1.3: cleaning the math configuration, toward a warning free build

David Cournapeau cournapeau@cslab.kecl.ntt.co...
Thu Sep 4 02:47:43 CDT 2008


	For numpy 1.3, there are several things I would like to work on, which
I have already hinted previously. The two big things are:
	- cleaning the math configuration
	- making numpy buildable warning-free with a good set a warning flags.

For the warning-free build, I have started a nep, since some decisions
are not obvious. Is this appropriate ?

For the first part, I want to clean-up the current umath module, mainly
the configuration: we have quite a big mess ATM with several intervened
configurations, and everytime I am trying to touch it, I break something
(adding trunc, modifying mingw configuration, etc...). I think it would
be nice to clean-up, have a per-function check (instead of the
HAVE_LONGDOUBLE heuristic); I noticed for example that depending on the
configuration, we have different implementations for the same function,
etc... Robert mentioned the configuration time cost increase, but I
think I have a solution to make it as fast as before for most
configurations, the ones which work today, and it will be longer only
for platforms which need a better configuration (mingw, etc...).

Should I write a nep for that too ? Or a patch is enough ?



More information about the Numpy-discussion mailing list