On 08/03/2016 13:49, BartC wrote:
On 08/03/2016 04:40, Steven D'Aprano wrote:
On Tuesday 08 March 2016 12:41, BartC wrote:
Nevertheless, in the real world, you have to deal with corrupt JPGs and
files mislabelled as JPGs. And "crashing" doesn't count as "deal with"
:-)
OK, I changed the 'raise' line to 'exit(0)'. Job done!
(I couldn't recreate the problem easily because the common failures
didn't call abortjpeg() at all.)
It doesn't make Py3 any faster than Py2 though...
So what, if 99% of people couldn't care less about that fact?
--
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.
Mark Lawrence
--
https://mail.python.org/mailman/listinfo/python-list
