The lengths we have to go to - eviltoast
      • UlrikHD@programming.dev
        link
        fedilink
        arrow-up
        16
        arrow-down
        1
        ·
        1 year ago

        4 spaces, although I’ll die on the hill that tabs should always be used instead of space for indentation. Not just in python.

    • kevincox@lemmy.ml
      link
      fedilink
      arrow-up
      15
      ·
      1 year ago
      1. Use tabs.
      2. Enable visible whitespace.

      Tada, your indentation level is nicely visible.

    • gandarf @midwest.social
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      2
      ·
      1 year ago

      Tabs. But really with modern IDE it’s irrelevant. Whatever the tech lead says I guess.

      • GBU_28@lemm.ee
        link
        fedilink
        English
        arrow-up
        8
        ·
        1 year ago

        With things like black, flake 8 and Isort I can code however I want, list/format however I want, and commit team compliant content. The dream is real

          • GBU_28@lemm.ee
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            So you can have a local, and a team config. So at time of commit the code rules your team has selected are enforced. So if I looked at my code, on GitHub, it would look as expected by the team.

            If I load it locally, it formats as I like.

            Check out the cicd stuff on PRs for github

        • CoderKat@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          I love such formatters and wish they were even more widespread. In many cases, I really want consistency above all and it’s so dang hard to achieve that without an opinionated formatter. If the formatters isn’t opinionated enough, it just leads to countless human enforced rules that waste time (and lead to an understandable chorus of “why can’t the formatter just do that for meeeee”).

      • RogueBanana@lemmy.zip
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        1 year ago

        Yeah but outside of that where the code is implemented or in a documentation, tabs are still easier to look through. And it does look pretty as long as there aren’t too many nested functions.

        • mexicancartel@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Even with nested functions tabs are neat.

          Does you app have too many nested functions?

          Use tab width = 2

          Do your app have too less nested functions?

          Use tab width = 8

          Is your app having average number of nested fns?

          Use tab width = 4(mostly default)

          And all theese can happen without modifying a single byte in the source file, unlike spaces!

    • Jakylla@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      3
      ·
      1 year ago

      4 Spaces, then one tab, then 3 spaces, then 2 tabs, then 2 spaces, then 3 tabs…

      Python supports that (and I hate this)

        • Jakylla@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          1 year ago

          Not any standard (and actually not at all something to do for real), but try it, it works

          def magic(a, b, c):
              if a > 0:
              	if b > 0:
              	   		if c > 0:
              	   		  return 'All positive'
              
              return 'Not all positive'
          
          print(magic(1,2,3))
          print(magic(-1,1,2))
          print(magic(1,-1,0))
          print(magic(-1,-1,-2))
          

          (you should be able to verify I used both tab and spaces f*cking bad way in this example, like I described)

          Output:

          All positive
          Not all positive
          Not all positive
          Not all positive
          
          
          ** Process exited - Return Code: 0 **
          Press Enter to exit terminal
          
          • realaether@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            That’s really interesting. So does that mean the interpreter just checks whether the current line is more indented, less indented, or equal vs. the preceding, without caring by how much?

      • grozzle@lemm.ee
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        1 year ago

        “indentation is indentation!” (mr_incredible_cereal.jpg)

        it may look messy, but would you actually rather Python didn’t support some inconsistency when the intent is clear?

        being exact just for the sake of being pedantic isn’t useful.