Menu
▾
▴
[Lxr-dev] [ lxr-Feature Requests-2808116 ] Handling of Python import
|
From: SourceForge.net <no...@so...> - 2011-03-31 17:30:40
|
Feature Requests item #2808116, was opened at 2009-06-18 04:06 Message generated for change (Comment added) made by ajlittoz 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: Andre-Littoz (ajlittoz) 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: Andre-Littoz (ajlittoz) Date: 2011-03-31 19:30 Message: Reopened manually after automatic close. To be put on "todo" list for a coming release ---------------------------------------------------------------------- Comment By: SourceForge Robot (sf-robot) Date: 2011-03-31 17:20 Message: This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-03-17 15:29 Message: I have added a generic processing. Read feature request "cope with language-specific syntax for include files" to see if that suits your needs. To test, either extract from CVS or wait for the 0.9.9 release, due very soon. Please give feed back. ---------------------------------------------------------------------- Comment By: David (hawaiian717) Date: 2009-06-30 22: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 21: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 |
