Ronny Pfannschmidt <[email protected]> writes: > given the rightfully reasserted constraints that seems a reasonable > course of action, > > i'd prefer to keep it reopened instead of won't fix, > and i'd like to see a revising of the deprecation policy,
What we can do according to our policy is saying in our documentation and announcements: in two releases time we'll break this backwards compatibility thing (whether that's new-style classes or marks). Then two releases later bump the major version and do it. It slows breakage a little bit down and I thought that was the reason for the current deprecation policy. Yes it is more annoying as we basically have to leave a pull-request or branch lying around for all that time and deal with the merging breakage resulting from this. Having said that, I'm happy to re-evaluate the policy if enough people think this is a bad idea. But I'd like some user feedback as well before changing it. Floris _______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
