1 Your Development Environment
2 ============================
8 Just about anything which can edit plain text will work for writing Python code,
9 however, using a more powerful editor may make your life a bit easier.
15 Vim is a text editor which uses keyboard shortcuts for editing instead of menus
16 or icons. There exist a couple of plugins and settings for the VIM editor to
17 aid python development. If you only develop in Python, a good start is to set
18 the default settings for indentation and line-wrapping to values compliant with
19 `PEP 8 <http://www.python.org/dev/peps/pep-0008/>`_. In your home directory,
20 open a file called `.vimrc` and add the following lines: ::
29 With these settings, newlines are inserted after 79 characters and indentation
30 is set to 4 spaces per tab. If you also use VIM for other languages, there is a
31 handy plugin at indent_, which handles indentation settings for python source
34 There is also a handy syntax plugin at syntax_ featuring some improvements over
35 the syntax file included in VIM 6.1.
37 These plugins supply you with a basic environment for developing in Python.
38 To get the most out of Vim, you should continually check your code for syntax
39 errors and PEP8 compliance. Luckily PEP8_ and Pyflakes_ will do this for you.
40 If your VIM is compiled with `+python` you can also utilize some very handy
41 plugins to do these checks from within the editor.
43 For PEP8 checking, install the vim-pep8_ plugin, and for pyflakes you can
44 install vim-pyflakes_. Now you can map the functions `Pep8()` or `Pyflakes()`
45 to any hotkey or action you want in Vim. Both plugins will display errors at
46 the bottom of the screen, and provide an easy way to jump to the corresponding
47 line. It's very handy to call these functions whenever you save a file. In
48 order to do this, add the following lines to your `vimrc`::
50 autocmd BufWritePost *.py call Pyflakes()
51 autocmd BufWritePost *.py call Pep8()
53 If you are already using syntastic_ you can enable it to run Pyflakes on write
54 and show errors and warnings in the quickfix window. An example configuration
55 to do that which also shows status and warning messages in the statusbar would be::
57 set statusline+=%#warningmsg#
58 set statusline+=%{SyntasticStatuslineFlag()}
60 let g:syntastic_auto_loc_list=1
61 let g:syntastic_loc_list_height=5
66 Python-mode_ is complex solution in VIM for work with python code.
69 - Async python code checking (pylint, pyflakes, pep8, mccabe) in any combination;
70 - Code refactoring and autocompletion with Rope;
71 - Fastest python folding;
72 - Nice and powered python syntax;
73 - Virtual env support;
74 - Search by python documentation and run python code;
75 - More other things like auto pep8 error fixes;
76 - Very customizable an documented as well;
77 - Have all required libraries in self;
82 .. _indent: http://www.vim.org/scripts/script.php?script_id=974
83 .. _syntax: http://www.vim.org/scripts/script.php?script_id=790
84 .. _Pyflakes: http://pypi.python.org/pypi/pyflakes/
85 .. _vim-pyflakes: https://github.com/nvie/vim-pyflakes
86 .. _PEP8: http://pypi.python.org/pypi/pep8/
87 .. _vim-pep8: https://github.com/nvie/vim-pep8
88 .. _syntastic: https://github.com/scrooloose/syntastic
89 .. _Python-mode: https://github.com/klen/python-mode
91 .. todo:: add supertab notes
96 "`TextMate <http://macromates.com/>`_ brings Apple's approach to operating
97 systems into the world of text editors. By bridging UNIX underpinnings and GUI,
98 TextMate cherry-picks the best of both worlds to the benefit of expert
99 scripters and novice users alike."
104 "`Sublime Text <http://www.sublimetext.com/>`_ is a sophisticated text editor
105 for code, html and prose. You'll love the slick user interface and
106 extraordinary features."
108 Sublime Text has excellent support for editing Python code and uses Python for
114 PyCharm / IntelliJ IDEA
115 -----------------------
117 `PyCharm <http://www.jetbrains.com/pycharm/>`_ is developed by JetBrains, also
118 known for IntelliJ IDEA. Both share the same code base and most of PyCharm's
119 features can be brought to IntelliJ with the free `Python Plug-In <http://plugins.intellij.net/plugin/?id=631/>`_.
125 The most popular Eclipse plugin for Python development is Aptana's
126 `PyDev <http://pydev.org>`_.
131 `Komodo IDE <http://www.activestate.com/komodo-ide>`_ is developed by
132 ActiveState and is a commercial IDE for Windows, Mac
139 `Spyder <http://code.google.com/p/spyderlib/>`_ an IDE specifically geared
140 toward working with scientific python libraries (namely `Scipy <http://www.scipy.org/>`_).
141 Includes integration with pyflakes_, `pylint <http://www.logilab.org/857>`_,
142 and `rope <http://rope.sourceforge.net/>`_.
144 Spyder is open-source (free), offers code completion, syntax highlighting,
145 class and function browser, and object inspection.
151 `WingIDE <http://wingware.com/>`_ a python specific IDE. Runs for Linux,
152 Windows, and Mac (as an X11 application, which frustrates some Mac users).
162 Virtualenv is a tool to keep the dependencies required by different projects
163 in separate places, by creating virtual Python environments for them.
164 It solves the "Project X depends on version 1.x but, Project Y needs 4.x"
165 dilemma and keeps your global site-packages directory clean and manageable.
167 `virtualenv <http://www.virtualenv.org/en/latest/index.html>`_ creates
168 a folder which contains all the necessary executables to contain the
169 packages that a Python project would need. An example workflow is given.
173 $ pip install virtualenv
176 Create a virtual environment for a project::
181 ``virtualenv venv`` will create a folder in the current directory
182 which will contain the Python executable files, and a copy of the ``pip``
183 library which you can use to install other packages. The name of the
184 virtual environment (in this case, it was ``venv``) can be anything;
185 omitting the name will place the files in the current directory instead.
187 In order the start using the virtual environment, run::
189 $ source venv/bin/activate
192 The name of the current virtual environment will now appear on the left
193 of the prompt (e.g. ``(venv)Your-Computer:your_project UserName$``) to
194 let you know that it's active. From now on, any package that you install
195 using ``pip`` will be placed in the venv folder, isolated from the global
196 Python installation. Install packages as usual::
198 $ pip install requests
200 To stop using an environment simply type ``deactivate``. To remove the
201 environment, just remove the directory it was installed into. (In this
202 case, it would be ``rm -rf venv``).
207 Running ``virtualenv`` with the option ``--no-site-packages`` will not
208 include the packages that are installed globally. This can be useful
209 for keeping the package list clean in case it needs to be accessed later.
211 In order to keep your environment consistent, it's a good idea to "freeze"
212 the current state of the environment packages. To do this, run
216 $ pip freeze > requirements.txt
218 This will create a ``requirements.txt`` file, which contains a simple
219 list of all the packages in the current environment, and their respective
220 versions. Later, when a different developer (or you, if you need to re-
221 create the environment) can install the same packages, with the same
226 $ pip install -r requirements.txt
228 This can help ensure consistency across installations, across deployments,
229 and across developers.
231 Lastly, remember to exclude the virtual environment folder from source
232 control by adding it to the ignore list.
237 `Virtualenvwrapper <http://pypi.python.org/pypi/virtualenvwrapper>`_ makes
238 virtualenv a pleasure to use by wrapping the command line API with a nicer CLI.
242 $ pip install virtualenvwrapper
245 Put this into your `~/.bash_profile` (Linux/Mac) file:
249 $ export VIRTUALENVWRAPPER_VIRTUALENV_ARGS='--no-site-packages'
251 This will prevent your virtualenvs from relying on your (global) site packages
252 directory, so that they are completely separate..
260 `IDLE <http://docs.python.org/library/idle.html>`_ is an integrated
261 development environment that is part of Python standard library. It is
262 completely written in Python and uses Tkinter GUI toolkit. Though IDLE
263 is not suited for full-blown development using Python , it is quite
264 helpful to try out small Python snippets and experiment with different
267 It provides following features:
269 * Python Shell Window (interpreter)
270 * Multi window text editor that colorizes Python code
271 * Minimal debugging facility
277 `IPython <http://ipython.org/>`_ provides a rich toolkit to help you make the
278 most out of using Python interactively. Its main components are:
280 * Powerful Python shells (terminal- and Qt-based).
281 * A web-based notebook with the same core features but support for rich media,
282 text, code, mathematical expressions and inline plots.
283 * Support for interactive data visualization and use of GUI toolkits.
284 * Flexible, embeddable interpreters to load into your own projects.
285 * Tools for high level and interactive parallel computing.
289 $ pip install ipython
296 `bpython <http://bpython-interpreter.org/>`_ is an alternative interface to the
297 Python interpreter for Unix-like operating systems. It has the following features:
299 * In-line syntax highlighting.
300 * Readline-like autocomplete with suggestions displayed as you type.
301 * Expected parameter list for any Python function.
302 * "Rewind" function to pop the last line of code from memory and re-evaluate.
303 * Send entered code off to a pastebin.
304 * Save entered code to a file.
310 $ pip install bpython