From: Joshua Lock <josh@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Supported Python version for OE?
Date: Wed, 12 May 2010 11:23:15 +0100 [thread overview]
Message-ID: <1273659795.2936.179.camel@localhost.localdomain> (raw)
In-Reply-To: <4BE91403.9080001@ge.com>
On Tue, 2010-05-11 at 09:23 +0100, Martyn Welch wrote:
> Joshua Lock wrote:
> > Hi,
> >
> > A question, (perhaps for the TSC?):
> >
> > "What's the minimum Python version we want to support in OE?"
> >
> > According to the wiki we support Python 2.4 and above but I wonder if
> > people have any thoughts with regards to bumping it?
> >
>
> I'd suggest that the better question to ask is:
>
> "Which versions of which distros do we currently intend OE to work on?"
That's a good way to re-phrase it.
>
> Given that the revisions of Python for the following distributions are
> as follows:
>
> Ubuntu 10.04 LTS - 2.6.5
> Ubuntu 8.04 LTS - 2.5.2
>
> Debian lenny (stable) - 2.5.2
> Debian squeeze (testing) - 2.5.3
> Debian sid (unstable) - 2.5.4
> Debian etch (oldstable) - 2.4.4
>
> Fedora 12 - 2.6.2
> Fedora 11 - 2.6
> Fedora 10 - 2.5.2
> Fedora 9 - 2.5.1
> Fedora 8 - 2.5.1
> Fedora 7 - 2.5
> Fedora 6 - 2.4.3
>
> RHEL6 (beta) - 2.6.2
> RHEL5 - 2.4.3
>
> OpenSUSE 11.2 - 2.6.2
> OpenSUSE 11.1 - 2.6.0
> OpenSUSE 11.0 - 2.5.2
>
> This would suggest that using 2.5 features should be ok for the majority
> of people. My one area of concern would be those using RHEL. RHEL 6
> isn't out yet and v.5 uses 2.4.3 - this wouldn't impact me, so I'm not
> overly fussed.
Hmm, thanks for the data. I'm not overly fussed either but suspect that
supporting RHEL5 is a desire for at least a while after RHEL6 comes out?
>
> > The reason I ask is because I had a user contact me about using Python
> > 2.5 features (str.partition) in relocatable.bbclass, I hadn't even
> > noticed this and seems like not many others have but it's clearly
> > affecting at least one person.
> >
> > I have a pretty trivial (if ugly) patch to work around this, but it
> > raised an interesting question so I thought I'd ask that before sending
> > the patch.
> >
>
> The only other question I can think of is "is there an advantage to
> using the Python 2.5 features?".
Only that it's less code and that the code is more thoroughly tested.
The patch was just what prompted me to question a Python 2.4 dependency.
Thanks,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre
prev parent reply other threads:[~2010-05-12 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 16:04 Supported Python version for OE? Joshua Lock
2010-05-10 16:50 ` Khem Raj
2010-05-11 8:23 ` Martyn Welch
2010-05-12 10:23 ` Joshua Lock [this message]
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=1273659795.2936.179.camel@localhost.localdomain \
--to=josh@linux.intel.com \
--cc=openembedded-devel@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 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.