File tree Expand file tree Collapse file tree 4 files changed +20
-3
lines changed
api/next_api_changes/development Expand file tree Collapse file tree 4 files changed +20
-3
lines changed Original file line number Diff line number Diff line change 11[flake8]
2- max-line-length = 79
2+ max-line-length = 88
33select =
44 # flake8 default
55 C90, E, F, W,
Original file line number Diff line number Diff line change 1+ Maximum line length increased to 88 characters
2+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3+
4+ The maximum line length for new contributions has been extended from 79 characters to
5+ 88 characters.
6+ This change provides an extra 9 characters to allow code which is a single idea to fit
7+ on fewer lines (often a single line).
8+ The chosen length is the same as `black <https://black.readthedocs.io/en/stable/the_black_code_style/current_style.html#line-length >`_.
Original file line number Diff line number Diff line change 99Status
1010======
1111
12- **Completed **
12+ **Superseded **
13+
14+ Current guidelines for style, including usage of pep8 are maintained
15+ in `our pull request guidelines <https://matplotlib.org/devdocs/devel/coding_guide.html >`_.
1316
1417We are currently enforcing a sub-set of pep8 on new code contributions.
1518
Original file line number Diff line number Diff line change @@ -30,7 +30,8 @@ rules before submitting a pull request:
3030 for more details.
3131
3232* Formatting should follow the recommendations of PEP8 _, as enforced by
33- flake8 _. You can check flake8 compliance from the command line with ::
33+ flake8 _. Matplotlib modifies PEP8 to extend the maximum line length to 88
34+ characters. You can check flake8 compliance from the command line with ::
3435
3536 python -m pip install flake8
3637 flake8 /path/to/module.py
@@ -156,6 +157,11 @@ Content topics:
156157* Does the PR conform with the :ref: `coding_guidelines `?
157158* Is the :ref: `documentation <pr-documentation >` (docstrings, examples,
158159 what's new, API changes) updated?
160+ * Is the change purely stylistic? Generally, such changes are discouraged when
161+ not part of other non-stylistic work because it obscures the git history of
162+ functional changes to the code. Reflowing a method or docstring as part of a
163+ larger refactor/rewrite is acceptable.
164+
159165
160166Organizational topics:
161167
You can’t perform that action at this time.
0 commit comments