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

[suggestion|lint] wrap code at column 120 #143

Closed
vit-zikmund opened this issue Feb 15, 2024 · 5 comments
Closed

[suggestion|lint] wrap code at column 120 #143

vit-zikmund opened this issue Feb 15, 2024 · 5 comments

Comments

@vit-zikmund
Copy link
Contributor

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 tried make 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!

@athornton
Copy link
Collaborator

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, make lint to reformat everything (or tox -e lint), develop the way you like, and then set it back and make lint again when you're ready to push and PR. And if Datopian prefers 120, then, well, I'll use that workflow in future but with short lines.

@rufuspollock
Copy link
Member

@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 🙂

@vit-zikmund
Copy link
Contributor Author

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!💪

@rufuspollock
Copy link
Member

It sounds like a wontfix here as we are sticking with 79. Long live line 79! (may the old ways never die!) 😉

@rufuspollock
Copy link
Member

WONTFIX

@rufuspollock rufuspollock closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2024
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

No branches or pull requests

3 participants