All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Barnett <ryanbarnett3@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 2/2] i2c-tools: add support to build python extension
Date: Thu, 9 Apr 2015 08:11:30 -0500	[thread overview]
Message-ID: <CALq67GDL-UzMvGBNUTKTCCwvtkaxgWde1fQkfThQrcqN2yDkAQ@mail.gmail.com> (raw)
In-Reply-To: <CA+TH9Vm4xFyS3Wz4TuPVa4zgR+AzTKk3w53EgEjTxEmEyTvUHA@mail.gmail.com>

Angelo,

On Thu, Apr 9, 2015 at 1:32 AM, Angelo Compagnucci
<angelo.compagnucci@gmail.com> wrote:
> Dear Ryan Barnett, Yann E. MORIN, Thomas Petazzoni,
>
>>> Applied. Did you check that i2c-tools python support was Python 2 only?
>>> Or does it also support Python 3 ?
>>
>> Yes, it is Python-2 only (see the v1->v2 changelog in the commit notes).
>
> This is not true! Py-smbus supports python 3, se the commit here for
> further reference:
>
> http://www.lm-sensors.org/changeset/6267

When I tried to compile for Python 3 - I had many errors about not
finding Python3 functions. I would image that was probably due to the
fact that the include paths weren't correct. However, at that time I
had lost interest.

Please feel free to add support for Python 3 for py-smbus (i2c-tools).
Will be sure to review and test it.

Thanks,
-Ryan

  reply	other threads:[~2015-04-09 13:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-05 22:15 [Buildroot] [PATCH v5 1/2] i2c-tools: add hash file Ryan Barnett
2015-04-05 22:15 ` [Buildroot] [PATCH v5 2/2] i2c-tools: add support to build python extension Ryan Barnett
2015-04-06  9:03   ` Thomas Petazzoni
2015-04-06  9:07     ` Yann E. MORIN
2015-04-09  6:32       ` Angelo Compagnucci
2015-04-09 13:11         ` Ryan Barnett [this message]
2015-04-09 20:26           ` Angelo Compagnucci
2015-04-06  9:03 ` [Buildroot] [PATCH v5 1/2] i2c-tools: add hash file Thomas Petazzoni

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=CALq67GDL-UzMvGBNUTKTCCwvtkaxgWde1fQkfThQrcqN2yDkAQ@mail.gmail.com \
    --to=ryanbarnett3@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.