From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <dvhart@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 1/1] kernel.py: replace os.popen with subprocess.Popen
Date: Tue, 12 Jun 2012 11:34:08 +0100 [thread overview]
Message-ID: <1339497248.28854.20.camel@ted> (raw)
In-Reply-To: <4FD21C99.8000904@linux.intel.com>
On Fri, 2012-06-08 at 08:39 -0700, Darren Hart wrote:
>
> On 06/08/2012 08:14 AM, Martin Jansa wrote:
> > On Fri, Jun 08, 2012 at 08:08:59AM -0700, Darren Hart wrote:
> >> And here I think subprocess.check_output(...) is preferred.
> >
> > That's only in python 2.7 and newer, are distros with python-2.6
> > unsupported now?
> >
> > I did the same mistake in opkg-utils (patch for it is on yocto
> > ML).
> > https://lists.yoctoproject.org/pipermail/yocto/2012-May/009182.html
>
> Ah,
> >
> thanks for catching that. What is the minimum python requirement?
>
> I thought we had something in place to allow for older distributions
> to work with more modern python syntax.
We have the option of the external python tarball but we only resort to
that for really old systems. Our minimum python version is currently 2.6
and whilst there are some benefits from 2.7 (such as the process stuff),
we've not seen enough to warrant switching at this point. We have
workarounds in place for the process pieces.
Cheers,
Richard
next prev parent reply other threads:[~2012-06-12 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 8:51 [PATCH 0/1] kernel.py: replace os.popen with subprocess.Popen Robert Yang
2012-06-01 8:51 ` [PATCH 1/1] " Robert Yang
2012-06-08 15:08 ` Darren Hart
2012-06-08 15:14 ` Martin Jansa
2012-06-08 15:39 ` Darren Hart
2012-06-12 10:34 ` Richard Purdie [this message]
2012-06-11 17:50 ` [PATCH 0/1] " Flanagan, Elizabeth
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=1339497248.28854.20.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.intel.com \
--cc=poky@yoctoproject.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 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.