Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pedro Sanchez <psanchez@fosstel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Python standard library problems
Date: Wed, 10 Aug 2011 15:18:52 -0400	[thread overview]
Message-ID: <4E42D99C.7080806@fosstel.com> (raw)

Hello,

I'm testing Python 2.7.1 as available in current BR and I find that I 
can't load several standard modules that otherwise seem to be present.

# python
Python 2.7.1 (r271:86832, Aug  4 2011, 16:19:27)
[GCC 4.5.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
 >>> import socket
Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
   File "/usr/lib/python2.7/socket.py", line 47, in <module>
ImportError: No module named _socket

 >>> import fcntl
Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
ImportError: No module named fcntl

 >>> from subprocess import Popen, PIPE
Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
   File "/usr/lib/python2.7/subprocess.py", line 428, in <module>
ImportError: No module named select


Any ideas what's going on? This is on BR from git.

-- 
Pedro

             reply	other threads:[~2011-08-10 19:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 19:18 Pedro Sanchez [this message]
2011-08-10 21:48 ` [Buildroot] Python standard library problems Dominic Newton
2011-08-11 13:14   ` Pedro Sanchez
2011-08-11 15:37     ` Dominic Newton
2011-08-11 18:23       ` Pedro Sanchez
2011-08-11 20:54         ` Pedro Sanchez
2011-08-12 10:01           ` Maxime Ripard
2011-08-12 15:44             ` Maxime Ripard
2011-08-12 17:47               ` Pedro Sanchez
2011-08-16  8:22                 ` Maxime Ripard
2011-08-29 15:58                   ` Maxime Ripard
2011-08-30 14:36                     ` Pedro Sanchez
2011-08-31 14:17                       ` Pedro Sanchez
2011-09-01  7:50                         ` Thomas Petazzoni
2011-09-01 14:18                           ` Pedro Sanchez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E42D99C.7080806@fosstel.com \
    --to=psanchez@fosstel.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox