I'm searching for Python style guidelines

[MartinRinehart]

There's a lot of dumb stuff out there. "Algorithms should be coded
efficiently ..." Thanks, I'll keep that in mind.

van Rossum's guidelines tend toward "pick something and stick to it"
which is OK if you have enough experience to pick something Pythonic.
I'm a relative newbie, not qualified to pick.

Anything written somewhere that's thorough? Any code body that should
serve as a reference?

[Peter Otten]

MartinRinehart wrote:

Anything written somewhere that's thorough? Any code body that should
serve as a reference?

http://www.python.org/dev/peps/pep-0008/

[Guilherme Polo]

2008/1/7, Ma************@ gmail.com <Ma************ @gmail.com>:

There's a lot of dumb stuff out there. "Algorithms should be coded
efficiently ..." Thanks, I'll keep that in mind.

van Rossum's guidelines tend toward "pick something and stick to it"
which is OK if you have enough experience to pick something Pythonic.
I'm a relative newbie, not qualified to pick.

Anything written somewhere that's thorough? Any code body that should
serve as a reference?

PEP 8
http://www.python.org/dev/peps/pep-0008/

--
http://mail.python.org/mailman/listinfo/python-list

--
-- Guilherme H. Polo Goncalves

[MartinRinehart]

Thank you both.

Stupid me, went to Python.org and found Style Guidelines and thought
that was the last word. Oh well.

PEP 8 reminds me a lot of Sun's Java conventions, in ways I wish it
didn't. The overall structure seems like a random list of topics and
it omits a lot. For Java I went from Sun to other conventions to try
to compile a meta-convention ( http://www.MartinRinehart.com/articl...nventions.html
).

Here's just one of my questions:

foo = [
'some item, quite long',
'more items, all demanding there own line as they are not short',
...

Where would you put the closing ']'?

[Fredrik Lundh]

Ma************@ gmail.com wrote:

Here's just one of my questions:

foo = [
'some item, quite long',
'more items, all demanding there own line as they are not short',
...

Where would you put the closing ']'?

on a line by itself, indented as your favourite Python editor indents it.

</F>

[Guilherme Polo]

2008/1/7, Ma************@ gmail.com <Ma************ @gmail.com>:

Thank you both.

Stupid me, went to Python.org and found Style Guidelines and thought
that was the last word. Oh well.

PEP 8 reminds me a lot of Sun's Java conventions, in ways I wish it
didn't. The overall structure seems like a random list of topics and
it omits a lot. For Java I went from Sun to other conventions to try
to compile a meta-convention ( http://www.MartinRinehart.com/articl...nventions.html
).

Here's just one of my questions:

foo = [
'some item, quite long',
'more items, all demanding there own line as they are not short',
...

Where would you put the closing ']'?

I would put ']' at a new line:

foo = [
'too long',
'too long too',
...
]

I don't really believe it should exist style guidelines for everything
that is possible (or if it did I doubt it would matter), many/most
people adapt the guidelines to fetch their own style. That is not
really a problem if you are consistent during all the code, and if it
is not too ugly as well =)

--
http://mail.python.org/mailman/listinfo/python-list

--
-- Guilherme H. Polo Goncalves

[MartinRinehart]

Guilherme Polo wrote:

foo = [
'too long',
'too long too',
...
]

OK, I'll put it there too, and it will be easy for us to read each
other's code (at least in this particular).

[Ben Finney]

ajaksu <aj****@gmail.c omwrites:

I've done this search before and it was very interesting, doing it
again gave me new results that also seem valuable. Here's most of
them (where PCG = Python Coding Guidelines).

Thanks, this is an awesome list. It's good to have a variety of real
examples when drafting a coding standard for a project.

Do you think this could be a valuable addition to the Python wiki?

Definitely!

--
\ "The most merciful thing in the world... is the inability of |
`\ the human mind to correlate all its contents." -- Howard |
_o__) Philips Lovecraft |
Ben Finney

[Martin Vilcans]

On 1/7/08, Guilherme Polo <gg****@gmail.c omwrote:

2008/1/7, Ma************@ gmail.com <Ma************ @gmail.com>:

Anything written somewhere that's thorough? Any code body that should
serve as a reference?

PEP 8
http://www.python.org/dev/peps/pep-0008/

The problem with PEP 8 is that even code in the standard libraries
doesn't follow the recommendations regarding the naming of functions
for example. The recommendation is to_separate_wor ds_with_undersc ore,
but some code uses lowerCamelCase instead.

I tended to dislike the underscore convention, but after forcing
myself to use it for a while I'm starting to appreciate its beauty.

--
ma****@librador .com
http://www.librador.com

[Colin J. Williams]

Martin Vilcans wrote:

On 1/7/08, Guilherme Polo <gg****@gmail.c omwrote:

>2008/1/7, Ma************@ gmail.com <Ma************ @gmail.com>:

>>Anything written somewhere that's thorough? Any code body that should
serve as a reference?

PEP 8
http://www.python.org/dev/peps/pep-0008/

The problem with PEP 8 is that even code in the standard libraries
doesn't follow the recommendations regarding the naming of functions
for example. The recommendation is to_separate_wor ds_with_undersc ore,
but some code uses lowerCamelCase instead.

I tended to dislike the underscore convention, but after forcing
myself to use it for a while I'm starting to appreciate its beauty.

I've come to like lowerCamelCase and a
tab of 2.

A tab of 4 wastes more space than is
needed for the occasional heavy
indenting.

Colin W.