platform.machine(): ImportError: No module named select

Ned Deily nad at
Wed Apr 15 22:10:50 CEST 2009

In article 
<a6b648e70904151125u5d458002tcd251ccf5e7fabb4 at>,
 "Ali H. Caliskan" <ali.h.caliskan at> wrote:
> I'm trying to use "platform.machine()" function, but it doesn't work on
> python 3.0.1. Am I doing something wrong here or is it suppose to not work
> on py3k? The errors I get while using the python interpreter:
> >>> import platform
> >>> platform.machine()
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
>   File "/opt/lib/python3.0/", line 1222, in machine
>     return uname()[4]
>   File "/opt/lib/python3.0/", line 1152, in uname
>     processor = _syscmd_uname('-p','')
>   File "/opt/lib/python3.0/", line 905, in _syscmd_uname
>     f = os.popen('uname %s 2> /dev/null' % option)
>   File "/opt/lib/python3.0/", line 629, in popen
>     import subprocess, io
>   File "/opt/lib/python3.0/", line 361, in <module>
>     import select
> ImportError: No module named select

It should work.  The select module should be there; if not, the Python 
build/installation is probably faulty.  From the path names, I'll guess 
this is on Solaris.  If so, there seems to be a long history of problems 
building select and friends.  See, for example:

Someone with current Solaris experience may be able to help.

 Ned Deily,
 nad at

More information about the Python-list mailing list