[Kevin Jacobs] > And there are a ton of problems/bugs in trace.py from the current Python > CVS. Doesn't surprise me. It's a hairy subject, and judging from the comments embedded in the code, none of the contributors so far have shown a complete grasp of the issues. :-) > I've fixed about a dozen so far, and still going. I'll submit diffs > as soon as I see the light at the end of the tunnel. Maybe I'm just > running trace in a very different way than most and exercising some > of the weirder code paths? Everybody who uses this code uses it in a completely ideosyncratic way. That's what makes it so frustrating to try to unify the changes. > In spite of the many esteemed contributors and the upcoming fixes > from me, the design and the code are very raw and are (IMHO) a long > way from being production quality. Of course, if everyone pitches > in and we have a code frag-fest, it could conceivably be ready quite > soon. Go for it! --Guido van Rossum (home page: http://www.python.org/~guido/)
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