On Mon, Apr 08, 2002, Barry A. Warsaw wrote: > > >>>>> "A" == Aahz <aahz@pythoncraft.com> writes: > > A> Hrm. But until it's no longer a separate package, why use > A> 2.2-specific features in the builtin package? > > Because it's convenient, and the semantics are subtly different (and > IMO suboptimal) without them. E.g. the builtin version uses a > generator in a few places, while the standalone version uses an > iterator. The generator version is much more intuitive, but to write > cross-version code that uses that interface you need to do something > like call list() on a return value. Well, sure. But you have to do that suboptimal stuff *anyway* in order to maintain the separate package. How is the overall development process more convenient to maintain two codebases? -- Aahz (aahz@pythoncraft.com) <*> http://www.pythoncraft.com/ "There are times when effort is important and necessary, but this should not be taken as any kind of moral imperative." --jdecker
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