From: Keshav U. <uk...@no...> - 2007-07-10 12:01:16
|
Hi i am working on this bug :- [ 837308 ] Importing bug i am having some issues associated with this :- 1). When ever some particular module is not find they will store it in = module list with its <name as key , Py.None as value> so when ever = again we import this module in future it will check form sys.module list = and return the result which is Py.None if i am not wrong it is done for efficiency purpose so that each time it = need not to search form the base path directly it will check in module = list and give the result directly . i have debug the flow and observed if some particular module is not found = we need not to store it in Module list or sys.module so that if that = module is created then next time it should search it from the base paths . 2). For solving this bug i am thinking for two approaches : a. Do not store< Module name and value Py.None >if that particular = module is not found in module list simply let it search form the base = path b. or if we are storing these values in to module list then if it = matches value Py.none then again search for the module form the base = (but it is not at all useful any how we will do it even though if we will = not wright it in to module list ) =20 please help me out in this case.=20 keshav upadhyaya |