[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

pygnulib development process documentation (was: [PATCH] gnulib-tool.py:

From: Mathieu Lirzin
Subject: pygnulib development process documentation (was: [PATCH] gnulib-tool.py: Clean the imports)
Date: Mon, 25 Sep 2017 21:30:10 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)

Dmitry Selyutin <address@hidden> writes:

>> Sorry, I was unaware of that branch.  What about adding some information
>> about the gnulib-tool.py development process in a "README-hacking" file?
> Frankly I don't know what to write here yet. :-) I mean that there must be 
> something already to play with, but the whole thing is too half-baked to even 
> mention it on the master branch.

What would be insteresting to write is precising the status of
gnulib-tool.py in master branch (maintenance mode?) and telling that new
development should be done on the python branch.

Since people are commiting to pygnulib in both branch, without such
documentation it is hard to understand the development process, and what
should be done on which branch.

>> Since there is no "gnulib-tool.py" nor unit tests for the pygnulib
>> module in that branch how are you working on it? with the REPL?  Am I
>> overlooking something?
> I really do have a simple script which is going to become a new gnulib-
> tool.py. I've just committed it; it already can successfully parse the whole 
> bunch of command-line options (except for some corner cases) and recently I 
> could even teach it do do the same transitive closure the original script 
> does 
> upon modules import. :-) I've just committed it; please check the pygnulib.py 
> from the python branch.



Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

reply via email to

[Prev in Thread] Current Thread [Next in Thread]