RetroSearch Browse

Wed Jul 23 01:47:20 CEST 2008 · http://mail.python.org/pipermail/python-dev/2008-July/081504.html

On Tue, Jul 22, 2008 at 6:43 PM, Victor Stinner <
victor.stinner at haypocalc.com> wrote:

> Le Monday 21 July 2008 21:23:21, vous avez écrit :
> > > It should raises an error instead of a warning, it has no sense to read
> a
> > > partial byte :-) But that should breaks some applications?
> >
> > This doesn't come into effect until 3.0.
>
> Would it possible to create an option "strict mode" which disallow
> dangerous
> cast? Especially in PyArg_Parse*() functions.

You could use -Wall to make the warning an error.

-- 
Cheers,
Benjamin Peterson
"There's no place like 127.0.0.1."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20080722/ba03076c/attachment.htm>

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

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

[Python-Dev] fileobj.read(float): warning or error?