Use quickstart config that was provided above.If you need get more information about the issue with the plugin: jedi selector as displayed in the following example.īy default, detailed (debug) loggin turned off and you would not see any messages in ST console, only exceptions. To specify rules which apply to Jedi tooltips only, use. To modify the style please follow mdpopups' styling guide.īasically a Packages/User/mdpopups.css is required to define your own style. If available mdpopups is used to display the docstring tooltips. these colors are actually scopes that were added to Sublime Text around build 3148 these scopes aren't documented, but the BracketHighlighter plugin has an excellent explanation here.other available options are "region.redish", "region.orangish", "region.yellowish", "eenish", "region.bluish", "region.purplish", "region.pinkish", "region.blackish".highlight_usages_color: color for highlighted symbols (default "region.bluish").highlight_usages_on_select: highlights usages of symbol in file when symbol is selected (default false).There are two settings related to finding usages: Find Related Names (“Find Usages”)įind function / method / variable / class usage, definition. If you want to travel back step by step the import path of the term then set this to False. If this setting is True (default behavior) you will travel directly to where the term was defined or declared. NOTE: You can configure the behavior of this command by changing the setting follow_imports. If you want auto-completion on dot, you can define a trigger in the Please set enable_in_sublime_repl: true in User/sublime_jedi.sublime-setting or in your project setting. If you want use autocompletion feature of SublimeJEDI in a repl, SublimeREPL integrationīy default completion for SublimeREPL turned off. Note that using placeholders and substitutions, like in regular Sublime Text Build System paths is not supported. When setting paths, Sublime Text Build System Variables and OS environment variables are automatically expanded. In other words, each item in "python_package_paths" list is a directory with extra packages and modules, not a direct path to package or module. NOTE: Please note that Python will goes through the directories from "python_package_paths" to search for modules and files. If you don't configure any of this then the default Python environment of your system will be used.
If you configure python_virtualen alone, the python_interpreter will be always where ever python_virtualen plus 'bin/python'. If you configure python_interpreter alone, the python_virtualen will be inferred so it will be 2 directories above python_interpreter. NOTE: You can configure python_interpreter and python_virtualen at the same time, no problem with that. "python_interpreter": "$project_path/././virtual/bin/python", "python_virtualenv": "$project_path/././virtual/",