Re: [Python-Dev] Coverity Open Source Defect Scan of Python

2006-03-13 Thread Scott David Daniels
Michael Chermside wrote: > (PS: too bad I can't buy stock in Coverity. How come all the GOOD > companies are private? I had to wait around 6 years before I could > buy stock in Google.) Maybe because the companies whose stock is available early are companies bent on producing stock profits, rather

Re: [Python-Dev] Coverity Open Source Defect Scan of Python

2006-03-13 Thread Michael Chermside
Dennis Allison writes: > I'd also encourage Coventry to explain their business model a bit more > clearly. Ben Chelf writes: > Of course it's no surprise that I see open > source projects everywhere -- as part of infrastructure or part of code > bases that people are developing. So from a Coverity

Re: [Python-Dev] Coverity Open Source Defect Scan of Python

2006-03-11 Thread Thomas Wouters
On 3/7/06, Ben Chelf <[EMAIL PROTECTED]> wrote: Putting on my idealistic hat and remembering back my grad school days, Ithink we're on to something very new in the world of source codeanalysis. I really just want every developer to use source code analysiswhile they write code (remember, idealistic

Re: [Python-Dev] Coverity Open Source Defect Scan of Python

2006-03-11 Thread Ben Chelf
> The Coverty marketing droids need to be a bit less anal about getting > people to register at the website. IMHO, the technology should be Honestly, I laughed out loud when I read this. ;) So thanks for that. > > I'd also encourage Coventry to explain their business model a bit more > clearl

Re: [Python-Dev] Coverity Open Source Defect Scan of Python

2006-03-06 Thread Jeremy Hylton
On 3/6/06, Thomas Wouters <[EMAIL PROTECTED]> wrote: > > > > On 3/6/06, Barry Warsaw <[EMAIL PROTECTED]> wrote: > > > Didn't we set up a "security swat team" some time ago? If not, we > > > should. Regardless, since I have more free time these days, I'd like > > > to be on it. > > > > Yep, it's c

Re: [Python-Dev] Coverity Open Source Defect Scan of Python

2006-03-06 Thread Guido van Rossum
FWIW, coverity has been busy marketing this already: http://www.pcpro.co.uk/news/84465/key-opensource-code-passes-muster.html -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Python-Dev mailing list Python-Dev@python.org http://mail.

Re: [Python-Dev] Coverity Open Source Defect Scan of Python

2006-03-06 Thread Dennis Allison
On Mon, 6 Mar 2006, Barry Warsaw wrote: > On Mon, 2006-03-06 at 14:26 -0500, Tim Peters wrote: > > [Ben Chelf <[EMAIL PROTECTED]>] > > > ... > > > I'd ask that if you are interested in really digging into the results a > > > bit > > > further for your project, please have a couple of core maintai

Re: [Python-Dev] Coverity Open Source Defect Scan of Python

2006-03-06 Thread Tim Peters
[Barry] > Yep, it's called [EMAIL PROTECTED] (with a semi-secret backing mailing > list, which I'd be happy for you to join!). If guessing the right Mailman URL was the semi-secret test, I passed :-) > I definitely think that group of folks at the least should review the results. Yup! _

Re: [Python-Dev] Coverity Open Source Defect Scan of Python

2006-03-06 Thread Thomas Wouters
On 3/6/06, Barry Warsaw <[EMAIL PROTECTED]> wrote: > Didn't we set up a "security swat team" some time ago?  If not, we> should.  Regardless, since I have more free time these days, I'd like> to be on it.Yep, it's called [EMAIL PROTECTED] (with a semi-secret backing mailinglist, which I'd be happy

Re: [Python-Dev] Coverity Open Source Defect Scan of Python

2006-03-06 Thread Barry Warsaw
On Mon, 2006-03-06 at 14:26 -0500, Tim Peters wrote: > [Ben Chelf <[EMAIL PROTECTED]>] > > ... > > I'd ask that if you are interested in really digging into the results a bit > > further for your project, please have a couple of core maintainers (or > > group nominated individuals) reach out to me

Re: [Python-Dev] Coverity Open Source Defect Scan of Python

2006-03-06 Thread Tim Peters
[Ben Chelf <[EMAIL PROTECTED]>] > ... > I'd ask that if you are interested in really digging into the results a bit > further for your project, please have a couple of core maintainers (or > group nominated individuals) reach out to me to request access. Didn't we set up a "security swat team" som