On Mon, Oct 7, 2024, at 06:04, Rohit Goswami wrote:
> I second Matti's comments about the validity of endorsing things we don't
> implement.
I don't think it is possible to make ecosystem-wide recommendation that will
fit each project like a glove. At best, we can try to come together as a
com
On Tue, Oct 8, 2024 at 8:36 AM Nathan via NumPy-Discussion <
numpy-discussion@python.org> wrote:
>
> Since the legacy RNG interface cannot be deprecated and we encourage
> downstream to use it in tests according to the text of NEP 19, I'm not sure
> about the text in SPEC 7 that talks about deprec
Can anyone shed some light on the expected behavior of code using
array(..., copy=True) with pandas objects? We ran into this in statsmodels
and I think there are probably plenty of places where we explicitly call
array(..., copy=True) and think we should have a totally independent copy
of the data
Thanks for clarifying! In that case I think endorsing SPEC 7 makes sense.
On Tue, Oct 8, 2024 at 3:08 PM Robert Kern wrote:
> On Tue, Oct 8, 2024 at 8:36 AM Nathan via NumPy-Discussion <
> numpy-discussion@python.org> wrote:
>
>>
>> Since the legacy RNG interface cannot be deprecated and we enco
On Tue, 2024-10-08 at 09:34 +0100, Kevin Sheppard via NumPy-Discussion
wrote:
> Can anyone shed some light on the expected behavior of code using
> array(..., copy=True) with pandas objects? We ran into this in
> statsmodels
> and I think there are probably plenty of places where we explicitly
> ca
Regarding thread safety - that's not a problem. At least for Python 3.13,
the GIL is temporarily re-enabled during imports. That won't necessarily be
true in the future, but separately CPython also uses per-module locks on
import, so there shouldn't be any issues with threads simultaneously
importi
Is SPEC 1 thread-safe enough for py313+nogil?
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member add
