zhengruifeng opened a new pull request, #37827:
URL: https://github.com/apache/spark/pull/37827

   ### What changes were proposed in this pull request?
   Pin mypy ==0.920 in dev/requirements.txt, the same as that in 
`.github/workflows/build_and_test.yml`
   
   
   ### Why are the changes needed?
   before:
   the installed version of mypy is `mypy 0.971` now, the `python-lint` always 
fail:
   ```
   (spark_dev) ➜  spark git:(master) ✗ dev/lint-python                          
   
   starting python compilation test...
   python compilation succeeded.
   
   starting black test...
   black checks passed.
   
   starting flake8 test...
   flake8 checks passed.
   
   starting mypy annotations test...
   annotations failed mypy checks:
   python/pyspark/streaming/context.py:372: error: Unused "type: ignore" comment
   python/pyspark/streaming/context.py:378: error: Unused "type: ignore" comment
   Found 2 errors in 1 file (checked 339 source files)
   1
   ```
   
   after:
   ```
   (spark_dev) ➜  spark git:(master) ✗ dev/lint-python                    
   starting python compilation test...
   python compilation succeeded.
   
   starting black test...
   black checks passed.
   
   starting flake8 test...
   flake8 checks passed.
   
   starting mypy annotations test...
   annotations passed mypy checks.
   
   starting mypy examples test...
   examples passed mypy checks.
   
   starting mypy data test...
   annotations passed data checks.
   
   
   all lint-python tests passed!
   ```
   
   ### Does this PR introduce _any_ user-facing change?
   No, only for spark contributors.
   
   
   ### How was this patch tested?
   manually test


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to