[python-committers] 3.3 rc1 next week
Dear committers, if the buffer/array-related blockers are resolved in time, the rc1 will be released one week from now. Since some people asked: at the moment we are not in the RC phase yet, so fixing bugs is allowed, but it would be advisable to have a second committer review any nontrivial fix. From the release of rc1, I will keep the code that will become 3.3 in a separate repo, so that commits to "default" on cpython *won't* go into 3.3. You will have to notify me of all commits that you think *should* go there, so that I can cherry-pick them. Not all bugfixes fall into that category; only showstopper-level ones. The rest will have to wait for 3.3.1. cheers, Georg ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] anyone still have access to the coverity scan results?
On Sat, Aug 18, 2012 at 11:01 AM, Christian Heimes wrote: > Am 18.08.2012 15:08, schrieb Stefan Krah: > > Christian Heimes wrote: > >> Yup, my login still works. I can send you a CSV or XML report if you > like. > > > > Thanks, got the CSV! > > > > If anyone has the possibility to create new accounts, I would like to > apply > > for one. > > Who usually uploads the necessary files to coverity? The current files > are rather old (patchlevel.h says 3.3.0a0). I was able to create the > report files but the files must be uploaded to a registered location. > I think I'm still listed as the main contact and I never uploaded anything. I believe Coverty pulls the files in themselves. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] anyone still have access to the coverity scan results?
On Sun, Aug 19, 2012 at 11:56 AM, Brett Cannon wrote: > > > On Sat, Aug 18, 2012 at 11:01 AM, Christian Heimes wrote: > >> Am 18.08.2012 15:08, schrieb Stefan Krah: >> > Christian Heimes wrote: >> >> Yup, my login still works. I can send you a CSV or XML report if you >> like. >> > >> > Thanks, got the CSV! >> > >> > If anyone has the possibility to create new accounts, I would like to >> apply >> > for one. >> >> Who usually uploads the necessary files to coverity? The current files >> are rather old (patchlevel.h says 3.3.0a0). I was able to create the >> report files but the files must be uploaded to a registered location. >> > > I think I'm still listed as the main contact and I never uploaded > anything. I believe Coverty pulls the files in themselves. > So when trying to log in (which didn't work; Coverty has changed this system so many times I don't what username/password works anymore) there was a notice that how you submit code has changed: At the same time, we also have changes in the process to submit the build to Coverity Scan for Open Source Projects. 0. With the new version, there are three steps to analyze a codebase: build, analyze, and commit. 1. You do the build step, then tar up the intermediate representation and stick it somewhere we can get it by http. 2. Our scripts wget it, analyze it, commit it to the DB and send you an email. The link to their build tools is http://scan.coverity.com/self-build/ . So it looks like we have to give them the files to analyze now after we have built them with their tool chain on LInux. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] anyone still have access to the coverity scan results?
Am 19.08.2012 18:02, schrieb Brett Cannon: > The link to their build tools is http://scan.coverity.com/self-build/ . > So it looks like we have to give them the files to analyze now after we > have built them with their tool chain on LInux. Yes, that's what I'm talking about. It took me a while to figure out the correct URL and my password, too. The new version of coverity doesn't pull the changes automatically. Instead you have to compile the code with a custom build system and provide a download link for the results: Coverity Scan Self-Build - updated July 2012 Coverity build tool link is: Linux-64 6.0.2 Linux-32 6.0.2 Downloading and building Do once: Download and extract the tarball Add the bin directory to your path Do for each build: cd to your build directory optional: Run any build steps that you don't want to analyze – i.e. ./configure cov-build --dir cov-int [BUILD CMD and ARGS] Create a README file with your name, email, and project's name tar czvf project.tgz README cov-int Upload the project.tgz to your server For your first build, after making the archive file available on a server, send the URL for it to scan-ad...@coverity.com. Once we sort out any issues with the archive processing, you will get project name, and password to submit builds automatically whenever you like. Submitting self-builds Enter project name, password, email and download URL here: http://scan.coverity.com/submit.html http://scan.coverity.com/self-build/6.0.2/cov-analysis-linux64-6.0.2.tar.gz http://scan.coverity.com/self-build/6.0.2/cov-analysis-linux32-6.0.2.tar.gz I've tried to upload my build of Python's py3k head but the system doesn't recognize my password for the upload process. I guess we need to get a different password for the upload process. Or you could try your login data. Perhaps I don't have the necessary permissions. My build is available at http://dl.dropbox.com/u/19557108/project.tgz Christian ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] anyone still have access to the coverity scan results?
On 20.01.2011 02:44, Steve Holden wrote: > Could we consider offering a complimentary PyCon registration to a > member of the Coverity team as an encouragement to have someone > around during the sprints? I am sure that much useful informal > education would take place, benefiting many sprints, if we enable it > and just let things happen. > > Or would this be seen as favoring one vendor? I would see nothing wrong with it, and getting this person in the conference may allow people to chat in person. Coverity has offered this free service, and even though they also had promotion of their product in mind, they actually do demonstrate a real interest in free software. Regards, Martin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] anyone still have access to the coverity scan results?
Le dimanche 19 août 2012 à 21:15 +0200, "Martin v. Löwis" a écrit : > On 20.01.2011 02:44, Steve Holden wrote: > > Could we consider offering a complimentary PyCon registration to a > > member of the Coverity team as an encouragement to have someone > > around during the sprints? I am sure that much useful informal > > education would take place, benefiting many sprints, if we enable it > > and just let things happen. > > > > Or would this be seen as favoring one vendor? > > I would see nothing wrong with it, and getting this person in > the conference may allow people to chat in person. Coverity > has offered this free service, and even though they also had > promotion of their product in mind, they actually do demonstrate > a real interest in free software. I don't know where Steve's message was posted (I can't see it in the archives or in my inbox). It seems this would be not only favoring a vendor, but favoring someone who doesn't participate in the community (unless we have a contributor who is also a Coverity employee). And it would favour one (US) Python conference over other non-US conferences, since typically sprints don't get recorded for remote viewing. Regards Antoine. -- Software development and contracting: http://pro.pitrou.net ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] anyone still have access to the coverity scan results?
On Aug 19, 2012 3:16 PM, Martin v. Löwis wrote: > > On 20.01.2011 02:44, Steve Holden wrote: > > Could we consider offering a complimentary PyCon registration to a > > member of the Coverity team as an encouragement to have someone > > around during the sprints? I am sure that much useful informal > > education would take place, benefiting many sprints, if we enable it > > and just let things happen. > > > > Or would this be seen as favoring one vendor? > > I would see nothing wrong with it, and getting this person in > the conference may allow people to chat in person. Coverity > has offered this free service, and even though they also had > promotion of their product in mind, they actually do demonstrate > a real interest in free software. I believe coverty is/was paid by a branch of the US government to do this in the name of security for key software. > > Regards, > Martin > ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
