summaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* Delete W601 -> W604 warningsDanny Sepler2022-10-181-12/+0
|
* make the example ignore a valid prefixAnthony Sottile2022-09-281-1/+1
| | | resolves #1104
* docs: Fix double-dash converted to en-dashWilliam Andrea2022-02-241-1/+1
| | | The double-dash for command line option `--ignore` was being converted to an en-dash.
* docs: E203 also applies to comma and semicolonWilliam Andrea2021-11-221-1/+1
| | | Per PEP8, "Avoid extraneous whitespace ... Immediately before a comma, semicolon, or colon". https://www.python.org/dev/peps/pep-0008/#pet-peeves
* Remove involuntary NBSP from the documentationPierre Sassoulas2021-11-091-2/+2
|
* run pyupgradeAnthony Sottile2021-11-081-7/+6
|
* add simple .pre-commit-config.yamlAnthony Sottile2021-10-101-44/+43
|
* drop python 3.4drop_py34Anthony Sottile2021-03-161-4/+4
| | | | github actions no longer supports python 3.4
* Support for space indents with size other than 4Jason Ansel2020-11-181-0/+1
| | | | This is an updated revision of pull requests #206 and #524
* Update documentation URLsSebastiaan Lokhorst2020-05-241-1/+1
|
* Add check for over-indented blocksJon Dufresne2019-01-241-0/+1
| | | | | | | | | In a project with all lines indented 4 spaces, I noticed pycodestyle was not catching code that was accidentally indented two levels (8 spaces). The over indentation was unintended and can be caught during static analysis. Fixes #430
* Remove suggestion and documentation of using unmaintained noseJon Dufresne2018-09-151-3/+0
| | | | | | | | | | | | | | The nose project has ceased development. The last commit is from Mar 3, 2016. From their docs page: https://nose.readthedocs.io/ > Note to Users > > Nose has been in maintenance mode for the past several years and will > likely cease without a new person/team to take over maintainership. > New projects should consider using Nose2, py.test, or just plain > unittest/unittest2.
* Update all pypi.python.org URLs to pypi.orgJon Dufresne2018-06-091-2/+2
| | | | | | For details on the new PyPI, see the blog post: https://pythoninsider.blogspot.ca/2018/04/new-pypi-launched-legacy-pypi-shutting.html
* Remove support for EOL Python 2.6 and 3.3Jon Dufresne2018-06-021-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Python 2.6 an 3.3 are end of life. They are no longer receiving bug fixes, including for security issues. Python 2.6 went EOL on 2013-10-29 and 3.3 on 2017-09-29. For additional details on support Python versions, see: https://devguide.python.org/#status-of-python-branches Removing support for EOL Pythons will reduce testing and maintenance resources. Removed all workarounds for older Pythons. Updated trove classifiers and documentation to better communicate supported Python versions. Additionally, pass python_requires argument to setuptools. Helps pip decide what version of the library to install. https://packaging.python.org/tutorials/distributing-packages/#python-requires > If your project only runs on certain Python versions, setting the > python_requires argument to the appropriate PEP 440 version specifier > string will prevent pip from installing the project on other Python > versions. https://setuptools.readthedocs.io/en/latest/setuptools.html#new-and-changed-setup-keywords > python_requires > > A string corresponding to a version specifier (as defined in PEP 440) > for the Python version, used to specify the Requires-Python defined in > PEP 345. Can now use more modern Python syntax including dictionary comprehension as well as more generators. Closes #755
* Implement W505 - Max Doc Length checkBrian Van Klaveren2018-05-111-6/+11
|
* Add explanation about the default configurationToshiki Hirao2018-04-221-0/+2
| | | Closes gh-685
* Merge pull request #684 from jdufresne/async-awaitIan Stapleton Cordasco2018-02-171-0/+2
|\ | | | | Add W606 warning for async and await keywords in Python 3.7
| * Add W606 warning for async and await keywords in Python 3.7Jon Dufresne2017-09-301-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From https://docs.python.org/3/whatsnew/3.6.html#new-keywords > async and await are not recommended to be used as variable, class, > function or module names. Introduced by PEP 492 in Python 3.5, they > will become proper keywords in Python 3.7. Starting in Python 3.6, the > use of async or await as names will generate a DeprecationWarning. By adding a warning to pycodestyle.py these future warnings and syntax errors can be caught during static code analysis. The await expression tests were taken from PEP-492. https://www.python.org/dev/peps/pep-0492/#id58
* | Describe code W504 line break after binary operatorPeter Cock2018-01-231-4/+7
| | | | | | Cross reference changes in pull request #502 which added this.
* | Add Python 3.6Hugo2017-12-111-2/+2
| | | | | | Plus Travis CI typo
* | Fix space in flag nameWilfred Hughes2017-10-251-2/+2
| | | | | | | | | | Previously, the line break in the source would result in `--hang- closing` (note the space) being rendered in the HTML.
* | Maintain alphabetical orderingAnn Paul2017-10-141-1/+1
| |
* | Config file example for boolean flagsAnn Paul2017-10-141-0/+2
|/
* Add W605 warning for invalid escape sequences in string literalsJon Dufresne2017-09-101-0/+2
| | | | | | | | | | | | | | | | | | | Starting with Python 3.6, invalid escape sequences in string literals are now deprecated. In a future version of Python, invalid escape sequences will be a syntax error. While this deprecation produces a runtime warning, it only appears if warnings are enabled and the first time the Python source is compiled to byte code. By adding a check to pycodestyle, projects can take advantage of static analysis to catch and fix these future syntax errors. For more information on the deprecation, see the Python release notes, https://docs.python.org/3/whatsnew/3.6.html#deprecated-python-behavior > A backslash-character pair that is not a valid escape sequence now > generates a DeprecationWarning. Although this will eventually become a > SyntaxError, that will not be for several Python releases. Fixes #633
* warn about bare except clauseŁukasz Rogalski2016-12-281-0/+2
|
* Add E306 to docs⁣ Florian Best2016-11-081-0/+2
|
* Fix issue #400: Require two blank lines after toplevel def, classNikhil Benesch2016-06-251-0/+2
|
* Updated text about running tests with tox; Closes #552Ian Lee2016-06-251-2/+1
|
* Merge pull request #525 from mtmiller/issue341Ian Lee2016-06-061-0/+6
|\ | | | | Detect single letter variable names enumerated in PEP-0008
| * Report E742 and E743 for badly named functions and classesMike Miller2016-06-031-0/+4
| |
| * Report E741 for prohibited single-letter variablesMike Miller2016-06-021-0/+2
| | | | | | | | | | | | | | Check for prohibited identifiers occuring to the lhs of an assignment operator or after the 'as' keyword. Closes #341
* | Updated Travis CI doc linkIan Lee2016-06-061-1/+1
| |
* | Updated docs related to tested Python versionsIan Lee2016-06-061-2/+2
| |
* | Fixed wrapping of text in developer.rstIan Lee2016-06-061-1/+2
| |
* | Updated developer documentation for testingIan Lee2016-06-061-4/+7
| | | | | | | | This builds upon and closes #533
* | Add test-requirements.txt with basic test packagesSusan Tan2016-06-061-0/+7
| |
* | Merge pull request #532 from mtmiller/doc-updateIan Lee2016-06-061-1/+1
|\ \ | | | | | | Update Python version list in docs
| * | Update Python version list in docsMike Miller2016-06-031-1/+1
| |/
* | Change all references to the pep8 project to say pycodestyleMaxPayton2016-06-031-10/+11
|/ | | | | | | | This fixes issue #518, pep8 still referenced in the cli help command As a side effect, `[pep8]` in setup.cfg now becomes `[pycodestyle]` Also, changed the path for the config file from ~/.config/pep8 to ~/.config/pycodestyle These feel like changes that should have come with the jump to version 2.0.0, as they are breaking, but support for as a name can still be added if it's desired enough
* Removed project level `.pep8` config fileIan Lee2016-05-311-3/+2
| | | | Closes #364
* Improved formatting of filename referencing in docsIan Lee2016-05-312-10/+10
|
* Updated docs to remove another pep8 based referenceIan Lee2016-05-311-3/+3
|
* Updated two more references to old namedoc-updateIan Lee2016-05-291-1/+2
|
* Updated project name in docsIan Lee2016-05-298-74/+69
| | | | | | Updated from references to pep8 -> pycodestyle, this fixes the sphinx build errors caught by readthedocs.
* Finished updating rtd linksupdate-rtd-linksIan Lee2016-05-291-1/+1
| | | | Updated references to pep8.readthedocs.io -> pycodestyle.readthedocs.io
* Convert readthedocs link for their .org -> .io migration for hosted projectsAdam Chainz2016-05-292-2/+2
| | | | | | | | As per their email ‘Changes to project subdomains’: > Starting today, Read the Docs will start hosting projects from subdomains on the domain readthedocs.io, instead of on readthedocs.org. This change addresses some security concerns around site cookies while hosting user generated data on the same domain as our dashboard. Test Plan: Manually visited all the links I’ve modified.
* Updated tests and doc examples -> pycodestylepackage-pycodestyleIan Lee2016-05-261-11/+11
|
* Changed heading line format for consistencyIan Lee2016-05-241-1/+1
|
* Re-added shebang line that was removedIan Lee2016-05-241-0/+1
|
* add examples showing StyleGuide config optionsNicholas Chammas2016-05-211-3/+19
|
View Lorry Controller Status