Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Resolved
-
None
Description
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" 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.
Attachments
Issue Links
- links to