Hi, Dino,
Von: Dino Viehland [mailto:di...@microsoft.com]
>> [... reporting warnings for old print statement syntax ...]
> You could add a thread static bool which tracks whether or not we're
> already reporting the warning, and if so don't recurse and report again.
That would fix the problem wit
python.org] On Behalf Of
Markus Schaber
Sent: Thursday, October 13, 2011 1:26 AM
To: Markus Schaber; Discussion of IronPython
Subject: Re: [Ironpython-users] Patch: Warn user when using old print syntax
Hi,
Von: ironpython-users-bounces+m.schaber=3s-software@python.org
> Von: Markus Sc
Hi,
Von: ironpython-users-bounces+m.schaber=3s-software@python.org
> Von: Markus Schaber
> > The patch below emits a warning during Compilation for print
> > statements whose argument list does not start with a '(' if Py3k warnings
> are enabled.
>
> Somehow, this patch leads to a StackOverFl
Hi,
Von: Markus Schaber
> The patch below emits a warning during Compilation for print statements
> whose argument list does not start with a '(' if Py3k warnings are enabled.
Somehow, this patch leads to a StackOverFlowException in some cases, so please
don't apply it.
(It seemed to work fine
Thanks!
Can you make this a pull request on GitHub? It's much easier to manage
patches from there.
- Jeff
On Wed, Oct 12, 2011 at 7:44 AM, Markus Schaber
wrote:
> Hi,
>
> Von: Markus Schaber
>> Von: Dino Viehland [mailto:di...@microsoft.com]
>> > So you want to warn if the file contains a print
Hi,
Von: Markus Schaber
> Von: Dino Viehland [mailto:di...@microsoft.com]
> > So you want to warn if the file contains a print statement w/o from
> > __future__ import print_function? What if it's a call to print such
> > as
> > print('foo') which is valid in both 2.x and 3.x?
>
> Considering o
