Re: [Python-ideas] PEP 8 update on line length

On Wed, Feb 27, 2019 at 5:53 AM Rhodri James wrote: > > To be a bit less harsh -- that is, change the clause: > > > > "For code maintained exclusively or primarily by a team that can reach > > agreement on this issue, it is okay ..." > > > > To maybe just > > > > "For code maintained by a team

Re: [Python-ideas] PEP 8 update on line length

On 26/02/2019 02:01, Christopher Barker wrote: We could reword: """ Some teams strongly prefer a longer line length. For code maintained exclusively or primarily by a team that can reach agreement on this issue, it is okay to increase the nominal line length from 80 to 100 characters

Re: [Python-ideas] PEP 8 update on line length

i thought it interesting as it presented a non py's view of things (web dev) for the 80 chars length. Abdur-Rahmaan Janhangeer http://www.pythonmembers.club | https://github.com/Abdur-rahmaanJ Mauritius ___ Python-ideas mailing list

Re: [Python-ideas] PEP 8 update on line length

> saw that today > > 80 Characters per Line Is a Standard Worth Sticking to Even Today > https://dev.to/nickjj/80-characters-per-line-is-a-standard-worth-sticking-to-even-today-26kk > Same arguments made in this thread. I noticed that most of the comments were from folks disagreeing:-) Anyway,

Re: [Python-ideas] PEP 8 update on line length

saw that today 80 Characters per Line Is a Standard Worth Sticking to Even Today https://dev.to/nickjj/80-characters-per-line-is-a-standard-worth-sticking-to-even-today-26kk Abdur-Rahmaan Janhangeer http://www.pythonmembers.club | https://github.com/Abdur-rahmaanJ Mauritius On Tue, 19 Feb 2019,

Re: [Python-ideas] PEP 8 update on line length

Alex Walters writes: > There is no way to win in changing the guideline. IMO this is true, despite the comment below: > PEP-8 is not a universal truth, or even a standard, we really > shouldn't be treating it like it is. Unfortunately, it's not us (at least, I don't think it is), and it's

Re: [Python-ideas] PEP 8 update on line length

As a human, and one who reads and writes code even, I know that MY ability to understands the meaning of a line of code starts to plummet when it reaches about 65-70 characters in length. Yes, of course there are some "it depends" caveats that make some lines easier and some harder. But an 80

Re: [Python-ideas] PEP 8 update on line length

> On Feb 22, 2019, at 1:10 PM, Greg Ewing wrote: >> “Typesetters hundreds of years ago used less than 80 chars per line, so >> that’s what we should do for Python code now” is a pretty weak argument. > > But that's not the entire argument -- the point it is that typesetters > had the goal of

Re: [Python-ideas] PEP 8 update on line length

> Probably because IBM decided on 80 columns for their punched cards. > And that probably didn't have anything to do with a readable width > for text. Nobody used computers for word processing back then. > In fact punched cards predate computers altogether, originally > being developed for

Re: [Python-ideas] PEP 8 update on line length

Hi, Le 22/02/2019 à 22:10, Greg Ewing a écrit : I would say it the other way around. Once you've reduced the complexity of a line to something a human can handle, *most* of the time 80 chars is enough. I totally agree with Greg Ewing on that point. The only time when line length is a hinder

Re: [Python-ideas] PEP 8 update on line length

On Fri, Feb 22, 2019 at 5:10 PM Greg Ewing wrote: > I would say it the other way around. Once you've reduced the complexity > of a line to something a human can handle, *most* of the time 80 chars > is enough. > +1 It has been known for a very long time. These are *old *books that talk about

Re: [Python-ideas] PEP 8 update on line length

Christopher Barker wrote: (And did they ever stop to wonder why those old terminals standardized on 80 columns?) Probably because IBM decided on 80 columns for their punched cards. And that probably didn't have anything to do with a readable width for text. Nobody used computers for

Re: [Python-ideas] PEP 8 update on line length

Raymond Hettinger posted a helpful example to this list. Here, I run his example, and a variant, through https://black.now.sh Raymond class Frabawidget: @wozzle.setter def wibble(self, woozle): if not (self.min_woozle < woozle < self.max_woozle): raise

Re: [Python-ideas] PEP 8 update on line length

On 2/21/19 10:33 PM, Steven D'Aprano wrote: (And did they ever stop to wonder why those old terminals standardized on 80 columns?) Punch cards? https://softwareengineering.stackexchange.com/questions/148677 There's an ensuing discussion regarding the history of the size/shape of the punch

Re: [Python-ideas] PEP 8 update on line length

> > > Chris, the convention to limit text to somewhere around 60-80 characters > predates old terminals by *literally centuries*. Not for code, it doesn’t— and centuries ago, there were other technical issues on play for papermaking, hand writing, and typesetting. > (And did they ever stop to

Re: [Python-ideas] PEP 8 update on line length

A general rule of thumb is, if Python feels inconvenient or awkward, you’re doing something wrong. ___ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct:

Re: [Python-ideas] PEP 8 update on line length

> From: pylang > To: Mike Miller > Cc: "python-ideas@python.org" > Bcc: > Date: Thu, 21 Feb 2019 17:32:12 -0500 > Subject: Re: [Python-ideas] PEP 8 update on line length > Some feedback: > > I code on a 13.5 inch laptop. I split my screen between m

Re: [Python-ideas] PEP 8 update on line length

> On Feb 21, 2019, at 5:06 PM, Chris Barker via Python-ideas > wrote: > > > class Frabawidget: > ... > @wozzle.setter > def (self, woozle): > if not (self.min_woozle < woozle < self.max_woozle): > raise ValueError(f"Expected woozle to be between >

Re: [Python-ideas] PEP 8 update on line length

On Thu, Feb 21, 2019 at 05:06:51PM -0800, Chris Barker via Python-ideas wrote: > To all the folks quoting theory: let's be honest. Yes, really long lines > are harder to read, but the 80 char limit comes from old terminals, NOT any > analysis that somehow that is optimum for readability. Chris,

Re: [Python-ideas] PEP 8 update on line length

On 2/21/19 7:06 PM, Chris Barker via Python-ideas wrote: > On Thu, Feb 21, 2019 at 12:01 PM Raymond Hettinger > wrote: >> class Frabawidget: >> ... >> @wozzle.setter >> def (self, woozle): >> if not (self.min_woozle < woozle < self.max_woozle): >> raise

Re: [Python-ideas] PEP 8 update on line length

On Thu, Feb 21, 2019 at 12:01 PM Raymond Hettinger < raymond.hettin...@gmail.com> wrote: > I concur. We now put expressions in f-strings and have assignment > expressions that easily spill over 80 characters if one uses all but the > most compact variable names. Comprehensions tend to make

Re: [Python-ideas] PEP 8 update on line length

Some feedback: I code on a 13.5 inch laptop. I split my screen between my browser on the left half and editor on the right half of the screen. The 80 character suggestion has been helpful to me in reading code. Otherwise I'd use up time with random horizontal scrolling. On Thu, Feb 21, 2019 at

Re: [Python-ideas] PEP 8 update on line length

On 2/21/19 10:53 AM, Paul Ferrell wrote: I think the solution is for everyone to rotate their widescreen monitors 90° into a really tall portrait mode. :) Yep, that's what I do, but would prefer a squarer monitor so I could get two windows side by side on that one also. My old 1600x1200 4:3

Re: [Python-ideas] PEP 8 update on line length

I think the solution is for everyone to rotate their widescreen monitors 90° into a really tall portrait mode. :) On Thu, Feb 21, 2019, 11:44 AM Mike Miller wrote: > > On 2/18/19 8:37 PM, Simon wrote: > > I'd like to propose an update to PEP8. Indeed, the 80 characters per > line > > guideline

Re: [Python-ideas] PEP 8 update on line length

On 2/18/19 8:37 PM, Simon wrote: I'd like to propose an update to PEP8. Indeed, the 80 characters per line guideline is, I feel, outdated. Hi, I don't agree it is outdated. As someone who has a second 4k monitor in portrait mode to minimize scrolling (recommended), the ~80 char line limit

Re: [Python-ideas] PEP 8 update on line length

On Thu, 21 Feb 2019 at 12:20, Paul Ferrell wrote: > > My linter is fine with a double indent after an 'if (A and'. I thought it > was in the standard. If I used a linter, I'd expect it to be fine with whatever I told it to be fine with :-) It's a linter's job to flag up violations of the

Re: [Python-ideas] PEP 8 update on line length

Brendan Barnwell wrote: I use an editor that VISUALLY wraps long lines and maintains the indentation on the wrapped portion, without changing the bytes in the file. I make my lines as long as I want, inserting linebreaks only where they have a semantic reason to be (such as between multiple

Re: [Python-ideas] PEP 8 update on line length

Christopher Barker writes: > On Wed, Feb 20, 2019 at 11:51 PM Lele Gaifax wrote: > >> if ((condition1 >>and condition2 >>and condition3)): >> do_something() >> > > ouch! ehy not jsut do: > > if (condition1 > and condition2 > and condition3)): >

Re: [Python-ideas] PEP 8 update on line length

On Wed, Feb 20, 2019 at 11:51 PM Lele Gaifax wrote: > that most annoys me is the "if" when the condition is very long, because my > eyes suffer when I see the following: > yup -- "if (" is four spaces -- exactly one indentation level -- that is really painful. I've got to figure out how to

Re: [Python-ideas] PEP 8 update on line length

On Wed, Feb 20, 2019 at 10:57 PM Abe Dillon wrote: > I wish you would have watched the video I linked > > that is an hour and 7 minute video! And I did watch some of it, and do agree with much of it. By the way, everyone should watch one of

Re: [Python-ideas] PEP 8 update on line length

Abe Dillon writes: > A better way to list arguments is only one indentation level above the > current: > > variable = some_class.method( > argument=value, > argument2=value) > > Trying to match the indentation of the opening line is less readable and > less robust to refactoring: > >

Re: [Python-ideas] PEP 8 update on line length

On 2019-02-20 18:41, Christopher Barker wrote: God no! I HATE that style -- for me, it makes it MUCH harder to read -- even more so if the variable names are a bit longer. But if you are going to do it, for the love of god, use more than four spaces! four spaces is one indentation, one

Re: [Python-ideas] PEP 8 update on line length

[Christopher Barker] > God no! I HATE that style -- for me, it makes it MUCH harder to read -- > even more so if the variable names are a bit longer. > But if you are going to do it, for the love of god, use more than four > spaces! four spaces is one indentation, one indentation is how a code

Re: [Python-ideas] PEP 8 update on line length

Most of this thread is all just so much opinion, so I have avoided chiming in -- but as for opinion: A better way to list arguments is only one indentation level above the > current: > > variable = some_class.method( > argument=value, > argument2=value) > God no! I HATE that style --

Re: [Python-ideas] PEP 8 update on line length

[Chris Angelico] > Not about HOW it works. That's irrelevant. You DO need to know about > what it does, which is what I said. So it is. I'm sorry I misread your comment. [Chris Angelico] > In the case of random.choice, that's very clearly defined by its > documentation: it chooses a random >

Re: [Python-ideas] PEP 8 update on line length

On Thu, Feb 21, 2019 at 12:26 PM Abe Dillon wrote: > You don't need to know EVERYTHING about how block_fork works to debug that > failure. You > probably don't need to know EVERYTHING about how random.choice works either. > You don't > need to know about how most of the functions in the code

Re: [Python-ideas] PEP 8 update on line length

[Chris Angelico] > > And this is always cited as the "obvious" solution. Yes. I think simon even referred to this "obvious" solution in his post when he said, "...which is a very common ocurence, *and doesn't warrant refactoring*" So, my comment may have been unwarranted. [Chris Angelico] >

Re: [Python-ideas] PEP 8 update on line length

On Wed, Feb 20, 2019 at 07:53:21PM +, Jonathan Fine wrote: > Steven D'Aprano wrote: > > > > I wasn't making a point. I was providing evidence. > > > > Evidence of what? > > > > What was the point of this evidence? > > > > If it was to demonstrate that it is possible to reformat function > >

Re: [Python-ideas] PEP 8 update on line length

First of all, thank you so much for taking the time to do some actual analysis! I only have one thing to add: [Paul Ferrell] > 3 - function calls > Function calls, even with the arguments put one per line, often exceed 80 > (and sometimes 100) character limit. The issue tends to be a combination

Re: [Python-ideas] PEP 8 update on line length

On Thu, Feb 21, 2019 at 11:09 AM Abe Dillon wrote: > > [simon.bordeyne] >> >> I find that 100 to 120 characters is ideal as far as line length goes. > > Your finding goes against a long history of people attempting to present text > in the most readable way possible. > AFIK, the human fovea

Re: [Python-ideas] PEP 8 update on line length

d Mertz > Date : 19/02/2019 07:28 (GMT+01:00) > À : Anders Hovmöller > Cc : Simon , python-ideas < > python-ideas@python.org> > Objet : Re: [Python-ideas] PEP 8 update on line length > > 60, or 68, or 80 characters, is not per se a cognitive limit. Yes, sure > whitespace

Re: [Python-ideas] PEP 8 update on line length

Thankfully, style guidelines are based upon the limitations of humans like the size of the fovea and the general ability for people to follow long lines, NOT on the limitations of tools like grep. On Tue, Feb 19, 2019 at 10:29 AM Anders Hovmöller wrote: > > If it were me, I'd probably write (or

Re: [Python-ideas] PEP 8 update on line length

[Samuel Colvin] > > I don't see how anyone can say that would be more readable with a 80 > character line limit. For starters, type annotations don't add anything that good documentation would have required before. In most docstring style guides that I know of, the arguments list is supposed to

Re: [Python-ideas] PEP 8 update on line length

Opinion first - I don't see a need to change PEP 8. I recommend 100 char width for Python, which is acceptable under PEP 8 anyway. I think the real limit should be around 70 characters per line, not including leading white-space, but I realize that's impractical. I work mostly at 100 character

Re: [Python-ideas] PEP 8 update on line length

On Thu, Feb 21, 2019 at 6:48 AM Jonathan Fine wrote: > Here's a suggestion, at least for people projects that use black.py > (such as Samuel's). It is to use black.py with a line-length of say 80 > characters for code that is saved in version control. And when editing > code, use whatever

Re: [Python-ideas] PEP 8 update on line length

Steven D'Aprano wrote: > > I wasn't making a point. I was providing evidence. > > Evidence of what? > > What was the point of this evidence? > > If it was to demonstrate that it is possible to reformat function > parameter lists to split over multiple lines, we already knew that. > > If it was to

Re: [Python-ideas] PEP 8 update on line length

I wrote: def resolve_annotations(raw_annotations: Dict[str, AnyType], module_name: Optional[str]) -> Dict[str, AnyType]: pass After using https://black.now.sh/ def resolve_annotations( raw_annotations:

Re: [Python-ideas] PEP 8 update on line length

On Wed, Feb 20, 2019 at 11:19 AM Steven D'Aprano wrote: > > On Wed, Feb 20, 2019 at 01:41:27AM +1100, Chris Angelico wrote: > > > page_count will usually be unambiguous. You might need total_pages to > > mean "not the current section", thus leaving the shorter one available > > for the narrower

Re: [Python-ideas] PEP 8 update on line length

On Wed, Feb 20, 2019 at 01:41:27AM +1100, Chris Angelico wrote: > page_count will usually be unambiguous. You might need total_pages to > mean "not the current section", thus leaving the shorter one available > for the narrower use. Obviously questions like this can't be answered > without

Re: [Python-ideas] PEP 8 update on line length

On Tue, Feb 19, 2019 at 11:38:04AM +0100, Nicolas Rolin wrote: > I understand that the writer wants to have shorter names, but why would I > want more ambigious names as a reader ? > How would you rename number_of_pages_in_current_section such that the > reader is not left wondering what does

Re: [Python-ideas] PEP 8 update on line length

On Tue, Feb 19, 2019 at 05:29:33PM +, Jonathan Fine wrote: > Previously, Samuel wrote that he would leave the conversation, because > it was primarily opinion based, which he finds annoying. > > I then provided evidence (namely how black.py reformats a specific > code example). > > Samuel

Re: [Python-ideas] PEP 8 update on line length

On Tue, Feb 19, 2019 at 02:13:24PM +, Paul Moore wrote: > Any linter or project that treats PEP 8 as mandatory has *already* > failed, as PEP 8 itself states that the rules can be broken as needed. > Of course individual projects are entirely allowed to impose whatever > draconian and

Re: [Python-ideas] PEP 8 update on line length

Samuel Colvin wrote: I just think that code with a 7 line function header is much harder to read and understand than code with a one line function header. But to me, a one-line function header that contains 7 lines worth of charaacters is *less* readable than a 7-line header, as long as it's

Re: [Python-ideas] PEP 8 update on line length

Samuel Colvin wrote: def resolve_annotations(*, raw_annotations: Dict[str, Type[Any]], module_name: Optional[str]) -> Dict[str, Type[Any]]: I don't see how anyone can say that would be more readable with a 80 character line limit. I would argue that it *is* more readable if it's not all on

Re: [Python-ideas] PEP 8 update on line length

>> Maybe you know some grep magic I don't? Is there a way to do multi line grep >> that knows that open paren means to ignore new lines until the matching >> close paren? I'd love to hear about it! > > I probably don't know any more grep magic than you, I've just never had cause > to grep

Re: [Python-ideas] PEP 8 update on line length

Previously, Samuel wrote that he would leave the conversation, because it was primarily opinion based, which he finds annoying. I then provided evidence (namely how black.py reformats a specific code example). Samuel then wrote: > I'm afraid I'm not sure of your point here. I wasn't making a

Re: [Python-ideas] PEP 8 update on line length

On 2/19/19 11:06 AM, Anders Hovmöller wrote: > Maybe you know some grep magic I don't? Is there a way to> do multi > line grep that knows that open paren means to ignore new lines until > the matching close paren? I'd love to hear about it! At the risk of jumping in over my head with respect to

Re: [Python-ideas] PEP 8 update on line length

On 19.02.2019 18:06, Anders Hovmöller wrote: > > >> On 19 Feb 2019, at 17:36, Rhodri James wrote: >> >> On 19/02/2019 16:26, Anders Hovmöller wrote: If it were me, I'd probably write (or would have re-written when I added the type hints) that as follows: def

Re: [Python-ideas] PEP 8 update on line length

On 19/02/2019 17:06, Anders Hovmöller wrote: On 19 Feb 2019, at 17:36, Rhodri James wrote: On 19/02/2019 16:26, Anders Hovmöller wrote: If it were me, I'd probably write (or would have re-written when I added the type hints) that as follows: def resolve_annotations( *,

Re: [Python-ideas] PEP 8 update on line length

> On 19 Feb 2019, at 17:36, Rhodri James wrote: > > On 19/02/2019 16:26, Anders Hovmöller wrote: >>> If it were me, I'd probably write (or would have re-written when I added >>> the type hints) that as follows: >>> >>>def resolve_annotations( >>>*, >>>

Re: [Python-ideas] PEP 8 update on line length

On 19/02/2019 16:26, Anders Hovmöller wrote: If it were me, I'd probably write (or would have re-written when I added the type hints) that as follows: def resolve_annotations( *, raw_annotations: Dict[str, Type[Any]], module_name: Optional[str]

Re: [Python-ideas] PEP 8 update on line length

> If it were me, I'd probably write (or would have re-written when I added > the type hints) that as follows: > >def resolve_annotations( >*, >raw_annotations: Dict[str, Type[Any]], >module_name: Optional[str] >) -> Dict[str, Type[Any]]: I would

Re: [Python-ideas] PEP 8 update on line length

I'm afraid I'm not sure of your point here. (By the way, that code is already run through black, just with a line length limit of 120) ___ Python-ideas mailing list

Re: [Python-ideas] PEP 8 update on line length

def resolve_annotations(raw_annotations: Dict[str, AnyType], module_name: Optional[str]) -> Dict[str, AnyType]: pass After using https://black.now.sh/ def resolve_annotations( raw_annotations: Dict[str,

Re: [Python-ideas] PEP 8 update on line length

> Nothing says that you have to write an entire function header on one line. Of course. I just think that code with a 7 line function header is much harder to read and understand than code with a one line function header. For example: it's less likely that two chunks of code I'm looking at are

Re: [Python-ideas] PEP 8 update on line length

On 2/19/19 8:28 AM, Samuel Colvin wrote: > Let's take a real life example from here > > (changed very slightly for this example), in tranitional python the > signature might be: > > def

Re: [Python-ideas] PEP 8 update on line length

On Tue, Feb 19, 2019 at 9:38 PM Nicolas Rolin wrote: > I understand that the writer wants to have shorter names, but why would I > want more ambigious names as a reader ? > How would you rename number_of_pages_in_current_section such that the reader > is not left wondering what does this

Re: [Python-ideas] PEP 8 update on line length

tphone Samsung Galaxy. >> >> ---- Message d'origine >> De : David Mertz >> Date : 19/02/2019 07:28 (GMT+01:00) >> À : Anders Hovmöller >> Cc : Simon , python-ideas < >> python-ideas@python.org> >> Objet : Re: [Python-ideas]

Re: [Python-ideas] PEP 8 update on line length

Date : 19/02/2019 07:28 (GMT+01:00) > À : Anders Hovmöller > Cc : Simon , python-ideas < > python-ideas@python.org> > Objet : Re: [Python-ideas] PEP 8 update on line length > > 60, or 68, or 80 characters, is not per se a cognitive limit. Yes, sure > whitespace counts much

Re: [Python-ideas] PEP 8 update on line length

I too would argue that it's time to reconsider line length limits. But the reason is not monitor changes, or any particularly strong personal opinion, but changes to python: Let's take a real life example from here

Re: [Python-ideas] PEP 8 update on line length

On Tue, Feb 19, 2019 at 3:07 PM simon.bordeyne wrote: > A good middle ground would be to enforce customization of that rule in the > most used python linters. A simple setting to set the number of characters > before a linting warning occurs would be acceptable. > Major linters already support

Re: [Python-ideas] PEP 8 update on line length

On Tue, 19 Feb 2019 at 14:08, simon.bordeyne wrote: > A good middle ground would be to enforce customization of that rule in the > most used python linters. A simple setting to set the number of characters > before a linting warning occurs would be acceptable. Any linter or project that

Re: [Python-ideas] PEP 8 update on line length

avid Mertz Date : 19/02/2019 07:28 (GMT+01:00) À : Anders Hovmöller Cc : Simon , python-ideas Objet : Re: [Python-ideas] PEP 8 update on line length 60, or 68, or 80 characters, is not per se a cognitive limit. Yes, sure whitespace counts much less towards that burden than do regular

Re: [Python-ideas] PEP 8 update on line length

My two cents, because this is a subject about which I have a strong opinion: - Yes, VT100s and other green screen terminals have long since been out of fashion, but there are still some people, including myself, who like their xterms and iTerms in the standard size (80x24). Also, we sometime need

Re: [Python-ideas] PEP 8 update on line length

I don't think you will find an agreement to raise the number of line length (we didn't even manage to find an agreement at my job with less than 10 people), so I would suggest every reader not interested in the disscussion to put it into the bin directly, as no decision will emerge from here.

Re: [Python-ideas] PEP 8 update on line length

On Tue, Feb 19, 2019 at 05:37:29AM +0100, Simon wrote: > Hello, > > I'd like to propose an update to PEP8. Indeed, the 80 characters per line > guideline is, I feel, outdated. I know this is not precisely what you are arguing, but the thought of people arguing that the only problem with a

Re: [Python-ideas] PEP 8 update on line length

On 19Feb2019 00:09, Terry Reedy wrote: On 2/18/2019 11:37 PM, Simon wrote: I'd like to propose an update to PEP8. Indeed, the 80 characters per line guideline is, I feel, outdated. I understand the need for it, back when monitors were small, and everyone coded on terminals, but nowadays, I

Re: [Python-ideas] PEP 8 update on line length

Am 19.02.19 um 05:37 schrieb Simon: > Hello, > > I'd like to propose an update to PEP8. Indeed, the 80 characters per line > guideline is, I feel, outdated. > > I understand the need for it, back when monitors were small, and everyone > coded on terminals, but nowadays, I feel like that

Re: [Python-ideas] PEP 8 update on line length

60, or 68, or 80 characters, is not per se a cognitive limit. Yes, sure whitespace counts much less towards that burden than do regular characters. And to a significant degrees, punctuation vs. letters vs. numbers matter. And sure familiar words such as keywords scan a bit easier than unfamiliar

Re: [Python-ideas] PEP 8 update on line length

From: Python-ideas On Behalf Of Anders Hovmöller Sent: 19 February 2019 06:11 To: David Mertz Cc: Simon ; python-ideas Subject: Re: [Python-ideas] PEP 8 update on line length > On 19 Feb 2019, at 05:48, David Mertz wrote: > > You either have much better eyes to read tiny fonts

Re: [Python-ideas] PEP 8 update on line length

> On 19 Feb 2019, at 05:48, David Mertz wrote: > > You either have much better eyes to read tiny fonts than I do, or maybe a > much larger monitor (it's hard for me to fit a 30"" monitor in my laptop bag). > > But that's not even the real issue. If the characters were in giant letters > on

Re: [Python-ideas] PEP 8 update on line length

On 2/18/2019 11:37 PM, Simon wrote: Hello, I'd like to propose an update to PEP8. Indeed, the 80 characters per line guideline is, I feel, outdated. Strictly speaking, PEP8 applies only to CPython stdlib code. Please read the introduction. Adapt it as you will for your code. I

Re: [Python-ideas] PEP 8 update on line length

You either have much better eyes to read tiny fonts than I do, or maybe a much larger monitor (it's hard for me to fit a 30"" monitor in my laptop bag). But that's not even the real issue. If the characters were in giant letters on billboards, I still would never want more than 80 of them on a

[Python-ideas] PEP 8 update on line length

Hello, I'd like to propose an update to PEP8. Indeed, the 80 characters per line guideline is, I feel, outdated. I understand the need for it, back when monitors were small, and everyone coded on terminals, but nowadays, I feel like that guideline is more of a hinderance, and that it promotes