[
https://issues.apache.org/jira/browse/TINKERPOP-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887671#comment-17887671
]
ASF GitHub Bot commented on TINKERPOP-3086:
-------------------------------------------
Cole-Greer commented on PR #2808:
URL: https://github.com/apache/tinkerpop/pull/2808#issuecomment-2400461781
> VOTE +1, though I'm curious why the bump is only to 3.9 since this is for
the master branch. Seems like it will need to be bumped again before any
release from this branch so you might want to make a follow-up Jira for that.
Good catch, this was intended for 3.6 and 3.7 (only permitted to update to
3.9 according to our policies). I've updated the PR to target 3.6-dev. I intend
to follow up later with a python upgrade (likely to 3.10) in master-http.
> Upgrade gremlin-python to newer Python interpreter
> --------------------------------------------------
>
> Key: TINKERPOP-3086
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3086
> Project: TinkerPop
> Issue Type: Improvement
> Components: python
> Affects Versions: 3.6.7
> Reporter: Cole Greer
> Priority: Blocker
>
> Currently gremlin-python (in all active branches) uses python 3.8 which will
> reach end of life in October 2024. According to the [runtime upgrade
> policy|https://tinkerpop.apache.org/docs/3.7.2/dev/developer/#runtimes], a
> deprecation notice should be added to 3.6 and 3.7 to set them up for an
> upgrade to python 3.9 after October.
> Master should be upgraded to a newer python version which will still receive
> support for several years to come (likely 3.11 or 3.12).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
