On 28 août 19:06, François Vanderkelen wrote: > Hi experts, Hi François, > I have another issue which seems to be related to namespaces but happening > only inside virtualenv. > > Whenever I am running pylint on a namespaced module calling dependencies > inside another module within the same namespace (or a parent one), I get an > unable to import "module" error. > > I missed a command and installed all my packages in my global environement > by mistake and ran the same pylint, everything was running smoothly (went > from -14,14 to 8.46 for a single file). > > I tried to change the vitualen pylint version to match the one installed > globally without success. Looks like the pylint inside my virtualenv is not > running on the correct path. > > I will continue digging and try to provide you with more details (and > files) but I was wondering if this was a known issue or just a > configuration thing ?
we've been suspecting such problems for a while but we're still missing some concret information about this (and I'm personnaly not much a user of virtual env and namesace pacckage splitted across various directories). So it would be valuable to add a new issue with all the information you get about the subject. Thanks! -- Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (05.62.17.16.42) 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 _______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
