From deamarialeon at gmail.com  Wed May  3 04:47:17 2023
From: deamarialeon at gmail.com (=?UTF-8?Q?Dea_Mar=C3=ADa?=)
Date: Wed, 3 May 2023 10:47:17 +0200
Subject: [Pandas-dev] Triage
Message-ID: <CAHrDCuzQqAUbdh8GpKGLLTA6YTU19beNXnUGzeT8-5vvrpib9w@mail.gmail.com>

Dear All,


If you are helping with triage, it would be nice if you could also remove
the ?needs triage? label after labelling the issue.


Sometimes the person who reported the issue also sets the labels. So, it is
not obvious if the labeling was done by a core-dev or not until I open the
issue.

Sure, it only takes a few seconds to find that my ?extremely important?
help ;-) is not needed. But newcomers? time is also valuable.


Please help us help you. :)


Thanks,

Dea
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20230503/816f171d/attachment.html>

From garcia.marc at gmail.com  Wed May  3 05:43:14 2023
From: garcia.marc at gmail.com (Marc Garcia)
Date: Wed, 3 May 2023 10:43:14 +0100
Subject: [Pandas-dev] Triage
In-Reply-To: <CAHrDCuzQqAUbdh8GpKGLLTA6YTU19beNXnUGzeT8-5vvrpib9w@mail.gmail.com>
References: <CAHrDCuzQqAUbdh8GpKGLLTA6YTU19beNXnUGzeT8-5vvrpib9w@mail.gmail.com>
Message-ID: <CAEk5N5ubi0F2twqT7k79g0Pco2qyeoervc_jBAY5PV+msC06kQ@mail.gmail.com>

Not sure if other set the label manually, but I assumed in most cases the
label is applied automatically by our issue templates. Regular users can't
set labels themselves afaik. And if I set labels manually, I consider I
already did the triage so I don't set that label.

Thanks for letting us know, this is helpful, if you still find the issue
after the message, it may be worth discussing the workflow with the exact
person (in the issue log you should be able to see who changes the labels.



On Wed, May 3, 2023, 10:21 Dea Mar?a <deamarialeon at gmail.com> wrote:

> Dear All,
>
>
> If you are helping with triage, it would be nice if you could also remove
> the ?needs triage? label after labelling the issue.
>
>
> Sometimes the person who reported the issue also sets the labels. So, it
> is not obvious if the labeling was done by a core-dev or not until I open
> the issue.
>
> Sure, it only takes a few seconds to find that my ?extremely important?
> help ;-) is not needed. But newcomers? time is also valuable.
>
>
> Please help us help you. :)
>
>
> Thanks,
>
> Dea
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20230503/f2e7ef19/attachment.html>

From deamarialeon at gmail.com  Wed May  3 06:07:28 2023
From: deamarialeon at gmail.com (=?UTF-8?Q?Dea_Mar=C3=ADa?=)
Date: Wed, 3 May 2023 12:07:28 +0200
Subject: [Pandas-dev] Triage
In-Reply-To: <CAEk5N5ubi0F2twqT7k79g0Pco2qyeoervc_jBAY5PV+msC06kQ@mail.gmail.com>
References: <CAHrDCuzQqAUbdh8GpKGLLTA6YTU19beNXnUGzeT8-5vvrpib9w@mail.gmail.com>
 <CAEk5N5ubi0F2twqT7k79g0Pco2qyeoervc_jBAY5PV+msC06kQ@mail.gmail.com>
Message-ID: <CAHrDCuy5Q-Taj2+u5A_2bft75cEuvZn2wjbYnEomCoPu-ZWJ=w@mail.gmail.com>

I just meant that in many cases people forget to remove the ?needs triage?
label after having done the triage.



On Wed, May 3, 2023 at 11:43?AM Marc Garcia <garcia.marc at gmail.com> wrote:

> Not sure if other set the label manually, but I assumed in most cases the
> label is applied automatically by our issue templates. Regular users can't
> set labels themselves afaik. And if I set labels manually, I consider I
> already did the triage so I don't set that label.
>
> Thanks for letting us know, this is helpful, if you still find the issue
> after the message, it may be worth discussing the workflow with the exact
> person (in the issue log you should be able to see who changes the labels.
>
>
>
> On Wed, May 3, 2023, 10:21 Dea Mar?a <deamarialeon at gmail.com> wrote:
>
>> Dear All,
>>
>>
>> If you are helping with triage, it would be nice if you could also remove
>> the ?needs triage? label after labelling the issue.
>>
>>
>> Sometimes the person who reported the issue also sets the labels. So, it
>> is not obvious if the labeling was done by a core-dev or not until I open
>> the issue.
>>
>> Sure, it only takes a few seconds to find that my ?extremely important?
>> help ;-) is not needed. But newcomers? time is also valuable.
>>
>>
>> Please help us help you. :)
>>
>>
>> Thanks,
>>
>> Dea
>> _______________________________________________
>> Pandas-dev mailing list
>> Pandas-dev at python.org
>> https://mail.python.org/mailman/listinfo/pandas-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20230503/62825388/attachment-0001.html>

From rhshadrach at gmail.com  Wed May  3 08:05:18 2023
From: rhshadrach at gmail.com (Richard Shadrach)
Date: Wed, 3 May 2023 08:05:18 -0400
Subject: [Pandas-dev] Triage
In-Reply-To: <CAHrDCuy5Q-Taj2+u5A_2bft75cEuvZn2wjbYnEomCoPu-ZWJ=w@mail.gmail.com>
References: <CAHrDCuzQqAUbdh8GpKGLLTA6YTU19beNXnUGzeT8-5vvrpib9w@mail.gmail.com>
 <CAEk5N5ubi0F2twqT7k79g0Pco2qyeoervc_jBAY5PV+msC06kQ@mail.gmail.com>
 <CAHrDCuy5Q-Taj2+u5A_2bft75cEuvZn2wjbYnEomCoPu-ZWJ=w@mail.gmail.com>
Message-ID: <CAJ=56RJxsvWn+zbh_RCExq7LeMPvxQCKahy2oEUhLBo0xPFNHQ@mail.gmail.com>

