From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-bluez still at Python 3.9, python interpreter can't find bluetooth module
Date: Mon, 31 Oct 2022 09:50:03 +0100 [thread overview]
Message-ID: <20221031085003.fevj-P3Fi6yCdnEiIzP-0mUDLC8yTGu5DjTlTf4p2Xo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40238@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 342 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/40238#issuecomment-1296779060
Comment:
5957216b89
Anyway, bluetooth has been supported natively in CPython from Python 3.10, but we didn't enable it.
It'll be available from our build of Python 3.11 which should be available next Monday.
next prev parent reply other threads:[~2022-10-31 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 8:44 [ISSUE] " rubin55
2022-10-31 8:50 ` [ISSUE] [CLOSED] " sgn
2022-10-31 8:50 ` sgn [this message]
2022-10-31 8:50 ` sgn
2022-10-31 8:51 ` sgn
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=20221031085003.fevj-P3Fi6yCdnEiIzP-0mUDLC8yTGu5DjTlTf4p2Xo@z \
--to=sgn@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).