Re: PEP8 compliance

2018-06-14 Thread Gregory Ewing
Chris Angelico wrote: ... and THIS RIGHT HERE is why the tool should not be called "pep8". Didn't this exact discussion come up and the tool got renamed? Seems it's been renamed to pycodestyle, but there's still an old project called pep8 on pypi.org. I guess there's always going to be some con

Re: PEP8 compliance

2018-06-13 Thread T Berger
On Wednesday, June 13, 2018 at 1:44:49 PM UTC-4, Paul Moore wrote: > On 13 June 2018 at 17:35, T Berger wrote: > > > I did make the changes in IDLE, but I thought I must be in the wrong place. > > The line of code I got in terminal was: > > /Users/TamaraB/Desktop/mymodules/vsearch.py:1:25: E231

Re: PEP8 compliance

2018-06-13 Thread Chris Angelico
On Thu, Jun 14, 2018 at 1:45 AM, Steven D'Aprano wrote: > On Wed, 13 Jun 2018 08:04:27 -0700, T Berger wrote: > >> Sorry for this basic question, but to change my code if it's failed the >> PEP8 test, what code do I use to open my program and make changes? > > Use your text editor to modify the so

Re: PEP8 compliance

2018-06-13 Thread Paul Moore
On 13 June 2018 at 17:35, T Berger wrote: > I did make the changes in IDLE, but I thought I must be in the wrong place. > The line of code I got in terminal was: > /Users/TamaraB/Desktop/mymodules/vsearch.py:1:25: E231 missing whitespace > after ':' > def search4vowels(phrase:str)->set: > > I t

Re: PEP8 compliance

2018-06-13 Thread Terry Reedy
On 6/13/2018 12:35 PM, T Berger wrote: I did make the changes in IDLE, but I thought I must be in the wrong place. This is a good place for beginners. The line of code I got in terminal was: /Users/TamaraB/Desktop/mymodules/vsearch.py:1:25: E231 missing whitespace after ':' def search4vowel

Re: PEP8 compliance

2018-06-13 Thread Rick Johnson
On Wednesday, June 13, 2018 at 10:47:40 AM UTC-5, Steven D'Aprano wrote: > I'm of two minds here... Obviously. > [...] So use your own judgement: if following PEP 8 becomes > a chore, or if you would rather follow your own style, > don't feel guilty about ignoring the style guide. IOWs: "

Re: PEP8 compliance

2018-06-13 Thread T Berger
On Wednesday, June 13, 2018 at 11:04:39 AM UTC-4, T Berger wrote: > Sorry for this basic question, but to change my code if it's failed the PEP8 > test, what code do I use to open my program and make changes? Obviously, I > should still be in bash, but then what? > > Thanks, > > Tamara I did m

Re: PEP8 compliance

2018-06-13 Thread Marko Rauhamaa
r...@zedat.fu-berlin.de (Stefan Ram): > T Berger writes: >>to change my code if it's failed the PEP8 test, >>what code do I use to open my program and make changes? > > A text editor (emacs, vim, pico, IDLE, notepad, ex, sed, ...). > What did you use to write your code in the first place? Th

Re: PEP8 compliance

2018-06-13 Thread Steven D'Aprano
On Wed, 13 Jun 2018 08:04:27 -0700, T Berger wrote: > Sorry for this basic question, but to change my code if it's failed the > PEP8 test, what code do I use to open my program and make changes? Use your text editor to modify the source code of the program. I'm of two minds here... on the one h

Re: PEP8 compliance

2018-06-13 Thread MRAB
On 2018-06-13 16:04, T Berger wrote: Sorry for this basic question, but to change my code if it's failed the PEP8 test, what code do I use to open my program and make changes? Obviously, I should still be in bash, but then what? You edit it in a plain text editor (i.e. an editor for plain tex

PEP8 compliance

2018-06-13 Thread T Berger
Sorry for this basic question, but to change my code if it's failed the PEP8 test, what code do I use to open my program and make changes? Obviously, I should still be in bash, but then what? Thanks, Tamara -- https://mail.python.org/mailman/listinfo/python-list

RE: PEP8 compliance and exception messages ?

2010-12-08 Thread Gerald Britton
I'm a bit late to the discussion, but remembering that raise takes an expression, I can break it up like this: >>> raise ( ... Exception ( ... "Long " ... "exception " ... "text." ... ) ... ) Traceback (most recent call last): File "", line 3, in Exception: Long exception text Then, you can in

