You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Antoine Pitrou <an...@python.org> on 2020/02/19 09:24:04 UTC
Python 2.7 support removed
Hello,
Following the previous discussions on this mailing-list, we have
entirely removed Python 2.7 support from the codebase (see ARROW-5757 on
JIRA). This deleted a lot of compatibility code that was spread around
the C++ and Python codebases.
As a reminder, Python 2.7 has stopped being supported by the upstream
CPython project (symbolically, a last 2.7 release will be made around
the next PyCon US, in April).
PyArrow now supports Python versions from 3.5 to 3.8, but there's also
an issue open to remove 3.5 support: see ARROW-5679 on JIRA.
Regards
Antoine.
Re: Python 2.7 support removed
Posted by Wes McKinney <we...@gmail.com>.
Perhaps we can make one more major release with 3.5 and then drop. 3.5
is the default in some Linux distributions so there is some value in
getting a reasonably up-to-date wheel when using the system python-pip
On Wed, Feb 26, 2020 at 6:21 AM Antoine Pitrou <an...@python.org> wrote:
>
>
> I would also be in favour of dropping 3.5, though it's much less costly
> to support it than to support 2.7.
>
> Regards
>
> Antoine.
>
>
> Le 26/02/2020 à 13:17, Krisztián Szűcs a écrit :
> > I'm not sure whether we have a decision on dropping support for python 3.5
> > or not, but the python 3.5 wheels are failing because of recent patches, see
> > https://issues.apache.org/jira/browse/ARROW-7936.
> >
> > We have another issue about dropping python 3.5 support:
> > https://issues.apache.org/jira/browse/ARROW-5679
> >
> > We should either drop support for 3.5 or fix ARROW-7936, personally I'd
> > prefer the former to reduce the maintenance cost for the wheels.
> >
> > Opinions?
> >
> > Regards, Krisztian
> >
> >
> > On Thu, Feb 20, 2020 at 9:56 AM Antoine Pitrou <an...@python.org> wrote:
> >>
> >>
> >> Hi Micah,
> >>
> >> Unlike 2.7, it's not onerous at all, so we can definitely maintain it
> >> for a couple more months if desired.
> >>
> >> Regards
> >>
> >> Antoine.
> >>
> >>
> >> Le 20/02/2020 à 04:47, Micah Kornfield a écrit :
> >>> Hi Antoine,
> >>> Do you have a timeline for the 3.5 support? If possible could it maybe
> >>> wait until after the next release or has it become onerous to maintain?
> >>>
> >>> Thanks,
> >>> Micah
> >>>
> >>> On Wed, Feb 19, 2020 at 1:24 AM Antoine Pitrou <an...@python.org> wrote:
> >>>
> >>>>
> >>>> Hello,
> >>>>
> >>>> Following the previous discussions on this mailing-list, we have
> >>>> entirely removed Python 2.7 support from the codebase (see ARROW-5757 on
> >>>> JIRA). This deleted a lot of compatibility code that was spread around
> >>>> the C++ and Python codebases.
> >>>>
> >>>> As a reminder, Python 2.7 has stopped being supported by the upstream
> >>>> CPython project (symbolically, a last 2.7 release will be made around
> >>>> the next PyCon US, in April).
> >>>>
> >>>> PyArrow now supports Python versions from 3.5 to 3.8, but there's also
> >>>> an issue open to remove 3.5 support: see ARROW-5679 on JIRA.
> >>>>
> >>>> Regards
> >>>>
> >>>> Antoine.
> >>>>
> >>>
Re: Python 2.7 support removed
Posted by Antoine Pitrou <an...@python.org>.
I would also be in favour of dropping 3.5, though it's much less costly
to support it than to support 2.7.
Regards
Antoine.
Le 26/02/2020 à 13:17, Krisztián Szűcs a écrit :
> I'm not sure whether we have a decision on dropping support for python 3.5
> or not, but the python 3.5 wheels are failing because of recent patches, see
> https://issues.apache.org/jira/browse/ARROW-7936.
>
> We have another issue about dropping python 3.5 support:
> https://issues.apache.org/jira/browse/ARROW-5679
>
> We should either drop support for 3.5 or fix ARROW-7936, personally I'd
> prefer the former to reduce the maintenance cost for the wheels.
>
> Opinions?
>
> Regards, Krisztian
>
>
> On Thu, Feb 20, 2020 at 9:56 AM Antoine Pitrou <an...@python.org> wrote:
>>
>>
>> Hi Micah,
>>
>> Unlike 2.7, it's not onerous at all, so we can definitely maintain it
>> for a couple more months if desired.
>>
>> Regards
>>
>> Antoine.
>>
>>
>> Le 20/02/2020 à 04:47, Micah Kornfield a écrit :
>>> Hi Antoine,
>>> Do you have a timeline for the 3.5 support? If possible could it maybe
>>> wait until after the next release or has it become onerous to maintain?
>>>
>>> Thanks,
>>> Micah
>>>
>>> On Wed, Feb 19, 2020 at 1:24 AM Antoine Pitrou <an...@python.org> wrote:
>>>
>>>>
>>>> Hello,
>>>>
>>>> Following the previous discussions on this mailing-list, we have
>>>> entirely removed Python 2.7 support from the codebase (see ARROW-5757 on
>>>> JIRA). This deleted a lot of compatibility code that was spread around
>>>> the C++ and Python codebases.
>>>>
>>>> As a reminder, Python 2.7 has stopped being supported by the upstream
>>>> CPython project (symbolically, a last 2.7 release will be made around
>>>> the next PyCon US, in April).
>>>>
>>>> PyArrow now supports Python versions from 3.5 to 3.8, but there's also
>>>> an issue open to remove 3.5 support: see ARROW-5679 on JIRA.
>>>>
>>>> Regards
>>>>
>>>> Antoine.
>>>>
>>>
Re: Python 2.7 support removed
Posted by Krisztián Szűcs <sz...@gmail.com>.
I'm not sure whether we have a decision on dropping support for python 3.5
or not, but the python 3.5 wheels are failing because of recent patches, see
https://issues.apache.org/jira/browse/ARROW-7936.
We have another issue about dropping python 3.5 support:
https://issues.apache.org/jira/browse/ARROW-5679
We should either drop support for 3.5 or fix ARROW-7936, personally I'd
prefer the former to reduce the maintenance cost for the wheels.
Opinions?
Regards, Krisztian
On Thu, Feb 20, 2020 at 9:56 AM Antoine Pitrou <an...@python.org> wrote:
>
>
> Hi Micah,
>
> Unlike 2.7, it's not onerous at all, so we can definitely maintain it
> for a couple more months if desired.
>
> Regards
>
> Antoine.
>
>
> Le 20/02/2020 à 04:47, Micah Kornfield a écrit :
> > Hi Antoine,
> > Do you have a timeline for the 3.5 support? If possible could it maybe
> > wait until after the next release or has it become onerous to maintain?
> >
> > Thanks,
> > Micah
> >
> > On Wed, Feb 19, 2020 at 1:24 AM Antoine Pitrou <an...@python.org> wrote:
> >
> >>
> >> Hello,
> >>
> >> Following the previous discussions on this mailing-list, we have
> >> entirely removed Python 2.7 support from the codebase (see ARROW-5757 on
> >> JIRA). This deleted a lot of compatibility code that was spread around
> >> the C++ and Python codebases.
> >>
> >> As a reminder, Python 2.7 has stopped being supported by the upstream
> >> CPython project (symbolically, a last 2.7 release will be made around
> >> the next PyCon US, in April).
> >>
> >> PyArrow now supports Python versions from 3.5 to 3.8, but there's also
> >> an issue open to remove 3.5 support: see ARROW-5679 on JIRA.
> >>
> >> Regards
> >>
> >> Antoine.
> >>
> >
Re: Python 2.7 support removed
Posted by Antoine Pitrou <an...@python.org>.
Hi Micah,
Unlike 2.7, it's not onerous at all, so we can definitely maintain it
for a couple more months if desired.
Regards
Antoine.
Le 20/02/2020 à 04:47, Micah Kornfield a écrit :
> Hi Antoine,
> Do you have a timeline for the 3.5 support? If possible could it maybe
> wait until after the next release or has it become onerous to maintain?
>
> Thanks,
> Micah
>
> On Wed, Feb 19, 2020 at 1:24 AM Antoine Pitrou <an...@python.org> wrote:
>
>>
>> Hello,
>>
>> Following the previous discussions on this mailing-list, we have
>> entirely removed Python 2.7 support from the codebase (see ARROW-5757 on
>> JIRA). This deleted a lot of compatibility code that was spread around
>> the C++ and Python codebases.
>>
>> As a reminder, Python 2.7 has stopped being supported by the upstream
>> CPython project (symbolically, a last 2.7 release will be made around
>> the next PyCon US, in April).
>>
>> PyArrow now supports Python versions from 3.5 to 3.8, but there's also
>> an issue open to remove 3.5 support: see ARROW-5679 on JIRA.
>>
>> Regards
>>
>> Antoine.
>>
>
Re: Python 2.7 support removed
Posted by Micah Kornfield <em...@gmail.com>.
Hi Antoine,
Do you have a timeline for the 3.5 support? If possible could it maybe
wait until after the next release or has it become onerous to maintain?
Thanks,
Micah
On Wed, Feb 19, 2020 at 1:24 AM Antoine Pitrou <an...@python.org> wrote:
>
> Hello,
>
> Following the previous discussions on this mailing-list, we have
> entirely removed Python 2.7 support from the codebase (see ARROW-5757 on
> JIRA). This deleted a lot of compatibility code that was spread around
> the C++ and Python codebases.
>
> As a reminder, Python 2.7 has stopped being supported by the upstream
> CPython project (symbolically, a last 2.7 release will be made around
> the next PyCon US, in April).
>
> PyArrow now supports Python versions from 3.5 to 3.8, but there's also
> an issue open to remove 3.5 support: see ARROW-5679 on JIRA.
>
> Regards
>
> Antoine.
>