From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: python 2.6 warning
Date: Mon, 11 May 2009 23:37:38 +0100 [thread overview]
Message-ID: <1242081458.5824.37.camel@ted> (raw)
In-Reply-To: <200905111619.42187.marcin@juszkiewicz.com.pl>
On Mon, 2009-05-11 at 16:19 +0200, Marcin Juszkiewicz wrote:
> Dnia poniedziałek, 11 maja 2009 o 11:22:56 Robert Schuster napisał(a):
> > Hi all,
> > those who are using bitbake with Python 2.6 (e.g. Ubuntu 09.04,
> > Debian sid) will notice this warning:
> >
> > /home/rschus/oe/bitbake/lib/bb/COW.py:29: DeprecationWarning: the
> > sets module is deprecated
> > import types, sets
> >
> > Is anyone from OE in the know how to fix that properly? I know its
> > only a warning but imagine an OE newbie reading this .... I would
> > like to fix it myself but even after years of contributing to OE my
> > Pyhton skills are severely limited. :|
>
> BitBake trunk has it fixed by me. Backporting to 1.8.x and to
> stable/2009 are on my todolist. And yes - it works fine with Python 2.5
> and even should with Python 2.4 which is minimal required version
> (should works with 2.3 but we do not support it).
It won't work with 2.3 but we don't care about 2.3, it will work with
2.4 onwards. I have no idea why we were using long deprecated stuff :/.
I've backported it to bitbake 1.8 and it seems to work along with
merging a number of fixes lurking in Poky.
I'm also intending to merge the virtual class extension stuff soon
unless anyone has a major objection (none were raised previously when I
proposed this).
Cheers,
Richard
next prev parent reply other threads:[~2009-05-11 22:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 9:22 python 2.6 warning Robert Schuster
2009-05-11 10:10 ` Michael 'Mickey' Lauer
2009-05-11 11:39 ` Philip Balister
2009-05-11 12:54 ` Richard Purdie
2009-05-11 14:19 ` Marcin Juszkiewicz
2009-05-11 22:37 ` Richard Purdie [this message]
2009-05-12 0:11 ` Otavio Salvador
2009-05-12 10:54 ` Roman I Khimov
2009-05-12 14:32 ` Richard Purdie
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=1242081458.5824.37.camel@ted \
--to=rpurdie@rpsys.net \
--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.