Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Stephano Cetola <stephano.cetola@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] subprocess: cleanup subprocess calls
Date: Thu, 29 Sep 2016 14:34:02 -0700	[thread overview]
Message-ID: <20160929213405.27018-1-stephano.cetola@linux.intel.com> (raw)

This is the beginning of an effort to move toward a unified way of
using the subprocess module. The end goal is somday create a fork 
of the subprocess.run command intro'd in python 3.5.

The biggest hurdle in these efforts is in testing some of the more
obscure code paths that are touched when changing these subprocess
calls. With more time, many of the Popen calls that still exist
could be moved to either check_output or sub.run.

Stephano Cetola (3):
  subprocess: remove strings and migrate to direct arrays
  utils.py: gut python 2 commands in favor of subprocess.run
  subprocess: remove Popen in favor of check_output

 meta/classes/buildstats.bbclass |  6 ++++-
 meta/classes/spdx.bbclass       | 11 ++++----
 meta/lib/oe/distro_check.py     |  2 +-
 meta/lib/oe/package.py          | 13 ++++-----
 meta/lib/oe/package_manager.py  | 59 ++++++++++++++++++++---------------------
 meta/lib/oe/utils.py            | 11 +++-----
 6 files changed, 51 insertions(+), 51 deletions(-)

-- 
2.10.0



             reply	other threads:[~2016-09-29 21:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 21:34 Stephano Cetola [this message]
2016-09-29 21:34 ` [PATCH 1/3] subprocess: remove strings and migrate to direct arrays Stephano Cetola
2016-09-30 16:10   ` Burton, Ross
2016-09-29 21:34 ` [PATCH 2/3] utils.py: gut python 2 commands in favor of subprocess.run Stephano Cetola
2016-09-29 22:20   ` Christopher Larson
2016-09-29 22:52     ` Stephano Cetola
2016-09-29 21:34 ` [PATCH 3/3] subprocess: remove Popen in favor of check_output Stephano Cetola

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=20160929213405.27018-1-stephano.cetola@linux.intel.com \
    --to=stephano.cetola@linux.intel.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