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, dgreiman, docs@python, eric.smith, eric.snow, ncoghlan, xiang.zhang
Date 2016-10-15.06:55:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1476514515.95.0.137073552812.issue28424@psf.upfronthosting.co.za>
In-reply-to
Content
For 3.4/5/6, I agree this is a documentation issue, where the data files need to be given a *non*-namespaced directory to live in. However, it's worth explicitly noting that subpackages of namespace packages can themselves be regular packages, so one possible solution is to do:

    pkg_util.get_data('my_namespace.my_package_data', 'resourcename')

rather than storing the data directly at the namespace level.
History
Date User Action Args
2016-10-15 06:55:15ncoghlansetrecipients: + ncoghlan, brett.cannon, eric.smith, dgreiman, docs@python, eric.snow, xiang.zhang
2016-10-15 06:55:15ncoghlansetmessageid: <1476514515.95.0.137073552812.issue28424@psf.upfronthosting.co.za>
2016-10-15 06:55:15ncoghlanlinkissue28424 messages
2016-10-15 06:55:15ncoghlancreate