On Sat, 2022-09-03 at 00:03 +, lpsm...@uw.edu wrote:
> Sebastian Berg wrote:
> > On Fri, 2022-08-19 at 23:56 +, lpsm...@uw.edu wrote:
> > > Thanks for the information! I've had to work on other project in
> > > the
> > > meantime, but was able to get back to this again.
> > > In an effort
Sebastian Berg wrote:
> On Fri, 2022-08-19 at 23:56 +, lpsm...@uw.edu wrote:
> > Thanks for the information! I've had to work on other project in the
> > meantime, but was able to get back to this again.
> > In an effort to wrap my head around the project's code, I realized
> > that I did not
On Fri, 2022-08-19 at 23:56 +, lpsm...@uw.edu wrote:
> Thanks for the information! I've had to work on other project in the
> meantime, but was able to get back to this again.
>
> In an effort to wrap my head around the project's code, I realized
> that I did not have a line like:
>
> #defin
Thanks for the information! I've had to work on other project in the meantime,
but was able to get back to this again.
In an effort to wrap my head around the project's code, I realized that I did
not have a line like:
#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION
in it. So, I added the
On Thu, 2022-07-07 at 22:37 +, lpsm...@uw.edu wrote:
> Hello! I am maintaining a C++ codebase with extensive ties to Python
> bindings (via SWIG). One of the features of the code is that we
> define (in C) a subclass of a NumPy Array. Everything worked until
> we started getting this message
On 8/7/22 01:37, lpsm...@uw.edu wrote:
Hello! I am maintaining a C++ codebase with extensive ties to Python bindings
(via SWIG). One of the features of the code is that we define (in C) a
subclass of a NumPy Array. Everything worked until we started getting this
message with numpy 1.23:
