Search results

nose2 is the followup library to nose. It is built on top of unittest2 (but so far seems to remain compatible with unittest). The primary reason for migrating

[dev-packages] nose = '*' unittest2 = {version = ">=1.0,<3.0", markers="python_version < '2.7.9' or (python_version >= '3.0' and python_version < '3.4')"}

simplest unittest for python, but it is the most universal so it deserves mentioning. ## Sample UnitTest File import unittest ## Import UnitTest from unnecessary_math

Outside of the main python language features (which are unlikely to change), this documents individual python modules (internal and external). Some of

tests directory. If I am running a python module, I can re-run it with dnose and the test will be run instead of the python module. ## See ~/.bash/aliases/all

Vim is extremely extensible, both using viml and python (if it is compiled into your version of vim). If you are looking for directions for creating your

are defined in the key. This can get fairly complex, but thankfully the python dateutils module provides a way to parse rrules. from dateutil import rrule

testobj = mock.Mock() testobj.side_effect = [ 0, 1, 2 ] testobj() # 0 testobj() # 1 testobj() # 2 method 2 This is much simpler than it might at first seem

assigning it it's own PID). When running python scripts from a python interpreter, python simulates this by calling the python-executable ( sys.executable ) with

filetype (ex: 'python.vim' is read when reading a '.py' file) they are in a directory whose name matches current buffer's filetype (ex: 'python/pymode.vim'