Hi I'm supporting this. However, as packages on PyPi are considered as "release artifacts", it has to be legally correct regarding The ASF policy.
Several Apache projects already publish PyPi packages (for instance https://superset.apache.org/docs/installation/pypi/). As we are in the incubator, we have to keep the incubating "tag". I will do a pass and check with you. Regards JB On Tue, Oct 14, 2025 at 6:17 PM Honah J. <[email protected]> wrote: > > Hi everyone, > > I’d like to start a discussion about publishing the Apache Polaris Python > CLI to PyPI and providing nightly builds (test PyPi). > > The main goal is to make the CLI easier to install (pip install > <package_name>) and to align its release and distribution process with ASF > guidelines. I’ve drafted a proposal [1] that outlines the key requirements > and the high-level release process if we include the Python CLI in the next > release. The proposal also covers how we might set up nightly builds on > Test PyPI for early testing. > > While some details can be finalized later, I’d like to first gather > feedback on the overall direction — specifically, whether the community > agrees with publishing to PyPI and providing nightly builds. > > If there’s general agreement, I plan to open two separate [VOTE] threads to > formalize these decisions: > 1. Whether to the Python CLI to PyPI > 2. Whether to provide nightly build (publish to test PyPi) > > Please let me know what you think! > > [1] > https://docs.google.com/document/d/1gbKYnFftpq884GhJ59waHdfoQG6MrevVAVCspf3hbrk/edit?usp=sharing > > > Best regards, > Jonas
