pep8   296

« earlier    

The uncompromising code formatter — Black 18.9b0 documentation
By using Black, you agree to cede control over minutiae of hand-formatting. In return, Black gives you speed, determinism, and freedom from pycodestyle nagging about formatting. You will save time and mental energy for more important matters.

Black makes code review faster by producing the smallest diffs possible. Blackened code looks the same regardless of the project you’re reading. Formatting becomes transparent after a while and you can focus on the content instead.
python  pep8  black 
january 2019 by bmdmc
Question: why does PEP8 recommend leaving a blank line at the end of a .py file? : Python |
I still cannot find where in PEP 8 it says this, though.
The newline character is considered a line terminator, not a line delimiter.

This is right, but I think still somewhat confusing to some people. The point is that every line should end with a newline, because as was pointed out the newline is considered a line terminator.

I think the proper way to think of it is not to think of it as a blank line at the end of the file - that blank line appears in text editors, but if you were to open the file in python or most programming languages and do readlines, you wouldn't see any blank line at the end. The newline would be the last character in the last line which would be the line before the apparent blank line.
pep8  codestyle  linter  newline  textprocessing  explained 
december 2018 by kme
PyCQA/prospector: Inspects Python source files and provides information about type and location of classes, methods etc
Inspects Python source files and provides information about type and location of classes, methods etc
github  python  code-analysis  pylint  mccabe  pep8 
august 2018 by snahor
How to Use Flake8
exclude = .git,*migrations*
max-line-length = 119
python  django  flake  flake8  pep8 
june 2018 by alexisbellido
PEP8: The Style Guide for Python Code
This stylized presentation of the well-established PEP 8 was created by Kenneth Reitz (for humans).
pep8  python  styleguide  style  programming 
may 2018 by gdw

« earlier    

related tags

2016  analysis  automation  bestpractices  black  cd  check  ci  clean  cleancode  code-analysis  code-linter  code-quality  code-review  code  code_checker  codeanalysis  codestyle  coding-standards  coding-style  coding  codingstyle  colon  commas  commit  configfile  conventions  customisation  customization  dev  devel  django  docstring  documentation  double  emacs  examples  explained  flake  flake8  format  formatter  formatting  game  gamedev  github  gofmt  google  guide  hacker-news  howto  idiom  in  indentation  instructions  kennethreitz  lint  linter  linters  linting  literal  mccabe  newline  online  opensource  pep  plugin  programming  pull  pycharm  pycodereview  pycodestyle  pyflakes  pylint  python  pythonic  qa  quality  quotes  reference  repo  request  rule  rules  singe  slice  software  solution  spaghetti  stars:5  static  string  style-guide  style  styleguide  sublime  sublimetext  syntastic  syntax  syntaxchecker  sytle  talk  test  testing  textprocessing  tool  tools  video  vim  yapf  youtube 

Copy this bookmark: