Title is kinda confusing, but basically, I followed the Python packaging process to set up my Python package development environment. My project structure is layed out the same, except for a .venv in the root directory (not in src), and additional Python files in the src/package_username directory.

I can build my package fine, but when I go to import it into other projects, I have to import it like import package_username.file or from package_username.file import SomethingInFile. For other python packages, I would only need to do import package or from package import Something.

How can I set up by build process to remove the need for the first portion in my import statements so it matches other packages like termcolor? Is there something I need to add in my __init__.py file?

you are viewing a single comment's thread
view the rest of the comments

[–] logging_strict@programming.dev 1 point 7 months ago

Better have a damn good reason to import everything into the package level namespace.

The reasoning sqlalchemy has is to prepare beforehand to be able to run in multiple threads without needing to import anything. Importing is slow and should be done up front.

So there is a slight delay when importing sqlalchemy.

Keep in mind, the sqlalchemy author and maintainers are waaaaaaay smarter than you and I. py315 may level the play field ever so slightly.

py315 is supposed to introduce soft import. So wait for that and then everyone jump ship like every previous version has rabies.

permalink

fedilink

source