I've come to depend on PyCheckMate (which I run via "Validate Syntax" in the Python bundle). But "all of a sudden" it has started doing a "Syntax check only" (I don't know exactly when this started), which is much less useful. (The syntax check misses a number of errors that the previous check would catch.)
The window that opens when I do a validate shows "PyCheckMate r7337". Did it fall back to syntax check only when I last updated TextMate? How do I go back to the full validation?
-- Daryl Spitzer
I've come to depend on PyCheckMate (which I run via "Validate Syntax" in the Python bundle). But "all of a sudden" it has started doing a "Syntax check only" (I don't know exactly when this started), which is much less useful. (The syntax check misses a number of errors that the previous check would catch.)
The window that opens when I do a validate shows "PyCheckMate r7337". Did it fall back to syntax check only when I last updated TextMate? How do I go back to the full validation?
Did anything change in your python environment? Looking at the source of pycheckmate, it looks like it should automatically use PyFlakes, Pylint, or PyChecker if they are installed. Alternately, you can set the TM_PYCHECKER name of the executable you want to use to check the syntax.
The last change to PyCheckMate was back in May 2007, which leads me to believe that something changed on your end.
– Alex
Thanks for the quick reply Alex.
...which leads me to believe that something changed on your end.
Yep, you're right. I forgot that I installed Python 2.5.
I was going to re-install PyChecker, but decided to try Pylint instead. It's working.
-- Daryl
On 10/18/07, Alex Ross alex.j.ross@gmail.com wrote:
I've come to depend on PyCheckMate (which I run via "Validate Syntax" in the Python bundle). But "all of a sudden" it has started doing a "Syntax check only" (I don't know exactly when this started), which is much less useful. (The syntax check misses a number of errors that the previous check would catch.)
The window that opens when I do a validate shows "PyCheckMate r7337". Did it fall back to syntax check only when I last updated TextMate? How do I go back to the full validation?
Did anything change in your python environment? Looking at the source of pycheckmate, it looks like it should automatically use PyFlakes, Pylint, or PyChecker if they are installed. Alternately, you can set the TM_PYCHECKER name of the executable you want to use to check the syntax.
The last change to PyCheckMate was back in May 2007, which leads me to believe that something changed on your end.
– Alex ______________________________________________________________________ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Oct 18, 2007, at 4:55 PM, Daryl Spitzer wrote:
Thanks for the quick reply Alex.
...which leads me to believe that something changed on your end.
Yep, you're right. I forgot that I installed Python 2.5.
I was going to re-install PyChecker, but decided to try Pylint instead. It's working.
I like being able to use both. See the attached commands.
j.
Jay,
How do you chose which (PyChecker or Pylint) to use? In other words, what are the advantages & disadvantages of each?
-- Daryl
On 10/18/07, Jay Soffian jay-txmt@soffian.org wrote:
On Oct 18, 2007, at 4:55 PM, Daryl Spitzer wrote:
Thanks for the quick reply Alex.
...which leads me to believe that something changed on your end.
Yep, you're right. I forgot that I installed Python 2.5.
I was going to re-install PyChecker, but decided to try Pylint instead. It's working.
I like being able to use both. See the attached commands.
j.
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Oct 18, 2007, at 7:00 PM, Daryl Spitzer wrote:
Jay,
How do you chose which (PyChecker or Pylint) to use? In other words, what are the advantages & disadvantages of each?
I use both. They overlap a lot, but they do each catch different things as well. Pylint has a lot more power for enforcing coding styles, if you care to do that. Another advantage of Pylint is that it can inspect code even if some of the imports are unavailable.
But in case, I almost always run both and take care of any errors/ warnings.
j.
In that case, have you thought about coming up with one command runs both (so you don't have to invoke two separate commands each time you want to validate)? Is it possible to have a single command open two output windows?
-- Daryl
On 10/18/07, Jay Soffian jay-txmt@soffian.org wrote:
On Oct 18, 2007, at 7:00 PM, Daryl Spitzer wrote:
Jay,
How do you chose which (PyChecker or Pylint) to use? In other words, what are the advantages & disadvantages of each?
I use both. They overlap a lot, but they do each catch different things as well. Pylint has a lot more power for enforcing coding styles, if you care to do that. Another advantage of Pylint is that it can inspect code even if some of the imports are unavailable.
But in case, I almost always run both and take care of any errors/ warnings.
j.
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
-
Alex Ross -
Daryl Spitzer -
Jay Soffian