Great. I also opened issue
1467<https://code.google.com/p/spyderlib/issues/detail?id=1467>since I
assume that the pyflakes now flags print statements other than
print() as syntax errors.

David


On 27 June 2013 07:03, Jed Ludlow <[email protected]> wrote:

> On Wednesday, June 26, 2013 3:43:58 PM UTC-5, David wrote:
>
>> I have the impression that in the current code base
>> from __future__ import print_function
>> leads to pyflakes marking
>> print ""
>> as a syntax error in the editor when using python2. Further, the
>> scientific startup script also uses python3 print style statements. It
>> took me a while to realize this (when I sent the first mail on this
>> thread I didn't). Although I think this is a good practice knowing
>> that python3 adoption is growing rapidly know. However, shouldn't
>> users (especially first timers) be made aware of this in some fashion?
>> For example: an additional print statement in scientific_startup.py
>> stating that python3 style print statements are in effect?
>
>
> David,
>
> You are correct that on the 2.3 development branch scientific_startup.py
> is importing the print_function for Python 2.7. It's a bug that needs to be
> addressed before 2.3 is released. I've opened issue 
> 1465<https://code.google.com/p/spyderlib/issues/detail?id=1465>to track it.
>
> Jed
>
> --
> You received this message because you are subscribed to the Google Groups
> "spyder" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/spyderlib.
>
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to