You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Mika Naylor (Jira)" <ji...@apache.org> on 2025/02/27 11:43:00 UTC

[jira] (FLINK-36900) Migrate away from Anaconda for managing Python environments for Flink Python

    [ https://issues.apache.org/jira/browse/FLINK-36900 ]


    Mika Naylor deleted comment on FLINK-36900:
    -------------------------------------

was (Author: JIRAUSER308097):
[~martijnvisser] With both PRs now in, should this issue be resolved or do we need to backport to any other branches?

> Migrate away from Anaconda for managing Python environments for Flink Python
> ----------------------------------------------------------------------------
>
>                 Key: FLINK-36900
>                 URL: https://issues.apache.org/jira/browse/FLINK-36900
>             Project: Flink
>          Issue Type: Technical Debt
>          Components: Test Infrastructure
>            Reporter: Mika Naylor
>            Assignee: Mika Naylor
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 2.1.0
>
>
> Currently, Flink uses conda (via miniconda) to manage Python environments for things like developer, testing and end-to-end testing Python environments. Given https://issues.apache.org/jira/browse/LEGAL-688, it would be best if we move away from conda to instead use a tool like `uv` for managing Python environments, and rely on the public PyPI index rather than the anaconda package index.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)