rope_py3k / rope / base /

# The default ````

def set_prefs(prefs):
    """This function is called before the project is opened"""

    # Specify which files and folders to ignore in the project.
    # Changes to ignored resources are not added to the history and
    # VCSs.  Also they are not shown in "Find File" dialog.
    prefs['ignored_resources'] = ['*.pyc', '*~', '.ropeproject', '.svn', '.hg']

    # Custom source folders:  By default rope searches the project
    # for finding source folders (folders that should be searched
    # for finding modules).  You can add paths to that list.  Note
    # that rope guesses project source folders correctly most of the
    # time; use this if you have any problems.
    # The folders should be relative to project root and use '/' for
    # separating folders regardless of the platform rope is running on.
    # 'src/my_source_folder' for instance.
    #prefs.add('source_folders', 'src')

    # You can extend python path:
    #prefs.add('python_path', '~/python/')

    # This option tells rope how to hold and save object information.
    # Possible values are:
    # * 'memory': It holds all information in
    #   memory.  So it is the fastest and the least memory efficient.
    #   Its biggest problem is that the data is not saved and
    #   the information is lost when you open a project in future.
    #   You probably never want to use this (it is used in unit
    #   tests), but if you decide not to have rope folder (see ~/.rope
    #   file) this db is used.
    # * 'persisted_memory': Exactly like 'memory' but the information is
    #   saved for future sessions.  The problem with this approach is
    #   that it might take lots of memory (this is not an issue for
    #   small to medium-sized projects).
    # * 'shelve': It stores data in `shelve` files.  This solves
    #   both the memory efficiency and the persistency problems.  But
    #   `shelve` is known to cause misterious problems in rare
    #   conditions.
    # * 'sqlite': It uses `sqlite3` module which is available in
    #   Python distributions starting from ``2.5``.  It is like
    #   'shelve' but probably more reliable.  But it is much less CPU
    #   efficient.
    # The choice of the objectdb might be hard.  I prefer
    # 'persisted_memory' and think it is the best.  For large
    # projects I prefer 'shelve'.  If you encounter mysterious
    # problems when using 'shelve' use the slower 'sqlite'.
    prefs['objectdb_type'] = 'persisted_memory'

    # Shows whether to save history across sessions.  Defaults to
    # `False`.
    prefs['save_history'] = True
    prefs['max_history_items'] = 100

    # If `False` when running modules or unit tests "Dynamic Object
    # Inference" is turned off.  This makes them much faster.  The
    # default is `True`.
    prefs['perform_doi'] = True

    # Rope can test the validity of its object DB when running.  You
    # can turn this feature off by using `False`.  Defaults to
    # `True`.
    prefs['validate_objectdb'] = True

    # If `True`, rope will analyze each module when it is saved.
    prefs['automatic_soi'] = True

    # Set the number spaces used for indenting.  According to
    # :PEP:`8`, it is best to use 4 spaces.  Since most of rope's
    # unit-tests use 4 spaces it is more reliable, too.
    prefs['indent_size'] = 4

    # If `True` modules with syntax errors are considered to be empty.
    # The default value is `False`; When `False` syntax errors raise
    # `rope.base.exceptions.ModuleSyntaxError` exception.
    prefs['ignore_syntax_errors'] = False

def project_opened(project):
    """This function is called after the project is opened"""
    # Do whatever you like here!
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.