Note that the last bug-fix release of Python 3.6 already happened at 2018-12-11 (3.6.8 release), and since then it's only supported for source-only and security-only releases.
But agreed with Antoine that it's currently not a big burden to keep Python 3.6 a bit longer. With the change of the release cadence of Python to annual releases (while they are still supported for 5 years for security fixes, as is the case now), this does mean more python versions to test against, though, if we keep supporting them the full 5 year in the future as well. Joris On Wed, 23 Jun 2021 at 20:40, Micah Kornfield <emkornfi...@gmail.com> wrote: > Could we postpone the dropping Python 3.6 support to be inline with what > the Python core maintainers deadline? Or at least until the Arrow 6 > release? > > Thanks, > Micah > > On Wed, Jun 23, 2021 at 10:36 AM Wes McKinney <wesmck...@gmail.com> wrote: > > > This seems reasonable to me. > > > > On Wed, Jun 23, 2021 at 11:39 AM Antoine Pitrou <anto...@python.org> > > wrote: > > > > > > > > Hello, > > > > > > In https://issues.apache.org/jira/browse/ARROW-12706 it was proposed > to > > > drop support for the aforementioned Python and Numpy versions. The > > > rationale is that they have ceased to be supported by Numpy, which is a > > > mandatory dependency of PyArrow. > > > > > > Besides, Pandas (an optional dependency of PyArrow) already dropped > > > support for Python 3.6, and Python 3.6 will be unsupported by the > Python > > > core team at the end of 2021. > > > > > > What do you think? If you are opposed to this, please speak up. > > > > > > Regards > > > > > > Antoine. > > > > > >
