Magnus Lycka enlightened us with:
> Think particularly about using version management systems and
> applying patches coming from different sources etc.
I was :)
> Finally, if you end up with something like...
>
> a= 1
> b
Magnus Lycka wrote:
> Touching more lines of code than you actually need will
> both make it difficult for a reviewer to understand what
> has changed (although good diff tools can be told to
> ignore pure whitespace changes) ...
Such features have a nasty interaction with languages that use
s
Sybren Stuvel wrote:
> Scott David Daniels enlightened us with:
>
>>One reason is such code changes too much on code edits, which makes
>>code differences hard to read.
>
> Good point. I'll keep it in mind :)
Think particularly about using version management systems
and applying patches coming f
rtilley enlightened us with:
> I took it literally when I first read it b/c it made sense to me and
> I did not notice the date. I don't think it will ever be _required_
> of all Python hackers, but I may be wrong.
Well, part of it is a serious PEP. It being _required_ was the joke.
Sybren
--
Th
Scott David Daniels enlightened us with:
> One reason is such code changes too much on code edits, which makes
> code differences hard to read.
Good point. I'll keep it in mind :)
Sybren
--
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, bu
Sybren Stuvel wrote:
> I just read the PEP where my way of alignment is under a 'NO' header.
> Too bad, since I think it can make things a lot clearer.
One reason is such code changes too much on code edits:
foo= 'bar'
foobar = 42
azimov = 3
to:
foo = 'bar'
somet
John Salerno wrote:
> All of it was a joke?
You'd have to ask Guido that :)
I took it literally when I first read it b/c it made sense to me and I
did not notice the date. I don't think it will ever be _required_ of all
Python hackers, but I may be wrong.
--
http://mail.python.org/mailman/list
rtilley wrote:
> Fredrik Lundh wrote:
>> in his april 1st, 2005 paper ?
>>
>> http://www.artima.com/weblogs/viewpost.jsp?thread=101968
>
> That was an April's Fools joke, right? I like it though :)
> Maybe it'll happen!
All of it was a joke?
--
http://mail.python.org/mailman/listinfo/python-list
rtilley wrote:
> John Salerno wrote:
>> A minor concern, but I'm curious if there is any kind of best practice
>> for using whitespace within expressions and argument lists in the
>> Python world. For example:
>>
>> 1 + 2 or 1+2
>
> IMO, good style calls for spaces. Most companies have style
Fredrik Lundh wrote:
> John Salerno wrote:
>
>> Guido listed a few rules that he'd like to see implemented in 2.5, and
>> one of them was no more than one consecutive white space. I don't know
>> how realistic some of those suggestions are, but they seem to be getting
>> a little to restrictive.
>
Fredrik Lundh wrote:
> in his april 1st, 2005 paper ?
>
> http://www.artima.com/weblogs/viewpost.jsp?thread=101968
That was an April's Fools joke, right? I like it though :)
Maybe it'll happen!
--
http://mail.python.org/mailman/listinfo/python-list
John Salerno enlightened us with:
> Guido listed a few rules that he'd like to see implemented in 2.5,
> and one of them was no more than one consecutive white space. I
> don't know how realistic some of those suggestions are, but they
> seem to be getting a little to restrictive.
I just read the
John Salerno wrote:
> Guido listed a few rules that he'd like to see implemented in 2.5, and
> one of them was no more than one consecutive white space. I don't know
> how realistic some of those suggestions are, but they seem to be getting
> a little to restrictive.
in his april 1st, 2005 paper
Sybren Stuvel wrote:
> John Salerno enlightened us with:
>> To me, the space makes it nicer and more readable, but I was
>> surprised to read in Guido's blog that he thinks 1+2 should be the
>> normal way to write it. What does everyone else think?
>
> I usually write 1 + 2 and func(a, b). Sometim
John Salerno enlightened us with:
> To me, the space makes it nicer and more readable, but I was
> surprised to read in Guido's blog that he thinks 1+2 should be the
> normal way to write it. What does everyone else think?
I usually write 1 + 2 and func(a, b). Sometimes I even use more spaces
to a
John Salerno wrote:
> A minor concern, but I'm curious if there is any kind of best practice
> for using whitespace within expressions and argument lists in the Python
> world. For example:
>
> 1 + 2 or 1+2
IMO, good style calls for spaces. Most companies have style guides for
programmers t
John Salerno <[EMAIL PROTECTED]> writes:
> 1 + 2 or 1+2
>
> func(1,2) or func(1, 2)
I prefer and use 1 + 2 and func(1, 2)
I don't do whitespaces only in argument defaults like
func(foo=baz)
--
Lawrence - http://www.oluyede.org/blog
"Anyone can freely use whatever he wants but the light at
A minor concern, but I'm curious if there is any kind of best practice
for using whitespace within expressions and argument lists in the Python
world. For example:
1 + 2 or 1+2
func(1,2) or func(1, 2)
To me, the space makes it nicer and more readable, but I was surprised
to read in Guido's
18 matches
Mail list logo
