On Thursday 11 January 2007 06:32, Georg Brandl wrote: > I guess there are quite a few people who won't start moving to > Python 3.0 with 2.6, or even when 3.1 is out, as long as their > program works fine with the 2.x line. There's no need to punish > them with extra overhead. Checking a single C global int is hardly going to make a huge impact at all. -- Anthony Baxter <anthony at interlink.com.au> It's never too late to have a happy childhood.
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