-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CodeStyle] add introducing isort
#331
Conversation
|
||
### 推进方式 | ||
|
||
第一个 PR(即 [PaddlePaddle/Paddle#46475](https://github.com/PaddlePaddle/Paddle/pull/46475))添加配置并修复部分文件,之后每个 PR 修复一部分文件(尽可能保持在 1000 左右,以避免 PR-CI-Coverage 流水线崩溃在参数传递处),利用大概 5 个以内 PR 修复绝大多数文件格式,之后利用一些 PR 专注于解决需要手动解决的问题。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
利用大概 5 个以内 PR 修复绝大多数文件格式
来自 @jeff41404 的建议,具体实施时建议找个不太冲突的时间集中改
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
目前 PaddlePaddle/Paddle#46475 过去四天了,只有三个冲突,其实一般情况下不专门找时间应该也能合入(任意晚上提 PR,第二天白天 merge),集中找时间改还需要保证各个 PR 之间互不干涉,感觉有点麻烦
前两个 PR 主要修改单测应该冲突概率都不高,第三个及之后 PR 可能主要是其他部分,这部分可能冲突概率高一些,如果确实冲突概率高的话,可以考虑那部分再找时间来改
@SigureMo 本次评审不再单独增设会议,采用邮件(已发)+ 讨论的方式进行评审
|
@SigureMo 和 @XiaoguangHu01 @raindrops2sea 讨论,评审没有问题,可以现在就启动代码合入了。 |
引入 isort RFC
preview: https://github.com/cattidea/community/blob/rfc/isort/rfcs/CodeStyle/20221111_introducing_isort.md