Latest revision |
Your text |
Line 10: |
Line 10: |
| | | |
| The implication is that in Python many otherwise amazing things become easily possible after a simple import statement and/or that there is a module for almost anything you'd want to do no matter how difficult.[[Special:Contributions/199.27.130.216|199.27.130.216]] 16:30, 29 April 2015 (UTC) | | The implication is that in Python many otherwise amazing things become easily possible after a simple import statement and/or that there is a module for almost anything you'd want to do no matter how difficult.[[Special:Contributions/199.27.130.216|199.27.130.216]] 16:30, 29 April 2015 (UTC) |
− |
| |
− | The explanation was wrong about many things. Python doesn't have a heavily-simplified syntax--it's about as simple as Perl (and a lot less simple than Lisp); the difference is that it's designed first and foremost to be consistent, easy to read, and easy to remember, even at the cost of occasionally being more verbose or rigid. Its syntax doesn't generally reduce complicated things to a single word; it does allow many complicated things that might take 20 statements in C to be reduced to a single statement, but that's because it's high-level (again, like Perl), not because of its syntax. Dynamic typing has nothing to do with declaring the types of values, much less specifically numeric values, and it has nothing to do with Python automatically knowing how much space to reserve for a value--in fact, it's the opposite; C knows to reserve 4 bytes for an int variable at compile time, whereas Python has no idea what kind of value you're going to put into the variable until runtime. And "like in Visual Basic or JavaScript" is very confused--Visual Basic is statically typed, while JavaScript is dynamically typed, just like Python.
| |
− |
| |
− | Also, the explanation didn't explain why Cueball's friend was reticent to use dynamic typing or significant whitespace, or what the point of importing modules is.
| |
− |
| |
− | So I rewrote most of it. [[Special:Contributions/162.158.255.69|162.158.255.69]] 20:55, 15 September 2015 (UTC)
| |
− |
| |
− | I remember this Roald Dahl story where some guy takes everything in the medicine cabinet of their grandparent and can fly. That's what i instanly thought when i saw that phrase. I'm not sure which story, but it was a good one and i think it's worth mentioning. [[Special:Contributions/172.64.238.49|172.64.238.49]] 17:37, 21 April 2023 (UTC)
| |
− |
| |
− | : Oh wait, i'm dumb it's //George's Marvellous Medicine// [[Special:Contributions/172.71.186.83|172.71.186.83]] 17:43, 21 April 2023 (UTC)
| |
− | ::Not really, because {{w|George's Marvellous Medicine|that}} was mostly about size-changing abilities of an entire houshold (and more?) of constituent ingredients. But getting (or hallucinating) the ability to fly after consuming random pharmaceuticals is a fairly typical trope that stands well on its own general merit.
| |
− | ::I reverted your change, though no doubt you could write a better hedging statement that ''compares'' the one situation with the other. [[Special:Contributions/141.101.98.77|141.101.98.77]] 19:22, 21 April 2023 (UTC)
| |
− |
| |
− | on a similar thing to antigravity.py, the emacs devs added "m-x butterfly" as an easter egg in reference to 378: real programmers [[User:An user who has no account yet|An user who has no account yet]] ([[User talk:An user who has no account yet|talk]]) 15:28, 5 September 2023 (UTC)
| |
− |
| |
− | I think a better joke for one-liner antigravity would be <code>from __future__ import antigravity</code>, as antigravity had not been invented IRL by 2008{{Citation needed}} but may perhaps be implemented in the future. While the <code>__future__</code> keyword [https://peps.python.org/pep-0236/ had been introduced] before the comic's release, it only became common after Python 3's release the next year. [[User:ChaoticNeutralCzech|ChaoticNeutralCzech]] ([[User talk:ChaoticNeutralCzech|talk]]) 09:18, 21 November 2023 (UTC)
| |