-
Notifications
You must be signed in to change notification settings - Fork 4.5k
BEAM-9626: Move out optional packages from core dependencies - 20259 #35297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
665570d
f70a239
6bba28a
beb3039
154bd93
3b5cccd
f7bc0e4
df7ca4c
c95aaf2
973ac57
e31b3ae
26e0126
2d13c45
9dd9262
ccc51b0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||
|---|---|---|---|---|
|
|
@@ -369,16 +369,13 @@ def get_portability_package_data(): | |||
| # TODO(https://github.com/grpc/grpc/issues/37710): Unpin grpc | ||||
| 'grpcio>=1.33.1,<2,!=1.48.0,!=1.59.*,!=1.60.*,!=1.61.*,!=1.62.0,!=1.62.1,<1.66.0; python_version <= "3.12"', # pylint: disable=line-too-long | ||||
| 'grpcio>=1.67.0; python_version >= "3.13"', | ||||
| 'hdfs>=2.1.0,<3.0.0', | ||||
| 'httplib2>=0.8,<0.23.0', | ||||
| 'jsonschema>=4.0.0,<5.0.0', | ||||
| 'jsonpickle>=3.0.0,<4.0.0', | ||||
| # numpy can have breaking changes in minor versions. | ||||
| # Use a strict upper bound. | ||||
| 'numpy>=1.14.3,<2.3.0', # Update pyproject.toml as well. | ||||
| 'objsize>=0.6.1,<0.8.0', | ||||
| 'packaging>=22.0', | ||||
| 'pymongo>=3.8.0,<5.0.0', | ||||
| 'proto-plus>=1.7.1,<2', | ||||
| # 1. Use a tighter upper bound in protobuf dependency to make sure | ||||
| # the minor version at job submission | ||||
|
|
@@ -391,10 +388,8 @@ def get_portability_package_data(): | |||
| # 3. Exclude protobuf 4 versions that leak memory, see: | ||||
| # https://github.com/apache/beam/issues/28246 | ||||
| 'protobuf>=3.20.3,<6.0.0.dev0,!=4.0.*,!=4.21.*,!=4.22.0,!=4.23.*,!=4.24.*', # pylint: disable=line-too-long | ||||
| 'pydot>=1.2.0,<2', | ||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Looks like some of these are causing failures because the appropriate extras aren't installed when running the test - could you take a look? (or feel free to revert/simplify to a smaller set of dependencies)
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I see you started on this, I think its probably just adding interactive/yaml to a few tox suites
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yes, I am not done with this change yet. I will update the tox suites soon.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @damccorm what is the easiest way to find the mapping of test environment and the tox.ini section? This could help me to easily identify the broken environment and fix it. Otherwise, it will take longer time. Also, I realized that
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would this line (
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Yeah, that's what I usually use, and then you can look at the gradle task. An alternative at the failed test log, you can see something like: Tox will create a folder with the task name (in this case py39-cloud) as part of the path name. So in this case, the task is py39-cloud - Line 99 in 9d75411
You'll also see this task show up elsewhere in the logs (e.g. tox-py39-cloud shows up a bunch of places). An llm probably could figure it out too, but I haven't tried it yet :) |
||||
| 'python-dateutil>=2.8.0,<3', | ||||
| 'pytz>=2018.3', | ||||
| 'redis>=5.0.0,<6', | ||||
| 'regex>=2020.6.8', | ||||
| 'requests>=2.24.0,<3.0.0', | ||||
| 'sortedcontainers>=2.4.0', | ||||
|
|
@@ -489,6 +484,7 @@ def get_portability_package_data(): | |||
| # Skip version 6.1.13 due to | ||||
| # https://github.com/jupyter/jupyter_client/issues/637 | ||||
| 'jupyter-client>=6.1.11,!=6.1.13,<8.2.1', | ||||
| 'pydot>=1.2.0,<2', | ||||
| 'timeloop>=1.0.2,<2', | ||||
| 'nbformat>=5.0.5,<6', | ||||
| 'nbconvert>=6.2.0,<8', | ||||
|
|
@@ -560,12 +556,22 @@ def get_portability_package_data(): | |||
| # `--update` / `-U` flag to replace the dask release brought in | ||||
| # by distributed. | ||||
| ], | ||||
| 'hdfs': [ | ||||
| 'hdfs>=2.1.0,<3.0.0', | ||||
| ], | ||||
| 'mongodb': [ | ||||
| 'pymongo>=3.8.0,<5.0.0' | ||||
| ], | ||||
| 'redis': [ | ||||
| 'redis>=5.0.0,<6' | ||||
| ], | ||||
| 'yaml': [ | ||||
| 'docstring-parser>=0.15,<1.0', | ||||
| 'jinja2>=3.0,<3.2', | ||||
| 'virtualenv-clone>=0.5,<1.0', | ||||
| # https://github.com/PiotrDabkowski/Js2Py/issues/317 | ||||
| 'js2py>=0.74,<1; python_version<"3.12"', | ||||
| 'jsonschema>=4.0.0,<5.0.0', | ||||
| ] + dataframe_dependency, | ||||
| # Keep the following dependencies in line with what we test against | ||||
| # in https://github.com/apache/beam/blob/master/sdks/python/tox.ini | ||||
|
|
||||
Uh oh!
There was an error while loading. Please reload this page.