On Thu, 2 Dec 1999, Michael Hudson wrote:
... class Acceptor: def __and__(self,rhs): return AndingAcceptor(self,rhs) def __or__(self,rhs): return OringAcceptor(self,rhs) def __neg__(self): return NotAcceptor(self)
Sorry... but this is just silly. This is taking a simple problem of file selection and throwing a mess of procedural code at the thing. How is this *any* better than a simple list of files or file patterns?
The distutils package must be *very* simple to gain acceptance. Requiring people to write code, understand how to subclass CCompiler, or provide a bazillion params to a setup() function is just not going to help.
The developer ought to be able to say "ship *.py and foomodule.c". distutils would package that into a target directory and see that foomodule.c is compiled to a module on the target system. Done.
Grain of salt time: until I step up and provide code to make distutils as simple as I hope it would be, my comments should be viewed as "peanut gallery" comments.