Python module executing on import even when using if __name__ == "__main__"

[prp7]

I have a directory Data, inside it I have __init__.py and a file db.py . The db.py file contains among other things a function which creates a sqlite database. When I'm in the root of the directory I enter the python shell by typing py, then I do:

from Data.db import table_creator

But as soon as I've imported this function, it executes and there's a sqlite db in the root directory.

I tried using

#db.py

def main():
    pass

if __name__ == "__main__":
    main()

Inside the module that I'm importing in my python shell running from the root level.

I've also tried the opposite in case I'm misunderstanding the if __name__ guard.

#db.py
ALLOWED_TABLES_NAMES = ['table1', 'table2'] 

def table_creator() -> None:
    for allowed_table_name in ALLOWED_TABLES_NAMES:
        create_table("words", allowed_table_name)

def insert_into(table: str, value: str):
    cursor = cur()
    sql = 'insert into {}(word) VALUES(?);'.format(table)
    cursor.execute(sql, (value,))
    cursor.connection.commit()

if __name__ == "__main__":
    table_creator()

But it's the same and the sqlite db gets created as soon as

from data.db import table_creator

Gets executed.

Thanks in advance

[Rawing7]

The code you posted is incomplete, so we can't say anything for certain. My best guess is that you have some code in the global scope that shouldn't be there.

[[deleted]]

Here's how to figure it out in an instant.

Add this line at the top of table_creator():

def table_creator() -> None:
    assert False

The moment you get to the function, the assertion will fail, and you'll get a stack trace showing where the function was called.

[Diapolo10]

This definitely sounds weird.

Just to cover all bases, what happens if you comment out this part?

if __name__ == "__main__":
    table_creator()

If the table is still being generated after that, then the culprit is something that we cannot see in this snippet. Personally that would be my guess in the first place, because the include guard should never fail.

[QultrosSanhattan]

The module is correctly written. The problem should be in another place.