On Sat, May 5, 2012 at 6:49 AM, Carl Meyer <c...@oddbird.net> wrote: > 2) In addition to the above, introduce a versioning marker in the standard > library (is there one already?) and have some code somewhere (insert > hand-waving here) check sys.version_info against the stdlib version, and > fail fast with an unambiguous error if there is a mismatch. This makes the > failure more explicit, but at the significant cost of making it more common: > at every mismatch, not just in the apparently-rare case of a breaking > change.
Variant: Could the versioning marker give a minimum and/or maximum? It'd then only cause the explicit failure in the actual case of a breaking change, and the rest of the time it could happily use any X.Y.* release. ChrisA _______________________________________________ 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
