James Addison

Thanks @kses - yep, documenting the terminal-based setup has already been extremely helpful. I should clarify that the web onboarding I'm suggesting would be after those terminal commands are completed,...

@ptmcg I think I'll close this branch in the next few days, unless there's anything of use here (the test coverage perhaps?) - I don't think it makes any significant...

Hi @iainrussell - apologies for the direct mention; you appeared when I checked the list of recent commits in this repository and I thought it might be worth tagging you...

Closing this pull request; please feel free to recover the commits (`git fetch origin pull/102/head:pr-102-recovered`, or similar) and apply/compare against those if they'd be useful in future.

The problem seems to be that the `failure_message` variable isn't being prefixed with the exception classname. One of the failing tests [looks for a pattern](https://github.com/Lemmons/pytest-raises/blob/ccbc9d5efc2081318358ca4b6ecc2d0b850f74ac/tests/test_raises.py#L277) `*ExpectedMessage: "other message" not in...

NB: also, some of the `excinfo` output warnings appear to be related to the [removal of the `_Result._excinfo` attribute](https://github.com/pytest-dev/pluggy/commit/fbc444218c442dd8cbe29bd68cde8fea52b56baf#diff-8100a2821f8749ee5d3b76dca9df273397d5b62172c06716a538332420ee3c86L43) in `pluggy` v1.1.0 onwards.

An additional example of this occurring: https://world.openfoodfacts.org/product/8052870001405/mousse-lamponi-senza-peccato

Could this also apply to product edits by subsequent users? The reason I ask is that I'm a data-quality daily volunteer, and sometimes I worry that my edits might also...

From attempting to perform identity-assurance checks on packages manually: bidirectional references can be a reassuring indicator. In context here: when a PyPi package points to a GitHub repository as its...

(issue labels updated; let me know if those seem accurate/inaccurate)