> [Skip Montanaro] > > #- Is it intended to remain 2.3-compatible for the forseeable > #- future? It's not > #- mentioned in PEP 291, nor is there any discussion of > #- portability to 2.3 in > #- PEP 327. > > I don't have plans to do some effort to keep it "2.3-runnable" when Py2.4 > hits the street. Don't know if Raymond or somebody will preocupate about > this. Yes, I've been keeping it Py2.3 compatible and periodically test it on 2.3 just to make sure. Am hesitant to introduce this as a specific, on-going restriction to the code, but I don't want to throw-away 2.3 compatibility unless there is a darned good offsetting gain. Raymond
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