Modules & Packaging interview questions

1. A.a single .py file whose top-level names become attributes importable elsewhere
2. B.an isolated directory with its own interpreter and installed packages, keeping project dependencies separate
3. C.the standardized configuration file declaring build system, metadata, and dependencies for a project
4. D.a directory of related modules, traditionally marked by an __init__ file, imported as a namespace

Answer + AI explanation with Pro

1. A.pyproject.toml
2. B.virtual environment
3. C.__name__ guard
4. D.module

Answer + AI explanation with Pro

1. A.module — the if check comparing the module's name to "__main__" to run code only when executed directly, not imported
2. B.module — a single .py file whose top-level names become attributes importable elsewhere
3. C.module — a directory of related modules, traditionally marked by an __init__ file, imported as a namespace
4. D.module — the standardized configuration file declaring build system, metadata, and dependencies for a project

Answer + AI explanation with Pro

1. A.the if check comparing the module's name to "__main__" to run code only when executed directly, not imported
2. B.an isolated directory with its own interpreter and installed packages, keeping project dependencies separate
3. C.a single .py file whose top-level names become attributes importable elsewhere
4. D.a directory of related modules, traditionally marked by an __init__ file, imported as a namespace

Answer + AI explanation with Pro

1. A.pyproject.toml
2. B.__name__ guard
3. C.virtual environment
4. D.package

Answer + AI explanation with Pro

1. A.package — an isolated directory with its own interpreter and installed packages, keeping project dependencies separate
2. B.package — a directory of related modules, traditionally marked by an __init__ file, imported as a namespace
3. C.package — a single .py file whose top-level names become attributes importable elsewhere
4. D.package — the standardized configuration file declaring build system, metadata, and dependencies for a project

Answer + AI explanation with Pro

1. A.the if check comparing the module's name to "__main__" to run code only when executed directly, not imported
2. B.a directory of related modules, traditionally marked by an __init__ file, imported as a namespace
3. C.an isolated directory with its own interpreter and installed packages, keeping project dependencies separate
4. D.a single .py file whose top-level names become attributes importable elsewhere

Answer + AI explanation with Pro

1. A.__name__ guard
2. B.virtual environment
3. C.pyproject.toml
4. D.module

Answer + AI explanation with Pro

1. A.__name__ guard — a single .py file whose top-level names become attributes importable elsewhere
2. B.__name__ guard — a directory of related modules, traditionally marked by an __init__ file, imported as a namespace
3. C.__name__ guard — an isolated directory with its own interpreter and installed packages, keeping project dependencies separate
4. D.__name__ guard — the if check comparing the module's name to "__main__" to run code only when executed directly, not imported

Answer + AI explanation with Pro

1. A.a single .py file whose top-level names become attributes importable elsewhere
2. B.the standardized configuration file declaring build system, metadata, and dependencies for a project
3. C.a directory of related modules, traditionally marked by an __init__ file, imported as a namespace
4. D.the if check comparing the module's name to "__main__" to run code only when executed directly, not imported

Answer + AI explanation with Pro

1. A.module
2. B.pyproject.toml
3. C.virtual environment
4. D.__name__ guard

Answer + AI explanation with Pro

1. A.pyproject.toml — the standardized configuration file declaring build system, metadata, and dependencies for a project
2. B.pyproject.toml — an isolated directory with its own interpreter and installed packages, keeping project dependencies separate
3. C.pyproject.toml — a single .py file whose top-level names become attributes importable elsewhere
4. D.pyproject.toml — the if check comparing the module's name to "__main__" to run code only when executed directly, not imported

Answer + AI explanation with Pro

1. A.a directory of related modules, traditionally marked by an __init__ file, imported as a namespace
2. B.an isolated directory with its own interpreter and installed packages, keeping project dependencies separate
3. C.the standardized configuration file declaring build system, metadata, and dependencies for a project
4. D.a single .py file whose top-level names become attributes importable elsewhere

Answer + AI explanation with Pro

1. A.module
2. B.__name__ guard
3. C.virtual environment
4. D.pyproject.toml

Answer + AI explanation with Pro

1. A.virtual environment — the standardized configuration file declaring build system, metadata, and dependencies for a project
2. B.virtual environment — the if check comparing the module's name to "__main__" to run code only when executed directly, not imported
3. C.virtual environment — a directory of related modules, traditionally marked by an __init__ file, imported as a namespace
4. D.virtual environment — an isolated directory with its own interpreter and installed packages, keeping project dependencies separate

Answer + AI explanation with Pro