Hi Collin, > GNU m4 gave the following error: > > bootstrap: running: gnulib/gnulib-tool.py --no-changelog --no-libtool > --symlink --update > Traceback (most recent call last): > File "/home/collin/.local/src/m4/gnulib/gnulib-tool.py", line 1171, in > <module> > main() > File "/home/collin/.local/src/m4/gnulib/gnulib-tool.py", line 886, in main > importer = classes.GLImport(config, mode) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/home/collin/.local/src/m4/gnulib/pygnulib/GLImport.py", line 243, in > __init__ > if self.checkInclTestCategory(TESTS['tests']) and self.config['conddeps']: > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > AttributeError: 'GLImport' object has no attribute 'checkInclTestCategory' > > I assume this was just caused by a small coding typo (if that is a > thing). This patch should fix it.
Thanks! Applied. > What is the status of the Python gnulib tool? I'm not sure how far > behind it is compared to the shell script but it seems like it would > be much faster. I would say more maintainable but I might just be bad > at writing shell scripts. :) Yes, it's the hope that it will be faster that is the main motivation behind the Python rewrite. 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 need to me implemented on the Python side. Then would come a phase of public testing... Bruno