I've always thought triage is more than labeling an issue. If it's a bug, I
consider triage as confirming it (a) exists on main (even if the user says
they did) and (b) confirming it is indeed undesired behavior. If it's
reported as a regression then in addition I think it should be confirmed it
does exist on the previous version of pandas.

All of this can be time intensive. However, I can quickly go through the
recently reported issues and appropriately label them so that they are more
visible to other developers who specialize in those areas of the code. When
I do this but not the above steps, I leave the Needs Triage on.

I'm interested to hear thoughts and feedback here, and if there is a more
desirable way.

Best,
Richard



On Wed, May 3, 2023, 06:07 Dea Mar?a <deamarialeon at gmail.com> wrote:

> I just meant that in many cases people forget to remove the ?needs triage?
> label after having done the triage.
>
>
>
> On Wed, May 3, 2023 at 11:43?AM Marc Garcia <garcia.marc at gmail.com> wrote:
>
>> Not sure if other set the label manually, but I assumed in most cases the
>> label is applied automatically by our issue templates. Regular users can't
>> set labels themselves afaik. And if I set labels manually, I consider I
>> already did the triage so I don't set that label.
>>
>> Thanks for letting us know, this is helpful, if you still find the issue
>> after the message, it may be worth discussing the workflow with the exact
>> person (in the issue log you should be able to see who changes the labels.
>>
>>
>>
>> On Wed, May 3, 2023, 10:21 Dea Mar?a <deamarialeon at gmail.com> wrote:
>>
>>> Dear All,
>>>
>>>
>>> If you are helping with triage, it would be nice if you could also
>>> remove the ?needs triage? label after labelling the issue.
>>>
>>>
>>> Sometimes the person who reported the issue also sets the labels. So, it
>>> is not obvious if the labeling was done by a core-dev or not until I open
>>> the issue.
>>>
>>> Sure, it only takes a few seconds to find that my ?extremely important?
>>> help ;-) is not needed. But newcomers? time is also valuable.
>>>
>>>
>>> Please help us help you. :)
>>>
>>>
>>> Thanks,
>>>
>>> Dea
>>> _______________________________________________
>>> Pandas-dev mailing list
>>> Pandas-dev at python.org
>>> https://mail.python.org/mailman/listinfo/pandas-dev
>>>
>> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20230503/7da68893/attachment.html>

From simonjayhawkins at gmail.com  Wed May  3 09:19:14 2023
From: simonjayhawkins at gmail.com (Simon Hawkins)
Date: Wed, 3 May 2023 14:19:14 +0100
Subject: [Pandas-dev] Triage
In-Reply-To: <CAJ=56RJxsvWn+zbh_RCExq7LeMPvxQCKahy2oEUhLBo0xPFNHQ@mail.gmail.com>
References: <CAHrDCuzQqAUbdh8GpKGLLTA6YTU19beNXnUGzeT8-5vvrpib9w@mail.gmail.com>
 <CAEk5N5ubi0F2twqT7k79g0Pco2qyeoervc_jBAY5PV+msC06kQ@mail.gmail.com>
 <CAHrDCuy5Q-Taj2+u5A_2bft75cEuvZn2wjbYnEomCoPu-ZWJ=w@mail.gmail.com>
 <CAJ=56RJxsvWn+zbh_RCExq7LeMPvxQCKahy2oEUhLBo0xPFNHQ@mail.gmail.com>
Message-ID: <CAFs9qGsdidqX2C_mwKkyBaS6A3K8qp=DCTyF0p3C+AQV2m9oXQ@mail.gmail.com>

Agree with Richard.

Even if not reported as a regression by the user, I often use to check the
behaviour of bugs reported on previous versions to double check (Once the
code sample is pasted into a notebook does not take long to re-run on
previous versions once setup)

If found to be a regression, I feel a bisect to isolate the commit is a
worthwhile part of the triage process (and cc the author)

For most issues, IMHO one should only remove the needs triage label if one
is knowledgeable enough to add a value add comment. Thanking the user,
clarifying the issue and suggesting an action to allow progress on the
issue for other readers. (If one is not knowledgeable enough about the
topic to do this, probably best to leave the needs triage to someone more
knowledgeable and not add noise.)

I think the actions of just adding additional labels to help others find
issues should not be considered triage but is also a very
worthwhile maintenance task.

My two cents
Simon

On Wed, 3 May 2023 at 13:05, Richard Shadrach <rhshadrach at gmail.com> wrote:

> I've always thought triage is more than labeling an issue. If it's a bug,
> I consider triage as confirming it (a) exists on main (even if the user
> says they did) and (b) confirming it is indeed undesired behavior. If it's
> reported as a regression then in addition I think it should be confirmed it
> does exist on the previous version of pandas.
>
> All of this can be time intensive. However, I can quickly go through the
> recently reported issues and appropriately label them so that they are more
> visible to other developers who specialize in those areas of the code. When
> I do this but not the above steps, I leave the Needs Triage on.
>
> I'm interested to hear thoughts and feedback here, and if there is a more
> desirable way.
>
> Best,
> Richard
>
>
>
> On Wed, May 3, 2023, 06:07 Dea Mar?a <deamarialeon at gmail.com> wrote:
>
>> I just meant that in many cases people forget to remove the ?needs
>> triage? label after having done the triage.
>>
>>
>>
>> On Wed, May 3, 2023 at 11:43?AM Marc Garcia <garcia.marc at gmail.com>
>> wrote:
>>
>>> Not sure if other set the label manually, but I assumed in most cases
>>> the label is applied automatically by our issue templates. Regular users
>>> can't set labels themselves afaik. And if I set labels manually, I consider
>>> I already did the triage so I don't set that label.
>>>
>>> Thanks for letting us know, this is helpful, if you still find the issue
>>> after the message, it may be worth discussing the workflow with the exact
>>> person (in the issue log you should be able to see who changes the labels.
>>>
>>>
>>>
>>> On Wed, May 3, 2023, 10:21 Dea Mar?a <deamarialeon at gmail.com> wrote:
>>>
>>>> Dear All,
>>>>
>>>>
>>>> If you are helping with triage, it would be nice if you could also
>>>> remove the ?needs triage? label after labelling the issue.
>>>>
>>>>
>>>> Sometimes the person who reported the issue also sets the labels. So,
>>>> it is not obvious if the labeling was done by a core-dev or not until I
>>>> open the issue.
>>>>
>>>> Sure, it only takes a few seconds to find that my ?extremely important?
>>>> help ;-) is not needed. But newcomers? time is also valuable.
>>>>
>>>>
>>>> Please help us help you. :)
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Dea
>>>> _______________________________________________
>>>> Pandas-dev mailing list
>>>> Pandas-dev at python.org
>>>> https://mail.python.org/mailman/listinfo/pandas-dev
>>>>
>>> _______________________________________________
>> Pandas-dev mailing list
>> Pandas-dev at python.org
>> https://mail.python.org/mailman/listinfo/pandas-dev
>>
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20230503/fdb6cd38/attachment-0001.html>

