On Thu, Mar 20, 2008 at 12:10 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Eric Smith schrieb: > > py3k supports future imports. For example, "from __future__ import > > with_statement" works, and I presume it's a no-op. I did not forward > > port print_function, but maybe I should? > > Python 3.0 must accept all future imports that are available in the 2.x > series although they are no-ops. from __future__ import feature has to > work even if the feature is already available by default. This surprises me greatly. The reason this is true in 2.x is for the obvious backward compatibility. 3.0 is about not worrying about backward compatibility. Why do we need to keep the future imports? -- Thomas Wouters <[EMAIL PROTECTED]> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
_______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
