Re: [Xen-devel] Python version requirements vs qemu-upstream

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 15.01.14 at 11:48, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> On Wed, 2014-01-15 at 10:21 +0000, Jan Beulich wrote:
>> >>> On 15.01.14 at 11:03, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
>> > On Wed, 2014-01-15 at 09:27 +0000, Jan Beulich wrote:
>> >> According to our own documentation, even Python 2.3 is supported
>> >> for building,
>> > 
>> > It might be time to consider reving that.
>> 
>> Post 4.4 perhaps, but I don't think now is the right time to consider
>> anything like that. IMO we ought to fix the build instead.
> 
> I think revving the minimum requirement to Python 2.4 would be a
> perfectly acceptable thing to do at this stage in the release, it's
> nothing more than a change to the README.

And tools/configure*.


>> And yes, bumping the requirement beyond 2.4 would require
>> me to find solutions for how to build on SLE10 (which continues
>> to be the lowest common denominator here to allow building
>> and testing of all code streams I currently need to support, i.e.
>> I'm keeping one system around for 32- and 64-bit each, and it
>> so happens that one of those is where I do most of my work on).
> 
> This is due to your workflow, not a SLE10 requirement to support latest
> Xen or anything like that, right?

Right.

>> > This is consistent with their configure script which checks for:
>> >         # Note that if the Python conditional here evaluates True we will 
>> > exit
>> >         # with status 1 which is a shell 'false' value.
>> >         if ! $python -c 'import sys; sys.exit(sys.version_info < (2,4) or 
>> > sys.version_info >= (3,))'; then
>> >           error_exit "Cannot use '$python', Python 2.4 or later is 
>> > required." \
>> >               "Note that Python 3 or later is not yet supported." \
>> >               "Use --python=/path/to/python to specify a supported Python."
>> >         fi
>> > 
>> > Did you hit that too?
>> 
>> No, I didn't (or didn't notice, which would mean the failure here
>> doesn't get propagated correctly) - it was the actual build that
>> was failing.
> 
> OK -- now I'm confused because you seem to say you expect to have hit
> this while above you say you are using Python 2.4.

I didn't look closely enough: I took the excerpt to mean > 2.4
whereas it means >=. Sorry for that.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel