Krew, It seems that the issue of having dependencies of NoneType.None is rather common and can be difficult to track down from personal experience. I think we should consider adding code that throws an exception if NoneType.None is added via env operations like Append, AppendUnique, Prepend, etc.
For backwards compatibility reasons were someone wants NoneType.None, we could have both a global check disable and/or an optional parameter to disable checks. Any thoughts? V/R, William
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
