Jonas, thanks for kicking this off! This sounds like a great direction! Publishing the Python CLI to PyPI will definitely make installation much smoother and improve UX. Nightly builds on Test PyPI are also nice for faster iteration and early feedback. I’m fully supportive of moving forward with this plan and appreciate the clear proposal outlining the process. Looking forward to the follow-up [VOTE] threads! The process also depends on the vote of Pypi project name and tool name. Hopefully we can finalize these votes around the same timeline.
Yufei On Tue, Oct 14, 2025 at 9:17 AM 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 >
