linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tedd Ho-Jeong An <tedd.an@linux.intel.com>
To: Barry Byford <31baz66@gmail.com>,
	Bluez mailing list <linux-bluetooth@vger.kernel.org>
Subject: Re: Deprecated Python Libraries
Date: Mon, 20 Sep 2021 20:48:20 -0700	[thread overview]
Message-ID: <055f1d07ae9f5f7485061c8de9a6e96e29465b4c.camel@linux.intel.com> (raw)
In-Reply-To: <CAAu3APZAJD-uPUO1d4g=7smD34LUzkn87MkQKfdEcTC41FM5Vg@mail.gmail.com>

Hi Barry,

On Fri, 2021-09-17 at 08:03 +0100, Barry Byford wrote:
> The Python examples in the test directory have some dependencies that
> have issues:
> 
> optparse
> According to the documentation this has now been deprecated
> 
> https://docs.python.org/3/library/optparse.html#:~:text=Deprecated%20since%20version%203.2
> 
> dbus-python
> This has some known issues according to the documentation
> 
> https://dbus.freedesktop.org/doc/dbus-python/#:~:text=Alternative%20ways%20to%20get%20your%20Python%20code%20onto%20D-Bus
> 
> The above documentation has recommendations of switching to
> import argparse
> from gi.repository import Gio
> 
> Both of these should already be on systems because argparse is built
> in to Python and gi.repository is used for GLib elsewhere in the
> examples.
> Would there be any interest in getting patches to change to these
> different libraries?
> Are these test scripts used in any of the automated tests?
> Can I submit a PR via https://github.com/bluez/bluez/pulls?

If you have a patch, please submit it via mailing list instead of github.
Github is for other purpose and not ready to accept the patches/PR at this point.

> 
> Thanks,
> Barry

Regards,
Tedd Ho-Jeong An



      parent reply	other threads:[~2021-09-21  3:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17  7:03 Deprecated Python Libraries Barry Byford
2021-09-17  8:04 ` Marijn Suijten
2021-09-19 13:45   ` Barry Byford
2021-09-21  3:48 ` Tedd Ho-Jeong An [this message]

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=055f1d07ae9f5f7485061c8de9a6e96e29465b4c.camel@linux.intel.com \
    --to=tedd.an@linux.intel.com \
    --cc=31baz66@gmail.com \
    --cc=linux-bluetooth@vger.kernel.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).