* [ISSUE] PyBluez is not up to date with python 3.10.
@ 2022-08-17 0:52 ysftaha
2022-08-17 5:04 ` icp1994
2022-08-17 6:53 ` [ISSUE] [CLOSED] " ysftaha
0 siblings, 2 replies; 3+ messages in thread
From: ysftaha @ 2022-08-17 0:52 UTC (permalink / raw)
To: ml
[-- 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)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: PyBluez is not up to date with python 3.10.
2022-08-17 0:52 [ISSUE] PyBluez is not up to date with python 3.10 ysftaha
@ 2022-08-17 5:04 ` icp1994
2022-08-17 6:53 ` [ISSUE] [CLOSED] " ysftaha
1 sibling, 0 replies; 3+ messages in thread
From: icp1994 @ 2022-08-17 5:04 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
New comment by icp1994 on void-packages repository
https://github.com/void-linux/void-packages/issues/38730#issuecomment-1217465031
Comment:
`python3-bluez` was [removed](https://github.com/void-linux/void-packages/commit/5957216b89b88d124a84e5d5045e183bf16a71aa). There was a PR for [restoring](https://github.com/void-linux/void-packages/pull/33626) it and a relevant ongoing [discussion](https://github.com/void-linux/void-packages/pull/36640).
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ISSUE] [CLOSED] PyBluez is not up to date with python 3.10.
2022-08-17 0:52 [ISSUE] PyBluez is not up to date with python 3.10 ysftaha
2022-08-17 5:04 ` icp1994
@ 2022-08-17 6:53 ` ysftaha
1 sibling, 0 replies; 3+ messages in thread
From: ysftaha @ 2022-08-17 6:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
Closed 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)
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-08-17 6:53 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-08-17 0:52 [ISSUE] PyBluez is not up to date with python 3.10 ysftaha
2022-08-17 5:04 ` icp1994
2022-08-17 6:53 ` [ISSUE] [CLOSED] " ysftaha
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).