On Tue, Mar 24, 2015 at 4:13 PM, Andreas Pakulat
wrote:
> On 2015-03-24 18:48, Fabio Zadrozny wrote:
>
>> Hi Andreas,
>>
>> You're right in both cases:
>>
>> 1. Duplicate module names under the same project are not supported -- I
>> do have plans to improve on that to support namespace-based pack
On 2015-03-24 18:48, Fabio Zadrozny wrote:
> Hi Andreas,
>
> You're right in both cases:
>
> 1. Duplicate module names under the same project are not supported -- I do
> have plans to improve on that to support namespace-based packages
> (I actually dislike those and find them a hack in Python,
Hi Andreas,
You're right in both cases:
1. Duplicate module names under the same project are not supported -- I do
have plans to improve on that to support namespace-based packages (I
actually dislike those and find them a hack in Python, but PyDev should
probably support that -- the issue here i
Hi Fabio,
thanks for the hint. I think the issue is that in my example both source
folders use the same module name, that is my project referencing the shared
module looks like this:
user (not a source folder)
- test1 (source folder)
| - test.py
|
- test2 (source folder)
- test.
Hi Andreas,
I recently changed some things in that area... (so, make sure you have the
latest development branch before starting to check it there to avoid
conflicts) the place which checks the modules we want to look for tokens is:
com.python.pydev.analysis.additionalinfo.AbstractAdditionalDepen
