The Python environmental protection agency wants to seal it in a cement chamber, with pictoral messages to future civilizations warning them about the danger of using sudo to install random Python packages.

Two solutions:1. Use your distribution's package manager and avoid the crazy dependency games of PIP/Pear/Packagist/NPM/RubyGems/CPAN or whatever.2. Stick with Bash and AWK scripts or use a compiled language.

What if you have to make a derivative of the code? Would it be "Mostly Harmless?"

I'm trying to decide if that file is required to have a "goto" in it, or if it's required not to.

I think the requirement is to use goto, but have rules to make it "safe". Like "every goto needs to be followed by a comment that says if the destination is above or below, and if the goto destination is above, it needs to be in a structure such that it's not actually a looping construct. Also, it's not legal to goto a line containing a goto." Or maybe just, "goto destinations need to be in structures such that they're not actually looping constructs."

Also, when someone points out that you can still make a loop by having a goto later on in that structure, you're required to hold your hands on your ears and sing "La la la" really loudly.

I apologize for the novice handcoded Python code, I *think* that does what I want it to, but I haven't actually tested it to be certain. I'm pretty sure it does. I'd be really surprised if it didn't, because what I want it to do is generate code that won't actually compile, and that's usually pretty simple. I'm trying to get better at this, but I find Python to be a difficult environment to work with for some reason.

What if you have to make a derivative of the code? Would it be "Mostly Harmless?"

I'm trying to decide if that file is required to have a "goto" in it, or if it's required not to.

I think the requirement is to use goto, but have rules to make it "safe". Like "every goto needs to be followed by a comment that says if the destination is above or below, and if the goto destination is above, it needs to be in a structure such that it's not actually a looping construct. Also, it's not legal to goto a line containing a goto." Or maybe just, "goto destinations need to be in structures such that they're not actually looping constructs."

Also, when someone points out that you can still make a loop by having a goto later on in that structure, you're required to hold your hands on your ears and sing "La la la" really loudly.

Considering the level of spaghetti caused by Object Oriented code (gods help you if someone is using multiple inheritance), I can't imagine anyone really complaining about the "harm" that goto causes. The worst issue is how little you gain from your spaghetti code (compared to well constructed object orientation).

It is astonishing that the next generation coding scheme broke all things that modular coding was trying to repair, and broke them even harder. What is more astonishing was that it appears it is the right thing to do (data structures matter more than algorithms, make sure they are prioritized; avoid having code repetition.

SatisfactionIn an online survey of pair programmers, 96% of them stated that they enjoyed their work more than when they programmed alone and 95% said that they were more confident in their solutions when they pair programmed.[5]

At least 91% of coders are reckless loners who really would rather just do things their own way!

"Another Pip" is absolutely an E:D reference, as a finite number of pips are used to divert power between ship systems (and there are upgrades that give you "one more" to distribute), and both "Anaconda" and "Python" are ships in the game. It's possible he was referencing both the game and the distribution in a typical bit of Munroe Meta-humor.

Anaconda and Python ships existed right from the ?1984? initial release of the classic Elite, as with several other snake-themed ship names, and kept in FE2, FFE and even Oolite.

It's extremely trivial to come up with the Anaconda name alongside something where Python is a thing. It could easily be all a direct reference to ED (especially if the Another Pip thing is 'a thing' there), but then again it could be something else. If Quentin Tarrantino hadn't themed his characters in the Deadly Viper Squad as he did (envenomating snakes, rather than constricting ones) we could have had copious .py puns arising from Kill Bill lore.