RetroSearch Browse

Wed Jul 15 10:39:37 CEST 2015 · http://mail.python.org/pipermail/python-dev/2015-July/140765.html

On 15 July 2015 at 19:17, Antoine Pitrou <solipsis at pitrou.net> wrote:
> On Wed, 15 Jul 2015 10:22:14 +1200
> Robert Collins <robertc at robertcollins.net> wrote:
>>
>> 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.
>
> I think removing them is a bit too strong. There's software out there
> that would like to have cross-version-compatible test suites.

Which they can do using 'mock'.

-Rob

-- 
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2015-July/140765.html below:

[Python-Dev] How far to go with user-friendliness