a67c02b86a
- Remove pyodps from requirements/base.txt since it is not listed in base.in (fixes check-python-deps CI failure) - Use real sqlite dialect instead of MagicMock in select_star tests to avoid TypeError from quote_table joining MagicMock strings - Mock sys.modules for odps in URI-no-match test so the local import succeeds and reaches the URI pattern matching code path - Remove broken patch of __func__ readonly attribute that caused AttributeError - Fix not-partitioned test to mock sys.modules instead of patching a module-level name that does not exist Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Python dependency logic
In this folder, the .in files, in conjunction with the ../pyproject.toml file (in the root of the repo) are used to generate the pinned requirements as .txt files.
To alter the pinned dependency, you can edit/alter the .in and pyproject.toml files, and then run the following command:
./scripts/uv-pip-compile.sh
:::warning
The pinned dependencies are based on the current version of python supported in Superset.
Output of ./scripts/uv-pip-compile.sh may vary slightly based on the python version you are using to run the command.
Check the pyproject.toml file for the current version of python supported.
:::
This will generate the pinned requirements in the .txt files, which will be used in our CI/CD pipelines and in the Docker images.
We recommend to everyone in the community to use the pinned requirements in their local development environments, to ensure consistency across different environments, though we don't force requirements as part of our python package semantics to allow flexibility for users to install different versions of the dependencies if they wish.
Note that development.txt is a superset of what's in base.txt, and all version numbers for shared library should fully match at all times. translations.txt is meant as a supplemental file to be used in conjunction with the other requirements files, and is not meant to be used standalone.