bug#44239: closed ([PATCH] Python double-digit version detection broken)

[GNU bug Tracking System]

Your message dated Tue, 27 Oct 2020 15:36:50 -0600
with message-id <202010272136.09RLaowO001206@freefriends.org>
and subject line Re: bug#44239: [PATCH] Python double-digit version detection 
broken
has caused the debbugs.gnu.org bug report #44239,
regarding [PATCH] Python double-digit version detection broken
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
44239: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=44239
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: [PATCH] Python double-digit version detection broken Date: Mon, 26 Oct 2020 14:00:43 +0100

Hi,

we have encountered an issue[1] with the python double-digit version detection.

The used `sys.version[:3]` used in automake strips digits from the python version. For example '3.10' is detected as '3.1'.

To fix this issue, `sys.version[:3]` is changed to `sys.version_info[:2]` in the attached patch.

Version: 1.16.2
How to reproduce: Use automake with python 3.10 (or any double-digit version)

More details can be found in the bugzilla below if needed.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1889732

--
Patrik Novotný
Associate Software Engineer
Red Hat
panovotn@redhat.com

0001-Fix-double-digit-python-version-detection.patch
Description: Source code patch

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#44239: [PATCH] Python double-digit version detection broken
>
>
>
>
> Date: 
>
> Tue, 27 Oct 2020 15:36:50 -0600
>
>
>
>
>     The patch is 
> https://src.fedoraproject.org/fork/churchyard/rpms/automake/raw/f8af40fe1fa92a3ea0a1520a9d5f0797d0019f0f/f/automake-1.16.2-python-version-multiple-digits.patch
>
> Thanks, I pushed it with some minor additional documentation updates.
>
>     python3.10 -c 'import sys; print("%u.%u" % sys.version_info[:2])'
>
> I also changed the invocation in python.m4 to be this (what you put in
> t/python-vars.sh), instead of the sys.stdout.write('%d.%d') which you
> had (following what was there before). Seemed better to have the two
> invocations be exactly the same. At least, I couldn't discern any reason
> why not, or any difference in the result, barring version numbers too
> big to fit in signed integers :). --thanks, karl.
>
>
> --- End Message ---