>>>>> "MAL" == M <mal@lemburg.com> writes:
MAL> In general, I think it's a good idea to be very careful about
MAL> introduce flashy new stuff to the std lib since it makes
MAL> backporting fixes harder, e.g. using Python 2.1 features is
MAL> OK, but not 2.2 features (if not absolutely necessary or only
MAL> if they are easily separatable from the rest of the code).
This is emerging as a common theme, and a good one to adhere to. I
wonder if we should formalize it (i.e. target the stdlib to Python 2.1
where possible)?
-Barry
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