All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel <openembedded-devel@openembedded.org>,
	bitbake-dev <bitbake-dev@lists.berlios.de>
Subject: Re: Bitbake 1.12.0 released!
Date: Sun, 27 Feb 2011 14:29:06 +0000	[thread overview]
Message-ID: <4D6A5FB2.4070604@cam.ac.uk> (raw)
In-Reply-To: <1298049536.11289.3126.camel@rex>

On 02/18/11 17:18, Richard Purdie wrote:
> Bitbake 1.12.0 has been released.
> 
> http://prdownload.berlios.de/bitbake/bitbake-1.12.0.tar.gz
> 
> This release has many cleanups and improvements to the bitbake core. The
> biggest and most user visible change is the parallel parsing work which
> is the driving reason for the release.
> 
> A git log of the differences between 1.10 and 1.12 follows.
> 
It's a dumb question, but what are the intended restrictions on python version
for running bitbake?  1.10 seems to work fine with python2.7 whereas I can
only get 1.12 to work with python2.6.

Issue is:

Traceback (most recent call last):
  File "./bitbake", line 43, in <module>
    from bb.server.process import ProcessServer, ServerCommunicator
ImportError: No module named process

I'm not having a great deal of luck tracking down why that happens but then
I haven't put all that much effort into it as yet!

Jonathan






  parent reply	other threads:[~2011-02-27 14:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 17:18 Bitbake 1.12.0 released! Richard Purdie
2011-02-18 17:50 ` Tom Rini
2011-02-20  9:08 ` Bitbake 1.12.0 released! - ImportError: No module named ply Steffen Sledz
2011-02-21  8:22   ` Steffen Sledz
2011-02-21 12:31   ` Richard Purdie
2011-02-21 13:28     ` Sledz, Steffen
2011-02-20 15:24 ` Bitbake 1.12.0 released! Koen Kooi
2011-02-21 14:36   ` Richard Purdie
2011-02-27 14:29 ` Jonathan Cameron [this message]
2011-02-27 15:30   ` Mike Westerhof
2011-02-27 20:14     ` Chris Larson
2011-02-27 22:15       ` Chris Larson
2011-02-28 16:47         ` Chris Larson
2011-02-27 15:36 ` Jonathan Cameron

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=4D6A5FB2.4070604@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=bitbake-dev@lists.berlios.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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 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.