Github messages for voidlinux
 help / color / mirror / Atom feed
From: ysftaha <ysftaha@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] PyBluez is not up to date with python 3.10.
Date: Wed, 17 Aug 2022 02:52:58 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38730@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]

New issue by ysftaha on void-packages repository

https://github.com/void-linux/void-packages/issues/38730

Description:
### Is this a new report?

Yes

### System Info

Void 5.18.17_1 x86_64 GenuineIntel uptodate rrFFFFF

### Package(s) Affected

python3-bluez-0.23_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

importing bluetooth module in a python3.10 script works.

### Actual behaviour

```sh
$ /bin/cat foo.py
#!/bin/python3
import bluetooth
$ /bin/python3 foo.py
Traceback (most recent call last):
  File "/home/u/tmp/Bluetooth_Headset_Battery_Level/test.py", line 2, in <module>
    import bluetooth
ModuleNotFoundError: No module named 'bluetooth'
$
```

### Steps to reproduce

NOTE: similar issue closed in 2019 #1509

1. download the latest python3-bluez
2. import bluetooth in a python script
3. run script

P.S. pybluez lives in /usr/lib/python3.9/site-packages/PyBluez-0.23-py3.9.egg-info (notice the 3.9 not 3.10 yet)

             reply	other threads:[~2022-08-17  0:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17  0:52 ysftaha [this message]
2022-08-17  5:04 ` icp1994
2022-08-17  6:53 ` [ISSUE] [CLOSED] " ysftaha

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38730@inbox.vuxu.org \
    --to=ysftaha@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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;
as well as URLs for NNTP newsgroup(s).