In article ,
Chris Angelico wrote:
> On Wed, Aug 14, 2013 at 7:59 AM, Joshua Landau wrote:
> > On 14 August 2013 02:20, Gregory Ewing wrote:
> >> Ned Batchelder wrote:
> >>>
> >>> Everyone: this program seems to be a direct and misguided transliteration
> >>> from a bash script.
> >>
> >> Not
On 14 August 2013 13:07, Chris Angelico wrote:
> On Wed, Aug 14, 2013 at 7:59 AM, Joshua Landau wrote:
>>
>> What's wrong with cat? Sure it's superfluous but what makes it *bad*?
>> Personally I often prefer the pipe "cat x | y" form to "x < y"... or
>> "< y x".
>
> What's the use of it, in that
On Wed, Aug 14, 2013 at 7:59 AM, Joshua Landau wrote:
> On 14 August 2013 02:20, Gregory Ewing wrote:
>> Ned Batchelder wrote:
>>>
>>> Everyone: this program seems to be a direct and misguided transliteration
>>> from a bash script.
>>
>> Not a particularly well-written bash script, either --
>>
On 14 August 2013 02:20, Gregory Ewing wrote:
> Ned Batchelder wrote:
>>
>> Everyone: this program seems to be a direct and misguided transliteration
>> from a bash script.
>
> Not a particularly well-written bash script, either --
> it's full of superfluous uses of 'cat'.
What's wrong with cat?
On 08/13/2013 04:31 AM, Devyn Collier Johnson wrote:
> For me, this style is easier to read. I have tried the "typical" style,
> but I find this one to be easier.
One thing I do know is that your style makes it very hard to find
errors, even when the parser flags them. And the fact that you post
Ned Batchelder wrote:
Everyone: this program seems to be a direct and misguided
transliteration from a bash script.
Not a particularly well-written bash script, either --
it's full of superfluous uses of 'cat'.
--
Greg
--
http://mail.python.org/mailman/listinfo/python-list
On 8/13/13 5:16 PM, Dave Angel wrote:
Denis McMahon wrote:
On Sat, 10 Aug 2013 22:19:23 -0400, Devyn Collier Johnson wrote:
I am checking my 1292-line script for syntax errors. I ran the following
commands in a terminal to check for errors, but I do not see the error.
JOB_WRITEURGFILES =
mul
On 13/08/2013 21:28, Denis McMahon wrote:
On Sat, 10 Aug 2013 22:19:23 -0400, Devyn Collier Johnson wrote:
I am checking my 1292-line script for syntax errors. I ran the following
commands in a terminal to check for errors, but I do not see the error.
JOB_WRITEURGFILES =
multiprocessing.Proc
Denis McMahon wrote:
> On Sat, 10 Aug 2013 22:19:23 -0400, Devyn Collier Johnson wrote:
>
>> I am checking my 1292-line script for syntax errors. I ran the following
>> commands in a terminal to check for errors, but I do not see the error.
>
>> JOB_WRITEURGFILES =
>> multiprocessing.Process(write
On Sat, 10 Aug 2013 22:19:23 -0400, Devyn Collier Johnson wrote:
> I am checking my 1292-line script for syntax errors. I ran the following
> commands in a terminal to check for errors, but I do not see the error.
> JOB_WRITEURGFILES =
> multiprocessing.Process(write2file('./mem/ENGINE_PID', ENGI
On 8/13/2013 6:31 AM, Devyn Collier Johnson wrote:
I now see why this programming style is called trolling.
'Trolling' is a posting style.
Your initial post was legitimate. When the first three respondents
missed the syntax error, ';' instead of ',' within function() calls, I
reported it. Y
On 2013-08-13, Joshua Landau wrote:
> On 12 August 2013 16:47, Roy Smith wrote:
>> I can't quite sort out the multiple quoting levels, but somebody said:
>>
> Programming like that is called trolling. A programmer that uses
> trolling is called a troll. A troll can also refer to such a li
On 2013-08-13 11:31, Devyn Collier Johnson wrote:
I now see why this programming style is called trolling.
This programming style is not called "trolling". It does not have a name. It's
just your particular style. I think you misinterpreted someone who accused you
of deliberately coding in t
On 08/13/2013 04:50 AM, Steven D'Aprano wrote:
On Tue, 13 Aug 2013 09:19:07 +0100, Joshua Landau wrote:
On 12 August 2013 16:47, Roy Smith wrote:
I can't quite sort out the multiple quoting levels, but somebody said:
Programming like that is called trolling. A programmer that uses
trolling
On Tue, 13 Aug 2013 09:19:07 +0100, Joshua Landau wrote:
> On 12 August 2013 16:47, Roy Smith wrote:
>> I can't quite sort out the multiple quoting levels, but somebody said:
>>
> Programming like that is called trolling. A programmer that uses
> trolling is called a troll. A troll can al
On 12 August 2013 16:47, Roy Smith wrote:
> I can't quite sort out the multiple quoting levels, but somebody said:
>
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
On 8/12/13 4:16 PM, Devyn Collier Johnson wrote:
On 08/12/2013 12:56 PM, Joel Goldstick wrote:
On Mon, Aug 12, 2013 at 11:47 AM, Roy Smith wrote:
I can't quite sort out the multiple quoting levels, but somebody said:
Programming like that is called trolling. A programmer that uses
trolling
On Mon, Aug 12, 2013 at 4:16 PM, Devyn Collier Johnson
wrote:
>
> On 08/12/2013 12:56 PM, Joel Goldstick wrote:
>>
>> On Mon, Aug 12, 2013 at 11:47 AM, Roy Smith wrote:
>>>
>>> I can't quite sort out the multiple quoting levels, but somebody said:
>>>
>> Programming like that is called trolli
On 08/12/2013 12:56 PM, Joel Goldstick wrote:
On Mon, Aug 12, 2013 at 11:47 AM, Roy Smith wrote:
I can't quite sort out the multiple quoting levels, but somebody said:
Programming like that is called trolling. A programmer that uses
trolling is called a troll. A troll can also refer to such
On Mon, Aug 12, 2013 at 5:56 PM, Joel Goldstick
wrote:
> If you like semicolons, use another language that needs them.
> I think you think it is some version of premature optimization. Since
> you are a novice at the language, stick with the standards, and learn
> to embrace them.
I'm a C progra
On Mon, Aug 12, 2013 at 11:47 AM, Roy Smith wrote:
> I can't quite sort out the multiple quoting levels, but somebody said:
>
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
I can't quite sort out the multiple quoting levels, but somebody said:
>>> 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 re
On Mon, Aug 12, 2013 at 10:37 AM, Zachary Ware
wrote:
> [snip my last reply with a few code samples]
My apologies for Gmail's mangling of my samples. Any code that is not
indented should be on the previous line.
--
Zach
--
http://mail.python.org/mailman/listinfo/python-list
On Mon, Aug 12, 2013 at 9:04 AM, Devyn Collier Johnson
wrote:
>
> Zachary, are you, Ned, and Terry trying to say the syntax should be
>
> job = multiprocessing.Process(func1(), func2())
>
> not
>
> job = multiprocessing.Process(func1(); func2())
>
Basically, yes. The first option there is equiva
In Devyn Collier Johnson
writes:
> I am checking my 1292-line script for syntax errors. I ran the following
> commands in a terminal to check for errors, but I do not see the error.
>File "./beta_engine", line 344
> JOB_WRITEURGFILES =
> multiprocessing.Process(write2file('./mem/ENG
On 08/12/2013 09:20 AM, Zachary Ware wrote:
On Mon, Aug 12, 2013 at 7:33 AM, Devyn Collier Johnson
wrote:
On 08/10/2013 10:47 PM, Chris Angelico wrote:
On Sun, Aug 11, 2013 at 3:43 AM, Roy Smith wrote:
In article ,
Chris Angelico wrote:
When you get a syntax error you can't understand
On 8/12/13 8:33 AM, Devyn Collier Johnson wrote:
On 08/10/2013 10:47 PM, Chris Angelico wrote:
On Sun, Aug 11, 2013 at 3:43 AM, Roy Smith wrote:
In article ,
Chris Angelico wrote:
When you get a syntax error you can't understand, look at the previous
line of code. Perhaps something ther
On Mon, Aug 12, 2013 at 7:33 AM, Devyn Collier Johnson
wrote:
>
> On 08/10/2013 10:47 PM, Chris Angelico wrote:
>>
>> On Sun, Aug 11, 2013 at 3:43 AM, Roy Smith wrote:
>>>
>>> In article ,
>>> Chris Angelico wrote:
>>>
When you get a syntax error you can't understand, look at the previous
On 08/10/2013 10:47 PM, Chris Angelico wrote:
On Sun, Aug 11, 2013 at 3:43 AM, Roy Smith wrote:
In article ,
Chris Angelico 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 parenthe
In article <52074b43$0$3$c3e8da3$54964...@news.astraweb.com>,
Steven D'Aprano wrote:
> On Sun, 11 Aug 2013 03:33:52 +0100, Chris Angelico wrote:
>
> > Next thing to do is split it into more lines. Why is all that in a
> > single line?
>
> The only good excuse for writing multiple statement
On 11 August 2013 09:28, Steven D'Aprano
wrote:
> into more lines. Why is all that in a
>> single line?
>
> The only good excuse for writing multiple statements on a single line
> separated by semi-colons is if the Enter key on your keyboard is broken.
That's not a good excuse.
It *is* a good ex
On Sun, 11 Aug 2013 03:33:52 +0100, Chris Angelico wrote:
> Next thing to do is split it into more lines. Why is all that in a
> single line?
The only good excuse for writing multiple statements on a single line
separated by semi-colons is if the Enter key on your keyboard is broken.
:-)
--
On 8/10/2013 10:19 PM, Devyn Collier Johnson wrote:
I am checking my 1292-line script for syntax errors. I ran the following
commands in a terminal to check for errors, but I do not see the error.
collier@Nacho-Laptop:/media/collier/AI/Pysh$ python3 -m py_compile
./beta_engine
File "./beta_en
On Sun, Aug 11, 2013 at 3:43 AM, Roy Smith wrote:
> In article ,
> Chris Angelico 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
In article ,
Chris Angelico 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 spl
On Sun, Aug 11, 2013 at 3:19 AM, Devyn Collier Johnson
wrote:
> am checking my 1292-line script for syntax errors. I ran the following
> commands in a terminal to check for errors, but I do not see the error.
>
> collier@Nacho-Laptop:/media/collier/AI/Pysh$ python3 -m py_compile
> ./beta_engine
>
I am checking my 1292-line script for syntax errors. I ran the following
commands in a terminal to check for errors, but I do not see the error.
collier@Nacho-Laptop:/media/collier/AI/Pysh$ python3 -m py_compile
./beta_engine
File "./beta_engine", line 344
JOB_WRITEURGFILES =
multiproce
37 matches
Mail list logo
