or we can even leave decision to users: if they want to use
pygnulib, they can get it from pygnulib repo
That sounds to me like a very sensible way to go, at present.
I'm also fine with having pygnulib inside gnulib, if (other) people want
that. I just got worried that all of gnulib was
Hi Karl,
that's why I've called it "proposal". :-) Critics are really accepted,
since our project is mature enough to not admit such changes without
discussions.
I've thought about the future replacement since it was the goal of
Google Summer of Code (to reimplement gnulib-tool in Python), but I
Hi Dimitry (and all),
I don't like to be so negative, but ... I was not aware of any general
agreement on replacing the current gnulib world with a Python-based
world.
Note that gnulib-tool now will be the name for the gnulib-tool.py.
It seems to me that gnulib will become completely unusabl
