Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=6391820 By: fabioz
In Python that's really not the way to go. Packages should not have the same name... (Python just checks the 1st one that'll succeed in the import and won't go to other paths making a 'merge' of them as Java does). Also note that if what's not working is the actual run (as opposed to code-completion facilities), that's not really Pydev's fault, but Python itself -- and in this case it's not really a bug (it's the way Python works). The usual way to work in python is that each project has a root and your namespace starts there. E.g.: Django project starts with 'django', so, all your imports start with from django import XXX. If you have another project that's an extension to the django project, you'd start it with something different like 'djangoex' (with a different namespace instead of something as'django.ex' -- which is something that'd be OK in Java). Cheers, Fabio ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=293649 ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Pydev-users mailing list Pydev-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pydev-users