project-structure

The Python src layout places your package code inside a src/ directory, preventing accidental imports of local unbuilt files during testing and ensuring you evaluate the actual installed package for safer packaging.

To organize a Python package directory, separate source code into a src/ folder, maintain canonical directories for tests and documentation, enforce consistent naming conventions, and include essential root-level files like pyproject.toml to ensure maintainability and adherence to community standards.

The best way to structure a Python monorepo involves adopting established monorepo patterns that isolate individual packages using the src/ layout, ensuring each sub-package maintains its own canonical directory organization, naming conventions, and py.typed marker for independent testability and packaging.

To design __init__.py files for a robust public API, define explicit imports and versioning within the file, exposing only the necessary public classes and functions while keeping internal modules hidden, ensuring a maintainable and clear interface for your Python package.

You need a py.typed marker in your Python package if you use type hints and want type checkers to recognize your package as typed, which is a community best practice that ensures better maintainability and IDE support for downstream users.