Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

QUESTION: Namespace Packages

See original GitHub issue

With namespace packages, you do not put the __init__.py in the root of the namespace, does setup.py create one?

Issue Analytics

State:
Created 2 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

webknjazcommented, Apr 9, 2021

It can but only if you use old-fashioned namespacing methods. Also, I don’t remember if you can have the top-level freesoda at all. But yes, if some of your namespace packages include it and others don’t, this will likely cause problems.

0reactions

achapkowskicommented, Apr 9, 2021

so the parent package can’t have an __init__.py? in the freesoda namespace?

Top Results From Across the Web

Problem with namespace packages: ModuleNotFoundError

I am using python3.7 and trying to get namespace packages to work, but having some module import issues. It is not clear to...

PEP 420 – Implicit Namespace Packages

Namespace packages are a mechanism for splitting a single Python package across multiple directories on disk. In current Python versions, an ...

I don't need `__init__.py`? PEP 420 and namespace ...

today I talk about namespace packages, what PEP 420 is, and why I don't use namespace packagesplaylist: ...

Python Namespace Packages - YouTube

python #setuptools #packaging #namespacing #django #papermergeIn this screencast we will learn about namespace packaging and few caveats ...

there's no documentation of how to package namespace ...

txt error: Namespace package problem: jaraco is a namespace package, but its __init__.py does not call declare_namespace()! Please fix it. (See the setuptools ......