Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

On Wed, Jan 10, 2007 at 06:04:05PM -0800, Raymond Hettinger wrote: > [Anthony Baxter] > > I've had a number of people say that this is something they would > > really, really like to see - the idea is both to let people migrate > > more easily, and provide reassurance that it won't be that bad to

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

[Anthony Baxter] > I've had a number of people say that this is something they would > really, really like to see - the idea is both to let people migrate > more easily, and provide reassurance that it won't be that bad to > migrate! If Py3.0 is going to come out before Py2.6, can we table the

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

On Thursday 11 January 2007 06:32, Georg Brandl wrote: > I guess there are quite a few people who won't start moving to > Python 3.0 with 2.6, or even when 3.1 is out, as long as their > program works fine with the 2.x line. There's no need to punish > them with extra overhead. Checking a single C

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

On Thursday 11 January 2007 07:48, Thomas Wouters wrote: > They serve a different purpose, and it isn't taking any time away > from me (or Anthony, I can confidently guess) working on 2to3. Correct. Note that checking for something like dict.has_key is going to be far far more reliable from insid

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

At 11:10 PM 1/10/2007 +, Paul Moore wrote: >On 10/01/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I've been assuming for some time that the only hope for Py3k compatibility > > within Twisted would be using PyPy as a translation layer. > >Does this ring as many warning bells for me as i

Re: [Python-Dev] python-ideas on gmane

[Georg Brandl] > is there any objection against making python-ideas available on gmane? It's already there. That's how I read it. -- David Goodger signature.asc Description: OpenPGP digital signature ___ Python-Dev maili

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

Paul Moore wrote: > How many other projects/packages anticipate *not* migrating to Py3K, I wonder? I certainly can't speak for the project as a whole, but I anticipate a fair bit of work to port Zope 3 (100+ KLOC) to Python 3.0. -- Benji York ___ Python

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

On 10/01/07, Paul Moore <[EMAIL PROTECTED]> wrote: > Does this ring as many warning bells for me as it does for others? ... for others as it does for me ... Doh. Paul ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listi

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

On 10/01/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I've been assuming for some time that the only hope for Py3k compatibility > within Twisted would be using PyPy as a translation layer. Does this ring as many warning bells for me as it does for others? I know very little about the curren

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

Thomas Wouters wrote: [...] > > Ok, so, you're actually agreeing, except for the DeprecationWarning > subclassing. There was never an intent to display these py3k deprecation > warnings without an explicit flag (at least, not in this thread.) > Hopefully that puts some people at ease. > If the

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

On 1/10/07, Steve Holden <[EMAIL PROTECTED]> wrote: Thomas Wouters wrote: > > > On 1/10/07, *Steve Holden* <[EMAIL PROTECTED] > > wrote: > > Collin Winter wrote: > > On 1/10/07, Thomas Wouters <[EMAIL PROTECTED] > > wrote: > >

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

Thomas Wouters wrote: > > > On 1/10/07, *Steve Holden* <[EMAIL PROTECTED] > > wrote: > > Collin Winter wrote: > > On 1/10/07, Thomas Wouters <[EMAIL PROTECTED] > > wrote: > >> On 1/10/07, Raymond Hettinger < [EMAIL PROTECTED]

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

On 07:42 pm, [EMAIL PROTECTED] wrote: >On 1/10/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote: >> >><"Anthony Baxter"> >> > Comments? What else should get warnings? >> >>It is my strong preference that we not go down this path. >>Instead, the 2.6 vs 3.0 difference analysis should go in an >>extern

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

sorry this is actually more an answer to Raymond's email but I accendidentally delete it some I'm replying there. On Wednesday 10 January à 20:42, Thomas Wouters wrote: > On 1/10/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote: > > <"Anthony Baxter"> > > Comments? What else should get war

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

[Thomas Wouters] > By Guido's plan, 3.0 will arrive well before 2.6, and the migration step is > not as > large as many fear it to be. Having Python 2.6 optionally warn for > 3.0-compatibility > is a lot easier for the average developer than having a separate tool or a > separately > compiled P

Re: [Python-Dev] python-ideas on gmane

On 1/10/07, Georg Brandl <[EMAIL PROTECTED]> wrote: > Hi, > > is there any objection against making python-ideas available on gmane? > Should I just suggest it myself, or has someone to do extra admin work > on the mailing list side? > Just email me personally the email address to subscribe. -Bre

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

On 1/10/07, Steve Holden <[EMAIL PROTECTED]> wrote: Collin Winter wrote: > On 1/10/07, Thomas Wouters <[EMAIL PROTECTED]> wrote: >> On 1/10/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote: >>> It is my strong preference that we not go down this path. >>> Instead, the 2.6 vs 3.0 difference analys

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

Collin Winter wrote: > On 1/10/07, Thomas Wouters <[EMAIL PROTECTED]> wrote: >> On 1/10/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote: >>> It is my strong preference that we not go down this path. >>> Instead, the 2.6 vs 3.0 difference analysis should go in an >>> external lint utility. >>> >>> T

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

On 1/10/07, Thomas Wouters <[EMAIL PROTECTED]> wrote: > On 1/10/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote: > > It is my strong preference that we not go down this path. > > Instead, the 2.6 vs 3.0 difference analysis should go in an > > external lint utility. > > > > The Py2.x series may live

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 10, 2007, at 2:42 PM, Thomas Wouters wrote: > The idea is that we only generate the warnings optionally, only for > things > that can be written in a manner compatible with prevalent Python > versions, > and in the most efficient manner we

[Python-Dev] python-ideas on gmane

Hi, is there any objection against making python-ideas available on gmane? Should I just suggest it myself, or has someone to do extra admin work on the mailing list side? Georg ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/m

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

On 1/10/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote: <"Anthony Baxter"> > Comments? What else should get warnings? It is my strong preference that we not go down this path. Instead, the 2.6 vs 3.0 difference analysis should go in an external lint utility. The Py2.x series may live-on for s

Re: [Python-Dev] [Python-3000-checkins] r53335 - in python/branches/p3yk: Doc/Makefile.deps Doc/lib/lib.tex Doc/lib/libsets.tex Doc/lib/libstdtypes.tex Lib/msilib/__init__.py Lib/sets.py Lib/test/test

On 1/9/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > On 1/9/07, Brett Cannon <[EMAIL PROTECTED]> wrote: > > Should we bother with deprecating 'sets' in the 2.x series? > > I'd say so, yes. > OK, I work on deprecating the sets module in 2.6 . -Brett

Re: [Python-Dev] [Python-3000] Warning for 2.6 and greater

<"Anthony Baxter"> > Comments? What else should get warnings? It is my strong preference that we not go down this path. Instead, the 2.6 vs 3.0 difference analysis should go in an external lint utility. The Py2.x series may live-on for some time and should do so as if Py3.x did not exist. Bur