Re: PEP8 compliance and exception messages ?

2010-12-07 Thread shearichard
On Dec 7, 9:17 am, Andreas Waldenburger wrote: > On Mon, 6 Dec 2010 00:22:49 -0500 Andreas Waldenburger > wrote: > > > > > On Sun, 5 Dec 2010 19:52:54 -0800 Chris Rebert > > wrote: > > > > On Sun, Dec 5, 2010 at 7:40 PM, shearichard > > > wrote: > > > > Hi - PEP8 says lines should not exceed 7

Re: PEP8 compliance and exception messages ?

2010-12-07 Thread shearichard
On Dec 6, 6:21 pm, Ben Finney wrote: > shearichard writes: > > Hi - PEP8 says lines should not exceed 79 characters in length > > (http://www.python.org/dev/peps/pep-0008/). > > > So if you've got some code that looks like this : > > > raise fooMod.fooException("Some message which is quite long")

Re: PEP8 compliance and exception messages ?

2010-12-06 Thread Andreas Waldenburger
On Mon, 6 Dec 2010 00:22:49 -0500 Andreas Waldenburger wrote: > On Sun, 5 Dec 2010 19:52:54 -0800 Chris Rebert > wrote: > > > On Sun, Dec 5, 2010 at 7:40 PM, shearichard > > wrote: > > > Hi - PEP8 says lines should not exceed 79 characters in length > > > ( http://www.python.org/dev/peps/pep-

Re: PEP8 compliance and exception messages ?

2010-12-05 Thread Steven D'Aprano
On Mon, 06 Dec 2010 06:15:06 +, Tim Harig wrote: >> But isn't explicit string literal concatenation better than implicit >> string literal concatenation? > > So add the "+", it really doesn't change it much. Perhaps not *much*, but it *may* change it a bit. Implicit concatenation of literal

Re: PEP8 compliance and exception messages ?

2010-12-05 Thread Tim Harig
On 2010-12-06, Andreas Waldenburger wrote: > On Sun, 5 Dec 2010 19:52:54 -0800 Chris Rebert wrote: > >> On Sun, Dec 5, 2010 at 7:40 PM, shearichard >> wrote: >> > Hi - PEP8 says lines should not exceed 79 characters in length >> > ( http://www.python.org/dev/peps/pep-0008/ ). >> > >> > So if you

Re: PEP8 compliance and exception messages ?

2010-12-05 Thread Andreas Waldenburger
On Sun, 5 Dec 2010 19:52:54 -0800 Chris Rebert wrote: > On Sun, Dec 5, 2010 at 7:40 PM, shearichard > wrote: > > Hi - PEP8 says lines should not exceed 79 characters in length > > ( http://www.python.org/dev/peps/pep-0008/ ). > > > > So if you've got some code that looks like this : > > > > rais

Re: PEP8 compliance and exception messages ?

2010-12-05 Thread Ben Finney
shearichard writes: > Hi - PEP8 says lines should not exceed 79 characters in length > ( http://www.python.org/dev/peps/pep-0008/ ). > > So if you've got some code that looks like this : > > raise fooMod.fooException("Some message which is quite long") PEP 8 also says those names are poorly chos

Re: PEP8 compliance and exception messages ?

2010-12-05 Thread MRAB
On 06/12/2010 03:40, shearichard wrote: Hi - PEP8 says lines should not exceed 79 characters in length ( http://www.python.org/dev/peps/pep-0008/ ). So if you've got some code that looks like this : raise fooMod.fooException("Some message which is quite long") ... and assuming a certain amount

Re: PEP8 compliance and exception messages ?

2010-12-05 Thread Chris Rebert
On Sun, Dec 5, 2010 at 7:40 PM, shearichard wrote: > Hi - PEP8 says lines should not exceed 79 characters in length > ( http://www.python.org/dev/peps/pep-0008/ ). > > So if you've got some code that looks like this : > > raise fooMod.fooException("Some message which is quite long") > > ... and as

PEP8 compliance and exception messages ?

2010-12-05 Thread shearichard
Hi - PEP8 says lines should not exceed 79 characters in length ( http://www.python.org/dev/peps/pep-0008/ ). So if you've got some code that looks like this : raise fooMod.fooException("Some message which is quite long") ... and assuming a certain amount of indenting you're going to break that g