Re: import from future

2007-01-29 Thread Peter Otten
Marc 'BlackJack' Rintsch wrote: > In <[EMAIL PROTECTED]>, Dan Bishop > wrote: > >> Now that nested_scopes and generators are no longer optional, the only >> thing left is "from __future__ import division", which makes the "/" >> operator on integers give the same result as for floats. > > From 2

Re: import from future

2007-01-28 Thread Marc 'BlackJack' Rintsch
In <[EMAIL PROTECTED]>, Dan Bishop wrote: > Now that nested_scopes and generators are no longer optional, the only > thing left is "from __future__ import division", which makes the "/" > operator on integers give the same result as for floats. >From 2.5 on we have `with_statement`:: >>> __f

Re: import from future

2007-01-28 Thread Dan Bishop
On Jan 28, 1:25 am, "lee" <[EMAIL PROTECTED]> wrote: > what are the things that we can do with import from future usage.i > heard its very interesting..thanks Now that nested_scopes and generators are no longer optional, the only thing left is "from __future__ import division", which make

Re: import from future

2007-01-27 Thread Marc 'BlackJack' Rintsch
In <[EMAIL PROTECTED]>, lee wrote: > what are the things that we can do with import from future usage.i > heard its very interesting..thanks Here's how to find out yourself (done with a 2.4 release): In [2]: import __future__ In [3]: dir(__future__) Out[3]: ['CO_FUTURE_DIVISION', 'CO_