From jbrockmendel at gmail.com  Wed May  3 10:36:07 2023
From: jbrockmendel at gmail.com (Brock Mendel)
Date: Wed, 3 May 2023 07:36:07 -0700
Subject: [Pandas-dev] Triage
In-Reply-To: <CAFs9qGsdidqX2C_mwKkyBaS6A3K8qp=DCTyF0p3C+AQV2m9oXQ@mail.gmail.com>
References: <CAHrDCuzQqAUbdh8GpKGLLTA6YTU19beNXnUGzeT8-5vvrpib9w@mail.gmail.com>
 <CAEk5N5ubi0F2twqT7k79g0Pco2qyeoervc_jBAY5PV+msC06kQ@mail.gmail.com>
 <CAHrDCuy5Q-Taj2+u5A_2bft75cEuvZn2wjbYnEomCoPu-ZWJ=w@mail.gmail.com>
 <CAJ=56RJxsvWn+zbh_RCExq7LeMPvxQCKahy2oEUhLBo0xPFNHQ@mail.gmail.com>
 <CAFs9qGsdidqX2C_mwKkyBaS6A3K8qp=DCTyF0p3C+AQV2m9oXQ@mail.gmail.com>
Message-ID: <CAKf8g9QvTX9RQ5-1euXF8xfrq-b+o2_f9A6hxSUSnz=4B36F8w@mail.gmail.com>

I think I'm one of the culprits who adds a label without removing
needs-triage.  Usually this is because I'm doing a quick-pass instead of a
close-look, so more eyeballs to take a closer look would still be helpful.
But if that habit is making things harder for others, I'll change it.
Thanks for all your hard work!

On Wed, May 3, 2023 at 6:19?AM Simon Hawkins <simonjayhawkins at gmail.com>
wrote:

> Agree with Richard.
>
> Even if not reported as a regression by the user, I often use to check the
> behaviour of bugs reported on previous versions to double check (Once the
> code sample is pasted into a notebook does not take long to re-run on
> previous versions once setup)
>
> If found to be a regression, I feel a bisect to isolate the commit is a
> worthwhile part of the triage process (and cc the author)
>
> For most issues, IMHO one should only remove the needs triage label if one
> is knowledgeable enough to add a value add comment. Thanking the user,
> clarifying the issue and suggesting an action to allow progress on the
> issue for other readers. (If one is not knowledgeable enough about the
> topic to do this, probably best to leave the needs triage to someone more
> knowledgeable and not add noise.)
>
> I think the actions of just adding additional labels to help others find
> issues should not be considered triage but is also a very
> worthwhile maintenance task.
>
> My two cents
> Simon
>
> On Wed, 3 May 2023 at 13:05, Richard Shadrach <rhshadrach at gmail.com>
> wrote:
>
>> I've always thought triage is more than labeling an issue. If it's a bug,
>> I consider triage as confirming it (a) exists on main (even if the user
>> says they did) and (b) confirming it is indeed undesired behavior. If it's
>> reported as a regression then in addition I think it should be confirmed it
>> does exist on the previous version of pandas.
>>
>> All of this can be time intensive. However, I can quickly go through the
>> recently reported issues and appropriately label them so that they are more
>> visible to other developers who specialize in those areas of the code. When
>> I do this but not the above steps, I leave the Needs Triage on.
>>
>> I'm interested to hear thoughts and feedback here, and if there is a more
>> desirable way.
>>
>> Best,
>> Richard
>>
>>
>>
>> On Wed, May 3, 2023, 06:07 Dea Mar?a <deamarialeon at gmail.com> wrote:
>>
>>> I just meant that in many cases people forget to remove the ?needs
>>> triage? label after having done the triage.
>>>
>>>
>>>
>>> On Wed, May 3, 2023 at 11:43?AM Marc Garcia <garcia.marc at gmail.com>
>>> wrote:
>>>
>>>> Not sure if other set the label manually, but I assumed in most cases
>>>> the label is applied automatically by our issue templates. Regular users
>>>> can't set labels themselves afaik. And if I set labels manually, I consider
>>>> I already did the triage so I don't set that label.
>>>>
>>>> Thanks for letting us know, this is helpful, if you still find the
>>>> issue after the message, it may be worth discussing the workflow with the
>>>> exact person (in the issue log you should be able to see who changes the
>>>> labels.
>>>>
>>>>
>>>>
>>>> On Wed, May 3, 2023, 10:21 Dea Mar?a <deamarialeon at gmail.com> wrote:
>>>>
>>>>> Dear All,
>>>>>
>>>>>
>>>>> If you are helping with triage, it would be nice if you could also
>>>>> remove the ?needs triage? label after labelling the issue.
>>>>>
>>>>>
>>>>> Sometimes the person who reported the issue also sets the labels. So,
>>>>> it is not obvious if the labeling was done by a core-dev or not until I
>>>>> open the issue.
>>>>>
>>>>> Sure, it only takes a few seconds to find that my ?extremely
>>>>> important? help ;-) is not needed. But newcomers? time is also valuable.
>>>>>
>>>>>
>>>>>
>>>>> Please help us help you. :)
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Dea
>>>>> _______________________________________________
>>>>> Pandas-dev mailing list
>>>>> Pandas-dev at python.org
>>>>> https://mail.python.org/mailman/listinfo/pandas-dev
>>>>>
>>>> _______________________________________________
>>> Pandas-dev mailing list
>>> Pandas-dev at python.org
>>> https://mail.python.org/mailman/listinfo/pandas-dev
>>>
>> _______________________________________________
>> Pandas-dev mailing list
>> Pandas-dev at python.org
>> https://mail.python.org/mailman/listinfo/pandas-dev
>>
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20230503/3e0aa9dd/attachment.html>

