plone.recipe.sublimetext 1.0.1

SublimeText configuration for buildout-based Python projects

Contents

• Introduction

• Installation

  • Available Options

• Links

• Known Issues

• Example Usage

• Contributors

• Changelog

  • 1.0.1 (2017-05-16)

  • 1.0.0 (2017-05-15)

Introduction

plone.recipe.sublimetext is for ST3 lover who wants python IDE like features while developing python Buildout based project. This tool will help you to create per project basis sublimetext settings with appropriate paths location assignment. Currently plone.recipe.sublimetext comes with supporting settings for Jedi, Sublimelinter, Sublimelinter-Flake8, Sublimelinter-Pylint. A general question may arise that why we will use this tool, weather we can create ST3 project settings easily (we have better knowledge over ST3 configuration)? Well i completely agree with you, but if you want to get benefited from Jedi’s python autocompletion feature (basically I am lover of autocompletion), you have to add all eggs links for Jedi’s paths settings and it is hard to manage eggs links manually if the size of project is big (think about any Plone powered project), beside Sublimelinter-Pylint also need list of paths to be added to sys.path to find modules.

Installation

Install plone.recipe.sublimetext is simple enough, just a section for sublimetext to your buildout. Before using plone.recipe.sublimetext make sure Jedi, Sublimelinter, Sublimelinter-Flake8 and/or Sublimelinter-Pylint plugins are already installed at your ST3. You could follow full [instruction here] if not your ST3 setup yet.

Example Buildout::

[buildout] parts += sublimetext

[sublimetext] recipe = plone.recipe.sublimetext eggs = ${buildout:eggs} jedi-enabled = True sublimelinter-enabled = True sublimelinter-pylint-enabled = True

Available Options

eggs

Required: Yes

Default: None

Your project’s list of eggs, that going to be added in path location for Jedi and Sublimelinter-Pylint.

overwrite

Required: No

Default: False

This option indicates wheather existing settings should be cleaned first or just updating changes. This situation may happen, you did create settings file manually with other configuration (those are not managed by plone.recipe.sublimetext) and you want keep those settings.

python-executable

Required: No

Default: plone.recipe.sublimetext will find current python executable path.

The python executable path for current project, if you are using virtual environment then should be that python path. FYI: ${home} and ${project} variable should work.

project-name

Required: No

Default: if you have a existing ST3 project file(settings file) in project/buildout root directory, plone.recipe.sublimetext will choose it as project-name, other than project/buildout directory name will become as project-name

The settings file name (no need to add suffix .sublime-project)

jedi-enabled

Required: No

Default: False

This option related to enable/disable Sublime Jedi

sublimelinter-enabled

Required: No

Default: False

Weather Sublimelinter you want to use this feature or not.

sublimelinter-pylint-enabled

Required: No

Default: False

Sublimelinter-Pylint if you want to use or not; sublimelinter-enabled option will be respected, means if parent option is set as disabled but you enable this option will not work.

sublimelinter-flake8-enabled

Required: No

Default: False

wheather you want to use Sublimelinter-Flake8 or not. Like sublimelinter-pylint-enabled parent option will be respected.

sublimelinter-flake8-executable

Required: No

Default: False

Project specific Flake8 executable path, this will gives you lots flexibility over using global Flake8 executable, because each project might have separate Python version.

ignore-develop

Required: No

Default: False

If you don’t want development eggs, should go for autocompletion.

ignores

Required: No

Default: “”

If you want specific eggs should not go for autocompletion.

packages

Required: No

Default: “”

Location of some python scripts or non standard modules (don’t have setup file), you want to be in system path.

Links

Code repository:

https://github.com/nazrulworld/plone.recipe.sublimetext

Continuous Integration:

https://travis-ci.org/nazrulworld/plone.recipe.sublimetext

Issue Tracker:

https://github.com/nazrulworld/plone.recipe.sublimetext/issues

Known Issues

• Sublimelinter-Flake8 might stop working if flake8-plone-api is installed as until 1.2 version, flake8-plone-api don’t support SublimeText (linting), see pull request here . That means upcoming version will support hopefully. It could happen, either you are using global or virtualenv flake8. You can see error in ST3 console:

  flake8_plone_api-1.2-py2.7.egg/flake8_plone_api.py", line 16, in run
  with open(self.filename) as f:
  IOError: [Errno 2] No such file or directory: 'stdin'

Example Usage

Minimal buildout::

>>> write('buildout.cfg',
... """
... [buildout]
... develop = .
... eggs =
...     zc.buildout
... parts = sublimetext
...
... [sublimetext]
... recipe = plone.recipe.sublimetext
... project-name = plone-recipe-sublime
... eggs = ${buildout:eggs}
... jedi-enabled = True
... """)
>>> system(buildout + ' -c buildout.cfg')
>>> import os
>>> os.path.exists('plone-recipe-sublime.sublime-project')
True

Standard buildout:

>>> write('buildout.cfg',
... """
... [buildout]
... develop = .
... eggs =
...     zc.buildout
... parts = sublimetext
...
... [sublimetext]
... recipe = plone.recipe.sublimetext
... project-name = plone-recipe-sublime
... eggs = ${buildout:eggs}
... jedi-enabled = True
... sublimelinter-enabled = True
... sublimelinter-flake8-enabled = True
... sublimelinter-flake8-executable = ${buildout:directory}/bin/flake8
... """)
>>> system(buildout + ' -c buildout.cfg')
>>> import json
>>> settings = json.loads(read('plone-recipe-sublime.sublime-project'))
>>> 'flake8' in settings['Sublimelinter']['linters']
True

Muilti Linters and without project name:

>>> write('buildout.cfg',
... """
... [buildout]
... develop = .
... eggs =
...     zc.buildout
... parts = sublimetext
...
... [sublimetext]
... recipe = plone.recipe.sublimetext
... eggs = ${buildout:eggs}
... jedi-enabled = True
... sublimelinter-enabled = True
... sublimelinter-flake8-enabled = True
... sublimelinter-flake8-executable = ${buildout:directory}/bin/flake8
... sublimelinter-pylint-enabled = True
... """)
>>> system(buildout + ' -c buildout.cfg')

(project filename shoul be plone-recipe-sublime.sublime-project as previously generated):

>>> settings = json.loads(read('plone-recipe-sublime.sublime-project'))
>>> 'pylint' in settings['Sublimelinter']['linters']
True

Contributors

• Md Nazrul Islam<[e-mail]>, Original Author

Changelog

1.0.1 (2017-05-16)

Bugfixes:

• [#1] Required options for sublime text project file is missing

1.0.0 (2017-05-15)

• Initial release. [nazrulworld]