Name space / Package issues

[giampaolo]

From billiej...@gmail.com on February 18, 2009 06:08:07

What steps will reproduce the problem?  
1. >>> import psutil
2. >>> psutil
3. <module 'psutil' from
'/usr/local/lib/python2.4/site-packages/psutil/__init__.pyc'>
4. >>> dir(psutil)
['Process', 'ProcessInfo', '__builtins__', '__doc__', '__file__',
'__name__', '__path__', '_pslinux', 'get_process_list', 'os', 'psutil',
'sys', 'test']
5. >>> psutil.psutil
<module 'psutil.psutil' from
'/usr/local/lib/python2.4/site-packages/psutil/psutil.pyc'>
6. >>> dir(psutil.psutil)
['Process', 'ProcessInfo', '__builtins__', '__doc__', '__file__',
'__name__', '_platform_impl', '_pslinux', 'get_process_list', 'os', 'sys',
'test']



Anomalies:

- step 4: 'psutil' shouldn't be there
- step 4: '_platform_impl' is missing
- step 6: '_platform_impl' is available in psutil.psutil (?)

Original issue: http://code.google.com/p/psutil/issues/detail?id=13

[giampaolo]

From jlo...@gmail.com on February 18, 2009 07:35:45

_platform_impl should not be visible since it is prefixed with an underscore 
are importing everything from psutil directory/module with "from psutil import 
which excludes "private" members.

The psutil.psutil module object is created because of the same import - the 
around it appears to be to place our code in __init__.py which I'm not all that 
of. I vote for leaving this alone for now and if we find a good reason we need 
move the code we can just move everything from psutil.py into __init__.py 
some later date.

[giampaolo]

From jlo...@gmail.com on February 18, 2009 09:56:23

Let's mark this as WontFix for now until/unless we need to change it someday.

Status: WontFix