> (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>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4