PyO3 / PyO3/setuptools-rust

No way to dynamically enable features via command line / environment

Open
#619 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
680
Forks
110
Avg merge
3d 18h
Merged PRs (30d)
1

Description

In https://github.com/PyO3/pyo3/pull/6300 we observed the setuptools-rust doesn't have the equivalent of MATURIN_PEP517_ARGS, so we weren't able to dynamically enable no-std testing.

Would be good to think how this can be done.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reviewing the behavior described in PyO3/pyo3#6300 and how MATURIN_PEP517_ARGS enables dynamic configuration. Then trace setuptools-rust's command-line and environment handling to determine a suitable interface for dynamically enabling features, including no-std testing. Done means users can configure feature enabling without editing project configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
build-system, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.