Thomas Wouters wrote: > If 2.5 warns and does the old thing, the upgrade path is easy and > defendable. This is also why there are future statements -- I > distinctly recall making the same argument back then :-) The cost of > continuing the misfeatures in struct for one release does not weigh > up to the cost of breaking compatibility unwarned.
This really sounds to me like a __future__ import would be useful to get the fixed behaviour. Tim Delaney _______________________________________________ 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
