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

Update mypy pre-commit hook to 0.910. #9448

Closed
wants to merge 7 commits into from

Conversation

bdice
Copy link
Contributor

@bdice bdice commented Oct 15, 2021

Following up from #9300 and #9433, this PR updates the mypy pre-commit hook to a modern version, 0.910. The 0.900 release of mypy made some breaking changes, and required nontrivial modifications to the code. The changes in newer versions of mypy had previously caused issues with our static checks over the codebase, which I documented in #9300.

See commit log for details on the changes that were needed.

@bdice bdice added 3 - Ready for Review Ready for review by team Python Affects Python cuDF API. improvement Improvement / enhancement to an existing function non-breaking Non-breaking change labels Oct 15, 2021
@bdice bdice self-assigned this Oct 15, 2021
@bdice bdice requested a review from a team as a code owner October 15, 2021 13:47
@galipremsagar galipremsagar requested review from shwina and removed request for marlenezw October 15, 2021 15:05
@ajschmidt8
Copy link
Member

rerun tests

@bdice
Copy link
Contributor Author

bdice commented Oct 21, 2021

Closing. See #9450 (comment).

@bdice bdice closed this Oct 21, 2021
@bdice bdice removed the 3 - Ready for Review Ready for review by team label Oct 21, 2021
rapids-bot bot pushed a commit that referenced this pull request Oct 21, 2021
…9490)

Some changes in #9412 and #9433 may lead to conflicts in VSCode / rapids-compose behavior for many developers. I am closing my PRs #9448 and #9450 for the same reason. See #9450 (comment) for details.

This PR reverts the problematic parts of #9412 and #9433, and makes the pre-commit configuration and the conda environment pinnings consistent.

Tagging @vyasr @galipremsagar @ajschmidt8 for awareness.

Authors:
  - Bradley Dice (https://github.com/bdice)

Approvers:
  - AJ Schmidt (https://github.com/ajschmidt8)
  - Vyas Ramasubramani (https://github.com/vyasr)

URL: #9490
@bdice bdice mentioned this pull request Oct 21, 2021
rapids-bot bot pushed a commit that referenced this pull request Nov 1, 2021
I noticed while working on #9448 that we `import six` but it doesn't appear to be a dependency of cuDF. Since that package is meant for Python 2 compatibility and we do not support Python 2, I think it can be removed.

`six` is probably being installed as a transitive dependency of some dependency of cuDF, if I were to guess, otherwise I'd think tests would fail.

Note: the `queryutils.py` module containing these lines may be somewhat outdated. The module [is not covered by tests from 21.08](https://app.codecov.io/gh/rapidsai/cudf/blob/branch-21.08/python/cudf/cudf/utils/queryutils.py) through 21.12, but [was covered by tests in 21.06](https://app.codecov.io/gh/rapidsai/cudf/blob/branch-21.06/python/cudf/cudf/utils/queryutils.py). It is currently only used in a couple places, which may deserve some cleanup: https://github.com/rapidsai/cudf/search?q=queryutils

Authors:
  - Bradley Dice (https://github.com/bdice)

Approvers:
  - GALI PREM SAGAR (https://github.com/galipremsagar)
  - Sheilah Kirui (https://github.com/skirui-source)

URL: #9495
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improvement / enhancement to an existing function non-breaking Non-breaking change Python Affects Python cuDF API.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants