Re: PyWart: PEP8: A cauldron of inconsistencies.

2011-07-30 Thread Chris Angelico
On Sat, Jul 30, 2011 at 5:52 PM, bruno.desthuilli...@gmail.com wrote: > On 28 juil, 00:34, rantingrick wrote: > >> In Python4000 i'm making it a syntax error to >> include ANY blank lines in a func/meth body. > > Hopefully this is not going to happen. It will happen when Rick stops ranting and s

Re: PyWart: PEP8: A cauldron of inconsistencies.

2011-07-30 Thread bruno.desthuilli...@gmail.com
On 28 juil, 00:34, rantingrick wrote: > In Python4000 i'm making it a syntax error to > include ANY blank lines in a func/meth body. Hopefully this is not going to happen. (snip remaining stupidities). -- http://mail.python.org/mailman/listinfo/python-list

Re: PyWart: PEP8: A cauldron of inconsistencies.

2011-07-28 Thread Chris Angelico
On Thu, Jul 28, 2011 at 8:34 AM, rantingrick wrote: >> -- >> Encodings (PEP 263) >> >> Code in the core Python distribution should always use the >> ASCII or Latin-1 encoding (a.k.a. ISO-8859-1).  For Python >> 3.0 and beyond, UTF-8 is prefer

Re: PyWart: PEP8: A cauldron of inconsistencies.

2011-07-27 Thread harrismh777
Steven D'Aprano wrote: On Thu, 28 Jul 2011 08:34 am rantingrick wrote: > WRONG! When in doubt be consistent! There should be one AND ONLY ONE > obvious way to do it! When we have multiple ways of doing the same > thing we induce an overhead into our work flows. Instead we need to > follow t

Re: PyWart: PEP8: A cauldron of inconsistencies.

2011-07-27 Thread Steven D'Aprano
On Thu, 28 Jul 2011 08:34 am rantingrick wrote: > WRONG! When in doubt be consistent! There should be one AND ONLY ONE > obvious way to do it! When we have multiple ways of doing the same > thing we induce an overhead into our work flows. Instead we need to > follow the zen; in other words, BE CON

Re: PyWart: PEP8: A cauldron of inconsistencies.

2011-07-27 Thread Andrew Berg
On 2011.07.27 08:34 PM, Cameron Simpson wrote: > I think when he releases Python4000 we'll all fall behind. That is, if he ever does release RickPy4000. ;) -- CPython 3.2.1 | Windows NT 6.1.7601.17592 | Thunderbird 5.0 PGP/GPG Public Key ID: 0xF88E034060A78FCB -- http://mail.python.org/mailman/l

Re: PyWart: PEP8: A cauldron of inconsistencies.

2011-07-27 Thread Cameron Simpson
On 28Jul2011 02:06, Thomas Jollans wrote: | On 28/07/11 00:34, rantingrick wrote: | > [ snip rant ] | | To be clear, the code is more what you'd call "guidelines" than actual | rules. Welcome aboard the Black Pearl, Mister Ranting! I think when he releases Python4000 we'll all fall behind. -- C

Re: PyWart: PEP8: A cauldron of inconsistencies.

2011-07-27 Thread Thomas Jollans
On 28/07/11 00:34, rantingrick wrote: > I believe the current Python style guide is inconsistent. The author > again allowed hie emotion to get in the way of logic. If you think that logic can be the foundation of a style [guide], then you have a very curious idea of what "logic" means. > [ snip

Re: PyWart: PEP8: A cauldron of inconsistencies.

2011-07-27 Thread Andrew Berg
On 2011.07.27 05:34 PM, rantingrick wrote: >> -- >> Use 4 spaces per indentation level. >> -- > > This should be the only acceptable indention level allowed by the > interpreter. All oth

PyWart: PEP8: A cauldron of inconsistencies.

2011-07-27 Thread rantingrick
I believe the current Python style guide is inconsistent. The author again allowed hie emotion to get in the way of logic. I will be posting blocks of text from the PEP8 and commenting below them. > -- > One of Guido's key insights is that c