[
https://issues.apache.org/jira/browse/TINKERPOP-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683514#comment-17683514
]
ASF GitHub Bot commented on TINKERPOP-2810:
-------------------------------------------
Cole-Greer commented on PR #1958:
URL: https://github.com/apache/tinkerpop/pull/1958#issuecomment-1414140226
Looks good to me, thanks for submitting this PR. Based on the feedback from
the recent release, I would say it's best to backport all the way to 3.5-dev to
reach the most users possible. It should only be withheld from 3.5-dev if
someone has specific objections preventing it from going in there.
> gremlinpython aiohttp dependency requirement too strict
> -------------------------------------------------------
>
> Key: TINKERPOP-2810
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2810
> Project: TinkerPop
> Issue Type: Improvement
> Components: python
> Affects Versions: 3.6.1
> Reporter: Gunther Vogel
> Assignee: Stephen Mallette
> Priority: Major
> Fix For: 3.7.0
>
>
> Currently, the requirements specify aiohttp >= 3.8.0, <= 3.8.1, disallowing
> newer bugfix releases of aiohttp (current version is 3.8.3). Following the
> general semantic versioning rules, the upper bound should be <4.0.0 (disallow
> breaking changes).
> The current requirements are the result of TINKERPOP-2668 which only had the
> goal of avoiding the bug contained in versions <= 3.7.4.
> Fixing aiohttp at a non-current bugfix release step increases the maintenance
> effort needed to get an error-free overall library setup; in my case,
> gremlinpython is not even used directly, but just pulled in by awswrangler.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
