All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Larson <kergoth@gmail.com>
To: bitbake-devel@lists.openembedded.org
Cc: Christopher Larson <chris_larson@mentor.com>
Subject: [master][PATCH 0/3] Fixes for PyPy
Date: Sat, 30 Apr 2016 12:43:30 -0700	[thread overview]
Message-ID: <cover.1462040900.git.chris_larson@mentor.com> (raw)

From: Christopher Larson <chris_larson@mentor.com>

These reduce the dependence upon CPython, allowing bitbake to run under PyPy.
There doesn't seem to be much performance improvement, but still likely
worthwhile.


Please review the following changes for suitability for inclusion. If you have
any objections or suggestions for improvement, please respond to the patches. If
you agree with the changes, please provide your Acked-by.

The following changes since commit 309f5907a3661821e041ed14645b5d165007b058:

  bitbake: Switch to post release version (2016-04-29 07:41:34 +0100)

are available in the git repository at:

  https://github.com/kergoth/bitbake pypy-fixup
  https://github.com/kergoth/bitbake/tree/pypy-fixup

Christopher Larson (3):
  bb.build: handle __builtins__ as a module
  bb.event: handle __builtins__ as a module
  bb.data_smart: use iter() for __len__

 lib/bb/build.py      |  9 +++++++--
 lib/bb/data_smart.py |  2 +-
 lib/bb/event.py      | 11 ++++++++---
 3 files changed, 16 insertions(+), 6 deletions(-)

-- 
2.8.0



             reply	other threads:[~2016-04-30 19:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-30 19:43 Christopher Larson [this message]
2016-04-30 19:43 ` [master][PATCH 1/3] bb.build: handle __builtins__ as a module Christopher Larson
2016-04-30 19:43 ` [master][PATCH 2/3] bb.event: " Christopher Larson
2016-04-30 19:43 ` [master][PATCH 3/3] bb.data_smart: use iter() for __len__ Christopher Larson

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=cover.1462040900.git.chris_larson@mentor.com \
    --to=kergoth@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=chris_larson@mentor.com \
    /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.