Nick Coghlan added the comment: On 12 Feb 2017 11:54 pm, "Serhiy Storchaka" <rep...@bugs.python.org> wrote:
Serhiy Storchaka added the comment: I don't understand how the table can make maintaining easier. You need to support multiple values in every branch even if the only one value is used. I'm sure unused values will became outdated pretty fast. "alpha" and "beta" stages are not related here. The test should be skipped at these stages (I recommend to use skipTest() or the skipUnless() decorator rather than just make test always success). Magic number can be changed multiple times at "alpha" and "beta" stages. Release manager needs to update the test only when forming the first release candidate. And his should not do anything if the magic number was not changed in this feature release. Serhiy's argument here & the fact we've switched to a cherrypick model for maintenance branches has persuaded me we just want a single "expected magic number" in the test case rather than the full table that covers multiple releases. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29514> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
