On Mon, Jan 22, 2001 at 11:52:17AM +0100, M.-A. Lemburg wrote: > "M.-A. Lemburg" wrote: > > I think the policy in setup.py should be to output warnings, > > but continue building the rest of the Python modules. > I haven't heard anything from the powers to be... what should the > policy be for auto-detected and -configured modules ? I think Andrew is still working on a way to disable modules from the command line somehow. (I think moving setup.py to setup.py.in, and using autoconf --options would be easiest on both developer and user, but that's just me.) I also think everyone agrees with you that a module that can't be build shouldn't stop the entire process in the final release (and possibly the betas) but that it's definately a good way to debug setup.py in the alphas. -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4