Re: [Python-Dev] Coverity scan
Am 03.09.2012 15:59, schrieb Christian Heimes: > It be nice if we get Coverity scans up and running this week to check > the upcoming release candidate for issues. Updates: - Noah has set up a VM for me on the PSF infrastructure. I've installed the Coverity tools, build dependencies of Python and a hg clone of the default branch. The instrumented coverage builds are working, too. - Brett has contacted Coverity to establish me as a second administrative contact besides him. Once it's done I'll request an upload account to submit the coverage data. I try to get everything in place by tomorrow so we have some time to check for bugs before the next RC is deployed. Stefan: Has Brett already requested an account for you or shall I request one for you? Christian ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Coverity scan
On Wed, Sep 5, 2012 at 8:43 AM, Christian Heimes wrote: > Am 03.09.2012 15:59, schrieb Christian Heimes: > > It be nice if we get Coverity scans up and running this week to check > > the upcoming release candidate for issues. > > Updates: > > - Noah has set up a VM for me on the PSF infrastructure. I've installed > the Coverity tools, build dependencies of Python and a hg clone of the > default branch. The instrumented coverage builds are working, too. > > - Brett has contacted Coverity to establish me as a second > administrative contact besides him. Once it's done I'll request an > upload account to submit the coverage data. > > I try to get everything in place by tomorrow so we have some time to > check for bugs before the next RC is deployed. > > Stefan: > Has Brett already requested an account for you or shall I request one > for you? > I have not for no other reason than I had not thought about it. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Edits to Metadata 1.2 to add extras (optional dependencies)
A few more edits at https://bitbucket.org/dholth/python-peps/diff/pep-0426.txt?diff2=058b058ee3f8&diff1=42ee0afd40ed rfc822 is nixed in favor of 'parseable by email.parser.Parser with the right policy' Encoding is strictly utf-8 with the warning that older revisions have no defined encoding (keys are still always ASCII) Extra names are now 'printable ascii except , [ ]' instead of 'valid Python identifiers'. Extension names are now 'ascii, with no whitespace or /', with the / separator between the extension name and the rest of the tag name. No 'the order doesn't matter' clause yet. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Coverity scan
Am 05.09.2012 14:45, schrieb Brett Cannon: > I have not for no other reason than I had not thought about it. Whatever, I wasn't even sure if Stefan has contacted you or asked for a account in a public message. He might have proclaimed his wish in a private mail. Christian ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Coverity scan
Christian Heimes wrote: > I try to get everything in place by tomorrow so we have some time to > check for bugs before the next RC is deployed. Fantastic. Thanks for pushing this forward! > Stefan: > Has Brett already requested an account for you or shall I request one > for you? Not yet, please do if it's no problem. Stefan Krah ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Coverity scan
Am 05.09.2012 14:43, schrieb Christian Heimes: > I try to get everything in place by tomorrow so we have some time to > check for bugs before the next RC is deployed. The people at Coverity are even faster than I hoped. I'm now in the possession of the Project password which mean I can upload the builds and add new users. I've already added Stefan and uploaded an instrumented build successfully: Your request for analysis of Python has been completed. The results should be available now in the database: http://scan5.coverity.com:8080/ Have fun! Christian ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Coverity scan
Christian Heimes wrote: > The people at Coverity are even faster than I hoped. I'm now in the > possession of the Project password which mean I can upload the builds > and add new users. I've already added Stefan and uploaded an > instrumented build successfully: > > Your request for analysis of Python has been completed. The results > should be available now in the database: http://scan5.coverity.com:8080/ Thanks Christian, works perfectly! Stefan Krah ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Coverity scan
And a thanks to Christian and Stefan for picking this up and running with it. I have not been the best keeper of this stuff as of late, but now that Christian, Stefan, and I all have admin access to the data we can spread the load so that none of us become a bottleneck. On Wed, Sep 5, 2012 at 12:50 PM, Stefan Krah wrote: > Christian Heimes wrote: > > The people at Coverity are even faster than I hoped. I'm now in the > > possession of the Project password which mean I can upload the builds > > and add new users. I've already added Stefan and uploaded an > > instrumented build successfully: > > > > Your request for analysis of Python has been completed. The results > > should be available now in the database: http://scan5.coverity.com:8080/ > > Thanks Christian, works perfectly! > > > Stefan Krah > > > ___ > Python-Dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/brett%40python.org > ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Coverity scan
Am 05.09.2012 18:56, schrieb Brett Cannon: > And a thanks to Christian and Stefan for picking this up and running > with it. I have not been the best keeper of this stuff as of late, but > now that Christian, Stefan, and I all have admin access to the data we > can spread the load so that none of us become a bottleneck. You are welcome! Sharing is caring (or so) *g* Coverity has some new features like notification of new possible issue and build steps. We could create a new mailing list for coverity scan builds and results, The mailing list should be exclusive to core devs as the issues may be security relevant. Christian ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Tru64 support
On Wed, Sep 5, 2012 at 1:15 AM, wrote: > 2.7 should absolutely be able to support Tru64 (even though it currently > may not - that would be a bug). Any potential contributor to fix Tru64 > support > should find it "easy" to add fixes. > > So being cautious and following existing code sounds like a good idea. > The world wouldn't end if the test broke on Tru64, though. > That's ok. Chris Jerdonek is working on tuning docs for subprocess. He wrote tests to make sure him changes are correct. We can update documentation only for 2.7. -- Thanks, Andrew Svetlov ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Online docs: make index search available everywhere
For the Windows Help version of the docs, the left side box has 4 tabs: Contents, Index, Search, Favorites. I now mostly use the Index tab. That means that I can enter an indexed keyword, topic, or object name and jump from place to place in the docs. The left margin of the online docs only has a text search box equivalent to the Windows search tab (which I essentially never use). The index is only available on the front page, possibly not even visible without scrolling. Consequently, people, especially beginners, tend to use the text search box when they should be using the index. The result is often useless. The issue came up on python-list about a beginner entering 'print' and getting nothing useful. With the Windows doc, 'print' in the index search immediately brings up print (builtin function) (twice, I did not look into why). The same thing in the search lists 153 pages, with the builtin functions page at 75. Not too surprising, as it is a long page with only 3 occurrences of 'print'. Also not useful. So I think the online docs should also have an always available index search box in addition to the text search box (which should be properly labeled as such). 'Enter a module, class, for function name.' should be applied to index search, not text search. An alternative is for the one box to give both index search results and text search results, but doing the latter when one only wants the former is a waste of both server and reader resources. I presume this suggestion does not belong on bugs.python.org, so I hope one of the docs people reading pydev will do something with it. -- Terry Jan Reedy ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Tru64 support
On 09/04/2012 03:15 PM, [email protected] wrote: The world wouldn't end if the test broke on Tru64, though. FWIW, HP drops support for Tru64 at the end of this year: http://h30097.www3.hp.com/tru64roadmap.pdf Of course, this doesn't directly imply Python should stop supporting it--IIRC Python's OS/2 support outlasted IBM's support by many years. //arry/ ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Tru64 support
On Wed, 05 Sep 2012 15:26:03 -0700 Larry Hastings wrote: > > On 09/04/2012 03:15 PM, [email protected] wrote: > > The world wouldn't end if the test broke on Tru64, though. > > FWIW, HP drops support for Tru64 at the end of this year: > > http://h30097.www3.hp.com/tru64roadmap.pdf > > > Of course, this doesn't directly imply Python should stop supporting > it--IIRC Python's OS/2 support outlasted IBM's support by many years. But Python for OS/2 had a dedicated maintainer. Regards Antoine. -- Software development and contracting: http://pro.pitrou.net ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Online docs: make index search available everywhere
On Thu, Sep 6, 2012 at 8:13 AM, Terry Reedy wrote: > I presume this suggestion does not belong on bugs.python.org, so I hope one > of the docs people reading pydev will do something with it. Why do you assume that? Docs infrastructure suggestions can go on the tracker under "enhancement", the same as improvements to the docs wording. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Tru64 support
Zitat von Larry Hastings : On 09/04/2012 03:15 PM, [email protected] wrote: The world wouldn't end if the test broke on Tru64, though. FWIW, HP drops support for Tru64 at the end of this year: http://h30097.www3.hp.com/tru64roadmap.pdf Of course, this doesn't directly imply Python should stop supporting it--IIRC Python's OS/2 support outlasted IBM's support by many years. It's perfectly fine (IMO) to drop support for Tru64. The main point of PEP 11 is that this shouldn't be done ad-hoc, but by giving users advance notice. So dropping support between bug fix releases is not ok (but unknowingly breaking test cases for some platform where we don't have a buildbot is ok, of course - whether the platform is little used or not). It's unfortunate that the presumed removal of Tru64 support in 3.0 didn't get recorded in PEP 11 (which may well be my fault as well); it's also unfortunate that it wasn't carried out completely, so that it's now not clear whether it was carried out at all. If 3.0 wouldn't have worked at all on Tru64 already, removing the remains would be a bug fix. If the removal was only documented but not implemented, support wasn't actually removed, so users may not have received the advance warning that configure should have spit out, in which case removal in 3.4 may appear ad-hoc to them. In any case, it appears that nobody ever announced removal of Tru64 support for 2.x, which means that it continues to be supported - except that it may not actually work. But if so, we should accept bug fixes that claim to restore support. Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
