Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11156] New: In python3 module 'socket' has no attribute 'AF_BLUETOOTH'
Date: Mon, 16 Jul 2018 19:14:12 +0000	[thread overview]
Message-ID: <bug-11156-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=11156

            Bug ID: 11156
           Summary: In python3 module 'socket' has no attribute
                    'AF_BLUETOOTH'
           Product: buildroot
           Version: 2018.05
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: grzegorz at blach.pl
                CC: buildroot at uclibc.org
  Target Milestone: ---

I have build system image for RaspberryPi 2 using `make raspberrypi2_defconfig`
with some customization. For eg. I have enabled bluez-tools, bluez-utils 5.x,
rpi-bt-firmware and of course python3. When I try to create bluetooth socket, I
get an error:

Python 3.6.3 (default, Jul 16 2018, 20:00:50) 
[GCC 7.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import socket
>>> s = socket.socket(socket.AF_BLUETOOTH, socket.SOCK_STREAM, socket.BTPROTO_RFCOMM)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: module 'socket' has no attribute 'AF_BLUETOOTH'


Bluetooth sockets works correctly in python3 on Raspbian.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2018-07-16 19:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 19:14 bugzilla at busybox.net [this message]
2018-07-17 11:18 ` [Buildroot] [Bug 11156] In python3 module 'socket' has no attribute 'AF_BLUETOOTH' bugzilla at busybox.net
2018-11-02 10:16 ` bugzilla at busybox.net

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=bug-11156-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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