PyO3/pyo3

Expose a way to access the `PYO3_CONFIG_FILE` values

Open

#2,033 opened on 2021年11月29日

GitHub で見る
 (2 comments) (0 reactions) (0 assignees)Rust (10,152 stars) (668 forks)batch import
Good First Issueneeds-implementer

説明

Some users have specific use cases where they would benefit from being able to access the PYO3_CONFIG_FILE values in some form from the pyo3 crate.

I generally wouldn't advise this, as a lot of these config files (such as library path) are unique to the build environment so wouldn't have any useful meaning in binaries intended to be deployed on other systems.

See original comment from #2000 below.

If anyone has need for this, I'm happy to help review designs and implementation.

It would be nice to have access to the library path from PYO3_CONFIG (or all values) but that is not a problem for me.

E.g. it could be based off the PYO3_CONFIG build mechanism - maybe we could have pyo3_config_var!("lib_path"). Or maybe just pyo3_lib_path!(). I'm open to hearing ideas on what's better.

An alternative could be a module filled with many const values, similar to what built does.

Originally posted by @jonasbb in https://github.com/PyO3/pyo3/issues/2000#issuecomment-979985994

コントリビューターガイド

技術スタック
rustpython
領域
developer experiencetooling
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
needs investigation
前提条件
understanding of Rust macrosfamiliarity with PyO3 build systemknowledge of config file parsing
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
20
調査方針
Review the existing PYO3 CONFIG mechanism (likely in pyo3 build config crate) and the suggested `pyo3 config var!` macro approach. Examine the comment thread for alternative proposals like a const module. Investigate how values like lib path are extracted and consider exposing them through a public API. Look at the linked issue #2000 for context.