11 Oct
2009
11 Oct
'09
10:48 a.m.
2009/10/11 ~suv <suv-sf@...58...>:
Or could this be handled entirely by the configure and packaging scripts, which then create an updated 'README.python' document included in the 'share/extensions'?
That's definitely not a good idea because globally you'd get thousands of versions of this README file, each one listing different versions, which would create no end of confusion. There's already some dependency checking functionality in the module system that lets you specify that some extension requires an external executable, and if the dependencies are not met the extension is disabled at runtime. I think we should extend that to allow INX files to specify Python dependencies.
Regards, Krzysztof