[Numpy-discussion] fread codes versus numpy types (original) (raw)
Fernando Perez fperez.net at gmail.com
Wed Jun 28 15:00:05 EDT 2006
- Previous message (by thread): [Numpy-discussion] fread codes versus numpy types
- Next message (by thread): [Numpy-discussion] matlab -> python translation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 6/28/06, David M. Cooke <cookedm at physics.mcmaster.ca> wrote:
On Wed, 28 Jun 2006 11:22:38 -0600 "Fernando Perez" <fperez.net at gmail.com> wrote: > Should I apply this patch, so we push the cleaned-up API even a bit harder?
Yes please. I think all the modules that still use the oldnumeric names actually import numpy.oldnumeric themselves.
Done, r2017. I also committed the simple one-liner:
Index: weave/inline_tools.py
--- weave/inline_tools.py (revision 2016) +++ weave/inline_tools.py (working copy) @@ -402,7 +402,7 @@ def compile_function(code,arg_names,local_dict,global_dict, module_dir, compiler='',
verbose = 0,
verbose = 1, support_code = None, headers = [], customize = None,
from a discussion we had a few weeks ago, I'd forgotten to put it in. I did it as a separate patch (r 2018) so it can be reverted separately if anyone objects.
Cheers,
f
- Previous message (by thread): [Numpy-discussion] fread codes versus numpy types
- Next message (by thread): [Numpy-discussion] matlab -> python translation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]