This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Taylor.Marks
Recipients Taylor.Marks
Date 2014-10-03.20:39:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1412368771.6.0.381085911452.issue22551@psf.upfronthosting.co.za>
In-reply-to
Content
On Python 2.7.8, on Windows 7, if I start up the Python interactive console using the flags -i -u -c, nothing else will be considered valid syntax from that point forward.

My understanding is:

-i tells Python to enter interactive mode after it's done running whatever else it's told to do
-u tells Python to not buffer output
-c tells Python to treat any further arguments as Python code and to run it
None of these flags should be causing the issues that I'm seeing, I don't think.

Example:

$ python -i -u -c "print('Test')"
Test
>>> print('verify')
  File "<stdin>", line 1
    print('verify')
                ^
SyntaxError: invalid syntax

This doesn't occur on my computer running OS X Mavericks (10.9.4) and Python 2.7.6 which leads me to think this may be a platform or version specific issue...
History
Date User Action Args
2014-10-03 20:39:31Taylor.Markssetrecipients: + Taylor.Marks
2014-10-03 20:39:31Taylor.Markssetmessageid: <1412368771.6.0.381085911452.issue22551@psf.upfronthosting.co.za>
2014-10-03 20:39:31Taylor.Markslinkissue22551 messages
2014-10-03 20:39:31Taylor.Markscreate