Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
Sender: zachary.ware@gmail.com
In-Reply-To: <5208D625.2000103@Gmail.com>
References: <5206F4AB.8050204@Gmail.com> <mailman.452.1376188442.1251.python-list@python.org> <roy-4A9C13.22431010082013@news.panix.com> <CAPTjJmoA+r3ABByjgMNC-23H0tB95r6S+d04T-KF-3xgbCNSOQ@mail.gmail.com> <5208D625.2000103@Gmail.com>
From: Zachary Ware <zachary.ware+pylist@gmail.com>
Date: Mon, 12 Aug 2013 08:20:15 -0500
Subject: Re: Am I not seeing the Error?
To: Devyn Collier Johnson <devyncjohnson@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: Python Mailing List <python-list@python.org>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.497.1376313643.1251.python-list@python.org>
Lines: 52
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:52414

On Mon, Aug 12, 2013 at 7:33 AM, Devyn Collier Johnson
<devyncjohnson@gmail.com> wrote:
>
> On 08/10/2013 10:47 PM, Chris Angelico wrote:
>>
>> On Sun, Aug 11, 2013 at 3:43 AM, Roy Smith <roy@panix.com> wrote:
>>>
>>> In article <mailman.452.1376188442.1251.python-list@python.org>,
>>>   Chris Angelico <rosuav@gmail.com> wrote:
>>>
>>>> When you get a syntax error you can't understand, look at the previous
>>>> line of code. Perhaps something there is incomplete; maybe you have
>>>> mismatched parentheses, so this line is considered to be part of the
>>>> same expression.
>>>>
>>>> Next thing to do is split it into more lines. Why is all that in a
>>>> single
>>>> line?
>>>
>>> Also, try reformatting the code in a tool like emacs or eclipse which
>>> does syntax coloring and auto indenting.  Often, if you're missing some
>>> piece of punctuation, it will become obvious when your tool tries to
>>> indent things in some unexpected way.  Or suddenly starts coloring all
>>> of your program text as if it were a string literal :-)
>>
>> Agreed. Though I've had some odd issues with SciTE in that way; I
>> think its Python handling may have bugs in it here and there. But 95%
>> of the time it's helpful.
>>
>> ChrisA
>
>
> Thanks everyone. Unfortunately, I have not found the problem yet. I use the
> Geany IDE which has syntax highlighting, but nothing wrong is seen. None of
> the suggestions helped. The lines before this one set variables. The lines
> further up "appear" fine. I will keep looking. If I ever figure it out, I
> will share with all of you.
>
> As for the code being one line, my style of coding is very different from
> others. I try to keep similar or related tasks on one line. Programming like
> that is called trolling. A programmer that uses trolling is called a troll.
> A troll can also refer to such a line of code itself. My scripts contain a
> lot of trolls. It is easier for me to read trolls than "typical" coding
> styles.

Obviously not, since you can't find the syntax error.  If you replace
each semicolon in that line with a newline, the syntax error will be
immediately obvious.  I'll even give you a hint: it's on the third
line.

-- 
Zach