[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: pygnulib: Portability fixes
From: |
Mathieu Lirzin |
Subject: |
Re: pygnulib: Portability fixes |
Date: |
Mon, 25 Sep 2017 23:12:23 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) |
Dmitry Selyutin <address@hidden> writes:
> Wow, that's a surprise. Sure, we must support all Python 3 versions. Thank
> you, I've applied it. Please check if everything is OK, I'm not a Git guru:
> since parser and config were a bit ahead, I did the same as you did,
> committed, then exported a patch via $(git format-patch HEAD~1), then put the
> original author and text (only lowercasing a one letter). Please let me know
> if you know a better way, I don't use Git intensively.
The usual process depends on your email client. Basically you have to
save the attached patch to a file in Gnulib Git repository. Then from
that directory the command 'git am 0001-blablaba.patch' will apply that
patch.
If your are comfortable with Emacs I recommend using Magit which is a
nice UI that can help becoming a "Git guru".
>> I suppose that in the context of Gnulib it is important to be compatible
> with Python 2?
> It is not. :-) Even in 2012 when I started the original work, Bruno wanted to
> stick to Python 3, but I still did everything in a crazy mix of both
> versions.
> Now the support for Python 2 seems to be redundant; hopefully most Unices
> either have Python 3 by default or at least have it in repositories, ports,
> etc. The cost of maintaining the script for both versions is really huge, I
> really think that Bruno was right from the very beginning.
That's fine with me. :-)
Thanks.
--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37