[Lxr-dev] [ lxr-Feature Requests-2808116 ] Handling of Python import

[SourceForge.net <no...@so...>]

Feature Requests item #2808116, was opened at 2009-06-17 19:06
Message generated for change (Comment added) made by hawaiian717
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2808116&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Language support
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: David (hawaiian717)
Assigned to: Nobody/Anonymous (nobody)
Summary: Handling of Python import

Initial Comment:
It would be nice if Python import statements were handled similar to C #includes, where the file links to the included file.  It appears that currently, certain imported modules will link to a keyword search and others will be unlinked.

Syntax for the import statement can be found here: http://docs.python.org/reference/simple_stmts.html#the-import-statement

----------------------------------------------------------------------

>Comment By: David (hawaiian717)
Date: 2009-06-30 13:53

Message:
Sorry for the delay in responding, I had a few other things come up before
I could get back to this.

I've attached an HTML file with some sample output (I removed some of the
header info, but you should still get the idea). "time" is a standard
Python module, so I wouldn't necessarily expect LXR to be able to link to
it.  "version", "management", and "device" are all in the same directory as
the test file.  One thing to note is that the include statement doesn't
include the .py filename extension.

----------------------------------------------------------------------

Comment By: AdrianIssott (adrianissott)
Date: 2009-06-19 12:50

Message:
David, please could you provide some examples of when the import statements
aren't linking to the included file.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2808116&group_id=27350