From m.e.gorelli at gmail.com  Wed May  3 11:09:27 2023
From: m.e.gorelli at gmail.com (Marco Gorelli)
Date: Wed, 3 May 2023 16:09:27 +0100
Subject: [Pandas-dev] Pandas-dev Digest, Vol 120, Issue 2
In-Reply-To: <mailman.552.1683119967.13556.pandas-dev@python.org>
References: <mailman.552.1683119967.13556.pandas-dev@python.org>
Message-ID: <CA+gwkEDdFdigO+trk44V9duCtshsCWKPCGr_WyL5xWMCbzgYhw@mail.gmail.com>

Thanks all for your comments here, some good points have been raised!

The maintainers' guide
<https://pandas.pydata.org/docs/dev/development/maintaining.html> doesn't
have any guidelines around "needs triage", so I'll put something together
based on the points brought up here

On Wed, May 3, 2023 at 2:19?PM <pandas-dev-request at python.org> wrote:

> Send Pandas-dev mailing list submissions to
>         pandas-dev at python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://mail.python.org/mailman/listinfo/pandas-dev
> or, via email, send a message with subject or body 'help' to
>         pandas-dev-request at python.org
>
> You can reach the person managing the list at
>         pandas-dev-owner at python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Pandas-dev digest..."
>
>
> Today's Topics:
>
>    1. Re: Triage (Richard Shadrach)
>    2. Re: Triage (Simon Hawkins)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 3 May 2023 08:05:18 -0400
> From: Richard Shadrach <rhshadrach at gmail.com>
> To: Dea Mar?a <deamarialeon at gmail.com>
> Cc: Marc Garcia <garcia.marc at gmail.com>, pandas-dev
>         <pandas-dev at python.org>
> Subject: Re: [Pandas-dev] Triage
> Message-ID:
>         <CAJ=
> 56RJxsvWn+zbh_RCExq7LeMPvxQCKahy2oEUhLBo0xPFNHQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I've always thought triage is more than labeling an issue. If it's a bug, I
> consider triage as confirming it (a) exists on main (even if the user says
> they did) and (b) confirming it is indeed undesired behavior. If it's
> reported as a regression then in addition I think it should be confirmed it
> does exist on the previous version of pandas.
>
> All of this can be time intensive. However, I can quickly go through the
> recently reported issues and appropriately label them so that they are more
> visible to other developers who specialize in those areas of the code. When
> I do this but not the above steps, I leave the Needs Triage on.
>
> I'm interested to hear thoughts and feedback here, and if there is a more
> desirable way.
>
> Best,
> Richard
>
>
>
> On Wed, May 3, 2023, 06:07 Dea Mar?a <deamarialeon at gmail.com> wrote:
>
> > I just meant that in many cases people forget to remove the ?needs
> triage?
> > label after having done the triage.
> >
> >
> >
> > On Wed, May 3, 2023 at 11:43?AM Marc Garcia <garcia.marc at gmail.com>
> wrote:
> >
> >> Not sure if other set the label manually, but I assumed in most cases
> the
> >> label is applied automatically by our issue templates. Regular users
> can't
> >> set labels themselves afaik. And if I set labels manually, I consider I
> >> already did the triage so I don't set that label.
> >>
> >> Thanks for letting us know, this is helpful, if you still find the issue
> >> after the message, it may be worth discussing the workflow with the
> exact
> >> person (in the issue log you should be able to see who changes the
> labels.
> >>
> >>
> >>
> >> On Wed, May 3, 2023, 10:21 Dea Mar?a <deamarialeon at gmail.com> wrote:
> >>
> >>> Dear All,
> >>>
> >>>
> >>> If you are helping with triage, it would be nice if you could also
> >>> remove the ?needs triage? label after labelling the issue.
> >>>
> >>>
> >>> Sometimes the person who reported the issue also sets the labels. So,
> it
> >>> is not obvious if the labeling was done by a core-dev or not until I
> open
> >>> the issue.
> >>>
> >>> Sure, it only takes a few seconds to find that my ?extremely important?
> >>> help ;-) is not needed. But newcomers? time is also valuable.
> >>>
> >>>
> >>> Please help us help you. :)
> >>>
> >>>
> >>> Thanks,
> >>>
> >>> Dea
> >>> _______________________________________________
> >>> Pandas-dev mailing list
> >>> Pandas-dev at python.org
> >>> https://mail.python.org/mailman/listinfo/pandas-dev
> >>>
> >> _______________________________________________
> > Pandas-dev mailing list
> > Pandas-dev at python.org
> > https://mail.python.org/mailman/listinfo/pandas-dev
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://mail.python.org/pipermail/pandas-dev/attachments/20230503/7da68893/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Wed, 3 May 2023 14:19:14 +0100
> From: Simon Hawkins <simonjayhawkins at gmail.com>
> To: Richard Shadrach <rhshadrach at gmail.com>
> Cc: Dea Mar?a <deamarialeon at gmail.com>, pandas-dev
>         <pandas-dev at python.org>
> Subject: Re: [Pandas-dev] Triage
> Message-ID:
>         <CAFs9qGsdidqX2C_mwKkyBaS6A3K8qp=
> DCTyF0p3C+AQV2m9oXQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Agree with Richard.
>
> Even if not reported as a regression by the user, I often use to check the
> behaviour of bugs reported on previous versions to double check (Once the
> code sample is pasted into a notebook does not take long to re-run on
> previous versions once setup)
>
> If found to be a regression, I feel a bisect to isolate the commit is a
> worthwhile part of the triage process (and cc the author)
>
> For most issues, IMHO one should only remove the needs triage label if one
> is knowledgeable enough to add a value add comment. Thanking the user,
> clarifying the issue and suggesting an action to allow progress on the
> issue for other readers. (If one is not knowledgeable enough about the
> topic to do this, probably best to leave the needs triage to someone more
> knowledgeable and not add noise.)
>
> I think the actions of just adding additional labels to help others find
> issues should not be considered triage but is also a very
> worthwhile maintenance task.
>
> My two cents
> Simon
>
> On Wed, 3 May 2023 at 13:05, Richard Shadrach <rhshadrach at gmail.com>
> wrote:
>
> > I've always thought triage is more than labeling an issue. If it's a bug,
> > I consider triage as confirming it (a) exists on main (even if the user
> > says they did) and (b) confirming it is indeed undesired behavior. If
> it's
> > reported as a regression then in addition I think it should be confirmed
> it
> > does exist on the previous version of pandas.
> >
> > All of this can be time intensive. However, I can quickly go through the
> > recently reported issues and appropriately label them so that they are
> more
> > visible to other developers who specialize in those areas of the code.
> When
> > I do this but not the above steps, I leave the Needs Triage on.
> >
> > I'm interested to hear thoughts and feedback here, and if there is a more
> > desirable way.
> >
> > Best,
> > Richard
> >
> >
> >
> > On Wed, May 3, 2023, 06:07 Dea Mar?a <deamarialeon at gmail.com> wrote:
> >
> >> I just meant that in many cases people forget to remove the ?needs
> >> triage? label after having done the triage.
> >>
> >>
> >>
> >> On Wed, May 3, 2023 at 11:43?AM Marc Garcia <garcia.marc at gmail.com>
> >> wrote:
> >>
> >>> Not sure if other set the label manually, but I assumed in most cases
> >>> the label is applied automatically by our issue templates. Regular
> users
> >>> can't set labels themselves afaik. And if I set labels manually, I
> consider
> >>> I already did the triage so I don't set that label.
> >>>
> >>> Thanks for letting us know, this is helpful, if you still find the
> issue
> >>> after the message, it may be worth discussing the workflow with the
> exact
> >>> person (in the issue log you should be able to see who changes the
> labels.
> >>>
> >>>
> >>>
> >>> On Wed, May 3, 2023, 10:21 Dea Mar?a <deamarialeon at gmail.com> wrote:
> >>>
> >>>> Dear All,
> >>>>
> >>>>
> >>>> If you are helping with triage, it would be nice if you could also
> >>>> remove the ?needs triage? label after labelling the issue.
> >>>>
> >>>>
> >>>> Sometimes the person who reported the issue also sets the labels. So,
> >>>> it is not obvious if the labeling was done by a core-dev or not until
> I
> >>>> open the issue.
> >>>>
> >>>> Sure, it only takes a few seconds to find that my ?extremely
> important?
> >>>> help ;-) is not needed. But newcomers? time is also valuable.
> >>>>
> >>>>
> >>>> Please help us help you. :)
> >>>>
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Dea
> >>>> _______________________________________________
> >>>> Pandas-dev mailing list
> >>>> Pandas-dev at python.org
> >>>> https://mail.python.org/mailman/listinfo/pandas-dev
> >>>>
> >>> _______________________________________________
> >> Pandas-dev mailing list
> >> Pandas-dev at python.org
> >> https://mail.python.org/mailman/listinfo/pandas-dev
> >>
> > _______________________________________________
> > Pandas-dev mailing list
> > Pandas-dev at python.org
> > https://mail.python.org/mailman/listinfo/pandas-dev
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://mail.python.org/pipermail/pandas-dev/attachments/20230503/fdb6cd38/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
>
>
> ------------------------------
>
> End of Pandas-dev Digest, Vol 120, Issue 2
> ******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20230503/6590b0c5/attachment-0001.html>

