Skip to content

Conversation

@MuellerSeb
Copy link
Contributor

@MuellerSeb MuellerSeb commented Apr 9, 2021

Steps

  • Add yourself to CONTRIBUTORS if you are a new contributor.
  • Add a ChangeLog entry describing what your PR does.
  • If it's a new feature or an important bug fix, add a What's New entry in
    doc/whatsnew/<current release.rst>.
  • Write a good description on what the PR does.

Description

Pylint crashed when trying to read setup.cfg with non-ascii characters.

Type of Changes

Force encoding to be "utf-8" in _cfg_has_config.

Type
🐛 Bug fix
✨ New feature
🔨 Refactoring
📜 Docs

Related Issue

Closes #4328

@coveralls
Copy link

coveralls commented Apr 9, 2021

Coverage Status

Coverage remained the same at 91.601% when pulling d284972 on MuellerSeb:fix_setupcfg_utf8_encoding into 316fc0d on PyCQA:master.

@MuellerSeb
Copy link
Contributor Author

I can't tell if the failing pre-commit check is important or not. Otherwise this PR is ready for review from my side.

Copy link
Member

@Pierre-Sassoulas Pierre-Sassoulas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for troubleshooting this and opening a pull request !

@cdce8p cdce8p added this to the 2.7.5 milestone Apr 9, 2021
@cdce8p cdce8p added the Bug 🪲 label Apr 9, 2021
@Pierre-Sassoulas Pierre-Sassoulas merged commit ac02be7 into pylint-dev:master Apr 10, 2021
@Pierre-Sassoulas
Copy link
Member

Thank you for fixing this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PyLint Fails when there are non-ascii characters in setup.cfg

4 participants