You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/11/06 09:03:00 UTC

[jira] [Updated] (FLINK-14506) Improve the release script for Python API release package

     [ https://issues.apache.org/jira/browse/FLINK-14506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-14506:
-----------------------------------
    Labels: pull-request-available  (was: )

> Improve the release script for Python API release package
> ---------------------------------------------------------
>
>                 Key: FLINK-14506
>                 URL: https://issues.apache.org/jira/browse/FLINK-14506
>             Project: Flink
>          Issue Type: Sub-task
>          Components: API / Python, Build System
>            Reporter: Dian Fu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>
> Currently it assumes that the required Python environment(i.e. Python 3.5+, setuptools, etc) are available in the local machine when executing create_binary_release.sh to perform the release. 
> This could be improved and there are two options in my mind:
> 1) Reuse the script defined in flink-python module(lint-python.sh) to create the required virtual environment and build the Python package using the created virtual environment.
> 2) Document the dependencies at the page "[Create a Flink Release|https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release#CreatingaFlinkRelease-Checklisttoproceedtothenextstep.1]" and add validation check in create_binary_release.sh to throw an meaningful error with hints how to fix it.
> Personally I prefer to option 1) as it's transparent for users. Welcome any feedback. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)