Add __pyo3__ attribute to native modules

[ongchi]

Closes #3426

[mejrs]

Thanks!

What is your motivation for using a (handwritten?) pyclass for this? We've so far avoided this because pyo3 is linked statically; when two users write their own pyo3 modules, they'll have two different PyO3Attr types. (See the discussion around PanicException for why this can be problematic).

[adamreichold]

We've so far avoided this because pyo3 is linked statically; when two users write their own pyo3 modules, they'll have two different PyO3Attr types. (See the discussion around PanicException for why this can be problematic).

I think the consensus reached so far is that we should ship a separate (pure Python for now) package called something like pyo3_runtime on PyPI which would contain shared types like PanicException and PyO3Attr, c.f. the discussion in the (eventually rejected) approach proposed in #3073 .

[davidhewitt]

Agreed, I've been meaning to do that for aaaaages, and finally did it! 😂

#3450
https://pypi.org/project/pyo3-runtime

[ongchi]

What is your motivation for using a (handwritten?) pyclass for this?

All because I'm noob.🤡

BTW, I think it will be nice if pyo3 modules include some build information (e.g. rust version, build target, features...) automatically with a general interface to fetch this info. This shall benefit both developers and users who install packages from pypi, could providing useful context for debugging/issue tracking.

[adamreichold]

BTW, I think it will be nice if pyo3 modules include some build information (e.g. rust version, build target, features...) automatically with a general interface to fetch this info. This shall benefit both developers and users who install packages from pypi, could providing useful context for debugging/issue tracking.

I think https://github.com/PyO3/pyo3-built might be what you are looking for?

[ongchi]

Cool! I'm not aware of that. Thanks for pointing this out.