On 15 July 2015 at 08:58, Berker Peksağ <berker.peksag at gmail.com> wrote: > On Wed, Jul 15, 2015 at 1:22 AM, Robert Collins >> For clarity, I think we should: >> - remove the assret check, it is I think spurious. >> - add a set of functions to the mock module that should be used in >> preference to Mock.assert* >> - mark the Mock.assert* functions as PendingDeprecation >> - in 3.6 move the PendingDeprecation to Deprecated >> - in 3.7 remove the Mock.assert* functions and the check for method >> names beginning with assert entirely. > > +1, but I think we need to get Larry's approval for the steps 2 and 3 > because 3.5 is in feature-freeze mode. There is zero urgency here, so nothing needs to change for 3.5. Robert's plan is a fine one to propose for 3.6 (and the PyPI mock backport). Remember folks, "Why wasn't I consulted?!?!?!?" is one of the more obnoxious behavours we can inflict on fellow open source maintainers giving us the gift of their time and energy. If we're putting folks at risk of losing data or otherwise having their systems compromised, then by all means yell loudly, but for anything less, remember: * it's almost certainly not urgent * tolerating the occasional design decision we dislike won't ruin our lives * a red bikeshed will still shelter our bikes, even if we'd have preferred blue * it's just software, so we can put a blue wrapper around the red bikeshed if we prefer it Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4