Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump wemake-python-styleguide from 0.13.4 to 0.14.0 #52

Conversation

dependabot-preview[bot]
Copy link
Contributor

@dependabot-preview dependabot-preview bot commented Mar 26, 2020

Bumps wemake-python-styleguide from 0.13.4 to 0.14.0.

Release notes

Sourced from wemake-python-styleguide's releases.

Version 0.14.0 aka The Walrus fighter

This release was focused on adding python3.8 support, removing dependencies that can be removed, and fixing bugs.

There are breaking changes ahead!

We also have this nice migration guide.

One more thing: flake8 still fails on := operator. And there's nothing we can do about it. Please, be patient – this linter does not allow to have := in the source code anyway!

Features

  • Breaking: removes flake8-executable, now using WPS452 instead of EXE001..EXE005
  • Breaking: removes flake8-print, now using WPS421 instead of T001
  • Breaking: removes flake8-builtins, now using WPS125 instead of A001..A005
  • Breaking: removes flake8-annotations-complexity, now using WPS234 instead of TAE002
  • Breaking: removes flake8-pep3101, now using WPS323 instead of S001, we also use a new logic for this violation: we check string defs for % patterns, and not for % operator
  • Breaking: WPS441 is no longer triggered for except blocks, it is now handled by F821 from flake8
  • Breaking: removes radon, because cognitive-complexity and mccabe is enough
  • Breaking: removes flake8-loggin-format as a direct dependency
  • Breaking: removes ImplicitTernaryViolation or WPS332, because it has too many false positives #1099
  • Removes flake8-coding, all encoding strings, visitor and tests for old WPS323 which is now reused for modulo formatting checks
  • Adds python3.8 support
  • Changes styleguide.toml and flake8.toml scripts definition
  • Extracts new violation - WPS450 from WPS436 #1118
  • Adds domain names options: --allowed-domain-names and --forbidden-domain-names, that are used to create variable names' blacklist #1106
  • Forbids to use \r (carriage return) as line breaks in strings #1111
  • Forbids to use := operator, it now reuses WPS332 code
  • Forbids to use positional only / arguments
  • Forbids to have too many names imported from a single from ... import
  • Forbids to use continue and break in finally
  • Forbids to use __reduce__ and __reduce_ex__ magic methods
  • Adds __call__ to list of methods that should be on top #1125
  • Allows _ to be now used as a defined variable
  • Removes cognitive_complexity dependency, now it is built in into our linter
  • Adds baseline information for all complexity violation messages: x > baseline
  • Changes how cognitive complexity is calculated
  • Adds support for positional arguments in different checks
  • Adds UnreadableNameViolation as WPS124 because there are some
... (truncated)
Changelog

Sourced from wemake-python-styleguide's changelog.

0.14.0 aka The Walrus fighter

This release was focused on adding python3.8 support, removing dependencies that can be removed, and fixing bugs.

There are breaking changes ahead!

We also have this nice migration guide.

Features

  • Breaking: removes flake8-executable, now using WPS452 instead of EXE001..EXE005
  • Breaking: removes flake8-print, now using WPS421 instead of T001
  • Breaking: removes flake8-builtins, now using WPS125 instead of A001..A005
  • Breaking: removes flake8-annotations-complexity, now using WPS234 instead of TAE002
  • Breaking: removes flake8-pep3101, now using WPS323 instead of S001, we also use a new logic for this violation: we check string defs for % patterns, and not for % operator
  • Breaking: WPS441 is no longer triggered for except blocks, it is now handled by F821 from flake8
  • Breaking: removes radon, because cognitive-complexity and mccabe is enough
  • Breaking: removes flake8-loggin-format as a direct dependency
  • Breaking: removes ImplicitTernaryViolation or WPS332, because it has too many false positives #1099
  • Removes flake8-coding, all encoding strings, visitor and tests for old WPS323 which is now reused for modulo formatting checks
  • Adds python3.8 support
  • Changes styleguide.toml and flake8.toml scripts definition
  • Extracts new violation - WPS450 from WPS436 #1118
  • Adds domain names options: --allowed-domain-names and --forbidden-domain-names, that are used to create variable names' blacklist #1106
  • Forbids to use \r (carriage return) as line breaks in strings #1111
  • Forbids to use := operator, it now reuses WPS332 code
  • Forbids to use positional only / arguments
  • Forbids to have too many names imported from a single from ... import
  • Forbids to use continue and break in finally
  • Forbids to use __reduce__ and __reduce_ex__ magic methods
  • Adds __call__ to list of methods that should be on top #1125
  • Allows _ to be now used as a defined variable
  • Removes cognitive_complexity dependency, now it is built in into our linter
  • Adds baseline information for all complexity violation messages: x > baseline
  • Changes how cognitive complexity is calculated
  • Adds support for positional arguments in different checks
  • Adds UnreadableNameViolation as WPS124 because there are some character combination which is not easy to read
  • Adds support for NamedExpr with in compare type violation
... (truncated)
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Mar 26, 2020
@dependabot-preview
Copy link
Contributor Author

Dependabot tried to update this pull request, but something went wrong. The most likely cause is #61, which may be blocking Dependabot from updating your dependency files.

@dependabot-preview dependabot-preview bot force-pushed the dependabot/pip/wemake-python-styleguide-0.14.0 branch from 753243c to a0887c6 Compare March 27, 2020 08:09
@skarzi
Copy link
Collaborator

skarzi commented Mar 27, 2020

I will adjust our code to wemake-python-styleguide==0.14.0 on the weekend.
I can also merge all other dependabot's PRs

@sobolevn
Copy link
Member

@skarzi thanks a lot! I have reported this problem here: python-poetry/poetry#496 and dependabot/dependabot-core#1556

@dependabot-preview dependabot-preview bot force-pushed the dependabot/pip/wemake-python-styleguide-0.14.0 branch 2 times, most recently from ed564d0 to 007e0f5 Compare March 27, 2020 20:33
@dependabot-preview dependabot-preview bot force-pushed the dependabot/pip/wemake-python-styleguide-0.14.0 branch from 007e0f5 to 795dbdf Compare March 27, 2020 21:14
@skarzi skarzi requested a review from sobolevn March 27, 2020 22:10
@sobolevn
Copy link
Member

Oops, I forgot that this PR exists! I am sorry.
I have done the same thing for no reason.

See 6216c22

@sobolevn sobolevn closed this Apr 15, 2020
@dependabot-preview
Copy link
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@sobolevn sobolevn deleted the dependabot/pip/wemake-python-styleguide-0.14.0 branch April 15, 2020 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants