Thread: [Lxr-dev] [ lxr-Feature Requests-2808116 ] Handling of Python import
Brought to you by:
ajlittoz
From: SourceForge.net <no...@so...> - 2009-06-18 02:06:59
|
Feature Requests item #2808116, was opened at 2009-06-17 19:06 Message generated for change (Tracker Item Submitted) 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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2808116&group_id=27350 |
From: SourceForge.net <no...@so...> - 2009-06-19 19:50:31
|
Feature Requests item #2808116, was opened at 2009-06-18 03:06 Message generated for change (Comment added) made by adrianissott 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: AdrianIssott (adrianissott) Date: 2009-06-19 20: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 |
From: SourceForge.net <no...@so...> - 2009-06-30 20:53:52
|
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 |
From: SourceForge.net <no...@so...> - 2011-03-17 14:29:44
|
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: Pending 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-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 |
From: SourceForge.net <no...@so...> - 2011-03-31 15:20:06
|
Feature Requests item #2808116, was opened at 2009-06-18 02:06 Message generated for change (Settings changed) made by sf-robot 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: Closed 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: SourceForge Robot (sf-robot) Date: 2011-03-31 15: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 14: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 20: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 19: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 |
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 |
From: SourceForge.net <no...@so...> - 2011-04-11 23:43:36
|
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: 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: David (hawaiian717) Date: 2011-04-11 16:43 Message: Just gave 0.9.9 a try; got an error when I tried to update the index: Sequence (?|...) not recognized in regex; marked by <-- HERE in m/^ # reminder: no initial space in the grammar ([\w\#]\s*[\w]*) # reserved keyword for include construct (\s+) # space (?| <-- HERE (")(.+?)(") # C syntax | (\0<)(.+?)(\0>) # C alternate syntax | ()([\w:]+)(\b) # Perl and others ) / at lib/LXR/Lang.pm line 88. Compilation failed in require at lib/LXR/Common.pm line 50. Compilation failed in require at lib/LXR/Index.pm line 23. BEGIN failed--compilation aborted at lib/LXR/Index.pm line 23. Compilation failed in require at /var/www/html/lxr/genxref line 26. BEGIN failed--compilation aborted at /var/www/html/lxr/genxref line 26. ---------------------------------------------------------------------- Comment By: David (hawaiian717) Date: 2011-04-01 18:39 Message: Testing the patch is also on my todo list. Hopefully I'll have a chance to test this next week. ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-03-31 10: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 08: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 07: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 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 |
From: SourceForge.net <no...@so...> - 2011-04-12 19:48:35
|
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-04-12 21:48 Message: This incompatibility has been discovered last week (2011-04-05) by Dr. Martin Wilck. A new feature has been added in Perl after version 5.8.8 (which is probably yours). Mine is 5.12.3 and contains this feature. Your choice is: 1/ upgrade Perl, or 2/ read Help forum, topic Help on non-regression checks after modifications; towards the end, you'll find a dirty patch to get around this incompatibility. Please send feedback. If you think it worth, I can try to use alternate syntax since this part of the code is not fully satisfactory. Regards ---------------------------------------------------------------------- Comment By: David (hawaiian717) Date: 2011-04-12 01:43 Message: Just gave 0.9.9 a try; got an error when I tried to update the index: Sequence (?|...) not recognized in regex; marked by <-- HERE in m/^ # reminder: no initial space in the grammar ([\w\#]\s*[\w]*) # reserved keyword for include construct (\s+) # space (?| <-- HERE (")(.+?)(") # C syntax | (\0<)(.+?)(\0>) # C alternate syntax | ()([\w:]+)(\b) # Perl and others ) / at lib/LXR/Lang.pm line 88. Compilation failed in require at lib/LXR/Common.pm line 50. Compilation failed in require at lib/LXR/Index.pm line 23. BEGIN failed--compilation aborted at lib/LXR/Index.pm line 23. Compilation failed in require at /var/www/html/lxr/genxref line 26. BEGIN failed--compilation aborted at /var/www/html/lxr/genxref line 26. ---------------------------------------------------------------------- Comment By: David (hawaiian717) Date: 2011-04-02 03:39 Message: Testing the patch is also on my todo list. Hopefully I'll have a chance to test this next week. ---------------------------------------------------------------------- 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 |
From: SourceForge.net <no...@so...> - 2012-08-03 17:56:43
|
Feature Requests item #2808116, was opened at 2009-06-17 19: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: Closed 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: 2012-08-03 10:56 Message: Ships with release 1.0 ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-04-12 12:48 Message: This incompatibility has been discovered last week (2011-04-05) by Dr. Martin Wilck. A new feature has been added in Perl after version 5.8.8 (which is probably yours). Mine is 5.12.3 and contains this feature. Your choice is: 1/ upgrade Perl, or 2/ read Help forum, topic Help on non-regression checks after modifications; towards the end, you'll find a dirty patch to get around this incompatibility. Please send feedback. If you think it worth, I can try to use alternate syntax since this part of the code is not fully satisfactory. Regards ---------------------------------------------------------------------- Comment By: David (hawaiian717) Date: 2011-04-11 16:43 Message: Just gave 0.9.9 a try; got an error when I tried to update the index: Sequence (?|...) not recognized in regex; marked by <-- HERE in m/^ # reminder: no initial space in the grammar ([\w\#]\s*[\w]*) # reserved keyword for include construct (\s+) # space (?| <-- HERE (")(.+?)(") # C syntax | (\0<)(.+?)(\0>) # C alternate syntax | ()([\w:]+)(\b) # Perl and others ) / at lib/LXR/Lang.pm line 88. Compilation failed in require at lib/LXR/Common.pm line 50. Compilation failed in require at lib/LXR/Index.pm line 23. BEGIN failed--compilation aborted at lib/LXR/Index.pm line 23. Compilation failed in require at /var/www/html/lxr/genxref line 26. BEGIN failed--compilation aborted at /var/www/html/lxr/genxref line 26. ---------------------------------------------------------------------- Comment By: David (hawaiian717) Date: 2011-04-01 18:39 Message: Testing the patch is also on my todo list. Hopefully I'll have a chance to test this next week. ---------------------------------------------------------------------- Comment By: Andre-Littoz (ajlittoz) Date: 2011-03-31 10: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 08: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 07: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 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 |