diff options
author | Peter Kolbus <peter.kolbus@gmail.com> | 2020-11-29 07:57:39 -0600 |
---|---|---|
committer | Pierre Sassoulas <pierre.sassoulas@gmail.com> | 2021-03-09 09:13:05 +0100 |
commit | 12beaa0d3fa050b68dff092520966c63d2f0e437 (patch) | |
tree | 43db9ce6bb831103042cc9c19e56145c7781ce25 /doc/technical_reference | |
parent | f17007b55e79af1e36d4aad5ec1802fe1ba51662 (diff) | |
download | pylint-git-12beaa0d3fa050b68dff092520966c63d2f0e437.tar.gz |
Add extension-pkg-allow-list option
Add an option extension-pkg-allow-list to the main checker. This is an
alternate name for extension-pkg-whitelist.
Diffstat (limited to 'doc/technical_reference')
-rw-r--r-- | doc/technical_reference/c_extensions.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/technical_reference/c_extensions.rst b/doc/technical_reference/c_extensions.rst index fbf25ec41..1bc7475c2 100644 --- a/doc/technical_reference/c_extensions.rst +++ b/doc/technical_reference/c_extensions.rst @@ -9,11 +9,11 @@ Linting C extension modules is not supported out of the box, especially since pylint has no way to get an AST object out of the extension module. But **pylint** actually has a mechanism which you might use in case you -want to analyze C extensions. **pylint** has a flag, called **extension-pkg-whitelist**, -through which you can tell it to import that module and to build an AST from that -imported module:: +want to analyze C extensions. **pylint** has a flag, called **extension-pkg-allow-list** +(formerly **extension-pkg-whitelist**), through which you can tell it to +import that module and to build an AST from that imported module:: - $ pylint --extension-pkg-whitelist=your_c_extension + $ pylint --extension-pkg-allow-list=your_c_extension Be aware though that using this flag means that extensions are loaded into the active Python interpreter and may run arbitrary code, which you may not want. This |