Fri, 09 Jun 2000 17:49:10 +0200
Moshe Zadka wrote:
> Great work, but one small nit: you use try/except in two places there.
> The first just catch ValueError's, and the second can catch
> (IOError, os.error), though I'm not sure what for: if there are problems
> reading config.h, it seems we're in a pretty mess: pretending everything
> is alright won't make it so <wink>
If there are problems reading config.h then probably the user deleted it
it to another place. In this case the user has the whole responibility
for his doing. ( for example he could specify a path to search
-I my/new/python/include/directory )
If it was deleted accidently or something similar, then
we should let the compiler complain about this missing
I think we only should print warnings if we are sure that
we are right. Without this file we cannot be sure
that something is wrong.