Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libepoxy: Use native python3
Date: Fri, 24 Jul 2015 10:18:44 -0600	[thread overview]
Message-ID: <55B26564.2000807@mlbassoc.com> (raw)
In-Reply-To: <CAJTo0LbL3bcH_EpWG_WLJhtV14f_cXF5MLVV4oeAqDd7-T0ZKQ@mail.gmail.com>

On 2015-07-24 09:08, Burton, Ross wrote:
>
> On 24 July 2015 at 00:00, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>
>     It seems that my host python3 is broken and doesn't have a working 'argparse'
>        $ python3
>        Python 3.1.2 (r312:79147, Aug 23 2010, 05:17:13)
>
>
> argparse is part of 3.2 onwards (and 2.7 onwards...).  If the script is going to use functions that only exist in specific versions of Python then it should really check.
> Personally I'd say patching the python check to only look for "python" or "python2" would be a reasonable workaround.

I tried that and it worked fine on my [semi-broken-python3] host.

Patch sent.

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


      reply	other threads:[~2015-07-24 16:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23  0:22 [PATCH] libepoxy: Use native python3 Gary Thomas
2015-07-23 22:33 ` Burton, Ross
2015-07-23 22:38   ` Gary Thomas
2015-07-23 22:42     ` Burton, Ross
2015-07-23 23:00       ` Gary Thomas
2015-07-23 23:06         ` Richard Purdie
2015-07-23 23:15           ` Gary Thomas
2015-07-24  7:52             ` Richard Purdie
2015-07-24 14:45               ` Gary Thomas
2015-07-24 15:01                 ` Gary Thomas
2015-07-24 15:08         ` Burton, Ross
2015-07-24 16:18           ` Gary Thomas [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=55B26564.2000807@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=openembedded-core@lists.openembedded.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