|
From: Peter V. <ve...@em...> - 2005-12-12 21:35:09
|
Hi Travis, I am curious about your experience with moving nd_image to scipy_core. I have not had the time to look at scipy_core, so I have not tried to do it myself, although it was on my very-long-term list of things to do. Did it require a lot of changes and did you get it to pass the unit tests? Cheers, Peter > A few days ago I played with nd_image and was able to make it > compile for scipy_core. In the process, I had some ideas for > making the transition to scipy_core easier for numarray users: > > 1) It would be nice if there was someway to document on the Python > level any needed changes. In the process, we might find things > that need to be added to scipy_core. I would like to have some > kind of program for automatically making most of those needed > changes before a 1.0 release of scipy_core. > > 2) On the C-API side, my experience with nd_image showed me that > quite a few of the numarray C-API calls can be written as macros > while some will need to be additional functions. I think we could > easily write a numcompatmodule.c and associated numcompat.h file so > that users needing the numarray C-API could include the numcompat.h > file and then the import_libnumarray() command would load the > numcompatmodule.c with it's compatibility functions. > > In this way, the transition for C-API users could be as easy as > changing the include file to numcompat.h? > -Travis > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through > log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD > SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Numpy-discussion mailing list > Num...@li... > https://lists.sourceforge.net/lists/listinfo/numpy-discussion |