Hi, On 10 janvier 13:00, Jürgen Hermann wrote: > [email protected]: " Making pylint able to understand the python > import machinery and its > extensions (eg zip, eggs file & co) *without actually import things* > is definitly a mess. We'll have to do something as some point since > it is higly desirable, though we don't use that features at Logilab > so other things usually take priority other it. " > > Hi, how about isolating pseudo-import machinery in pylint into a single > interface (class) and make the implementation to be used configurable in > pylint.rc? I.e. something like "importer = pylint.importing:DefaultImporter". > This would allow easy 3rd party experimentation outside of the core code > (until a stable alternative version can be contributed back), and also has no > impact on people not needing such features.
I would be fine with such a solution. -- Sylvain Thénault LOGILAB, Paris (France) Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services CubicWeb, the semantic web framework: http://www.cubicweb.org _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
