[
https://issues.apache.org/jira/browse/FLINK-26763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600298#comment-17600298
]
bo zhao commented on FLINK-26763:
---------------------------------
I think reusing system conda had been supported in pyflink:
see
[https://github.com/apache/flink/blob/master/flink-python/README.md#running-test-cases]
and
[https://github.com/apache/flink/blob/master/flink-python/dev/lint-python.sh#L699]
But the bash will always install the test python environment by each
lint-python execution, so I suspect that your quesion/issue here is reuse the
python environment?
This looks a CICD tool, from my personal thought, create the fresh test env
before test execution and flush the test env after finish testing would be good
towards the py env. ;)
> PyFlink support using system conda when running checks and tests
> ----------------------------------------------------------------
>
> Key: FLINK-26763
> URL: https://issues.apache.org/jira/browse/FLINK-26763
> Project: Flink
> Issue Type: Improvement
> Components: API / Python
> Reporter: Juntao Hu
> Priority: Minor
>
> Currently lint-python.sh script uses hardcoded conda path under dev
> directory, and several tools under the "base" env of this conda. It would be
> great to reuse system conda and user-specified env rather than installing a
> dedicated one.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
