distutils-r1 displays a QA warning if you define the python_*_all functions without calling the distutils-r1_python_*_all equivalent. There may in face be some circumstances in which this is done intentionally by the developer. There is currently no officially supported way to disable the warnings. As well, some developers have expressed skepticism that displaying a QA message by default for a problem that might not actually be a problem is a good idea. One possible alternative would be to make this an opt-in warning based on a magic var in the environment. This would be similar to the JAVA_PKG_STRICT variable as used in the java eclasses (see java-utils-2.eclass). Thoughts, comments, suggestions?
I can't say I know the perfect solution, but I am one of said developers who doesn't like a QA warning for things which are intentional. We have so many QA warnings just in a stock stage1-3 build run already, adding things that MIGHT be a QA issue just seems completely unacceptable to me. If there is a way for a developer to override it like "IT_ISNT_A_QA_VIOLATION=1" or something stupid like that it's okay with me, but that would need to be documented in the QA warning so devs actually use it. Of course, so many of the devs appear to not use the dev profile anyway, it's hard to say if anyone but Patrick and I actually see these QA warnings. Okay, spanky sees them too....
And where is calling the default unintentional?
