Charles R Harris wrote: > > > > Just to be clear, there are *already* macros in the ndarrayobject.h file > that aren't py3k compatible. How do you propose to fix those?
I don't understand the connection with the public vs private issue. If the py3k compatibility header is to be shared by several extensions, it has to be in a different header, included separately from any numpy headers. Fixing the ndarrayobject.h to be py3k-compatible can and should be done without adding extra public macros. David _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
