JShint will be executed with paver run_jshint, which will use a defined set of
directories (likewise defined are directories to ignore). A limit can be imposed
on the total number of violations. Note that this change does NOT include adding
jshint to diff-quality or `paver run_quality`.
This would allow a user to set up and run servers, with an open prompt for killing
them. Likewise a user could open a different terminal session and run tests only.
How-to:
* At a terminal/ssh session, start bok-choy servers with
`paver test_bokchoy --serversonly`
(or, if you've already run collectstatic on your system:
`paver test_bokchoy --serversonly --fasttest`)
* When the above is running, you can now open a separate terminal/ssh session
and run:
`paver test_bokchoy -t my_tests --testsonly`
Keep in mind, the 'testsonly' flag does no setup. There is some minimal teardown; however,
such as clearing mongo and flushing the lms database. (Some tests have non-unique identifiers
and could not be run more than once.)
With the old logic, we weren't running pylint on openedx at all. We
were also running it on lms/lib/comment_client twice, and on the
installed xblock third-party library.
If you have a branch named "remove-all-.pyc", the original code would
clobber it inside the .git directory, because branches become files with
the same name. This prevents find from looking in .git, saving your
precious oddly named branches.
This allows developers to pass the `--pdb` flag to paver test commands,
and that flag will be proxied to the `nosetests` command. It's useful
for debugging purposes.
There are now folders under static that have sass that should not be compiled
as a part of our asset pipeline, they were getting pulled in because the wildcard
for `SASS_UPDATE_DIRS` was too broad. This update makes it more specific for most
folders but leaves it broad for the common folder where the xmodule has its own sass
that needs compiling from a non-standard location.
So the time-consuming i18n_extract step can be skipped for situations that only the translated strings are modified while the source strings are still the same.
We are not using the limit flag in the actual run_pep8 method; removing
that from scripts. Operationally, pep8 has been enforcing a limit of
zero for awhile; this finishes that realization.
Also, all pep8 reports now appear under the reports/pep8 folder, rather than
per-system.
