[EMAIL PROTECTED] wrote: > I am not addressing this message to the py3k list because its general > message of extreme conservatism on new features is more applicable to > python-dev. However, py3k designers might also take note: if py3k is > going to do something in this area and drop support for the "legacy" > os.path, it would be good to choose something that is known to work and > have few gotchas, rather than just choosing the devil we don't know over > the devil we do. The weaknesses of os.path are at least well-understood.
that's another reason why a new design might as well be defined in terms of the old design -- especially if the main goal is call-site convenience, rather than fancy new algorithms. </F> _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
