black

The python formatter, I guess. https://github.com/psf/black

What a relief to click on this and see it isn't a screed against https://github.com/psf/black

I don't understand how it's ever an actual problem and not just people being lazy / literally just starting out learning the language. Every Python editor / IDE is capable of, and immediately will, notify you of any formatting issues of the sort. Python also has great, trivial to use autoformatters like black[1] that essentially all production code should use and which ensure that you never, ever have to think about this again. What realistic scenario is there where it actually makes sense deviating from the standard the language is trying to enforce? And even if you can think of one (I honestly cannot), is now having to write an “end” keyword all over your code really a tradeoff worth making? [1] https://github.com/psf/black

From my advice, try to stay on Python. I am currently doing the opposite. Moving an old Java stack to Python/Django. Been able to do so under 9 months. I think upgrading to Python 3 should be doable. What's the version of your Django stack? You just need to try to reach Django 2.2. And if you are at Django 1.1, 90% of your code can be upgraded to Python 3. Nothing fancy. You just need to use libraries such as pyupgrade [0] to automatically upgrade your code, combined with black [1], flake [2],... Everything is done in less than 20 commits. From there you jump to 2.2 which supports Python 3.6+ . It will be very difficult to implement all the goodies given by Django ORM/SQLAlchemy. But ... You if Java/C# is the tech that you feel confortable with, no problem. You have to use it. But, I really think it's easier to understand the "business d

> Given how much programming now consists of "copy, paste, and modify," enforcing style conventions on Stack Overflow might do more to improve general coding standards than anything else we could try. I'm guessing most of developers use a formatter like black [0] nowadays so that will have less and less impact. [0]: https://github.com/psf/black

I don't see the black python formatter[0] mentioned. I use it for all of my projects and I love it as I prefer not to have a linter distract me while I type. You can see a demo[1] without installing it to check how it works. [0] https://github.com/psf/black [1] https://black.vercel.app/

Prettier works for JS. A similar Python tool is Black: https://github.com/psf/black > Black makes code review faster by producing the smallest diffs possible.

Enforce consistent formatting, e.g. with black (https://github.com/psf/black) this gets formatted to [0xF or x in (1, 2, 3)].

Well, all I ask for is consistency. If "Black" is to be capitalized, "White" should be too, all men (and women) being equal and whatnot (though I suppose you could argue "Caucasian" is capitalized). Still, I don't like politicization of colors and I actively want to defuse attempts to politicize the word "black". It's getting so bad that literally the color black is coming under attack - for example the python formatter "black"[0] [0] https://github.com/psf/black/issues/1830

I don't totally disagree. My company uses the black formatter, which does this[0]. There are flags to skip string formatting, but is frowned upon at my organization. [0] https://github.com/psf/black/blob/master/docs/the_black_code...