From simonjayhawkins at gmail.com  Thu May  4 06:27:32 2023
From: simonjayhawkins at gmail.com (Simon Hawkins)
Date: Thu, 4 May 2023 11:27:32 +0100
Subject: [Pandas-dev] Pandas-dev Digest, Vol 120, Issue 2
In-Reply-To: <CA+gwkEDdFdigO+trk44V9duCtshsCWKPCGr_WyL5xWMCbzgYhw@mail.gmail.com>
References: <mailman.552.1683119967.13556.pandas-dev@python.org>
 <CA+gwkEDdFdigO+trk44V9duCtshsCWKPCGr_WyL5xWMCbzgYhw@mail.gmail.com>
Message-ID: <CAFs9qGsk0bC2q6ccBSuwGMuQ6Lrm2nQM_d8cuiUV+2Wy1sXGDA@mail.gmail.com>

Maybe worth expanding on confirming the bug bit... If a bug is in recently
added behaviour, then probably worth cc the author of the enhancement
otherwise if the bug looks to be long-standing, then chances are that it
has been reported before or that something related has been discussed.
Although it can be time consuming to search/review other issues during the
triage process (and sometimes a rabbit hole), closing duplicates or
consolidation of issues is worthwhile.

On Wed, 3 May 2023 at 16:10, Marco Gorelli <m.e.gorelli at gmail.com> wrote:

