On Tue, Feb 18, 2014 at 1:30 AM, M.-A. Lemburg <m...@egenix.com> wrote: >> >> Also think of the implications of changing None at this point. It would >> allow us to write programs that work Python >= 3.5 and Python <= 2.7, but >> fail mysteriously in all other versions in between. What a mess that would >> be... > > Yes, that's unfortunately true.
I don't know that that's in itself that much of a problem. (BTW, I wouldn't call it "<= 2.7"; it'd be all 2.x, it's not like some of the 2.7.y versions aren't included.) There are already barriers to supporting 2.7 and 3.1/3.2, like the u"asdf" notation for Unicode literals. Making it easier to support 2.x and 3.x from the same codebase is an improvement that has been done and will be done more. It's not such a mysterious failure; it's just that you support Python 2.5+ and 3.4+ (or whatever the specific versions are). ChrisA _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
