Bruno Haible <br...@clisp.org> writes: > The status: It's about 2/3 complete. 4 months of work have gone into it, > and 2 months of work still remaining. (That's my estimation, based on > two weeks of work that I put in, in 2022.) > 65% of the .py code has been verified to be in sync with the bash code; > 35% still to go. And then, the changes from the gnulib-tool.py.TODO list
I see. I had it open and compared some of it to the shell script and it wasn't too hard to follow. Maybe I could help hack away at some of in my free time. I assume the best way to test it would be to create a small test directory with a few modules? I think all of the header file replacements would break the build so whichever ones avoid using those.
