trigger a deprecationwarning for Result.excinfo

[RonnyPfannschmidt]

pluggy/pluggy/callers.py

Lines 32 to 34 in 1037dc9

	@property
	def excinfo(self):
	return self._excinfo

we kept the code for pytest, but we should at least deprecate it and remove the use in future

[goodboy]

@RonnyPfannschmidt works for me.

[goodboy]

@RonnyPfannschmidt wait so we don't want to allow for public access at all?
Is the idea that users can catch the underlying exception instead from get_result()?

[RonnyPfannschmidt]

correct

[goodboy]

@RonnyPfannschmidt waiting on you still as per your #155 comment as to how to move forward with an alternative system for this.

[RonnyPfannschmidt]

@tgoodlet thanks for the reminder, i still haven't come up with a reasonable failure indication system, i believe this will require a little collaborative brainstorming to generate ideas

[nicoddemus]

What was the rationale for not exposing the exception object again?

[RonnyPfannschmidt]

closing this one as it will disappear with the deprecation/removal of result objects in #260