On 08/12/2013 09:20 AM, Zachary Ware wrote:
On Mon, Aug 12, 2013 at 7:33 AM, Devyn Collier Johnson
<devyncjohn...@gmail.com> wrote:
On 08/10/2013 10:47 PM, Chris Angelico wrote:
On Sun, Aug 11, 2013 at 3:43 AM, Roy Smith <r...@panix.com> wrote:
In article <mailman.452.1376188442.1251.python-l...@python.org>,
Chris Angelico <ros...@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.
Zachary, are you, Ned, and Terry trying to say the syntax should be
job = multiprocessing.Process(func1(), func2())
not
job = multiprocessing.Process(func1(); func2())
DCJ
--
http://mail.python.org/mailman/listinfo/python-list
