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

   ## What is the purpose of the change
   
   The following doc describes the version specification: 
https://peps.python.org/pep-0440/#developmental-releases
   
   Extract:
   ```
   Developmental releases are also permitted for pre-releases and post-releases:
   
   X.YaN.devM       # Developmental release of an alpha release
   X.YbN.devM       # Developmental release of a beta release
   X.YrcN.devM      # Developmental release of a release candidate
   X.Y.postN.devM   # Developmental release of a post-release
   ```
   
   At the moment pyflink supports only `.dev0` development version. In this PR 
I've added `.devM` support.
   
   ## Brief change log
   
   Added `.devM` support.
   
   ## Verifying this change
   
   Manually:
   ```
   cd flink
   
   conda env remove -n venv
   conda create -y -n venv python=3.10
   conda activate venv
   pip3 install -r flink-python/dev/dev-requirements.txt
   
   cd flink-python
   python3 setup.py sdist bdist_wheel
   
   cd apache-flink-libraries
   python3 setup.py sdist
   ```
   
   ## 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