Hi Tim, thank you for your kind words! As for merging into master, I tried to do it, but didn't succeed: git complains a lot on whitespaces and similar stuff. I suspect it may be caused by custom git hook. Bruno, Paul, could you help me with merging? I suppose that right now almost everything shall be merged, except for the files I've added recently:
pygnulib/error.py pygnulib/generator.py pygnulib/config.py pygnulib/filesystem.py These files represent the development branch; I'm trying to cleanup and mostly rewrite the API. Could you help me with merge, please? If necessary, I can try using some kind of tool which formats the code automatically. 6 сент. 2017 г. 7:42 ПП пользователь "Tim Rühsen" <tim.rueh...@gmx.de> написал: > On Dienstag, 5. September 2017 23:35:54 CEST Dmitry Selyutin wrote: > > Hi Tim, > > > > that's exactly what I've done today. I've just pushed some changes into > > repository; could you please try the latest version? > > I didn't have time to integrate --no-changelog support yet (it seems it > was > > either unimplemented before or appeared after project was completed). > > Thank you for trying the Python version; please let me know if it works > for > > you or if there are some other errors to be fixed. > > > > P.S. I've started cleaning the entire code base, also rewriting some slow > > paths, but there is a lot of work to be done; stay tuned. :-) > > Awesome, Dmitry ! \o/ > > Works like a charm on a quick test (will do some more testing the next > days). > > That's really *much* faster than before. > Now: > real 0m34,265s > user 0m31,524s > sys 0m2,279s > > Before: > real 1m20,295s > user 1m16,460s > sys 0m16,050s > > The bottleneck now is autoreconf followed by libtoolize :-) > > If you remove the gnulib-tool from branch 'pygnulib' and instead add a link > gnulib-tool -> gnulib-tool.py then one wouldn't have to edit ./bootstrap. > > I just can't say how much I appreciate your work ! > > Regards, Tim >
