Something like the following could be a solution, in which Nmspc could be considered the meta-project of Ping and Pong. It's not actually tested, so some tweaking will be needed.
The directory tree might look like this:
.
├── NmspcCore
│ ├── nmspc
│ │ └── _core
│ │ ├── __init__.py
│ │ └── common.py
│ └── setup.py
├── NmspcPing
│ ├── nmspc
│ │ └── ping
│ │ ├── __init__.py
│ │ └── foo.py
│ └── setup.py
└── NmspcPong
├── nmspc
│ └── pong
│ ├── __init__.py
│ └── bar.py
└── setup.py
3 Python projects:
- NmspcCore provides
nmspc._core(the leading underscore denotes a private element) and should not be installed directly - NmspcPing provides
nmspc.pingand depends on NmspcCore - NmspcPong provides
nmspc.pongand depends on NmspcCore
They all make use of namespace packages. They can be designed according to the instructions from the Python Packaging User Guide on "Packaging namespace packages, Native namespace packages". There is another example here.
NmspcCore/setup.py:
#!/usr/bin/env python3
import setuptools
setuptools.setup(
name='NmspcCore',
version='1.2.3',
packages=['nmspc._core',],
)
NmspcCore/nmspc/_core/common.py
MARCO = 'polo'
NmspcPing/setup.py (and similarly NmspcPong/setup.py):
#!/usr/bin/env python3
import setuptools
setuptools.setup(
name='NmspcPing',
version='1.2.3',
packages=['nmspc.ping',],
install_requires=['NmspcCore',],
)
NmspcPing/nmspc/ping/foo.py
import nmspc._core
print(nmspc._core.common.MARCO)
An umbrella project Nmspc could also be considered. Such a project would be empty (no actual code), but would have NmspcPing and NmspcPong as direct dependencies, so that one could install the whole projects ensemble all at once.
Thanks for this clear answer! I am not sure I fully understand the underscore issue, though. Wat is the benefit of making
_coreprivate? Could you elaborate a little further?1. The leading underscore is just a Python convention. This basically means "for internal use only". When one sees the underscore, they should know not to mess with this, they should for example not import it. But remember that it is just a convention, the underscore has no actual effect and the elements are still importable. 2. The phrasing is probably misleading: the project can and will be installed but there is no point in installing it independently since it is meant as a library for internal use.
You might also want to consider an umbrella project Nmspc that would be empty (no actual code), but that would have NmspcPing and NmspcPong as direct dependencies, so that one could install the whole project all at once.