Hi,
It seems that pyarrow.compute.ascii_trim can not be used without a TrimOption.
However a TrimOption can not be given as a keyword only argument either. This
looks like a bug since utf8_trim does not have this problem. Is my
understanding correct?
Also it seems that there is a lot of Python
+1 non-binding
On Wed, Jun 30, 2021, 2:53 AM Weston Pace wrote:
> This vote is a result of previous discussion[1][2]. This vote is also
> a prerequisite for the PR in [5].
>
> ---
> Some date & time libraries have three temporal concepts. For the sake
> of this document we will call them Local
+1
On Wed, Jun 30, 2021 at 9:25 AM Benjamin Kietzman
wrote:
> +1
>
> On Wed, Jun 30, 2021, 08:54 David Li wrote:
>
> > +1
> >
> > On Wed, Jun 30, 2021, at 08:46, Wes McKinney wrote:
> > > +1
> > >
> > > On Wed, Jun 30, 2021 at 12:03 PM Antoine Pitrou
> > wrote:
> > > >
> > > > +1
> > > >
> > >
+1
On Wed, Jun 30, 2021, 08:54 David Li wrote:
> +1
>
> On Wed, Jun 30, 2021, at 08:46, Wes McKinney wrote:
> > +1
> >
> > On Wed, Jun 30, 2021 at 12:03 PM Antoine Pitrou
> wrote:
> > >
> > > +1
> > >
> > >
> > > Le 30/06/2021 à 11:52, Weston Pace a écrit :
> > > > This vote is a result of prev
+1
On Wed, Jun 30, 2021, at 08:46, Wes McKinney wrote:
> +1
>
> On Wed, Jun 30, 2021 at 12:03 PM Antoine Pitrou wrote:
> >
> > +1
> >
> >
> > Le 30/06/2021 à 11:52, Weston Pace a écrit :
> > > This vote is a result of previous discussion[1][2]. This vote is also
> > > a prerequisite for the PR
+1
On Wed, Jun 30, 2021 at 12:03 PM Antoine Pitrou wrote:
>
> +1
>
>
> Le 30/06/2021 à 11:52, Weston Pace a écrit :
> > This vote is a result of previous discussion[1][2]. This vote is also
> > a prerequisite for the PR in [5].
> >
> > ---
> > Some date & time libraries have three temporal conce
+1
Le 30/06/2021 à 11:52, Weston Pace a écrit :
This vote is a result of previous discussion[1][2]. This vote is also
a prerequisite for the PR in [5].
---
Some date & time libraries have three temporal concepts. For the sake
of this document we will call them LocalDateTime, ZonedDateTime, a
This vote passes (+8 binding / +3 non-binding). I've created
ARROW-13218 and started a PR [1] to tackle both this vote and the
other vote (regarding instants). The PR will need to wait until the
other vote settles to be merged but I'd appreciate any comments /
refinements in the meantime.
[1] ht
This vote is a result of previous discussion[1][2]. This vote is also
a prerequisite for the PR in [5].
---
Some date & time libraries have three temporal concepts. For the sake
of this document we will call them LocalDateTime, ZonedDateTime, and
Instant. An Instant is a timestamp that has no m
As of now there are 9 votes for C, 1 for D, and 4 for E (although all
E votes were second-choice votes). It seems there is consensus around
C. I apologize for all the noise but to follow the process I'll go
ahead and create one more vote thread to wrap this up.
On Mon, Jun 28, 2021 at 5:44 PM Br
Le 30/06/2021 à 10:04, Wes McKinney a écrit :
I guess my concern with this is how to quickly separate out "PRs I am
keeping an eye on". If there are 100 active PRs and only 20 of them
are ones you've interacted with, how do you know which ones need your
attention? GitHub does have the "reviewe
On Tue, Jun 29, 2021 at 8:05 PM Weston Pace wrote:
>
> I apologize. I did plan on working on this but it's taken a back seat
> for a while. I would still recommend shying away from a standalone
> UI. You will end up making a lot of requests (and possibly running
> into Github throttles) if you
12 matches
Mail list logo
