On 10/5/21 8:43 pm, Sebastian Berg wrote:
But right now the proposal says this is static, and I honestly don't
see much reason for it to be freeable?
I think this is the crux of the issue. The current design is for a
singly-allocated struct to be passed around since it is just an
aggregate
On Mon, 2021-05-10 at 10:01 +0100, Eric Wieser wrote:
> > The Python version of this does have a `void *ctx`, but I am not
> > sure if
> the use for this is actually valuable for the NumPy use-cases.
>
> Do you mean "the CPython version"? If so, can you link a reference?
Yes, sorry, had been a wh
Hi All,
On behalf of the NumPy team I am pleased to announce the release of NumPy
1.20.3. NumPy 1,20.3 is a bugfix release containing several fixes merged to
the main branch after the NumPy 1.20.2 release. The Python versions
supported for this release are 3.7-3.9. Wheels can be downloaded from Py
Hello, Mahesh!
We will take your project into consideration and let you know of our
decision shortly.
Cheers!
Melissa
On Sat, May 8, 2021 at 4:19 PM Mahesh S wrote:
> Hi there everyone,
>
> I am attaching my in depth proposal for Google Season of Docs 2021 with
> NumPy along with this mail. K
Thank you, Ayush! We will take your project into consideration and let you
all know of our decision shortly.
Cheers!
- Melissa
On Mon, May 10, 2021 at 8:26 AM Ayush Verma wrote:
> I have updated the statement with links to a personal project's
> documentation following the Diataxis framework g
> The Python version of this does have a `void *ctx`, but I am not sure if
the use for this is actually valuable for the NumPy use-cases.
Do you mean "the CPython version"? If so, can you link a reference?
> While I like the `PyObject *` idea, I am also not sure that it helps
much. If we want a
