[
https://issues.apache.org/jira/browse/FLINK-37775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dian Fu updated FLINK-37775:
----------------------------
Fix Version/s: 2.2
> Consolidate PyFlink development dependencies in pyproject.toml
> --------------------------------------------------------------
>
> Key: FLINK-37775
> URL: https://issues.apache.org/jira/browse/FLINK-37775
> Project: Flink
> Issue Type: Technical Debt
> Components: API / Python
> Reporter: Mika Naylor
> Assignee: Mika Naylor
> Priority: Minor
> Labels: pull-request-available
> Fix For: 2.2
>
>
> Currently, development/testing dependencies for the PyFlink project are
> distributed in several places. These are:
> * In {{{}flink-python/dev/dev-requirements.txt{}}}, which are dependencies
> generally needed for doing development on PyFlink itself.
> * Distributed around various places in
> {{{}flink-python/dev/lint-python.sh{}}}. These are dependencies needed for
> things like running tests, type checking and building the documentation.
> [PEP 735|https://peps.python.org/pep-0735/] introduced support for dependency
> groups in pyproject.toml. Unlike optional dependencies, which are included in
> the distribution of the package, dependency groups are useful for defining
> named groups of dependencies for internal project use. Currently the latest
> versions of pip, uv, etc support this with {{pip install --group
> <group-name>.}}
> Having the dependencies distributed around in different files and in
> different forms makes tracking, auditing and maintaining them a bit more of a
> burden than they need to be. It would be nice to consolidate them in
> PyFlink's pyproject.toml.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
