▲ 1320 ▼ The lengths we have to go to (sh.itjust.works) submitted 2 years ago by alphacyberranger@sh.itjust.works to c/programmer_humor@programming.dev 124 comments fedilink hide all child comments
[–] beckerist@lemmy.world 15 points 2 years ago (6 children) spaces or tabs permalink fedilink source hideshow 12 child comments replies: [–] reflex@kbin.social 16 points 2 years ago* (1 child) Doesn't PEP 8 say spaces somewheres? permalink fedilink source parent hideshow 2 child comments replies: [–] UlrikHD@programming.dev 15 points 2 years 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. permalink fedilink source parent [–] kevincox@lemmy.ml 15 points 2 years ago Use tabs. Enable visible whitespace. Tada, your indentation level is nicely visible. permalink fedilink source parent [–] GandarfDeGrape@midwest.social 13 points 2 years ago (2 children) Tabs. But really with modern IDE it's irrelevant. Whatever the tech lead says I guess. permalink fedilink source parent hideshow 4 child comments replies: [–] GBU_28@lemm.ee 8 points 2 years ago (2 children) 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 permalink fedilink source parent hideshow 4 child comments replies: [–] CoderKat@lemm.ee 1 point 2 years 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"). permalink fedilink source parent [–] theneverfox@pawb.social 1 point 2 years ago (1 child) Wait wait wait, what is this black magic and how have I not heard of it? permalink fedilink source parent hideshow 2 child comments replies: [–] GBU_28@lemm.ee 2 points 2 years 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 permalink fedilink source parent [–] RogueBanana@lemmy.zip 2 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] mexicancartel@lemmy.dbzer0.com 1 point 2 years 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! permalink fedilink source parent [–] Ocelot@lemmies.world 6 points 2 years ago* Questions like that are likely to start a war permalink fedilink source parent [–] TheBananaKing@lemmy.world 5 points 2 years ago (1 child) semicolons permalink fedilink source parent hideshow 2 child comments replies: [–] Agent641@lemmy.world 4 points 2 years ago Full colons permalink fedilink source parent [–] Jakylla@sh.itjust.works 1 point 2 years ago (2 children) 4 Spaces, then one tab, then 3 spaces, then 2 tabs, then 2 spaces, then 3 tabs... Python supports that (and I hate this) permalink fedilink source parent hideshow 4 child comments replies: [–] realaether@lemmy.world 1 point 2 years ago* (1 child) Please elaborate (eg which standard is this defined in?) permalink fedilink source parent hideshow 2 child comments replies: [–] Jakylla@sh.itjust.works 1 point 2 years ago* (last edited 2 years ago) (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] realaether@lemmy.world 2 points 2 years 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? permalink fedilink source parent [–] grozzle@lemm.ee 0 points 2 years 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. permalink fedilink source parent
[–] reflex@kbin.social 16 points 2 years ago* (1 child) Doesn't PEP 8 say spaces somewheres? permalink fedilink source parent hideshow 2 child comments replies: [–] UlrikHD@programming.dev 15 points 2 years 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. permalink fedilink source parent
[–] UlrikHD@programming.dev 15 points 2 years 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. permalink fedilink source parent
[–] kevincox@lemmy.ml 15 points 2 years ago Use tabs. Enable visible whitespace. Tada, your indentation level is nicely visible. permalink fedilink source parent
[–] GandarfDeGrape@midwest.social 13 points 2 years ago (2 children) Tabs. But really with modern IDE it's irrelevant. Whatever the tech lead says I guess. permalink fedilink source parent hideshow 4 child comments replies: [–] GBU_28@lemm.ee 8 points 2 years ago (2 children) 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 permalink fedilink source parent hideshow 4 child comments replies: [–] CoderKat@lemm.ee 1 point 2 years 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"). permalink fedilink source parent [–] theneverfox@pawb.social 1 point 2 years ago (1 child) Wait wait wait, what is this black magic and how have I not heard of it? permalink fedilink source parent hideshow 2 child comments replies: [–] GBU_28@lemm.ee 2 points 2 years 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 permalink fedilink source parent [–] RogueBanana@lemmy.zip 2 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] mexicancartel@lemmy.dbzer0.com 1 point 2 years 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! permalink fedilink source parent
[–] GBU_28@lemm.ee 8 points 2 years ago (2 children) 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 permalink fedilink source parent hideshow 4 child comments replies: [–] CoderKat@lemm.ee 1 point 2 years 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"). permalink fedilink source parent [–] theneverfox@pawb.social 1 point 2 years ago (1 child) Wait wait wait, what is this black magic and how have I not heard of it? permalink fedilink source parent hideshow 2 child comments replies: [–] GBU_28@lemm.ee 2 points 2 years 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 permalink fedilink source parent
[–] CoderKat@lemm.ee 1 point 2 years 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"). permalink fedilink source parent
[–] theneverfox@pawb.social 1 point 2 years ago (1 child) Wait wait wait, what is this black magic and how have I not heard of it? permalink fedilink source parent hideshow 2 child comments replies: [–] GBU_28@lemm.ee 2 points 2 years 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 permalink fedilink source parent
[–] GBU_28@lemm.ee 2 points 2 years 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 permalink fedilink source parent
[–] RogueBanana@lemmy.zip 2 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] mexicancartel@lemmy.dbzer0.com 1 point 2 years 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! permalink fedilink source parent
[–] mexicancartel@lemmy.dbzer0.com 1 point 2 years 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! permalink fedilink source parent
[–] Ocelot@lemmies.world 6 points 2 years ago* Questions like that are likely to start a war permalink fedilink source parent
[–] TheBananaKing@lemmy.world 5 points 2 years ago (1 child) semicolons permalink fedilink source parent hideshow 2 child comments replies: [–] Agent641@lemmy.world 4 points 2 years ago Full colons permalink fedilink source parent
[–] Jakylla@sh.itjust.works 1 point 2 years ago (2 children) 4 Spaces, then one tab, then 3 spaces, then 2 tabs, then 2 spaces, then 3 tabs... Python supports that (and I hate this) permalink fedilink source parent hideshow 4 child comments replies: [–] realaether@lemmy.world 1 point 2 years ago* (1 child) Please elaborate (eg which standard is this defined in?) permalink fedilink source parent hideshow 2 child comments replies: [–] Jakylla@sh.itjust.works 1 point 2 years ago* (last edited 2 years ago) (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] realaether@lemmy.world 2 points 2 years 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? permalink fedilink source parent [–] grozzle@lemm.ee 0 points 2 years 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. permalink fedilink source parent
[–] realaether@lemmy.world 1 point 2 years ago* (1 child) Please elaborate (eg which standard is this defined in?) permalink fedilink source parent hideshow 2 child comments replies: [–] Jakylla@sh.itjust.works 1 point 2 years ago* (last edited 2 years ago) (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] realaether@lemmy.world 2 points 2 years 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? permalink fedilink source parent
[–] Jakylla@sh.itjust.works 1 point 2 years ago* (last edited 2 years ago) (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] realaether@lemmy.world 2 points 2 years 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? permalink fedilink source parent
[–] realaether@lemmy.world 2 points 2 years 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? permalink fedilink source parent
[–] grozzle@lemm.ee 0 points 2 years 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. permalink fedilink source parent