Predict an import error with jaraco.vcs.fixtures

[bswck]

No description provided.

[jaraco]

I'm kinda disinclined to add the conditional import. I expect no one to import jaraco.vcs.fixtures unless they have pytest installed (and have the fixture enabled).

Is there a scenario where this would need to be supported?

[bswck]

I'm kinda disinclined to add the conditional import. I expect no one to import jaraco.vcs.fixtures unless they have pytest installed (and have the fixture enabled).

Is there a scenario where this would need to be supported?

This isn't really a conditional import (we're reraising the exception), but a guide on what to do just in case of an error.
For instance, one may be testing with unittest only and think that jaraco.vcs.fixtures has something for them.

[jaraco]

Right. I see that now. I do try to keep the code simple and tight and only add behavior where it has demonstrable value. Here the value seems small if not negligible. Making this change also implies this change should be applied to all other fixtures in the ecosystem. Let's instead rely on the benefits of inversion of control and dependency injection that entry points provides and assume that pytest will be present. If anyone encounters this error and is confused by it, they can report their use case and we can consider an intervention then.