George Lee wrote:
That entirely depends on how independent you want to keep philikon.a
from philikon.b. But that question also arises when having just a and b.
Is it possible/typical/advised to have a base set of functionality in philikon,
and then be developing separate packages philikon.a and philikon.b down the line
that use philikon?
Not really. 'philikon' is a namespace package, that means it doesn't
have any functionality of its own. You'd have to make something like
Zope3-users mailing list