Re: Understanding and dealing with an exception

References	<CALyJZZXtxD5HZCZ6C21-uPgxQUhvWw7xaUZsmPw-whTvhjGBsA@mail.gmail.com> <CAPTjJmo96WxHi-Y+ZbhQD3P3rBFLstn5OtOoydXZxDKpGcsjBg@mail.gmail.com> <CALyJZZUe51=Ge68X1Cnwsb4-eDGcxy3sOH9Yyzsay3h4MAOktw@mail.gmail.com>
Date	2012-10-14 15:49 +1100
Subject	Re: Understanding and dealing with an exception
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.2166.1350190179.27098.python-list@python.org> (permalink)

Show all headers | View raw

On Sun, Oct 14, 2012 at 3:36 PM, Vincent Davis <vincent@vincentdavis.net> wrote:
> Oops, I was going to make note of the file size. 1.2MB

Then I'd definitely declare the file bad; I don't know what the valid
ranges for channels and ysize are, but my reading of that is that your
file's completely corrupt, maybe even malicious. PIL probably ought to
check these things, so there may be a tracker issue coming from this,
but I'd be inclined to declare any thrown exception as meaning it's a
bad file. Call it "failed a security check" perhaps.

ChrisA

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Understanding and dealing with an exception Chris Angelico <rosuav@gmail.com> - 2012-10-14 15:49 +1100

csiph-web