google/open-location-code

Add pylint checks for Python code

Open

#327 创建于 2019年5月6日

在 GitHub 查看
 (1 评论) (1 反应) (0 负责人)Java (3,945 star) (500 fork)batch import
help wantedpython

描述

Python got code formatting added in #326 - in addition we should add pylint checking as well to pick up common errors.

We could adopt the pylintrc from the YAPF project.

Note: The pylintrc and the YAPF style will need to agree - for example the indentation in YAPF is four spaces and the above pylintrc uses two spaces.

It will need to be added to the travis.yml, and all the issues (there will be lots) addressed.

贡献者指南

技术栈
python
领域
ci cdtesting
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Python knowledgeBasic understanding of pylintFamiliarity with Travis CI
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
65
研究方向
Review the existing Python code formatting changes in PR #326 to understand current setup. Examine the pylintrc from the YAPF project linked in the issue. Ensure the pylint configuration aligns with YAPF's style (e.g., indentation). Then modify the .travis.yml to add a pylint job, run pylint on the codebase, and fix all reported issues. Consider the balance between pylint rules and YAPF formatting.