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

Improve iterable typing (2) #79296

Merged
merged 2 commits into from
Sep 30, 2022
Merged

Improve iterable typing (2) #79296

merged 2 commits into from
Sep 30, 2022

Conversation

cdce8p
Copy link
Member

@cdce8p cdce8p commented Sep 29, 2022

Proposed change

Iterable doesn't have a __len__ method. This could lead to cases where a variable typed as Iterable is always true.

def func(var: Iterable[str]) -> None:
    if var:
        ...

If func would be called with a Generator, a valid input, the if-clause would always be true. In practice, most often func is only called with things like list, tuple, or set. For these Collection is a better base type as it includes __len__.

Mypy will soon be able to emit a specific warning: python/mypy#13762

Ref: https://docs.python.org/3/library/collections.abc.html#collections-abstract-base-classes

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • The code has been formatted using Black (black --fast homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
  • Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

  • No score or internal
  • 🥈 Silver
  • 🥇 Gold
  • 🏆 Platinum

To help with the load of incoming pull requests:

@homeassistant
Copy link
Contributor

Hey there @bdraco, @Djelibeybi, mind taking a look at this pull request as it has been labeled with an integration (lifx) you are listed as a code owner for? Thanks!

@homeassistant
Copy link
Contributor

Hey there @bdraco, mind taking a look at this pull request as it has been labeled with an integration (homekit) you are listed as a code owner for? Thanks!

@cdce8p cdce8p added the smash Indicator this PR is close to finish for merging or closing label Sep 29, 2022
@elupus elupus merged commit 249922b into home-assistant:dev Sep 30, 2022
@cdce8p cdce8p deleted the type-iterable-2 branch September 30, 2022 22:14
@github-actions github-actions bot locked and limited conversation to collaborators Oct 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla-signed code-quality integration: homekit integration: lifx small-pr PRs with less than 30 lines. smash Indicator this PR is close to finish for merging or closing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants