vim/syntastic
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
79564f9847
syntastic/syntax_checkers/python/python.vim

35 lines
1.2 KiB
VimL
Raw Normal View History

Add python checker that uses python itself The advantage to this is that no 3rd party modules are required. People new to Python probably won't have flake8/pyflakes/pylint installed. This will get them basic syntax checking (no linting) out of the box.
2012-12-01 15:17:46 -05:00
"============================================================================
"File: python.vim
"Description: Syntax checking plugin for syntastic.vim
"Author: Artem Nezvigin <artem at artnez dot com>
"
" `errorformat` derived from:
" http://www.vim.org/scripts/download_script.php?src_id=1392
"
"============================================================================
refactor all the syntax checkers to use the new API and dir layout
2013-01-27 15:08:30 -05:00
function! SyntaxCheckers_python_python_IsAvailable()
refactor how we represent and store checkers using python as a demo Add 2 classes: SyntasticChecker and SyntasticRegistry. SyntasticChecker represents a checker. It holds funcrefs to the checker func, the highlight regex func and a new `isAvailable()` func (that essentially just checks if the checker exe is installed) SyntasticRegistry is responsible for: * loading checkers * storing checkers * fetching the checkers to use according to availability and the users settings Motivation/benefits: * in the current system only one checker can be loaded per filetype * syntax checkers cant be "chained" together * the system is hard to add features to since fundamental concepts like syntax checkers and location lists arent represented explicitly Things left to do: * add a call to g:SyntasticRegistry.CreateAndRegisterChecker() to all checkers * add an `isAvailable` function to all checkers * move all checkers into `syntax_checkers/filetype/checkername.vim` - g:SyntasticRegistry assumes this layout, and its a good idea anyway for consistency and it makes it easier for users to add their own checkers Things to do after all of the above: * add a LocationList class and move all the filtering functions onto it * possibly add an Error class that wraps up each item in a loc list Random notes: * with the new system you can select the checkers to use with e.g. `let g:syntastic_python_checkers=['flake8', 'pylint']` This will try flake8 first, and if no errors are detected it will move onto pylint.
2013-01-23 19:01:30 -05:00
return executable('python')
endfunction
Add python checker that uses python itself The advantage to this is that no 3rd party modules are required. People new to Python probably won't have flake8/pyflakes/pylint installed. This will get them basic syntax checking (no linting) out of the box.
2012-12-01 15:17:46 -05:00
refactor all the syntax checkers to use the new API and dir layout
2013-01-27 15:08:30 -05:00
function! SyntaxCheckers_python_python_GetLocList()
Add python checker that uses python itself The advantage to this is that no 3rd party modules are required. People new to Python probably won't have flake8/pyflakes/pylint installed. This will get them basic syntax checking (no linting) out of the box.
2012-12-01 15:17:46 -05:00
let l:path = shellescape(expand('%'))
let l:cmd = "compile(open(" . l:path . ").read(), " . l:path . ", 'exec')"
let l:makeprg = 'python -c "' . l:cmd . '"'
let l:errorformat =
\ "\%A\ \ File\ \"%f\"\\\,\ line\ %l\\\,%m," .
\ "\%C\ \ \ \ %.%#," .
\ "\%+Z%.%#Error\:\ %.%#," .
\ "\%A\ \ File\ \"%f\"\\\,\ line\ %l," .
\ "\%+C\ \ %.%#," .
\ "\%-C%p^," .
\ "\%Z%m," .
\ "\%-G%.%#"
return SyntasticMake({ 'makeprg': l:makeprg, 'errorformat': l:errorformat })
endfunction
refactor how we represent and store checkers using python as a demo Add 2 classes: SyntasticChecker and SyntasticRegistry. SyntasticChecker represents a checker. It holds funcrefs to the checker func, the highlight regex func and a new `isAvailable()` func (that essentially just checks if the checker exe is installed) SyntasticRegistry is responsible for: * loading checkers * storing checkers * fetching the checkers to use according to availability and the users settings Motivation/benefits: * in the current system only one checker can be loaded per filetype * syntax checkers cant be "chained" together * the system is hard to add features to since fundamental concepts like syntax checkers and location lists arent represented explicitly Things left to do: * add a call to g:SyntasticRegistry.CreateAndRegisterChecker() to all checkers * add an `isAvailable` function to all checkers * move all checkers into `syntax_checkers/filetype/checkername.vim` - g:SyntasticRegistry assumes this layout, and its a good idea anyway for consistency and it makes it easier for users to add their own checkers Things to do after all of the above: * add a LocationList class and move all the filtering functions onto it * possibly add an Error class that wraps up each item in a loc list Random notes: * with the new system you can select the checkers to use with e.g. `let g:syntastic_python_checkers=['flake8', 'pylint']` This will try flake8 first, and if no errors are detected it will move onto pylint.
2013-01-23 19:01:30 -05:00
call g:SyntasticRegistry.CreateAndRegisterChecker({
\ 'filetype': 'python',
refactor all the syntax checkers to use the new API and dir layout
2013-01-27 15:08:30 -05:00
\ 'name': 'python'})
Reference in New Issue Copy Permalink