On Apr 12, 1:41 pm, "Malcolm Greene" <[EMAIL PROTECTED]> wrote:
> Is there any consensus on what "from __future__ import" options
> developers should be using in their Python 2.5.2 applications?
>
> Is there a consolidated list of "from __future__ import" options to
> choose from?
Just look inside
Malcolm Greene wrote:
> Is there a consolidated list of "from __future__ import" options to
> choose from?
Well, that bit's easy:
import __future__
print __future__.all_feature_names
TJG
--
http://mail.python.org/mailman/listinfo/python-list
Is there any consensus on what "from __future__ import" options
developers should be using in their Python 2.5.2 applications?
Is there a consolidated list of "from __future__ import" options to
choose from?
Thank you,
Malcolm
--
http://mail.python.org/mailman/listinfo/python-list
