third_party.pylibs.pylint.src/pylint/__main__.py

#!/usr/bin/env python

# Licensed under the GPL: https://www.gnu.org/licenses/old-licenses/gpl-2.0.html
# For details: https://github.com/PyCQA/pylint/blob/master/COPYING

import os
import sys

import pylint

# Strip out the current working directory from sys.path.
# Having the working directory in `sys.path` means that `pylint` might
# inadvertently import user code from modules having the same name as
# stdlib or pylint's own modules.
# CPython issue: https://bugs.python.org/issue33053
sys.path = [p for p in sys.path if p not in ("", os.getcwd())]

pylint.run_pylint()
Fix E265 block comment should start with '# ' 2021-02-07 13:55:38 +00:00			`#!/usr/bin/env python`

Add the new shorter license header, including to missing files. Close #894. 2016-06-01 15:11:29 +00:00			`# Licensed under the GPL: https://www.gnu.org/licenses/old-licenses/gpl-2.0.html`
			`# For details: https://github.com/PyCQA/pylint/blob/master/COPYING`

Do not allow ``python -m pylint ...`` to import user code (#3396) ``python -m pylint ...`` adds the current working directory as the first element of ``sys.path``. This opens up a potential security hole where ``pylint`` will import user level code as long as that code resides in modules having the same name as stdlib or pylint's own modules. Close #3386 2020-02-11 12:08:01 +00:00			`import os`
			`import sys`

Run as a python module 'python -m pylint'. Convenience feature on Windows, where Python scripts are never added to %PATH% directories by default. python -m pip install pylint python -m pylint 2013-09-22 09:06:37 +00:00			`import pylint`
Reformat the code with black 2018-09-16 15:33:50 +00:00
Do not allow ``python -m pylint ...`` to import user code (#3396) ``python -m pylint ...`` adds the current working directory as the first element of ``sys.path``. This opens up a potential security hole where ``pylint`` will import user level code as long as that code resides in modules having the same name as stdlib or pylint's own modules. Close #3386 2020-02-11 12:08:01 +00:00			`# Strip out the current working directory from sys.path.`
			# Having the working directory in `sys.path` means that `pylint` might
			`# inadvertently import user code from modules having the same name as`
			`# stdlib or pylint's own modules.`
			`# CPython issue: https://bugs.python.org/issue33053`
Properly strip dangerous sys.path entries (not just the first one) (#4153) 51c646bf70a6e0a86492bfd2ddd1885671d64d67 only stripped the first bad sys.path entry, causing problems when PYTHONPATH starts or ends with a colon. Closes: https://github.com/PyCQA/pylint/issues/3636 2021-02-28 16:50:05 +00:00			`sys.path = [p for p in sys.path if p not in ("", os.getcwd())]`
Do not allow ``python -m pylint ...`` to import user code (#3396) ``python -m pylint ...`` adds the current working directory as the first element of ``sys.path``. This opens up a potential security hole where ``pylint`` will import user level code as long as that code resides in modules having the same name as stdlib or pylint's own modules. Close #3386 2020-02-11 12:08:01 +00:00
Run as a python module 'python -m pylint'. Convenience feature on Windows, where Python scripts are never added to %PATH% directories by default. python -m pip install pylint python -m pylint 2013-09-22 09:06:37 +00:00			`pylint.run_pylint()`