On 05/26/2012 03:48 AM, Yagnesh Raghava Yakkala wrote:
> Hello David,
> Thanks for the reply.,
> David Engster<deng@...> writes:
>> Yagnesh Raghava Yakkala writes:
>>> I get to see these warnings when I start editing python files (with
>>> imports in them)
>>> WARNING: semantic-find-file-noselect called for
>>> /home/yagnesh/local/python2.7.2/lib/python2.7/gettext.py while in
>>> set-auto-mode for
>>> /home/yagnesh/local/python2.7.2/lib/python2.7/gettext.py. You should
>>> call the responsible function into `mode-local-init-hook'.
>>> I don't have any fancy configuration for cedet.
>>> I am not what they mean.? could you explain about them.?
>> This is an internal debug message. It is most likely a bug in the python
>> parser, but unfortunately I currently do not have time to look into this
>> further. Just ignore it for the time being.
> Another question (I consider it bug), why is semantic is opening all imports.?
> Suppose if I open a python file containing following line.
> --8<---------------cut here---------------start------------->8---
> import os
> --8<---------------cut here---------------end--------------->8---
> Semantic opens "os.py" file into a new buffer background instead of just
> parsing. is there a I can stop this?
Doing any kind of code analysis can be time consuming, so Semantic
opens and parses your includes in idle time in preparation of doing some
code analysis. It can't parse the file unless it opens it, so it will
open the file for parsing.
If it leaves it open when it is done, that would be a bug, though I
am not that familiar with the python specific bits. Is that what you
mean, or are you just seeing the file access?