This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author christian.heimes
Recipients Alexander Riccio, BreamoreBoy, christian.heimes, loewis, paul.moore, r.david.murray, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2016-08-25.15:31:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1472139087.36.0.776626697512.issue25847@psf.upfronthosting.co.za>
In-reply-to
Content
Coverity Scan has two steps. In the first step the code is compiled with the coverity tool chain. It's a wrapper around the preprocessor and compiler. Next up the result is uploaded and analyzed by a service.

So yes, the project needs to be build before it can be analyzed.
History
Date User Action Args
2016-08-25 15:31:27christian.heimessetrecipients: + christian.heimes, loewis, terry.reedy, paul.moore, tim.golden, r.david.murray, BreamoreBoy, zach.ware, steve.dower, Alexander Riccio
2016-08-25 15:31:27christian.heimessetmessageid: <1472139087.36.0.776626697512.issue25847@psf.upfronthosting.co.za>
2016-08-25 15:31:27christian.heimeslinkissue25847 messages
2016-08-25 15:31:27christian.heimescreate