code: drop Experimental API label from ExceptionInfo.from_exc_info

[bluetech]

This API is OK, I don't think we're going to change something about it at this point.

[RonnyPfannschmidt]

The only caveat this poses is that it may be harder to drop exception info as is (it's one of the inheritances from pylib that's unfortunately very intertwined

[RonnyPfannschmidt]

Since modern exceptions carry the traceback /context, maybe we can directly deprecate this

[bluetech]

The only caveat this poses is that it may be harder to drop exception info as is (it's one of the inheritances from pylib that's unfortunately very intertwined

Right, but I don't see us dropping ExceptionInfo without a major overhaul, it's exposed by pytest.raises.

Since modern exceptions carry the traceback /context, maybe we can directly deprecate this

This is not yet possible, since various Python APIs still use the exc_info triplet, and AFAIU it's not guaranteed to be equivalent before 3.12 (or maybe 3.11). So we got to keep it for now.

[RonnyPfannschmidt]

thanks for the clarification on python version ranges

indeed, raises is raising some serious future work ^^

[nicoddemus]

The only caveat this poses is that it may be harder to drop exception info as is (it's one of the inheritances from pylib that's unfortunately very intertwined

Curious, drop it in favor of what? As of now, it is inside pytest and it seems to do its role OK-ish -- perhaps it exposes other internals like ReprExceptionInfo and that's undesirable, is that what you mean?

[RonnyPfannschmidt]

It's neither nicely serializable nor does it print pretty /filters nicely

Im very curious about the stuff rich and sentry do wrt exceptions, but it currently is on the lower end of the bucket list for me