Re: gnulib-tool.py: Don't fail when given a bad module name.

2024-04-21 Thread Collin Funk
Hi Bruno, On 4/21/24 4:37 AM, Bruno Haible wrote: > The former makes an implicit statement that the function is searching > for the file. The latter does not; it does not say or hint to as what > function internally does. Thus it is better to use the latter wording. Agreed, thanks for the change

Re: gnulib-tool.py: Don't fail when given a bad module name.

2024-04-21 Thread Bruno Haible
Hi Collin, > When using --create-testdir with a bad module name: > > $ gnulib-tool.py --create-testdir --dir aaa bad-module-name > gnulib-tool: warning: module bad-module-name doesn't exist > Traceback (most recent call last): > File "/home/collin/.local/src/gnulib/.gnulib-tool.py", line 30, in

gnulib-tool.py: Don't fail when given a bad module name.

2024-04-20 Thread Collin Funk
le objects before using them. I also documented the meaning of a None return in GLModuleSystem.find() since this problem occurred in GLImport previously. CollinFrom f9ff066e21adcd12de167ceea5a4c64a1f012a6b Mon Sep 17 00:00:00 2001 From: Collin Funk Date: Sat, 20 Apr 2024 20:29:44 -0700 Subject