Closed Bug 1526286 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 15134 - Update pycodestyle to 2.5.0

Categories

(Testing :: web-platform-tests, enhancement, P4)

Product:
Testing
Component:
web-platform-tests
Type:
enhancement

Tracking

(firefox67 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla67
Tracking Flags:
Tracking Status
firefox67 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 15134 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/15134
Details from upstream follow.

pyup-bot <github-bot@pyup.io> wrote:

Update pycodestyle to 2.5.0

This PR updates pycodestyle from 2.4.0 to 2.5.0.

<details>
<summary>Changelog</summary>

### 2.5.0
```
------------------

New checks:

  • E117: Over-indented code blocks
  • W505: Maximum doc-string length only when configured with --max-doc-length

Changes:

  • Remove support for EOL Python 2.6 and 3.3. PR 720.
  • Add E117 error for over-indented code blocks.
  • Allow W605 to be silenced by noqa and fix the position reported by W605
  • Allow users to omit blank lines around one-liner definitions of classes and
    functions
  • Include the function return annotation (-&gt;) as requiring surrounding
    whitespace only on Python 3
  • Verify that only names can follow await. Previously we allowed numbers
    and strings.
  • Add support for Python 3.7
  • Fix detection of annotated argument defaults for E252
  • Cprrect the position reported by W504

</details>

<details>
<summary>Links</summary>

The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/8176f12aabea
[wpt PR 15134] - Update pycodestyle to 2.5.0, a=testonly
Result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/8176f12aabea

Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox67: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.