On Fri, 2 Aug 2002, Guido van Rossum wrote: > > > (I suppose you still *support* the SET_LINENO opcode?) > > > > No. Do you think I should? > > I like to be on the conservative side. Also, it would make life > easier for the compiler package until Jeremy has time to fix it. :-) OK. I guess it can go down the bottom of the eval loop now (if that makes any difference). > > > BTW, you should change the .pyc magic number in your patch. > > > > Really? It's already changed since the last released Python. Easy > > enough to change again, though, and it makes testing easier. > > Given that each time I try your patches I get unknown opcode errors, > please change it. OK, but it's 5pm on a Friday here :) Have a good weekend everyone. Cheers, M.
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