On Jan 9, 10:19 pm, John Machin wrote:
> On Jan 10, 2:55 pm, Benjamin wrote:
>
> > We'll need good documentation. Unfortunately, as you
> > note below, this isn't exactly the case yet.
>
> So is there a plot to remedy this? Where do we sign up?
Feel free to contribute to the wiki page:
http://w
On Jan 10, 2:55 pm, Benjamin wrote:
> On Jan 8, 11:35 pm, John Machin wrote:
> > > Actually, don't bother now; I've fixed it up in the trunk.
>
> > Would you mind giving a pointer to where or what your fix is? The
> > reason for asking is that Thorsten's suggestion is ambiguous: warn
> > about s
On Jan 8, 11:35 pm, John Machin wrote:
> On Jan 9, 1:56 pm, Benjamin wrote:
>
> > On Jan 8, 4:21 pm, Thorsten Kampe wrote:
>
> > > * Terry Reedy (Thu, 08 Jan 2009 17:04:04 -0500)
> > > > Since you are, I believe, at least the second person to report being bit
> > > > by this confusion, please op
On Jan 9, 1:56 pm, Benjamin wrote:
> On Jan 8, 4:21 pm, Thorsten Kampe wrote:
>
> > * Terry Reedy (Thu, 08 Jan 2009 17:04:04 -0500)
> > > Since you are, I believe, at least the second person to report being bit
> > > by this confusion, please open an issue at bugs.python.org and suggest a
> > > c
On Jan 8, 4:21 pm, Thorsten Kampe wrote:
> * Terry Reedy (Thu, 08 Jan 2009 17:04:04 -0500)
> > Since you are, I believe, at least the second person to report being bit
> > by this confusion, please open an issue at bugs.python.org and suggest a
> > couple of revised sentences that you think are mo
* Terry Reedy (Thu, 08 Jan 2009 17:04:04 -0500)
> Thorsten Kampe wrote:
> > * Marc 'BlackJack' Rintsch (8 Jan 2009 16:26:55 GMT)
> >> On Thu, 08 Jan 2009 16:38:53 +0100, Thorsten Kampe wrote:
> >>> [Python 2.6.1]
> >>>
> >>> to test existing Python code, I ran "python -3" ("warn about Python 3.x
>
Thorsten Kampe wrote:
* Marc 'BlackJack' Rintsch (8 Jan 2009 16:26:55 GMT)
On Thu, 08 Jan 2009 16:38:53 +0100, Thorsten Kampe wrote:
[Python 2.6.1]
to test existing Python code, I ran "python -3" ("warn about Python 3.x
incompatibilities") against a test file that only contains "print
'test'".
* Marc 'BlackJack' Rintsch (8 Jan 2009 16:26:55 GMT)
> On Thu, 08 Jan 2009 16:38:53 +0100, Thorsten Kampe wrote:
> > [Python 2.6.1]
> >
> > to test existing Python code, I ran "python -3" ("warn about Python 3.x
> > incompatibilities") against a test file that only contains "print
> > 'test'".
> >
Steve Holden holdenweb.com> writes:
> Thorsten Kampe wrote:
> > Unfortunately I saw no warnings about print becoming a function in
> > Python 3 ("print()"). Where is the problem?
> >
> I *believe* that's not flagged because 2to3 will fix it automatically.
This is correct; there's not much point
Thorsten Kampe wrote:
> [Python 2.6.1]
>
> Hi,
>
> to test existing Python code, I ran "python -3" ("warn about Python 3.x
> incompatibilities") against a test file that only contains "print
> 'test'".
>
> Unfortunately I saw no warnings about print becoming a function in
> Python 3 ("print()
On Thu, 08 Jan 2009 16:38:53 +0100, Thorsten Kampe wrote:
> [Python 2.6.1]
>
> Hi,
>
> to test existing Python code, I ran "python -3" ("warn about Python 3.x
> incompatibilities") against a test file that only contains "print
> 'test'".
>
> Unfortunately I saw no warnings about print becoming
[Python 2.6.1]
Hi,
to test existing Python code, I ran "python -3" ("warn about Python 3.x
incompatibilities") against a test file that only contains "print
'test'".
Unfortunately I saw no warnings about print becoming a function in
Python 3 ("print()"). Where is the problem?
Thorsten
--
htt
12 matches
Mail list logo