mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
gecko-dev/tools/lint/py3.yml

51 строка
1.2 KiB
YAML
Исходник Обычный вид История

Bug 1391019 - Add py2 and py3 compatability linters, r=gps check_compat.py was adapted from gps' check-py3-compat.py in mercurial: https://www.mercurial-scm.org/repo/hg/file/tip/contrib/check-py3-compat.py The py3 linter simply runs ast.parse(f) for each file being linted. Any syntax errors are formatted as mozlint results and dumped to stdout as json. I looked into also importing the file (using 3.5+'s importlib.util.spec_from_file_location), but there were too many problems: 1. Lots of false positives (e.g module not found) 2. Some files seemed to run indefinitely on import I decided to punt on importing for now, we can always investigate in a follow-up. The py2 linter runs ast.parse(f), and also checks that the file has: from __future__ import absolute_import, print_function Initially every python file in the tree is excluded from the py2 check, though at least this makes it easy to find+fix, and new files in un-excluded directories will automatically be linted. MozReview-Commit-ID: ABtq9dnPo9T --HG-- extra : rebase_source : 60762937284d498514cd020b90cbfd2ba23f0b70
2017-08-31 17:12:02 +03:00
---
py3:
description: Python 3 compatibility check
include: ['.']
exclude:
- browser/app
- browser/components
- browser/extensions
- build
- client.py
- config
- dom/bindings
- dom/canvas/test
- dom/media/test
- gfx
- intl/icu
- ipc/chromium
- ipc/ipdl
- js/src
- layout/reftests
- layout/style
- layout/tools/reftest
- media
- memory/replace
- modules/freetype2
- nsprpub
- security/manager/ssl
- security/nss
- services/common/tests/mach_commands.py
- servo
- testing/awsy
- testing/firefox-ui/harness/firefox_ui_harness/runners/update.py
- testing/gtest
Backed out changeset dbe60b600dc0 (bug 1397853) for failining linter py-compat at testing/mochitest/runtests.py:2236. r=backout
2017-09-28 15:58:36 +03:00
- testing/mochitest
Bug 1391019 - Add py2 and py3 compatability linters, r=gps check_compat.py was adapted from gps' check-py3-compat.py in mercurial: https://www.mercurial-scm.org/repo/hg/file/tip/contrib/check-py3-compat.py The py3 linter simply runs ast.parse(f) for each file being linted. Any syntax errors are formatted as mozlint results and dumped to stdout as json. I looked into also importing the file (using 3.5+'s importlib.util.spec_from_file_location), but there were too many problems: 1. Lots of false positives (e.g module not found) 2. Some files seemed to run indefinitely on import I decided to punt on importing for now, we can always investigate in a follow-up. The py2 linter runs ast.parse(f), and also checks that the file has: from __future__ import absolute_import, print_function Initially every python file in the tree is excluded from the py2 check, though at least this makes it easy to find+fix, and new files in un-excluded directories will automatically be linted. MozReview-Commit-ID: ABtq9dnPo9T --HG-- extra : rebase_source : 60762937284d498514cd020b90cbfd2ba23f0b70
2017-08-31 17:12:02 +03:00
- testing/mozharness
- testing/tools/iceserver
- testing/tps
- testing/web-platform
- third_party
- toolkit
- tools/jprof
- tools/profiler
- tools/rb
- tools/update-packaging
- xpcom/idl-parser
- xpcom/typelib
extensions: ['py']
type: external
payload: python.compat:lintpy3
Bug 1436792 - [py-compat] Improve error messaging when python is missing, r=jmaher This patch makes a few changes around error handling: 1) Prints the name of the linter that produced non-json output 2) Changes the 'python not found' error to a warning (as this is not fatal) 3) Makes sure said warning only gets printed once (by moving it to the setup function) MozReview-Commit-ID: Dkq7CulTs91 --HG-- extra : rebase_source : 5d4bd32a62264a88520c09420f5acd90edcdc740
2018-02-08 22:26:15 +03:00
setup: python.compat:setuppy3