Open tbarron opened 6 years ago
@keleshev Please merge this change. Only test code is affected, and the tests continue to pass.
@tbarron Maybe you want to explain the change, i.e. why using message
causes an error and using args[0]
doesn't, so that merging is made easier.
Re: why using message causes an error and using args[0] doesn't
It's been a while since I looked at this, but I think it had to do with a change to the interface of the Error class (or one of the subclasses). It was something like one of the Python version updates removed or renamed the message() method but the info was available in the args[] array across the version update.
I hope this helps... Tom
On Wed, May 31, 2023 at 12:49 Peter Bittner @.***> wrote:
@keleshev https://github.com/keleshev Please merge this change. Only test code is affected, and the tests continue to pass.
@tbarron https://github.com/tbarron Maybe you want to explain the change, i.e. why using message causes an error and using args[0] doesn't, so that merging is made easier. Related
- Pytest API reference https://docs.pytest.org/en/latest/reference/reference.html#pytest.raises
— Reply to this email directly, view it on GitHub https://github.com/keleshev/docopt-dispatch/pull/6#issuecomment-1570578651, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAER6D6F5REFUAVNHI7OHG3XI5ZDJANCNFSM4FUBR5AQ . You are receiving this because you were mentioned.Message ID: @.***>
This pull request addresses issue #5