Re: [Python-Dev] Importing bsddb 4.6.21; with or without AES encryption?

2008-05-23 Thread Trent Nelson
> I just committed bsddb3 4.7.0. Please install Berkeley DB >=4.7.25. Oh my. Just finished plugging 4.7.25 into the Windows build environment. Upon running regrtest.py -v -u bsddb test_bsddb test_bsddb3, I get about 300 lines like this printed to stderr: DB->key_range: method not permitted be

[Python-Dev] Summary of Tracker Issues

2008-05-23 Thread Tracker
ACTIVITY SUMMARY (05/16/08 - 05/23/08) Tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 1884 open (+40) / 12889 closed (+16) / 14773 total (+56) Open issues with patches: 559 Average durati

Re: [Python-Dev] Importing bsddb 4.6.21; with or without AES encryption?

2008-05-23 Thread Trent Nelson
> I just committed bsddb3 4.7.0. Please install Berkeley DB >=4.7.25. I'll be working on this over the weekend. Trent. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.pyt

Re: [Python-Dev] Importing bsddb 4.6.21; with or without AES encryption?

2008-05-23 Thread M.-A. Lemburg
On 2008-05-23 01:15, Bill Janssen wrote: That's all fine, but then I'm missing the OpenSSL license and attribution notice somewhere in the installer, the README of the installation or elsewhere. Good point. We need this for both the ssl module and the hashlib module. FYI: I've opened ticket

Re: [Python-Dev] Addition of "pyprocessing" module to standard lib.

2008-05-23 Thread Georg Brandl
Nick Coghlan schrieb: Alex Martelli wrote: On Wed, May 21, 2008 at 1:53 PM, Raymond Hettinger <[EMAIL PROTECTED]> wrote: Putting this functionality in 2.6/3.0 would provide a really nice incentive to update from Py2.5. It would be a sad lost opportunity if this module had to wait another coupl

Re: [Python-Dev] Slice as a copy... by design?

2008-05-23 Thread Nick Coghlan
Greg Ewing wrote: Some way of explicitly requesting a view into another string might be desirable, but it shouldn't be the default behaviour for string slicing. Backporting 3.0's memoryview to 2.6 would be the way to go about that. Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | B