Using cscope to browse Python code with VIM?

问题:

Has anyone managed successfully using cscope with Python code? I have VIM 7.2 and the latest version of cscope installed, however it doesn't get my code's tags correctly (always off by a couple of lines). I tried the pycscope script but its output isn't supported by the modern version of cscope.

Any ideas? Or an alternative for browsing Python code with VIM? (I'm specifically interested in the extra features cscope offers beyond the simple tags of ctags)

回答1:

EDIT: I'm going to run through the process step by step:

Preparing the sources:

exhuberant ctags, has an option: -x

   Alternatively,  ctags  can generate a cross reference file which lists,
   in human readable form, information about the  various  source  objects
   found in a set of language files.

This is the key to the problem:

 ctags -x $(ls **/*.py);                  # replace with find if no zsh

will give you your database of source objects in a known, format, described under

 man ctags;                               # make sure you use exuberant ctags!

Gnu Global is not limited to only the "out of the box" type of files. Any regular file format will serve.

Also, you can use gtags-cscope, which comes with global as mentioned in section 3.7 of the manual, for a possible shortcut using gtags. You'll end up with an input of a ctags tabular file which Global/gtags can parse to get your objects, or you can use the source for pycscope together with your ctags file of known format to get an input for the vim cscope commands in

if_cscope.txt.

Either way it's quite doable.

Perhaps you'd prefer idutils?

Definintely possible since

z3c.recipe.tags

on pypi makes use of both ctags and idutils to create tag files for a buildout, which is a method I shall investigate in short while.

Of course, you could always use the greputils script below, it has support for idutils , we know idutils works with python, and if that fails, there is also something called vimentry from this year that also uses python, idutils and vim.

Reference links (not complete list):

• gtags vimscript, uses Gnu global. updated 2008
• greputils vimscript, contains support for the *id idutils, 2005
• lid vimscript, Ancient, but this guy is pretty good, his tag and buffer howtos are amazing 2002
• An updated version of pyscope, 2010

Hopefully this helps you with your problem, I certainly helped me. I would have been quite sad tonight with a maggoty pycscope.

回答2:

This seems to work for me:

Change to the top directory of your python code. Create a file called cscope.files:

find . -name '*.py' > cscope.files

cscope -R

You may need to perform a cscope -b first if the cross references don't get built properly.

回答3:

1. From a correspondence with the maintainer of cscope, this tool isn't designed to work with Python, and there are no plans to implement that compatibility. Whatever works now, apparently works by mistake, and there is no promise whatsoever that it will keep working.
2. It appears I've been using an out-of-date version of pycscope. The latest version 0.3 is supported by the cscope DB. The author of pycscope told me that he figured out the output format for the cscope DB from reading the source code of cscope. That format isn't documented, on purpose, but nevertheless it currently works with pycsope 0.3, which is the solution I'll be using.

---

I'm going to accept this answer since unfortunately no other answer provided help even after bounty was declared. No answers are upvoted, so I honestly have no idea where the bounty will go.

回答4:

There is a wonderful Python-mode-klen plugin. If you have it and rope (python refactoring library) installed, then going to the definition of a particular term is as simple as <C-c>g or <C-c>rag (first is filetype mapping, second is a global one). There are much more useful features, some useless for me. All of them are disableable. Features from list of questions found at cscope-intro:

1. Where is this symbol used? <C-c>f. Rather confusing though, as results in quickfix list do show - instead of the actual lines (though they point to the correct location). Maybe it will be fixed.
2. Where is it defined?, What is this global symbol's definition?, Where is this function in the source files? <C-c>g
3. What is <...> global symbol's definition? <C-c>raj

Not very much, but I am not too experienced user of ropevim.

回答5:

I got the same question you got, after browsing the internet, I found a way to fix this:

create a python script: cscope_scan.py

import os

codeRootDir = os.getcwd()

__revision__ = '0.1'
__author__ = 'lxd'

FILE_TYPE_LIST= ['py']

if __name__ == '__main__':
    import os
    f = open('cscope.files','w')
    for root,dirs,files in os.walk(codeRootDir):
        for file in files:
            for file_type in FILE_TYPE_LIST:
                if file.split('.')[-1] == file_type:
                    f.write('%s\n' %os.path.join(root,file))
    f.close()
    cmd = 'cscope -bk'
    os.system(cmd)

excute this script under you code's root folder, this will generate the cscope.files and then excute cscope -b I don't know what happens to my computer, the last two lines aren't working well, but I think manually type a cscope -bk is acceptable:)