On Tue, Nov 23, 2010 at 8:01 AM, Michael Foord
wrote:
> On 22/11/2010 21:08, Guido van Rossum wrote:
>>
>> On Mon, Nov 22, 2010 at 11:24 AM, Brett Cannon wrote:
>>>
>>> The problem with that is it means developers who switch to Python 3.2
>>> or whatever are suddenly going to have their tests fai
2010/11/23 Łukasz Langa :
> If you agree to do that for regrtest I will clean up the tests for warnings.
> Already did that for zipfile so it doesn't raise ResourceWarnings anymore. I
> just need to correct multiprocessing and xmlrpc ResourceWarnings, silence
> some DeprecationWarnings in the tests
Wiadomość napisana przez Michael Foord w dniu 2010-11-22, o godz. 23:01:
> On 22/11/2010 21:08, Guido van Rossum wrote:
>> On Mon, Nov 22, 2010 at 11:24 AM, Brett Cannon wrote:
>>> The problem with that is it means developers who switch to Python 3.2
>>> or whatever are suddenly going to have the
On Mon, Nov 22, 2010 at 13:08, Guido van Rossum wrote:
> On Mon, Nov 22, 2010 at 11:24 AM, Brett Cannon wrote:
>> The problem with that is it means developers who switch to Python 3.2
>> or whatever are suddenly going to have their tests fail until they
>> update their code to turn the warnings o
On 22/11/2010 21:08, Guido van Rossum wrote:
On Mon, Nov 22, 2010 at 11:24 AM, Brett Cannon wrote:
The problem with that is it means developers who switch to Python 3.2
or whatever are suddenly going to have their tests fail until they
update their code to turn the warnings off.
That sounds li
On Mon, Nov 22, 2010 at 11:24 AM, Brett Cannon wrote:
> The problem with that is it means developers who switch to Python 3.2
> or whatever are suddenly going to have their tests fail until they
> update their code to turn the warnings off.
That sounds like a feature to me... :-)
--
--Guido van
On Mon, Nov 22, 2010 at 10:58, Ezio Melotti wrote:
> On 22/11/2010 19.45, Michael Foord wrote:
>>
>> On 22/11/2010 17:35, Łukasz Langa wrote:
>>>
>>> Am 22.11.2010 18:14, schrieb Ezio Melotti:
I would like to re-enable by default warnings for regrtest and/or
unittest.
>>>
>>> +1
>>>
On 22/11/2010 19.45, Michael Foord wrote:
On 22/11/2010 17:35, Łukasz Langa wrote:
Am 22.11.2010 18:14, schrieb Ezio Melotti:
I would like to re-enable by default warnings for regrtest and/or
unittest.
+1
Especially in regrtest it could help manage stdlib quality (currently
we have a horde
On 22/11/2010 17:35, Łukasz Langa wrote:
Am 22.11.2010 18:14, schrieb Ezio Melotti:
I would like to re-enable by default warnings for regrtest and/or
unittest.
+1
Especially in regrtest it could help manage stdlib quality (currently
we have a horde of ResourceWarnings, zipfile mostly). I wou
Am 22.11.2010 18:14, schrieb Ezio Melotti:
I would like to re-enable by default warnings for regrtest and/or
unittest.
+1
Especially in regrtest it could help manage stdlib quality (currently we
have a horde of ResourceWarnings, zipfile mostly). I would even be +1 on
making warnings errors f
I would like to re-enable by default warnings for regrtest and/or unittest.
The reasons are:
1) these tools are used mainly by developers and they (should) care
about warnings;
2) developers won't have to remember that warning are silenced and
how to enable them manually;
3) developers wo
11 matches
Mail list logo
