On Mon, Feb 15, 2010 at 11:00 PM, David Cournapeau <da...@silveregg.co.jp>wrote:
> 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. > > So I had the impression that the compatibility header couldn't be included in some of the code that needed it. Is that the case. > Fixing the ndarrayobject.h to be py3k-compatible can and should be done > without adding extra public macros. > I wasn't adding extra public macros, I propose putting ifdefs around the *current* macros so that they are compatible with py3k. Chuck
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
