> (there's still a possibility that someone checks in a fix without realizing > that > the original bug is an attack vector, but I don't think Coverity has > discovered > anything like that in the Python code base; we're mainly talking about leaks > and null-pointer references here).
to clarify, "potential leaks and null-pointer references". we already have Neal for leaks, and a large user base for null-pointer references... </F> _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
