#568 Improper 'Unresolved Import' Annotation

1.3.8
closed-works-for-me
Editor (491)
7
2007-09-07
2007-09-06
MirgNave
No

The attached sample project illustrates this bug where an 'Unresolved Import' annotation is shown in the editor for the sampleModule.py file even though when run, the program has no import errors.

Discussion

  • MirgNave
    MirgNave
    2007-09-06

    Bug Demonstration

     
    Attachments
  • MirgNave
    MirgNave
    2007-09-06

    • priority: 5 --> 7
     
  • MirgNave
    MirgNave
    2007-09-06

    Logged In: YES
    user_id=1016895
    Originator: YES

    Shamelessly increasing priority while hoping my status as a pydev extensions site-license holder (swri.org) might entitle this bug to more attention.

     
  • Fabio Zadrozny
    Fabio Zadrozny
    2007-09-07

    • status: open --> closed-works-for-me
     
  • Fabio Zadrozny
    Fabio Zadrozny
    2007-09-07

    Logged In: YES
    user_id=617340
    Originator: NO

    Actually, the source folders seem to be conflicting... that's why you have the error...

    In the example attached, only the project root (/bugCheck) should be configured as your source folder (and not /bugCheck/samplePackage and /bugCheck/sampleSource) -- basically, if you want to have some name in your namespace, the source folder should be one level before that -- basically mimicking your pythonpath configuration.

    Note that there's a bug in the pydev package explorer about the outline not being correct when the project root is also the source folder: http://sourceforge.net/tracker/index.php?func=detail&aid=1789127&group_id=85796&atid=577329, but everything else should work (and that bug is already in progress -- although I'm not sure if it'll be able to enter the next release).

    Cheers,

    Fabio