Hi Ronny, IIUC, the motivation for the py.code merge is to fix bugs in py.code in a timely manner without depending on py releases, and py.code contains more code than just the exception representation. If that's correct, this having a different code for the exception representation wouldn't prevent us from merging py.code at all.
Having said that, I'm not against changing the exception representation at all. :) Cheers, Bruno. On Sun, Jan 24, 2016 at 9:38 PM Ronny Pfannschmidt < [email protected]> wrote: > Hi everyone, > > this is probably a bit late, in particular since Bruno did already spend > a considerable amount of time, > > but instead of merging py.code for the exception repressentation, > i would like to propose introducing a abstraction layer, > and allowing to set the exception representation in pytest.ini or via > plugins > > this would allow more free experimentation, and also a really clean > transition from > py.code as default * new possible, to py.code the legacy and new code > the default. > > -- Ronny > _______________________________________________ > pytest-dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/pytest-dev >
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
