Without compilation, how to find bugs?
Chris Angelico
rosuav at gmail.com
Fri Oct 14 05:38:26 EDT 2016
More information about the Python-list mailing list
Fri Oct 14 05:38:26 EDT 2016
- Previous message (by thread): Without compilation, how to find bugs?
- Next message (by thread): Without compilation, how to find bugs?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Oct 14, 2016 at 8:04 PM, BartC <bc at freeuk.com> wrote: > On 14/10/2016 01:59, sohcahtoa82 at gmail.com wrote: >> >> On Thursday, October 13, 2016 at 4:06:36 PM UTC-7, pozz wrote: > > >>> Are the things exactly how I understood, or do I miss something in >>> Python? >> >> >> As others have said, user a linter. > > > With Python you're supposed to just be able run any source code instantly; > how will using a 'lint' tool impact that process? Or is it only meant to be > used infrequently? > In any serious project (in any language), you should have unit tests. Python doesn't force you to run those every time you build - nor does C, nor does any other language. It's up to you how often you run your tests. Linters are basically just heuristic testing systems - less precise, but more general. Type checkers in Python are the same. ChrisA
- Previous message (by thread): Without compilation, how to find bugs?
- Next message (by thread): Without compilation, how to find bugs?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list