classification
Title: The inittab modules cannot be packages
Type: enhancement Stage:
Components: Versions: Python 3.4
process
Status: open Resolution:
Dependencies: 1644818 Superseder:
Assigned To: Nosy List: brett.cannon, kayhayen, ncoghlan, r.david.murray
Priority: normal Keywords:

Created on 2010-08-30 18:28 by kayhayen, last changed 2014-06-21 04:11 by kayhayen.

Messages (6)
msg115235 - (view) Author: Kay Hayen (kayhayen) Date: 2010-08-30 18:28
Hello,

I try to include modules with PyImport_AppendInittab or PyImport_ExtendInittab and that works fine. But if these modules are part of a package, i.e. I provide "package_name.module_name" as the name, they never get considered.

Is there any way to add a package with modules below it from C/API? So that an import package_name.module_name from other modules will find it?

Yours,
Kay Hayen
msg116285 - (view) Author: Kay Hayen (kayhayen) Date: 2010-09-13 07:17
Why did you remove Python2.7 from the versions list? Isn't this supposed to track the affected versions? (This is not the first time I encountered that.)

I understand that you may not fix all bugs in 2.x, but is it already unsupported in the sense that its bugs are not tracked, then remove it from the tracker. In the alternative, please add 2.7 (and 2.6) back.

Thanks,
Kay
msg116294 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2010-09-13 11:18
We use versions to track which versions we are going to fix, not which versions are affected (which is why we don't list any versions pre-2.5...2.5 and 2.6 occasionally get security fixes, but no earlier versions even get those).

Now, why Brett removed 2.7 is more of a mystery...
msg116303 - (view) Author: Nick Coghlan (ncoghlan) * (Python committer) Date: 2010-09-13 13:33
I assume Brett marked this 3.x only because we currently don't support builtin packages at all, so making this work crosses way over into feature request territory. That makes it unsuitable for a branch in maintenance mode (i.e. 2.7).

Added the relevant dependency regarding support for builtin packages and removed 3.2 as a target version (as per Brett's comment on the other issue - the necessary spec work hasn't even been started, so there's no way this is a chance for 3.2).
msg116323 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2010-09-13 16:20
Both David and Nick are correct as to why I did what I did.
msg221152 - (view) Author: Kay Hayen (kayhayen) Date: 2014-06-21 04:11
Are you still tracking this as a feature request. If so, please note that I don't need it anymore. The meta path based import mechanism is fully sufficient to me.
History
Date User Action Args
2014-06-21 04:11:42kayhayensetmessages: + msg221152
2013-01-11 16:06:01brett.cannonsetversions: + Python 3.4, - Python 3.3
2010-09-13 16:20:12brett.cannonsetmessages: + msg116323
2010-09-13 13:33:59ncoghlansettype: behavior -> enhancement
dependencies: + Allow built-in packages and submodules as well as top-level modules
messages: + msg116303
versions: - Python 3.2
2010-09-13 11:18:27r.david.murraysetnosy: + r.david.murray
messages: + msg116294
2010-09-13 07:17:21kayhayensetmessages: + msg116285
2010-09-13 02:07:51brett.cannonsetversions: + Python 3.2, Python 3.3, - Python 2.7
2010-09-13 01:22:27eric.araujosetnosy: + brett.cannon, ncoghlan

type: enhancement -> behavior
versions: - Python 2.6
2010-08-30 18:28:16kayhayencreate