pip distribution (in addition to npm)?

Open
#812 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
32/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python, rust

Research direction

Review the existing npm packaging and release workflow, then assess how a pyproject.toml and per-platform Python wheels would fit the Rust CLI build. Define the platform coverage and PyPI publication flow alongside npm; done would mean a documented, maintainable packaging plan or implementation that works in CI.

Written by the indexing model from the issue text.

Description

I work mostly in Python environments and pip install would be a more natural fit than npm for that context.

Some Rust CLI tools ship as platform-specific Python wheels with no Python code at all — just the binary, wired into PATH on install. Ruff does this. I don't know if that'd fit this project's build setup, but figured it was worth a mention.

Rough shape if it did: a pyproject.toml, per-platform wheels in CI, PyPI publish on release alongside the existing npm one.

Dominant language
Rust
Stars
32.3k
Forks
2k
Avg merge
16h 3m
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleworkspace/cli

All issues in googleworkspace/cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.