this post was submitted on 18 Mar 2026
13 points (100.0% liked)

Python

7835 readers
30 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

📅 Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

🐍 Python project:
💓 Python Community:
✨ Python Ecosystem:
🌌 Fediverse
Communities
Projects
Feeds

founded 2 years ago
MODERATORS
erlingur@programming.dev
jnovinger@programming.dev
norambna@programming.dev
13
Help with improving imports of built python package development? (lemmy.world)
submitted 1 week ago by AstroLightz@lemmy.world to c/python@programming.dev
6 comments fedilink hide all child comments
 

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
[–] dgdft@lemmy.world 4 points 1 week ago* (last edited 1 week ago)

You’re barking up the right tree. Add a relative import call to your top-level __init__.py and they’ll get namespaced in the way you’re wanting.

E.g. adding from .file import SomethingInFile as Newthing will let you run import package and reference package.Newthing.

See the docs for the __all__ dunder as well.