i have ideas for replacing/changing it in the back of my head since a while now, so i'd like to have a reasonable/easy testbed
also we could avoid the need for api compatibility even if we copy in py.code given that the old api would be available also exception representation is a very low-ganging fruit in various ways, in particular since it kinda works but i think before 3.0 its a very good point in time to reconsider after all for xdist we need a serializable variant, and i think the current api does way too much the harsher we can trim down in future, the better -- Ronny Am 25.01.2016 um 11:17 schrieb holger krekel: > Hi Ronny, > > On Mon, Jan 25, 2016 at 00:38 +0100, Ronny Pfannschmidt 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. > In all the years of pytest/py development no one ever seemed to seriously > want to replace the exception representation so i think going full-scale > flexible here is premature. Also the move of code from py.code to > py.test is kind of orthogonal as Bruno already mentioned. > > best, > holger _______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