> Thanks all for your comments here, some good points have been raised!
>
> The maintainers' guide
> <https://pandas.pydata.org/docs/dev/development/maintaining.html> doesn't
> have any guidelines around "needs triage", so I'll put something together
> based on the points brought up here
>
> On Wed, May 3, 2023 at 2:19?PM <pandas-dev-request at python.org> wrote:
>
>> Send Pandas-dev mailing list submissions to
>>         pandas-dev at python.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>         https://mail.python.org/mailman/listinfo/pandas-dev
>> or, via email, send a message with subject or body 'help' to
>>         pandas-dev-request at python.org
>>
>> You can reach the person managing the list at
>>         pandas-dev-owner at python.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Pandas-dev digest..."
>>
>>
>> Today's Topics:
>>
>>    1. Re: Triage (Richard Shadrach)
>>    2. Re: Triage (Simon Hawkins)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Wed, 3 May 2023 08:05:18 -0400
>> From: Richard Shadrach <rhshadrach at gmail.com>
>> To: Dea Mar?a <deamarialeon at gmail.com>
>> Cc: Marc Garcia <garcia.marc at gmail.com>, pandas-dev
>>         <pandas-dev at python.org>
>> Subject: Re: [Pandas-dev] Triage
>> Message-ID:
>>         <CAJ=
>> 56RJxsvWn+zbh_RCExq7LeMPvxQCKahy2oEUhLBo0xPFNHQ at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> I've always thought triage is more than labeling an issue. If it's a bug,
>> I
>> consider triage as confirming it (a) exists on main (even if the user says
>> they did) and (b) confirming it is indeed undesired behavior. If it's
>> reported as a regression then in addition I think it should be confirmed
>> it
>> does exist on the previous version of pandas.
>>
>> All of this can be time intensive. However, I can quickly go through the
>> recently reported issues and appropriately label them so that they are
>> more
>> visible to other developers who specialize in those areas of the code.
>> When
>> I do this but not the above steps, I leave the Needs Triage on.
>>
>> I'm interested to hear thoughts and feedback here, and if there is a more
>> desirable way.
>>
>> Best,
>> Richard
>>
>>
>>
>> On Wed, May 3, 2023, 06:07 Dea Mar?a <deamarialeon at gmail.com> wrote:
>>
>> > I just meant that in many cases people forget to remove the ?needs
>> triage?
>> > label after having done the triage.
>> >
>> >
>> >
>> > On Wed, May 3, 2023 at 11:43?AM Marc Garcia <garcia.marc at gmail.com>
>> wrote:
>> >
>> >> Not sure if other set the label manually, but I assumed in most cases
>> the
>> >> label is applied automatically by our issue templates. Regular users
>> can't
>> >> set labels themselves afaik. And if I set labels manually, I consider I
>> >> already did the triage so I don't set that label.
>> >>
>> >> Thanks for letting us know, this is helpful, if you still find the
>> issue
>> >> after the message, it may be worth discussing the workflow with the
>> exact
>> >> person (in the issue log you should be able to see who changes the
>> labels.
>> >>
>> >>
>> >>
>> >> On Wed, May 3, 2023, 10:21 Dea Mar?a <deamarialeon at gmail.com> wrote:
>> >>
>> >>> Dear All,
>> >>>
>> >>>
>> >>> If you are helping with triage, it would be nice if you could also
>> >>> remove the ?needs triage? label after labelling the issue.
>> >>>
>> >>>
>> >>> Sometimes the person who reported the issue also sets the labels. So,
>> it
>> >>> is not obvious if the labeling was done by a core-dev or not until I
>> open
>> >>> the issue.
>> >>>
>> >>> Sure, it only takes a few seconds to find that my ?extremely
>> important?
>> >>> help ;-) is not needed. But newcomers? time is also valuable.
>> >>>
>> >>>
>> >>> Please help us help you. :)
>> >>>
>> >>>
>> >>> Thanks,
>> >>>
>> >>> Dea
>> >>> _______________________________________________
>> >>> Pandas-dev mailing list
>> >>> Pandas-dev at python.org
>> >>> https://mail.python.org/mailman/listinfo/pandas-dev
>> >>>
>> >> _______________________________________________
>> > Pandas-dev mailing list
>> > Pandas-dev at python.org
>> > https://mail.python.org/mailman/listinfo/pandas-dev
>> >
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> https://mail.python.org/pipermail/pandas-dev/attachments/20230503/7da68893/attachment-0001.html
>> >
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Wed, 3 May 2023 14:19:14 +0100
>> From: Simon Hawkins <simonjayhawkins at gmail.com>
>> To: Richard Shadrach <rhshadrach at gmail.com>
>> Cc: Dea Mar?a <deamarialeon at gmail.com>, pandas-dev
>>         <pandas-dev at python.org>
>> Subject: Re: [Pandas-dev] Triage
>> Message-ID:
>>         <CAFs9qGsdidqX2C_mwKkyBaS6A3K8qp=
>> DCTyF0p3C+AQV2m9oXQ at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Agree with Richard.
>>
>> Even if not reported as a regression by the user, I often use to check the
>> behaviour of bugs reported on previous versions to double check (Once the
>> code sample is pasted into a notebook does not take long to re-run on
>> previous versions once setup)
>>
>> If found to be a regression, I feel a bisect to isolate the commit is a
>> worthwhile part of the triage process (and cc the author)
>>
>> For most issues, IMHO one should only remove the needs triage label if one
>> is knowledgeable enough to add a value add comment. Thanking the user,
>> clarifying the issue and suggesting an action to allow progress on the
>> issue for other readers. (If one is not knowledgeable enough about the
>> topic to do this, probably best to leave the needs triage to someone more
>> knowledgeable and not add noise.)
>>
>> I think the actions of just adding additional labels to help others find
>> issues should not be considered triage but is also a very
>> worthwhile maintenance task.
>>
>> My two cents
>> Simon
>>
>> On Wed, 3 May 2023 at 13:05, Richard Shadrach <rhshadrach at gmail.com>
>> wrote:
>>
>> > I've always thought triage is more than labeling an issue. If it's a
>> bug,
>> > I consider triage as confirming it (a) exists on main (even if the user
>> > says they did) and (b) confirming it is indeed undesired behavior. If
>> it's
>> > reported as a regression then in addition I think it should be
>> confirmed it
>> > does exist on the previous version of pandas.
>> >
>> > All of this can be time intensive. However, I can quickly go through the
>> > recently reported issues and appropriately label them so that they are
>> more
>> > visible to other developers who specialize in those areas of the code.
>> When
>> > I do this but not the above steps, I leave the Needs Triage on.
>> >
>> > I'm interested to hear thoughts and feedback here, and if there is a
>> more
>> > desirable way.
>> >
>> > Best,
>> > Richard
>> >
>> >
>> >
>> > On Wed, May 3, 2023, 06:07 Dea Mar?a <deamarialeon at gmail.com> wrote:
>> >
>> >> I just meant that in many cases people forget to remove the ?needs
>> >> triage? label after having done the triage.
>> >>
>> >>
>> >>
>> >> On Wed, May 3, 2023 at 11:43?AM Marc Garcia <garcia.marc at gmail.com>
>> >> wrote:
>> >>
>> >>> Not sure if other set the label manually, but I assumed in most cases
>> >>> the label is applied automatically by our issue templates. Regular
>> users
>> >>> can't set labels themselves afaik. And if I set labels manually, I
>> consider
>> >>> I already did the triage so I don't set that label.
>> >>>
>> >>> Thanks for letting us know, this is helpful, if you still find the
>> issue
>> >>> after the message, it may be worth discussing the workflow with the
>> exact
>> >>> person (in the issue log you should be able to see who changes the
>> labels.
>> >>>
>> >>>
>> >>>
>> >>> On Wed, May 3, 2023, 10:21 Dea Mar?a <deamarialeon at gmail.com> wrote:
>> >>>
>> >>>> Dear All,
>> >>>>
>> >>>>
>> >>>> If you are helping with triage, it would be nice if you could also
>> >>>> remove the ?needs triage? label after labelling the issue.
>> >>>>
>> >>>>
>> >>>> Sometimes the person who reported the issue also sets the labels. So,
>> >>>> it is not obvious if the labeling was done by a core-dev or not
>> until I
>> >>>> open the issue.
>> >>>>
>> >>>> Sure, it only takes a few seconds to find that my ?extremely
>> important?
>> >>>> help ;-) is not needed. But newcomers? time is also valuable.
>> >>>>
>> >>>>
>> >>>> Please help us help you. :)
>> >>>>
>> >>>>
>> >>>> Thanks,
>> >>>>
>> >>>> Dea
>> >>>> _______________________________________________
>> >>>> Pandas-dev mailing list
>> >>>> Pandas-dev at python.org
>> >>>> https://mail.python.org/mailman/listinfo/pandas-dev
>> >>>>
>> >>> _______________________________________________
>> >> Pandas-dev mailing list
>> >> Pandas-dev at python.org
>> >> https://mail.python.org/mailman/listinfo/pandas-dev
>> >>
>> > _______________________________________________
>> > Pandas-dev mailing list
>> > Pandas-dev at python.org
>> > https://mail.python.org/mailman/listinfo/pandas-dev
>> >
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> https://mail.python.org/pipermail/pandas-dev/attachments/20230503/fdb6cd38/attachment.html
>> >
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> Pandas-dev mailing list
>> Pandas-dev at python.org
>> https://mail.python.org/mailman/listinfo/pandas-dev
>>
>>
>> ------------------------------
>>
>> End of Pandas-dev Digest, Vol 120, Issue 2
>> ******************************************
>>
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20230504/e321d3e6/attachment-0001.html>

