-
Notifications
You must be signed in to change notification settings - Fork 31
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
[suggestion|lint] wrap code at column 120 #143
Comments
Well, I chose 79 because it's what my own organization uses and I find short lines and a bigger font much easier on my old eyes, which have a hard time focusing on nearby text (I'm going to guess I have a couple decades on you). If anyone from Datopian has a preference, feel free to weigh in. In the meantime @vit-zikmund feel free to set line-length to 120 in [tool.ruff] in pyproject.toml, |
@athornton at Datopian we generally use 79 character limit. In general here on Giftless we're happy to follow your lead and for you to make choices / recommendations 🙂 - i.e. act as the defacto lead on these matters 🙂 |
I guess that makes me the single person among all the stakeholders that would want this differently. No problem with that, though. I eventually learned to accept this draconian measure 😄 Long live the 79th column!💪 |
It sounds like a wontfix here as we are sticking with 79. Long live line 79! (may the old ways never die!) 😉 |
WONTFIX |
Hi folks, namely @athornton. I see you pushed the spring cleanup pretty good! Thanks for that 🚀
While currently working in my private fork at #128, I synced your changes on
main
and carelessly triedmake lint
before a beefy commit 🤕 only to find the code has been wrapped to the 79th column.While this being entirely a matter of taste, I still want to know if there would be a chance to wrap at the 120th column (PyCharm default). With so many modern "spring" goodies, we could maybe get one more? 😇
Thanks!
The text was updated successfully, but these errors were encountered: