Hi, On 2/26/12 12:34 PM, Ned Batchelder wrote: > There are already __future__ imports that violate this principle: from > __future__ import division. That doesn't mean I'm in favor of this new > __future__, just keeping a wide angle on the viewfinder. That's actually mentioned in the PEP :-)
> A quick poll on Twitter about the use of the division future import > supported my suspicions that people opt out of behaviour-changing > future imports because they are a maintenance burden. Every time you > review code you have to check the top of the file to see if the > behaviour was changed. Regards, Armin _______________________________________________ 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
