On 23. 08. 22 16:19, Sebastian Berg wrote:
On Tue, 2022-08-23 at 14:00 +0200, Petr Viktorin wrote:
On 23. 08. 22 11:46, Sebastian Berg wrote:
[snip]
One thing that I am not clear about are e.g. creation functions.
They
are public C-API so they have no way of getting a "self" or
type/module
pas
Angélica Cardozo took initiative to translate into Portuguese the subtitles
for the video “Find your way in the NumPy codebase” (
https://www.youtube.com/watch?v=mTWpBf1zewc) posted on the official NumPy
YouTube channel (https://www.youtube.com/c/NumPy_team).🎉 We are currently
looking for a contri
Sorry for the late reply. Adding a new "*.npy" format feature to allow
writing to the file in chunks is nice but seems a bit limited. As I
understand the proposal, reading the file back can only be done in the
chunks that were originally written. I think other libraries like zar or
h5py have so
Hi Inessa,
I can help. I'm mostly sitting still at home these days, still recovering,
so I have plenty of time. Feel free to send me the link to the PR and I'll
be more than happy to help.
Regards,
Ricardo
On Wed, Aug 24, 2022 at 9:59 AM Inessa Pawson wrote:
> Angélica Cardozo took initiative
On Tue, Aug 23, 2022 at 3:47 AM Sebastian Berg
wrote:
> What is the status of immortality? None of these seem forbidding on
> first sight, so long that we can get the state everywhere.
> Having immortal object seems convenient, but probably not particularly
> necessary.
The current proposal for
On Tue, Aug 23, 2022 at 6:01 AM Petr Viktorin wrote:
> And if the CPython API is lacking, it would be best to solve that in
> CPython.
+1
In some ways, new CPython APIs would be the most important artifacts of this
discussion. We want to minimize the effort it takes to support
multiple interpre
On Wed, Aug 24, 2022 at 4:42 AM Petr Viktorin wrote:
> On 23. 08. 22 16:19, Sebastian Berg wrote:
> > Our public C-API is currently exported as a single static struct into
> > the library loading NumPy. If types depend on the interpreter, it
> > would seem we need to redo the whole mechanism?
>
>
Hi Matti, hi all,
@Matti: I don’t know what exactly you are referring to (Pull request or the
Github project, links see below). Maybe some clarification is needed, which I
hereby try to do ;)
A .npy file created by some appending process is a regular .npy file and does
not need to be read in c
Hi, Ricardo!
Wonderful! I’ll send you all the details via email.
--
Cheers,
Inessa
Inessa Pawson
Contributor Experience Lead | NumPy
https://numpy.org/
GitHub: inessapawson
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe
