[Numpy-discussion] Github migration?
Thu Sep 2 09:45:20 CDT 2010
On Wed, Sep 1, 2010 at 10:46 AM, Charles R Harris <firstname.lastname@example.org
> On Tue, Aug 31, 2010 at 2:56 PM, Jason McCampbell <
> email@example.com> wrote:
>> Hi Chuck (and anyone else interested),
>> I updated the refactoring page on the NumPy developer wiki (seems to be
>> down or I'd paste in the link). It certainly isn't complete, but there are
>> a lot more details about the data structures and memory handling and an
>> outline of some additional topics that needs to be filled in.
> Thanks Jason. How much of the core library can be used without any
> reference counting? I was originally thinking that the base ufuncs would
> just be functions accepting a pointer and a descriptor and handling memory
> allocations and such would be at a higher level. That is to say, the object
> oriented aspects of numpy would be removed from the bottom layers where they
> just get in the way.
Hi Chuck. Unfortunately pretty much all of the main core object are
reference counted. We had hoped to avoid this, but the issue is that many
of the objects reference each other. For example, some functions create a
"new" array, but that array may just be a view of another array. The same
is true for the descriptor objects.
One option was to push all memory management up into the interface, but that
had the effect of requiring quite a few callbacks which makes the core a lot
harder to use from standard C/C++ application.
> Also, since many of the public macros expect the old type structures, what
> is going to happen with them? They are really part of the API, but a
> particularly troublesome part for going forward.
Are there any specific macros that are a particular problem? I do agree, I
dislike macros in general and some have been simplified, but largely they
are similar to what was there before.
> NumPy-Discussion mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion