Skip to content

docs(pypi): add a guide for migrating from rules_pycross - #3

Draft
aignas wants to merge 2 commits into
feat.aignas.pycross-parity-basefrom
feat.aignas.pycross-parity-01-docs
Draft

aignas wants to merge 2 commits into
feat.aignas.pycross-parity-basefrom
feat.aignas.pycross-parity-01-docs

Conversation

@aignas

@aignas aignas commented Nov 19, 2026

Copy link
Copy Markdown
Owner

rules_pycross users have no map from its lock file extensions, package
settings, platforms and labels to rules_python, so it is hard to tell what
a migration needs and what is missing.

This adds a "Migrating from rules_pycross" page to the PyPI docs. It has a
concept map, a worked example based on the rules_pycross examples/bzlmod
module, tables for the package settings, platforms, flags and labels, the
options for building from source, the differences in behaviour and a feature
matrix. Features that are not available yet are marked as planned and later
changes in this series update their rows.

Stack (fork test PRs): this is the first PR on top of
feat.aignas.pycross-parity-base (main + bazel-contrib#4522 + bazel-contrib#4523).

@aignas

aignas commented Nov 19, 2026

Copy link
Copy Markdown
Owner Author

This PR series (rules_pycross feature parity) is prepared by an AI coding agent (Claude Code) working for @aignas, as test PRs on the fork for review before anything goes upstream. Each PR is reviewed by a separate agent before it is opened. Review comments here are read by @aignas, and the agent only acts on them when asked; replies from the agent are approved by @aignas.

Agent-generated comment, posted automatically as part of the PR creation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant