On Mar 7, 6:59 pm, Carl Banks wrote:
>
> I see that Brett Canon's importlib has finally made it into Python
> standard library. Congrats there (if you still read this list), I am
> struggling with Python's arcane import semantics (for something
> ridiculously silly) now and I feel your pain.
>
H
Colin J. Williams ncf.ca> writes:
> Do you have any schedule for a Windows
> binary release?
They should materialize on Monday.
--
http://mail.python.org/mailman/listinfo/python-list
Benjamin Peterson wrote:
On behalf of the Python development team and the Python community, I'm
happy to announce the first alpha release of Python 3.1.
Python 3.1 focuses on the stabilization and optimization of features and changes
Python 3.0 introduced. The new I/O system has been rewritten
Benjamin Peterson:
>It provides a good incentive for people to upgrade. :)<
Sometimes at work you are forced you to use Python 2.x, so incentives
aren't much relevant.
Christian Heimes:
> No, the MS Visual C compiler doesn't supported labels as values [1]. The
> feature is only supported by som
bearophileh...@lycos.com wrote:
> Are the computed gotos used in the future pre-compiled Windows binary
> (of V.3.1) too?
No, the MS Visual C compiler doesn't supported labels as values [1]. The
feature is only supported by some compilers like GCC.
Christian
[1] http://gcc.gnu.org/onlinedocs/gcc
lycos.com> writes:
>
> Are the computed gotos used in the future pre-compiled Windows binary
> (of V.3.1) too?
I doubt it. I don't think they've even been built yet. Martin will now, though.
>
> Is such optimization going to be backported to the 2.x series too,
> like Python 2.7?
Probably n
Are the computed gotos used in the future pre-compiled Windows binary
(of V.3.1) too?
Is such optimization going to be backported to the 2.x series too,
like Python 2.7?
Bye and thank you for your work,
bearophile
--
http://mail.python.org/mailman/listinfo/python-list
Scott David Daniels Acm.Org> writes:
>
> Benjamin Peterson wrote:
> > On behalf of the Python development team and the Python community, I'm
> > happy to announce the first alpha release of Python 3.1.
>
> Congratulations on the release.
> I know 3.0 didn't have installers built for the alphas,
On Mar 7, 10:53 am, Benjamin Peterson wrote:
> On behalf of the Python development team and the Python community, I'm
> happy to announce the first alpha release of Python 3.1.
>
> Python 3.1 focuses on the stabilization and optimization of features and
> changes
> Python 3.0 introduced. The new
Benjamin Peterson wrote:
On behalf of the Python development team and the Python community, I'm
happy to announce the first alpha release of Python 3.1.
Congratulations on the release.
I know 3.0 didn't have installers built for the alphas, will that be the
case for 3.1?
--Scott David Daniels
[Benjamin Peterson]
On behalf of the Python development team and the Python community, I'm
happy to announce the first alpha release of Python 3.1.
Thanks for the good work.
Raymond
--
http://mail.python.org/mailman/listinfo/python-list
2009/3/7 Gerard Flanagan :
> Benjamin Peterson wrote:
> On the release page, the bzip link says '3.0' not '3.1'.
That should be fixed now.
>
>> See PEP 375 for release schedule details:
>>
>> http://www.python.org/dev/peps/pep-0361/
That URL is actually supposed to be http://www.python.org/d
On behalf of the Python development team and the Python community, I'm
happy to announce the first alpha release of Python 3.1.
Python 3.1 focuses on the stabilization and optimization of features and changes
Python 3.0 introduced. The new I/O system has been rewritten in C for speed.
Other featu
13 matches
Mail list logo
