[Python-3000] Python3 - it's awesome (fwd)

[sk...@pobox.com]

Kudos to the Python 3.0 folks from a poster on comp.lang.python. And it's
not even been released yet...

Cheers,

Skip

[Michael Bayer]

Seconded.  I tried Python 3K for the first time this weekend, spent a few hours with the 2to3 tool and we have 80% of SQLAlchemy unit tests passing on 3.0 now.   It was far easier than I'd hoped, and the decisions made in PY3K make perfect sense to me.  Its a better language and I think it will become popular more quickly than we've all thought.   Great job to everyone on the list here who's spent many months hammering out all the details !

To be determined on our end is how to maintain 2.XX and 3.XX branches, either through an automated 2to3 process, or by maintaining separate branches.  I'm leaning towards the former, possibly by augmenting 2to3 with specially annotated comments that give hints to particularly thorny sections.   As I go through the code base making post-2to3 manual fixes, I'm adding in comments denoting the manual changes which I hope to turn into....something.

It will be critical that we get DBAPI implementations going soon, other than pysqlite I haven't perceived any activity in that area.   It will be interesting to see if we remain with the maintsays of MySQLdb, psycopg2, cx_oracle, or if new 3.0-era contenders come on the scene.

From: Johannes Bauer <dfnson...@gmx.de>

Date: November 17, 2008 4:30:07 AM EST

To: pytho...@python.org

Subject: Python3 - it's awesome

Hello list,

since I've read so much about Python 3 and ran into some trouble which
was supposed to be fixed with 3k, I yesterday came around to compile it
and try it out.

To sum it up: It's awesome. All the promised things like Unicode support
"just work", all significant changes in the lanugage (try/except-Syntax,
float division, file opening, print) I've encountered so far made
absolute sense and it was quite easy to change over (I've been using 2.5
so far). It was really easy to install it locally as my user (I want to
try it out some more before I install it system-wide).

So, why I am posting this here: First, thanks to the great work to
anyone who has contributed. Secondly, I want to encourage anyone who
hasn't tried Python3 out yet to do - it really is easier than you think
and you won't be disappointed.

Kind regards,
Johannes

--
"Meine Gegenklage gegen dich lautet dann auf bewusste Verlogenheit,
verlästerung von Gott, Bibel und mir und bewusster Blasphemie."
        -- Prophet und Visionär Hans Joss aka HJP in de.sci.physik
                        <48d8bf1d$0$7510$5402...@news.sunrise.ch>
--
http://mail.python.org/mailman/listinfo/python-list


_______________________________________________
Python-3000 mailing list
Pytho...@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe: http://mail.python.org/mailman/options/python-3000/mike_mp%40zzzcomputing.com

[Walter Dörwald]

Michael Bayer wrote:

> [...]

> It will be critical that we get DBAPI implementations going soon, other
> than pysqlite I haven't perceived any activity in that area. It will
> be interesting to see if we remain with the maintsays of MySQLdb,
> psycopg2, cx_oracle, or if new 3.0-era contenders come on the scene.

Anthony Tuininga is currently updating cx_Oracle for Python 3.0. See for
example this checkin:

http://cx-oracle.svn.sourceforge.net/viewvc/cx-oracle?view=rev&revision=175

Servus,
Walter

_______________________________________________
Python-3000 mailing list
Pytho...@python.org
http://mail.python.org/mailman/listinfo/python-3000

Unsubscribe: http://mail.python.org/mailman/options/python-3000/python-3000-garchive-63646%40googlegroups.com

[Nick Coghlan]

Michael Bayer wrote:
> Seconded. I tried Python 3K for the first time this weekend, spent a
> few hours with the 2to3 tool and we have 80% of SQLAlchemy unit tests
> passing on 3.0 now. It was far easier than I'd hoped, and the
> decisions made in PY3K make perfect sense to me. Its a better language
> and I think it will become popular more quickly than we've all thought.
> Great job to everyone on the list here who's spent many months
> hammering out all the details !
>
> To be determined on our end is how to maintain 2.XX and 3.XX branches,
> either through an automated 2to3 process, or by maintaining separate
> branches. I'm leaning towards the former, possibly by augmenting 2to3
> with specially annotated comments that give hints to particularly thorny
> sections. As I go through the code base making post-2to3 manual fixes,
> I'm adding in comments denoting the manual changes which I hope to turn
> into....something.

Personally, I think some kind of doctest-style comment based hints or
directives for 2to3 could be very useful in helping folks to automate
the generation of the 3.0 versions of their code.

But it will take feedback from those doing the conversions to determine
what kind of directives would actually be helpful (if any).

Cheers,
Nick.

--
Nick Coghlan | ncog...@gmail.com | Brisbane, Australia
---------------------------------------------------------------

_______________________________________________
Python-3000 mailing list
Pytho...@python.org
http://mail.python.org/mailman/listinfo/python-3000

Unsubscribe: http://mail.python.org/mailman/options/python-3000/python-3000-garchive-63646%40googlegroups.com