@ Introducing Python: Modern Computing in Simple Packages by Bill Lubanovic (No. 432 / 12833)
The import this was posted.
@ paiza
https://paiza.io/?locale=ja-jp Execute with "Try code creation (free)".
// Here your code !
import this
print("XXXXXXXX")
~~```txt:result main.swift:2:8: error: no such module 'this' import this
(Addition 2017/01/09)
As @nukorou confirmed, Easter eggs were also displayed in paiza.
@ ideone > Python (version 2?)
http://ideone.com/q2dtSc
```py
# your code goes here
import this
result
The Zen of Python, by Tim Peters
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
https://www.tutorialspoint.com/execute_python_online.php
# Hello World program in Python
import this
print "Hello World!\n"
result
sh-4.3$ python main.py
The Zen of Python, by Tim Peters
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
Hello World!
sh-4.3$
http://www.tutorialspoint.com/execute_bash_online.php
--Procedure --Enter python --Enter import this (Easter egg is displayed) --End with quit ()
~~ There is a difference in the Python implementation method. (Although the specific implementation method inside is unknown). ~~
The Easter egg was displayed in all of the above.
I've seen an article that some online code execution environments intentionally prevent certain imports.
Recommended Posts