Either way having a Dockerfile in the project to test with PyPy sounds like
a good idea.
On Thu, Oct 22, 2020 at 6:37 AM Antoine Pitrou wrote:
>
> We can, but we cannot be expected to act if something breaks. So this
> would be wasting CPU resources for little use.
>
> Regards
>
> Antoine.
>
>
We can, but we cannot be expected to act if something breaks. So this
would be wasting CPU resources for little use.
Regards
Antoine.
Le 22/10/2020 à 13:33, Krisztián Szűcs a écrit :
> On Thu, Oct 22, 2020 at 1:21 PM Antoine Pitrou wrote:
>>
>>
>> Hi Niklas,
>>
>> Le 22/10/2020 à 13:16, Nik
On Thu, Oct 22, 2020 at 1:21 PM Antoine Pitrou wrote:
>
>
> Hi Niklas,
>
> Le 22/10/2020 à 13:16, Niklas B a écrit :
> >
> > Would the arrow project be open to a PR with the above patch, even though
> > it doesn’t give you full PyPy support?
>
> I think that would be ok, but you'll have to provid
Hi Niklas,
Le 22/10/2020 à 13:16, Niklas B a écrit :
>
> Would the arrow project be open to a PR with the above patch, even though it
> doesn’t give you full PyPy support?
I think that would be ok, but you'll have to provide maintenance when
needed, because I think we're unlikely to make PyPy
Hi,
I’ve been (together with the PyPy team) working on getting arrow to build on
PyPy3. I’m not looking for full feature capability, but specifically getting it
to work with pandas read_parquet/to_parquet which it now does. There were a few
roadblocks solved by the awesome Matti Picus on the Py
