🍴 ST3 only: A rewrite of SublimeRope for ST3, uses the Rope library to add python completions and refactoring to ST3
Python JavaScript
Pull request Compare This branch is 8 commits behind JulianEberius:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
gutter_mark_themes
messages
pyflakes
server
.gitignore
.no-sublime-package
Context.sublime-menu
Default (Linux).sublime-mousemap
Default (OSX).sublime-mousemap
Default (Windows).sublime-mousemap
LICENSE.txt
Main.sublime-menu
README.markdown
SublimePython.sublime-commands
SublimePython.sublime-settings
__init__.py
messages.json
pep8.py
sublime_python.py
sublime_python_colors.py
sublime_python_commands.py
sublime_python_errors.py
sublime_python_linting.py
sublime_python_refactorings.py

README.markdown

SublimePythonIDE

This plugin adds Python completions and some IDE-like functions to Sublime Text 3, through the use of the Rope library. It is a complete rewrite of SublimeRope for ST2. It should be a lot faster and easier to use than SublimeRope was.

In contrast to SublimeRope, it does use the built in Python only for UI-related functions, the completions and refactorings are calculated using the exact same python interpreter you use for your project (e.g. the one in your virtualenv). This eliminates a lot of small and big problems that SublimeRope had, e.g., not recognizing dict comprehensions because Python2.6 is used in ST2, or not recognizing some of your libraries because you did not configure all the paths etc.. Everything your projects interpreter sees, should be visible to SublimePython -> easier configuration.

I also added a lot caching throughout the underlying Rope library which improved completion performance by several orders of magnitude. I hope no functionality breaks because of this ;-)

Configuration

Python location

The only necessary configuration is pointing SublimePythonIDE at the correct Python interpreter to use. There are four mechanisms for detecting Python that are used in the following order:

  • Checking the option "python_interpreter" in project settings (see below)
  • Auto-detecting a virtual environment (in "venv" or $WORKON_HOME for virtualenvwrapper)
  • Reading a #! (shebang) line in the active file
  • Auto-detecting the system Python from $PATH

The option "python_interpreter" can be set in the projects settings (Project->Edit Project). Example:

{
    "folders": [
        {
           "path": "XYZ"
        },
        {
            "path": "ABC"
        }
    ],
    "settings": {
        "python_interpreter": "/path/to/some/virtualenv/bin/python"
    }
}

This is also the way to select a virtualenv (point it to the interpreter in the venv) and thus get the completions/definitions for you project working.

To suppress the "Could not find Python dialog", save the following setting:

"suppress_python_not_found_error": false,

Imports location

SublimePythonIDE will also look up imports relative to the project root directory (the top directory of your project).

In cases where the project directory is outside of your root python module, you may optionally set a custom source root directory in the project settings:

{
    "folders": [
        {
           "path": "XYZ"
        },
    ],
    "settings": {
        "src_root": "XYZ/THE_ACTUAL_SRC"
        "python_interpreter": "/path/to/some/virtualenv/bin/python",
    }
}

See Packages/SublimePythonIDE/SublimePython.sublime-settings for other options. As with all ST packages, copy this file into your Packages/User folder and editing the copy there.

Copyright (C) 2013 Julian Eberius

License:

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Have a look at "LICENSE.txt" file for more information.

EXTERNAL LICENSES

This project uses code from other open source projects (Rope) which may include licenses of their own.