Skip to content
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

[BUILD] Disable W503 in pyproject.toml #2575

Merged
merged 1 commit into from
Oct 31, 2023
Merged

[BUILD] Disable W503 in pyproject.toml #2575

merged 1 commit into from
Oct 31, 2023

Conversation

nhat-nguyen
Copy link
Collaborator

This PR #2555 disabled W503 (means line breaks can now occur before a binary operator).

The change surprisingly didn't take any effect nor required any style changes in triton main pre-commit stage. But our triton-shared pipeline run (see Check pre-commit stage) picked this up correctly and complained about formatting issues. I'm not entirely sure what could be the cause for such difference, but if we also disable W503 in pyproject.toml then the rule is picked up correctly.

@ptillet ptillet merged commit 0cf3a67 into main Oct 31, 2023
2 of 3 checks passed
@ptillet ptillet deleted the nhat/w503 branch October 31, 2023 18:57
pingzhuu pushed a commit to siliconflow/triton that referenced this pull request Apr 2, 2024
This PR triton-lang#2555 disabled `W503`
(means line breaks can now occur before a binary operator).

The change surprisingly didn't take any effect nor required any style
changes in `triton` main `pre-commit` stage. But our `triton-shared`
[pipeline
run](https://github.com/microsoft/triton-shared/actions/runs/6710459100/job/18236352821)
(see `Check pre-commit` stage) picked this up correctly and complained
about formatting issues. I'm not entirely sure what could be the cause
for such difference, but if we also disable `W503` in `pyproject.toml`
then the rule is picked up correctly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants