/usr/lib/python2.6/site-packages/nose
NameSizeModeActions
ext/-0755rm
plugins/-0755rm
case.py125080644editdlrm
case.pyc142820644editdlrm
case.pyo142820644editdlrm
commands.py45700644editdlrm
commands.pyc50030644editdlrm
commands.pyo50030644editdlrm
config.py202030644editdlrm
config.pyc198900644editdlrm
config.pyo198900644editdlrm
core.py171750644editdlrm
core.pyc175490644editdlrm
core.pyo175490644editdlrm
exc.py3760644editdlrm
exc.pyc5760644editdlrm
exc.pyo5760644editdlrm
failure.py8500644editdlrm
failure.pyc13670644editdlrm
failure.pyo13670644editdlrm
importer.py54900644editdlrm
importer.pyc50940644editdlrm
importer.pyo50940644editdlrm
inspector.py69040644editdlrm
inspector.pyc59250644editdlrm
inspector.pyo59250644editdlrm
loader.py214370644editdlrm
loader.pyc160800644editdlrm
loader.pyo160800644editdlrm
proxy.py58400644editdlrm
proxy.pyc73270644editdlrm
proxy.pyo71200644editdlrm
result.py58490644editdlrm
result.pyc59130644editdlrm
result.pyo59130644editdlrm
selector.py90030644editdlrm
selector.pyc88760644editdlrm
selector.pyo88760644editdlrm
suite.py186930644editdlrm
suite.pyc186630644editdlrm
suite.pyo186630644editdlrm
tools.py50230644editdlrm
tools.pyc72090644editdlrm
tools.pyo71290644editdlrm
twistedtools.py52680644editdlrm
twistedtools.pyc58150644editdlrm
twistedtools.pyo58150644editdlrm
util.py192750644editdlrm
util.pyc201250644editdlrm
util.pyo201250644editdlrm
__init__.py149850644editdlrm
__init__.pyc152830644editdlrm
__init__.pyo152830644editdlrm
Edit: /usr/lib/python2.6/site-packages/nose/commands.pyc (5003B)
Ñò ž€DHc @s¥dZyddklZWnej od ZZniXddklZlZl Z l Z l Z ddk l Z ddklZd„Zdefd„ƒYZd S( s5 nosetests setuptools command ---------------------------- You can run tests using the `nosetests` setuptools command:: python setup.py nosetests This command has one benefit over the standard `test` command: all nose plugins are supported. To configure the `nosetests` command, add a [nosetests] section to your setup.cfg. The [nosetests] section can contain any command line arguments that nosetests supports. The differences between issuing an option on the command line and adding it to setup.cfg are: * In setup.cfg, the -- prefix must be excluded * In setup.cfg, command line flags that take no arguments must be given an argument flag (1, T or TRUE for active, 0, F or FALSE for inactive) Here's an example [nosetests] setup.cfg section:: [nosetests] verbosity=1 detailed-errors=1 with-coverage=1 cover-package=nose debug=nose.loader pdb=1 pdb-failures=1 If you commonly run nosetests with a large number of options, using the nosetests setuptools command and configuring with setup.cfg can make running your tests much less tedious. (Note that the same options and format supported in setup.cfg are supported in all other config files, and the nosetests script will also load config files.) Another reason to run tests with the command is that the command will install packages listed in your `tests_require`, as well as doing a complete build of your package before running tests. For packages with dependencies or that build C extensions, using the setuptools command can be more convenient than building by hand and running the nosetests script. iÿÿÿÿ(tCommand(tConfigtoption_blacklisttuser_config_filestflagt_bool(t TestProgram(tDefaultPluginManagercCs±g}x¤|iD]™}|iddtjoqn|idd}|idjo|d}nd }|io|idd}n|i|||ipdfƒqW|S( sAconvert a optparse option list into a distutils option tuple listiit store_truet store_falset=it(RR N(t option_listt _long_optsRtactiontNonet _short_optstappendthelp(tparsertopt_listtoptt long_namet short_name((s1/usr/lib/python2.6/site-packages/nose/commands.pytget_user_options8s  $t nosetestscBseeZdZedeƒdeƒƒZeiƒZe eƒZ d„Z d„Z d„Z d„ZRS(sRun unit tests using noseteststfilestpluginscCsmh|_xT|iiD]F}|idd}|iddƒ}||i|,s(