From lele.venturi at gmail.com  Thu May 18 16:46:35 2023
From: lele.venturi at gmail.com (Gabriele Venturi)
Date: Thu, 18 May 2023 22:46:35 +0200
Subject: [Pandas-dev] PandasAI
In-Reply-To: <7a7995ed-a530-49dc-a915-8e76c21ed235@Spark>
References: <7a7995ed-a530-49dc-a915-8e76c21ed235@Spark>
Message-ID: <8c7446de-d5c2-4252-a0aa-4f4ecdccb555@Spark>

Dear sirs,
let me introduce myself. I?m Gabriele, author of PandasAI, a library that aims to wrap pandas in a conversational layer.

I?m reaching out to you since yesterday a GitHub user pointed out that calling the repo ?PandasAI? could be considered unethical or misleading. When I launched the library, I just picked the most obvious name: since I was adding AI on the top of the pandas library, PandasAI just made a lot of sense to me.

However, I don?t want to offend anyone or being unethical, this has never been the idea. That?s why I?m reaching out to you. I?d love to get your feedback about it, and if you believe the name has to be changed, I can definitely rename it.

Thanks a lot for your time.

Best,

Gabriele
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20230518/db478947/attachment.html>

From bhasha03 at outlook.com  Thu May 18 11:04:08 2023
From: bhasha03 at outlook.com (Bhavani Shankar)
Date: Thu, 18 May 2023 15:04:08 +0000
Subject: [Pandas-dev] Typo in the documentation
Message-ID: <DS7PR19MB5877DBEF9722BA302D516AE1CE7F9@DS7PR19MB5877.namprd19.prod.outlook.com>


Hi,

In the section:
?How do I select specific rows and columns from a DataFrame?

In the following snippet the value 3 means 4th column.:

In [26]: titanic.iloc[0:3, 3] = "anonymous"

But in the sentence ?When selecting specific rows and/or columns with loc or iloc, new values can be assigned to the selected data. For example, to assign the name anonymous to the first 3 elements of the third column:? . The word highlighted in bold talks about 3rd column. Please correct it. Thank you.

Best Regards,
Bhavani Shankar.

Ref: How do I select a subset of a DataFrame? ? pandas 2.0.1 documentation (pydata.org)<https://pandas.pydata.org/docs/getting_started/intro_tutorials/03_subset_data.html>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20230518/451690cb/attachment.html>

From garcia.marc at gmail.com  Wed May 24 11:46:41 2023
From: garcia.marc at gmail.com (Marc Garcia)
Date: Wed, 24 May 2023 18:46:41 +0300
Subject: [Pandas-dev] Typo in the documentation
In-Reply-To: <DS7PR19MB5877DBEF9722BA302D516AE1CE7F9@DS7PR19MB5877.namprd19.prod.outlook.com>
References: <DS7PR19MB5877DBEF9722BA302D516AE1CE7F9@DS7PR19MB5877.namprd19.prod.outlook.com>
Message-ID: <CAEk5N5v1fzqw9W6OCTfgb62MmuU1xy6Mqf7RkKg+Zss6mdvYHQ@mail.gmail.com>

Thanks for the report Bhavani. Do you mind sending the report via a GitHub
issue? That way it's easier for us to get it assigned to someone and fix
it: https://github.com/pandas-dev/pandas/issues/new/choose

Thank you!

On Wed, May 24, 2023, 15:13 Bhavani Shankar <bhasha03 at outlook.com> wrote:

>
>
> Hi,
>
>
> In the section:
> *?How do I select specific rows and columns from a **DataFrame**?*
>
>
>
> In the following snippet the value * 3* means 4th column.:
>
>
>
> *In [26]: titanic.iloc[0:3, 3] = "anonymous"*
>
>
>
> But in the sentence ?When selecting specific rows and/or columns with loc
>  or iloc, new values can be assigned to the selected data. For example,
> to assign the name anonymous to the first 3 elements of the *third*
> column:? . The word highlighted in bold talks about 3rd column. Please
> correct it. Thank you.
>
>
>
> Best Regards,
>
> Bhavani Shankar.
>
>
>
> Ref: How do I select a subset of a DataFrame? ? pandas 2.0.1
> documentation (pydata.org)
> <https://pandas.pydata.org/docs/getting_started/intro_tutorials/03_subset_data.html>
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20230524/6cf80e11/attachment-0001.html>

