On Fri, Dec 14, 2012 at 6:30 PM, Paul Rudin wrote:
> Chris Angelico writes:
>
>> On Fri, Dec 14, 2012 at 6:12 AM, RCU wrote:
>>> Dave,
>>> Thanks for the reply.
>>> The script was originally edited on Windows with proper \r\n endings,
>>
>> It's worth noting that many Windows-based edi
Chris Angelico writes:
> On Fri, Dec 14, 2012 at 6:12 AM, RCU wrote:
>> Dave,
>> Thanks for the reply.
>> The script was originally edited on Windows with proper \r\n endings,
>
> It's worth noting that many Windows-based editors and interpreters are
> quite happy with \n line endings.
On Fri, Dec 14, 2012 at 6:12 AM, RCU wrote:
> Dave,
> Thanks for the reply.
> The script was originally edited on Windows with proper \r\n endings,
It's worth noting that many Windows-based editors and interpreters are
quite happy with \n line endings. You may be able to save yourself
s
Dave,
Thanks for the reply.
The script was originally edited on Windows with proper \r\n endings, but the
PythonTidy script somehow does the doubling (I guess it assumes UNIX format only), i.e.,
\r\r\n . So indeed, that's kind of messy (and the Python Lang Reference specifies clearly
On 12/12/2012 2:10 PM, RCU wrote:
I would like to report a parser bug manifesting on Python 2.5, 2.7
(but not on 2.2) and 3.3.
You are not the first to erroneously attribute a problem to Python
itself. But seriously, the interpreter itself is so thoroughly tested on
a daily basis that yo
On Wed, Dec 12, 2012 at 2:10 PM, RCU wrote:
> With this occasion I would like to ask also what are the limits of the
> Python 2.x and 3.x parser. Where can I find what are the limits on the
> size/lines of the parsed script?
The Python Language Reference is probably what you're looking for:
h
On 12/12/2012 02:10 PM, RCU wrote:
> Hello.
> I would like to report a parser bug manifesting on Python 2.5, 2.7
> (but not on 2.2) and 3.3.
> Please see the attached script.
> Basically this bug appeared after applying PythonTidy on a valid
> script.
>
> More exactly, when runnin
Hello.
I would like to report a parser bug manifesting on Python 2.5, 2.7 (but not on 2.2)
and 3.3.
Please see the attached script.
Basically this bug appeared after applying PythonTidy on a valid script.
More exactly, when running:
python -c "import iCam_GIT5_5"