| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
Add changelog items for 2.3.1...master
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
| |
This adds some module level configuration points for users to define
how many blank lines they want in their code. It paves the way for
someone to develop a flake8 plugin to configure this in pycodestyle.
Fixes #732
|
|
|
|
|
|
|
|
| |
* Add special case to maximum_line_length to ignore long shebang lines.
* Add test for ignoring long shebang lines.
* Clean up shebang line check.
|
|
|
|
|
|
|
|
| |
Python 3.7 added a warning for a future feature of nested regular expressions. To avoid
this warning we escape what is not a nested regex. This also keeps track of the `async`
keyword and handles it appropriately.
Closes gh-728
|
|\
| |
| | |
Add W606 warning for async and await keywords in Python 3.7
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
|
|\ \
| | |
| | | |
Add E252 on missing whitespace for annotated parameter defaults
|
| | | |
|
|\ \ \
| | | |
| | | | |
Describe code W504 line break after binary operator
|
|/ / /
| | |
| | | |
Cross reference changes in pull request #502 which added this.
|
|\ \ \
| | | |
| | | | |
Add W504 for line breaks before binary operators
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
This flips the W503 rule to enforce line breaks before binary operators.
Related #498
|
|\ \ \
| |/ /
|/| | |
Fix handling of diffs with mnemonic prefixes
|
|/ / |
|
|\ \
| | |
| | | |
Add Python 3.6 to test list in dev docs
|
|/ /
| |
| | |
Plus Travis CI typo
|
|\ \
| | |
| | | |
Allow continuation of verbosity level
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Fix space in flag name
|
|/ / /
| | |
| | |
| | |
| | | |
Previously, the line break in the source would result in
`--hang- closing` (note the space) being rendered in the HTML.
|
|\ \ \
| | | |
| | | | |
Fix missed quoting in E722 check
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The warning looks fairly odd:
E722 do not use bare except'
change this to
E722 do not use bare 'except'
|
|\ \ \
| | | |
| | | | |
Document all supported Python versions as trove classifiers
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I frequently use PyPI trove classifiers to check if a 3rd party package
is usable by my projects. Documenting the supported versions makes this
much easier for potential library users.
|
|\ \ \ \
| | | | |
| | | | | |
Enable pip cache in Travis CI
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Can speed up builds and reduce load on PyPI servers.
For more information, see:
https://docs.travis-ci.com/user/caching/#pip-cache
|
|\ \ \ \
| | | | |
| | | | | |
Include license file in the generated wheel package
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use MANIFEST.in to include LICENSE in the source distribution.
The wheel package format supports including the license file. This is
done using the [metadata] section in the setup.cfg file. For additional
information on this feature, see:
https://wheel.readthedocs.io/en/stable/index.html#including-the-license-in-the-generated-wheel-file
|
|\ \ \ \
| |_|_|/
|/| | | |
Add examples
|
| | | | |
|
|/ / / |
|
|\ \ \
| |_|/
|/| | |
Add W605 warning for invalid escape sequences in string literals
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| | |
| | | |
Fix variable annotations
|
| |\ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Had to catch a "No signature found for builtin <built-in method
search of _sre.SRE_Pattern object at 0x...>" in 3.4:
In python3.4 the search was not detected as a function, now that it's
wrapped in an lru_cache it is, yet it still has no signature (it has
in 3.5+).
|
| |/
|/|
| |
| |
| |
| |
| | |
See:
https://bitbucket.org/pypa/wheel/src/54ddbcc9cec25e1f4d111a142b8bfaa163130a61/wheel/bdist_wheel.py?fileviewer=file-view-default#bdist_wheel.py-119:125
http://pythonwheels.com/
|
| |
| |
| | |
Users' global .gitattributes files may attempt to auto-fix certain files.
|