A convenience utility for software source code validation and linting
VVV is a tool for easy validation and linting integration for your software project containing multiple kinds of files. It integrates with version control and prevents committing files containing bad formatting or syntax errors.
Example output from validating the demo repository where we find errors in a Python and a CSS file. You enter the folder and run vvv against the current folder (.)
$ vvv . Running vvv against . /Users/moo/code/vvv/demo/demo.py validation output: ************* Module demo E0602: 1,9: Undefined variable 'get_magic' W3C CSS Validator results for file:/Users/moo/code/vvv/demo/foobar.css Line : 2 .foo Property backgrnd doesn't exist : yellow
VVV is writte in in Python programming language and is compatible with Python interpreter 2.7 or later, including 3.x series.
- Enforce coding conventions across multiple developers
- Enable linting and validators support for your software project with a single command
- Automatically guide committers to policy guidelines and let them fix errors themselves, instead of having post-commit personal coaching.
- Provide sane default validation and linting options for all popular programming languages and file formats
- Run VVV as continuous integration service with systems like Travis CI or Jenkins and shoot down bad code push-ins
What VVV doesn’t do
- This is not automated testing tool. We just scan files against a policy, not for programming errors. Linting tools tend to pick up programming errors, too though, like mistyped names.
- Set-up for your software repository with two files validation-options.yaml (configuration) and validation-files.yaml (whitelist/blacklist)
- VVV automatically downloads and locally installs required software - you don’t need to spend time hunting downloads or distribution packages
- Check file against hard tabs and whitespace policies - no more different tab width ever
- Prevent committing hard source code breakpoints, like Python’s import pdb ; pdb.set_trace()
- Support (on its way) for Subversion, Git, Github, Travis CI, Jenkings and other popular version control and continuous integration systems
Please see the VVV documentation.
Source code is available on Github. Please use Github issue tracker to contact the authors.
Explore different linting and validators available.
Current trunk continuous integration status with Travis CI
- Windows compatibility confirmed [jsalonen]
- Fixed more issues with bad command line options [miohtama]
- Handle empty / missing config files more gracefully [miohtama]
- Python 2.7 compatibility added [miohtama]
- Refactored text plug-ins to silently ignore bad encoding [miohtama]
- Intelligent git pre-commit hook; check only changed files [miohtama]
- Evil spacebar buster added [miohtama]
- jshint now properly reads config files (was non-std parsing by Node.js argument library) [miohtama]
- Reorganized docs to have Tools section [miohtama]
- Depend on docutils as RST validator soft-depends on it, but cannot install docutils in host environment [miohtama]
- Correctly pick up RST validator script from path if not under virtualenv [miohtama]
- More git hook silent install corner case fixes
- Smarter way to detect vvv command location when installing a precommit hook [miohtama]
- Integration documentation updates [miohtama]
- Fixed changelog formatting now that PyPi README page is intact again
- pylint-command option added [miohtama]
- Ghetto-CI continuous integration script [miohtama]
- Configuration file reader refactored to something more beautiful [miohtama]
- Now you can VVV individual files [miohtama]
- VVV can walk up in the directory tree to find validation-options.yaml file [miohtama]
- Set zip_safe = False on the egg just in case [miohtama]
- Added Github links to README [miohtama]
- Initial release