From garcia.marc at gmail.com  Wed May 24 11:54:13 2023
From: garcia.marc at gmail.com (Marc Garcia)
Date: Wed, 24 May 2023 18:54:13 +0300
Subject: [Pandas-dev] PandasAI
In-Reply-To: <8c7446de-d5c2-4252-a0aa-4f4ecdccb555@Spark>
References: <7a7995ed-a530-49dc-a915-8e76c21ed235@Spark>
 <8c7446de-d5c2-4252-a0aa-4f4ecdccb555@Spark>
Message-ID: <CAEk5N5s0tWaoAf9WKjRz-Vf4NzZDVdQbDKpC37cp44aJdut93w@mail.gmail.com>

Thanks Gabriele for letting us know. The pandas trademark is managed by the
NumFOCUS non-profit. The name can be used with what is called fair use,
which summarized means that you reference to the project, but do not imply
affiliation or endorsement.

The way you're using pandas doesn't personally bother me, but it's the
legal team at NumFOCUS who will be sending you a notification about a
trademark violation if applies. So, I think it's better if you can ask them
directly at info at numfocus.org, since I don't really know if this case it's
fair use or not.

Cheers!

On Wed, May 24, 2023, 15:12 Gabriele Venturi <lele.venturi at gmail.com> wrote:

> Dear sirs,
> let me introduce myself. I?m Gabriele, author of PandasAI, a library that
> aims to wrap pandas in a conversational layer.
>
> I?m reaching out to you since yesterday a GitHub user pointed out that
> calling the repo ?PandasAI? could be considered unethical or misleading.
> When I launched the library, I just picked the most obvious name: since I
> was adding AI on the top of the pandas library, PandasAI just made a lot of
> sense to me.
>
> However, I don?t want to offend anyone or being unethical, this has never
> been the idea. That?s why I?m reaching out to you. I?d love to get your
> feedback about it, and if you believe the name has to be changed, I can
> definitely rename it.
>
> Thanks a lot for your time.
>
> Best,
>
> *Gabriele*
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20230524/7fd5b16a/attachment.html>

From garcia.marc at gmail.com  Mon May 29 04:25:56 2023
From: garcia.marc at gmail.com (Marc Garcia)
Date: Mon, 29 May 2023 12:25:56 +0400
Subject: [Pandas-dev] ANN: pandas v2.0.2
Message-ID: <CAEk5N5vzq9z1TU6CQqz3yzbRUYH3Yx5tbu9E4PXuPhJzn=cE_A@mail.gmail.com>

We are pleased to announce the release of pandas v2.0.2.

This is a patch release in the 2.0.x series and includes some regression
fixes and bug fixes. We recommend that all users in the 2.0.x series
upgrade to this version.

See the release notes <https://pandas.pydata.org/docs/whatsnew/v2.0.2.html> for
a list of all the changes.

The release can be installed from PyPI

    python -m pip install --upgrade pandas==2.0.2

Or from conda-forge

    mamba install -c conda-forge pandas==2.0.2

Please report any issues with the release on the pandas issue tracker
<https://github.com/pandas-dev/pandas/issues/new/choose>.

Thanks to all the contributors
<https://pandas.pydata.org/docs/whatsnew/v2.0.2.html#contributors> who made
this release possible.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20230529/3148eff9/attachment.html>

From lele.venturi at gmail.com  Mon May 29 10:17:04 2023
From: lele.venturi at gmail.com (Gabriele Venturi)
Date: Mon, 29 May 2023 16:17:04 +0200
Subject: [Pandas-dev] PandasAI
In-Reply-To: <CAEk5N5s0tWaoAf9WKjRz-Vf4NzZDVdQbDKpC37cp44aJdut93w@mail.gmail.com>
References: <7a7995ed-a530-49dc-a915-8e76c21ed235@Spark>
 <8c7446de-d5c2-4252-a0aa-4f4ecdccb555@Spark>
 <CAEk5N5s0tWaoAf9WKjRz-Vf4NzZDVdQbDKpC37cp44aJdut93w@mail.gmail.com>
Message-ID: <946abffc-8025-4f3a-9e61-e196dd1aa865@Spark>

Dear Marc,

thanks a lot for the kind feedback. I?ve just reach out to them and asked more information.

Thank you so much for your time once again!

Best,

Gabriele
On 24 May 2023, 17:54 +0200, Marc Garcia <garcia.marc at gmail.com>, wrote:
> Thanks Gabriele for letting us know. The pandas trademark is managed by the NumFOCUS non-profit. The name can be used with what is called fair use, which summarized means that you reference to the project, but do not imply affiliation or endorsement.
>
> The way you're using pandas doesn't personally bother me, but it's the legal team at NumFOCUS who will be sending you a notification about a trademark violation if applies. So, I think it's better if you can ask them directly at info at numfocus.org, since I don't really know if this case it's fair use or not.
>
> Cheers!
>
> > On Wed, May 24, 2023, 15:12 Gabriele Venturi <lele.venturi at gmail.com> wrote:
> > > Dear sirs,
> > > let me introduce myself. I?m Gabriele, author of PandasAI, a library that aims to wrap pandas in a conversational layer.
> > >
> > > I?m reaching out to you since yesterday a GitHub user pointed out that calling the repo ?PandasAI? could be considered unethical or misleading. When I launched the library, I just picked the most obvious name: since I was adding AI on the top of the pandas library, PandasAI just made a lot of sense to me.
> > >
> > > However, I don?t want to offend anyone or being unethical, this has never been the idea. That?s why I?m reaching out to you. I?d love to get your feedback about it, and if you believe the name has to be changed, I can definitely rename it.
> > >
> > > Thanks a lot for your time.
> > >
> > > Best,
> > >
> > > Gabriele
> > > _______________________________________________
> > > Pandas-dev mailing list
> > > Pandas-dev at python.org
> > > https://mail.python.org/mailman/listinfo/pandas-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20230529/ece6083f/attachment.html>