This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients brett.cannon, eric.snow, eryksun, jkloth, mattip, ncoghlan, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-02-26.13:32:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As a note in favour of the "Allow package nesting to be encoded in names, not just directories" approach, we actually have a similar problem affecting builtin modules: they're currently limited to top-level modules, with no way for the module to indicate that it's actually part of the parent package. Details at (yes, that's a SourceForge era issue number).

The solutions may not overlap in practice, but they're conceptually related (i.e. outside frozen modules, the package topology is pretty tightly coupled to the underlying filesystem layout)
Date User Action Args
2019-02-26 13:32:49ncoghlansetrecipients: + ncoghlan, brett.cannon, paul.moore, tim.golden, jkloth, eric.snow, zach.ware, mattip, eryksun, steve.dower
2019-02-26 13:32:49ncoghlansetmessageid: <>
2019-02-26 13:32:49ncoghlanlinkissue36085 messages
2019-02-26 13:32:49ncoghlancreate