On behalf of the Python development team and the Python
community, I'm happy to announce the second alpha release
of Python 2.5.
This is an *alpha* release of Python 2.5. As such, it is not
suitable for a production environment. It is being released to
solicit feedback and hopefully discover bugs,
Terry Reedy wrote:
> "Alexander Myodov" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > and even list comprehensions:
> > b1 = [l for l in a1]
> > print "l: %s" % l
>
> This will go away in 3.0. For now, del l if you wish.
Or use a generator expression:
>>> b1 = list(l for l
"Alexander Myodov" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hello,
> for k in a1:
>pass
> print "k: %s" % k
> where "k" lives long after the actual need in it was lost,
There are occasions, especially when one breaks out of the loop, when
keeping k bound *is* useful.
Alexander Myodov wrote:
> Or maybe you have an idea how this can be fixed? The
> simplest way I see is putting all the "controlled" variables into a
> dedicated class... and do that each time for each block of variables I
> need control lifetime. Is there any simpler way?
I wouldn't use the word
Alexander Myodov wrote:
> Sorry, I misworded the question - RIIA is indeed present at least by
> the reason that the examples from PEP pass. Agree, my problem is a bit
> different, and I a bit mixed up initialization/acquisition with
> lifetime blocks. So, seems that we indeed have one and still do
>> No, it means that Python 2.5 supports 'resource initialisation is
>> acquisition', but that has nothing to do with the restricting the
>> lifetime of a variable.
> Sorry, I misworded the question - RIIA is indeed present at least by
> the reason that the examples from PEP pass. Agree, my problem
Hello Duncan,
You wrote:
> Alexander Myodov wrote:
>> So, with 2.5, I tried to utilize "with...as" construct for this, but
>> unsuccessfully:
>> ...
>> So, does this mean that we still don't have any kind of RIIA in
>> Python, any capability to localize the lifetime of variables on a
>> level less
Alexander Myodov wrote:
> So, with 2.5, I tried to utilize "with...as" construct for this, but
> unsuccessfully:
>from __future__ import with_statement
>with 5 as k:
> pass
>print k
> - told me that "AttributeError: 'int' object has no attribute
> '__context__'".
>
>
> So, does
Hello,
Having heard that Python 2.5 offers some kind of RIIA concept via
PEP343, got it downloaded (Windows version) and tried. But it did not
work as expected and as wanted.
For the time since I first learned Python, the only reason why I just
could not use it was inability to localize the lifeti
"Michele Simionato" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Michael Ekstrand wrote:
>> The day Python (without using Stackless) has true continuations will be
>> a happy day.
Don't hold your breath. Guido regards 'true continuations' as complexity
overload for the typical
Michael Ekstrand wrote:
> Michele Simionato wrote:
> > Michael Ekstrand wrote:
> >> After reading AMK's survey of what's new in Python 2.5, I am suitably
> >> impressed. As usual, I can't wait to start using the cool new
> >> features... extended generators? (mind is currently swimming with the
>
Michele Simionato wrote:
> Michael Ekstrand wrote:
>> After reading AMK's survey of what's new in Python 2.5, I am suitably
>> impressed. As usual, I can't wait to start using the cool new
>> features... extended generators? (mind is currently swimming with the
>> question of "can I implement Sche
There are lot of new things!
Is Hettinger's collections.bag going in Python 2.5 too?
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/259174
Bye,
bearophile
--
http://mail.python.org/mailman/listinfo/python-list
That is cool and that will be a great addition to the libraries.
Robert
--
http://mail.python.org/mailman/listinfo/python-list
Michael Ekstrand wrote:
> Anyway, the more important question that came to mind: I see that 2.5
> will include the excellent ElementTree. Will cElementTree be included
> where available? or is it only the pure-Python version that will be in
> the standard library?
they're both available, via the
Michael Ekstrand wrote:
> After reading AMK's survey of what's new in Python 2.5, I am suitably
> impressed. As usual, I can't wait to start using the cool new
> features... extended generators? (mind is currently swimming with the
> question of "can I implement Scheme's call-with-current-continua
Michael Ekstrand wrote:
> [...]
> Anyway, the more important question that came to mind: I see that 2.5
> will include the excellent ElementTree. Will cElementTree be included
> where available? or is it only the pure-Python version that will be in
> the standard library?
Both elementtree as (
After reading AMK's survey of what's new in Python 2.5, I am suitably
impressed. As usual, I can't wait to start using the cool new
features... extended generators? (mind is currently swimming with the
question of "can I implement Scheme's call-with-current-continuation
using extended generato
On behalf of the Python development team and the Python
community, I'm happy to announce the first alpha release
of Python 2.5.
This is an *alpha* release of Python 2.5, and is the *first*
alpha release. As such, it is not suitable for a production
environment. It is being released to solicit feed
"D Hering" wrote:
> I just installed 2.5a0
what part of aahz's "There is no Python 2.5 alpha" did you not
understand?
> in an alternative directory (make altinstall) which
> build and tested out fine. I'm gonna now attempt to compile the module
> pa
So far so good. Numeric-24.0b2, numarray-1.3.3, pytables-1.1.1 (gonna
wait alittle on the scipy install) all built. Tests passed except one
trivial test in numarray but does function:
1 items had failures:
1 of 1205 in cache pass
***Test Failed*** 1 failures.
File "/usr/local/lib/python2.5/site
Hi Aahz,
Yes thank you. To clarify the cvs dist README listed Python version 2.5
alpha 0. I should have realized before posting that replacing was a bad
idea and another "slot-ed" version could be installed (package manager
already has 2.3.5 & 2.4.1). I just installed 2.5a0 in an alternative
direct
D.Hering wrote:
> under gentoo linux 2.6.
that does not exist. gentoo labels installers 2005.0 etc, but I have
never heard of version numbers.
do you mean gentoo with linux 2.6 ?
--
http://mail.python.org/mailman/listinfo/python-list
In article <[EMAIL PROTECTED]>,
D.Hering <[EMAIL PROTECTED]> wrote:
>
>Generally, what sort of compatibility problems should I expect if I
>were to replace 2.4.1 with 2.5 alpha (current cvs dist)? I'm working
>under gentoo linux 2.6.
There is no Python 2.5 alpha.
Generally, what sort of compatibility problems should I expect if I
were to replace 2.4.1 with 2.5 alpha (current cvs dist)? I'm working
under gentoo linux 2.6.
Specifically, should I expect any problems with Numarray, Scipy, or
Pytables or IDE's. My degree of understanding such things is limited,
25 matches
Mail list logo