The main reason is because importing a module runs it. However, a module's __name__ attribute is only set to "__main__" if it was executed directly, instead of imported.
Thus, you can write a module to run by itself, but also import it without having it try to run as if it were the main script.
Consistency is important besides, so we just conventionally use the if __name__ == '__main__': syntax, even if we don't think we'll need it. There are exceptions, but you should default to using it until you have a reason not to.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The main reason is because importing a module runs it. However, a module's
__name__attribute is only set to"__main__"if it was executed directly, instead of imported.Thus, you can write a module to run by itself, but also
importit without having it try to run as if it were the main script.Consistency is important besides, so we just conventionally use the
if __name__ == '__main__':syntax, even if we don't think we'll need it. There are exceptions, but you should default to using it until you have a reason not to.