On Tue, 07 Oct 2008 14:12:06 -0400, Terry Reedy <tjreedy@udel.e duwrote:
It's fixed in 2.6. I doubt the fix will be backported to 2.5, since it
involved re-implementing most of the warnings module in C (introducing
some unpleasant incompatibiliti es).
Of course, it doesn't much matter that it's fixed in 2.6, since both of
these warnings are errors in 2.6. ;)
Jean-Paul
>Peter Otten wrote:
>
>Then Grant could file a tracker item explaining that this is a nuisance and
>request that the bypass be changed. I have no idea what that would entail.
>>Grant Edwards wrote:
>>
>>The "with" and "as" warnings bypass the warning mechanism. The only way I
>>can see to avoid them is to compile the python code:
>>>I'm getting awfully tired of constant warnings about what's
>>>going to happen at some point in the future.
>>>
>>>Warnings like this:
>>>
>>>./surfplot.py:313 : Warning: 'with' will become a reserved keyword in
>>>Python 2.6
>>>going to happen at some point in the future.
>>>
>>>Warnings like this:
>>>
>>>./surfplot.py:313 : Warning: 'with' will become a reserved keyword in
>>>Python 2.6
>>The "with" and "as" warnings bypass the warning mechanism. The only way I
>>can see to avoid them is to compile the python code:
>Then Grant could file a tracker item explaining that this is a nuisance and
>request that the bypass be changed. I have no idea what that would entail.
involved re-implementing most of the warnings module in C (introducing
some unpleasant incompatibiliti es).
Of course, it doesn't much matter that it's fixed in 2.6, since both of
these warnings are errors in 2.6. ;)
Jean-Paul