On Fri, 28 Jun 2002, Tim Peters wrote: > I don't know what causes this. The little time I've been able to spend on > it ended up finding an obvious buglet in some new-in-2.3 gcmodule code: > > for (i = 0; i <= generation; i++) > generations[generation].count = 0; > > That was certainly intended to index by "i", not by "generation". Good catch! I missed that in spite of reading those lines 20 times. > Note that bound methods in 2.2 also create new objects, etc; that was good > deduction, but not yet good enough <wink>. That is why I added my "PS" about not looking into why it didn't blow up in Python 2.2. In reality, I did look, but only for 30 seconds, and then decided I didn't want to know. -Kevin -- Kevin Jacobs The OPAL Group - Enterprise Systems Architect Voice: (216) 986-0710 x 19 E-mail: jacobs@theopalgroup.com Fax: (216) 986-0714 WWW: http://www.theopalgroup.com
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