Richard Purdie 8bef99d3c8 bitbake: methodpool: Retire it, remove global method scope ... Having a global method scope confuses users and with the introduction of parallel parsing, its not even possible to correctly detect conflicting functions. Rather than try and fix that, its simpler to retire the global method scope and restrict functions to those locations they're defined within. This is more what users actually expect too. If we remove the global function scope, the need for methodpool is reduced to the point we may as well retire it. There is some small loss of caching of parsed functions but timing measurements so the impact to be neglibile in the overall parsing time. (Bitbake rev: 4d50690489ee8dc329a9b0c7bc4ceb29b71e95e9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2013-05-24 10:34:52 +01:00
..
BBHandler.py	bitbake: methodpool: Retire it, remove global method scope	2013-05-24 10:34:52 +01:00
ConfHandler.py	bitbake: lib: Clean up various file access syntax	2013-05-09 22:28:04 +01:00
__init__.py	3.0 prep	2010-07-02 15:41:37 +01:00