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

Jing Ge reassigned FLINK-33839:
-------------------------------

    Assignee:     (was: Jing Ge)

> Deploy Python artifacts to PyPI (need PMC role)
> -----------------------------------------------
>
>                 Key: FLINK-33839
>                 URL: https://issues.apache.org/jira/browse/FLINK-33839
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Jing Ge
>            Priority: Major
>
> Release manager should create a PyPI account and ask the PMC add this account 
> to pyflink collaborator list with Maintainer role (The PyPI admin account 
> info can be found here. NOTE, only visible to PMC members) to deploy the 
> Python artifacts to PyPI. The artifacts could be uploaded using 
> twine([https://pypi.org/project/twine/]). To install twine, just run:
> {code:java}
> pip install --upgrade twine==1.12.0
> {code}
> Download the python artifacts from dist.apache.org and upload it to pypi.org:
> {code:java}
> svn checkout 
> https://dist.apache.org/repos/dist/dev/flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
> cd flink-${RELEASE_VERSION}-rc${RC_NUM}
>  
> cd python
>  
> #uploads wheels
> for f in *.whl; do twine upload --repository-url 
> https://upload.pypi.org/legacy/ $f $f.asc; done
>  
> #upload source packages
> twine upload --repository-url https://upload.pypi.org/legacy/ 
> apache-flink-libraries-${RELEASE_VERSION}.tar.gz 
> apache-flink-libraries-${RELEASE_VERSION}.tar.gz.asc
>  
> twine upload --repository-url https://upload.pypi.org/legacy/ 
> apache-flink-${RELEASE_VERSION}.tar.gz 
> apache-flink-${RELEASE_VERSION}.tar.gz.asc
> {code}
> If upload failed or incorrect for some reason (e.g. network transmission 
> problem), you need to delete the uploaded release package of the same version 
> (if exists) and rename the artifact to 
> {{{}apache-flink-${RELEASE_VERSION}.post0.tar.gz{}}}, then re-upload.
> (!) Note: re-uploading to pypi.org must be avoided as much as possible 
> because it will cause some irreparable problems. If that happens, users 
> cannot install the apache-flink package by explicitly specifying the package 
> version, i.e. the following command "pip install 
> apache-flink==${RELEASE_VERSION}" will fail. Instead they have to run "pip 
> install apache-flink" or "pip install apache-flink==${RELEASE_VERSION}.post0" 
> to install the apache-flink package.
>  
> ----
> h3. Expectations
>  * Python artifacts released and indexed in the 
> [PyPI|https://pypi.org/project/apache-flink/] Repository



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to