On Tue, Mar 16, 2010 at 07:45:27PM -0400, David Malcolm wrote:
> Python 2.6.5 and 3.1.2 are due at the end of this week.
>
> I plan to build 2.6.5 and 3.1.2 into Fedora 14 as soon as they're
> released (though if any other maintainer wants to do this, feel free!)
>
> My feeling is that they're to
Python 2.6.5 and 3.1.2 are due at the end of this week.
I plan to build 2.6.5 and 3.1.2 into Fedora 14 as soon as they're
released (though if any other maintainer wants to do this, feel free!)
My feeling is that they're too late for F-13 at this point in the
schedule [1]. Having said that, if en
IIRC, we currently jump through some hoops in brp-python-bytecompile;
upstream landed some new ways of doing this in this patch for 2.7/3.2:
http://bugs.python.org/issue8140
(Not sure if it's helpful as I think Toshio solved this already in F13's
rpm-build, but I wanted to at least send it to the
On Sun, Mar 14, 2010 at 10:53 PM, David Malcolm wrote:
> I suspect we'd need an exclusion syntax (e.g. "this module isn't
> buildable on PyPy", "this module isn't buildable on 2.7 with ppc"); you
> can perhaps express this using things like:
>
> if [ $(rpm-pyconfig --eval @major_versi...@minor_ver
Hi David,
I have to say I'm a bit sceptic about adding more runtimes to one
distribution [1]. This will increase the maintenance burden and the
general packaging complexity with no real benefit to me.
Personally I (as a developer) find it easy enough to support Python
2.4-2.6 in one software (
