gaborgsomogyi opened a new pull request, #23359:
URL: https://github.com/apache/flink/pull/23359

   ## What is the purpose of the change
   
   * Python 3.7.17 is the latest security patch of the 3.7 line. This version 
is end-of-life and is no longer supported: 
https://www.python.org/downloads/release/python-3717/
   * Miniconda 4.7.10 is released on 2019-07-29 which is 4 years old already 
and not supporting too many architectures (x86_64 and ppc64le)
   * The latest miniconda which has real multi-arch feature set supports the 
following python versions: 3.8, 3.9, 3.10, 3.11 and no 3.7 support
   
   In this PR  python 3.7 support dropped and upgrade miniconda to the latest 
version which opens the door to other platforms + python 3.11 support
   
   ## Brief change log
   
   * Python 3.7 support dropped
   * Upgrade miniconda to the latest version
   * Add arm support
   * Upgrade `mypy==1.5.1` (latest)
   * `flink-python/apache-flink-libraries/setup.py` python versions fix (still 
3.6 was there which is dropped long time ago)
   
   ## Verifying this change
   
   * Existing python tests.
   * Manually
   ```
   dev/build-wheels.sh
   ```
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to