[issue8166] hashlib constructors for sha224, sha256, sha384, sha512 missing in Python 3.1.2rc1 with openssl 0.9.7

Ned Deily added the comment: Should be: "Still later, r77608 was auto-merged [...]" -- ___ Python tracker ___ ___ Python-bugs-list mai

[issue8166] hashlib constructors for sha224, sha256, sha384, sha512 missing in Python 3.1.2rc1 with openssl 0.9.7

New submission from Ned Deily : 3.1.2 Release Blocker If Python 3.1.2rc1 is built with openssl 0.9.7 (which lacks support for sha256 and sha512), hashlib is supposed to substitute use of built-in C implementations for them. With 3.1.2rc1, the "built-in" versions are available via hashlib.new

[issue8165] logging.handlers.RotatingFileHandler fails when delay parameter is set to True

Changes by Vinay Sajip : -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/optio

[issue8165] logging.handlers.RotatingFileHandler fails when delay parameter is set to True

Vinay Sajip added the comment: I've investigated: this issue was fixed in r68829 dated 20 Jan, 2009. This was after the release of 2.6.1 but before the release of 2.6.2. Please upgrade to Python 2.6.2. -- ___ Python tracker

[issue8165] logging.handlers.RotatingFileHandler fails when delay parameter is set to True

Vinay Sajip added the comment: I've investigated: this issue was fixed in r68829 dated 20 Jan, 2009. This was after the release of 2.6.1 but before the release of 2.6.2. Please upgrade to Python 2.6.2. -- resolution: works for me -> out of date status: pending -> closed _

[issue8165] logging.handlers.RotatingFileHandler fails when delay parameter is set to True

Vinay Sajip added the comment: Please check that there is nothing wrong with your Python installation. I get this result: vi...@eta-jaunty:~/projects/scratch$ ls testing.log ls: cannot access testing.log: No such file or directory vi...@eta-jaunty:~/projects/scratch$ cat rfhtest.py import log

[issue7512] shutil.copystat may fail EOPNOTSUPP

Joerg Sonnenberger added the comment: A better approach might be to change the function to: def copystat(src, dst): st = os.stat(src) st_dst = os.stat(dst) mode = stat.S_IMODE(st.st_mode) mode_dst = stat.S_IMODE(st_dst.st_mode) if hasattr(os, 'utime'): if st.st_atime != st_dst.st_

[issue8104] socket.recv_into doesn't support a memoryview as an argument

Antoine Pitrou added the comment: Committed in trunk, and additional tests ported to py3k. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker __

[issue8162] logging.disable() incoherency

Vinay Sajip added the comment: - Original Message > From: Pascal Chambon > I guess it's not important if messages > of severity 0 will allways be ignored with the current semantic > ? Levels are supposed to be positive integers, zero is a special value indicating a level that isn

[issue8155] Incompatible change to test.test_support.check_warnings behaviour

Nick Coghlan added the comment: Ah, I didn't notice that there were already tests for this in test_warnings (that's what I get for commenting late at night). Updated patch looks good. -- ___ Python tracker __

[issue8164] (lambda:"foo").func_doc

Benjamin Peterson added the comment: Fixed in r79034. -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue8165] logging.handlers.RotatingFileHandler fails when delay parameter is set to True

Changes by Benjamin Peterson : -- assignee: -> vinay.sajip nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue8165] logging.handlers.RotatingFileHandler fails when delay parameter is set to True

New submission from Eli Courtwright : Here's a summary of the issue (also presented at http://stackoverflow.com/questions/2465073) When I run the following code {{{ import logging from logging.handlers import RotatingFileHandler rfh = RotatingFileHandler("testing.log", delay=True) logging.get

[issue8155] Incompatible change to test.test_support.check_warnings behaviour

Florent Xicluna added the comment: Patch updated. -- Added file: http://bugs.python.org/file16573/issue8155_check_warnings_quiet_v2.diff ___ Python tracker ___ _

[issue8155] Incompatible change to test.test_support.check_warnings behaviour

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file16572/issue8155_check_warnings_quiet.diff ___ Python tracker ___ ___ Pyt

[issue8162] logging.disable() incoherency

Pascal Chambon added the comment: Thanks you B-) I guess it's not important if messages of severity 0 will allways be ignored with the current semantic ? -- ___ Python tracker

[issue477863] Print warning at shutdown if gc.garbage not empty

Changes by Antoine Pitrou : -- stage: -> needs patch title: New gc work -> Print warning at shutdown if gc.garbage not empty versions: +Python 3.2 -Python 3.1 ___ Python tracker __

[issue477863] New gc work

Changes by Antoine Pitrou : -- nosy: +flox ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue1518] Fast globals/builtins access (patch)

Antoine Pitrou added the comment: Thanks Collin, recommend closing then. -- ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue1518] Fast globals/builtins access (patch)

Collin Winter added the comment: Antoine: yes, this optimization is already implemented in the Unladen JIT. -- ___ Python tracker ___

[issue1518] Fast globals/builtins access (patch)

Antoine Pitrou added the comment: There probably isn't any point in such a complication, until perhaps we have a JIT that magnifies the improvement. (but I assume the JIT will be able to treat references to globals and builtins as "frozen" using its own logic) --

[issue3581] failures in test_uuid

Changes by Antoine Pitrou : -- assignee: pitrou -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue3580] failures in test_os

Changes by Antoine Pitrou : -- assignee: pitrou -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue3783] dbm.sqlite proof of concept

Changes by Antoine Pitrou : -- type: behavior -> feature request ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue2746] ElementTree ProcessingInstruction uses character entities in content

Changes by Antoine Pitrou : -- nosy: +flox resolution: accepted -> fixed status: pending -> closed ___ Python tracker ___ ___ Python-bu

[issue7682] Optimisation of if with constant expression

Changes by Antoine Pitrou : -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue3890] ssl.SSLSocket.recv() implementation may not work with non-blocking sockets

Antoine Pitrou added the comment: Will apply after 2.6.5. -- assignee: -> pitrou resolution: -> accepted stage: patch review -> commit review ___ Python tracker ___ ___

[issue7512] shutil.copystat may fail EOPNOTSUPP

Antoine Pitrou added the comment: Barry, I suppose this doesn't warrant being a release blocker for 2.6.5, but in any case you're welcome to advise. -- nosy: +barry ___ Python tracker _

[issue7512] shutil.copystat may fail EOPNOTSUPP

Antoine Pitrou added the comment: For the record, this seems to break Mercurial on NFS-mounted repositories: http://www.selenic.com/pipermail/mercurial/2010-March/030716.html -- ___ Python tracker _

[issue7512] shutil.copystat may fail EOPNOTSUPP

Changes by Antoine Pitrou : -- assignee: -> pitrou nosy: +pitrou resolution: -> accepted stage: -> commit review ___ Python tracker ___

[issue8164] (lambda:"foo").func_doc

New submission from Armin Rigo : Lambdas are a bit confused about their docstrings. Usually they don't have any, but: >>> (lambda x: "foo"+x).func_doc 'foo' -- keywords: easy messages: 101233 nosy: arigo priority: low severity: normal status: open title: (lambda:"foo").func_d

[issue3928] os.mknod missing on Solaris

Jesús Cea Avión added the comment: Sorry, Barry. Don't know what happened. Probably write a followup without reloading the page and "undid" previous changes. I keep my issues permanently open in firefox tabs. I will try to be more careful. -- ___

[issue2531] float compared to decimal is silently incorrect.

Mark Dickinson added the comment: For anyone interested, there's an ongoing python-dev discussion about how to resolve this at http://mail.python.org/pipermail/python-dev/2010-March/098437.html -- ___ Python tracker

[issue8142] libffi update to 3.0.9

Matthias Klose added the comment: the ports which are maintained separately still need an update: libffi_msvc libffi trunk now has a port to x86/msvc. might require some extra updates from libffi. libffi_osx: 3.0.9 has support for darwin on powerpc and x86 libffi_wince: same, support

[issue8034] logging: Improve error handing in RotatingFileHandler.doRollover()

Vinay Sajip added the comment: Closing, as no feedback received. Please feel free to reopen when you have the answer to my question! -- resolution: -> invalid status: pending -> closed ___ Python tracker

[issue8162] logging.disable() incoherency

Vinay Sajip added the comment: I've updated the docstring and documentation to be more precise (r79026). -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue8155] Incompatible change to test.test_support.check_warnings behaviour

Nick Coghlan added the comment: On a second look, there are a couple of things missing: - the default value didn't actually get changed! - we should add an explicit test that the no argument behaviour doesn't raise a warning by default Since we don't really have an existing test suite for the

[issue3890] ssl.SSLSocket.recv() implementation may not work with non-blocking sockets

Jim Smyth added the comment: Is there any chance of this being resolved in time for any 2.x release? I have a non-blocking application that I recently switched over to SSL and ran into this bug. I can work around it by trying to shorten the messages and beefing up the buflen, but these soluti

[issue8155] Incompatible change to test.test_support.check_warnings behaviour

Florent Xicluna added the comment: I hesitate to do it differently: with check_warnings(('', RuntimeWarning)): ==> translate to check_warnings(('', RuntimeWarning), quiet=False) with check_warnings(): ==> translate to check_warnings(quiet=True) If the developer passes some arguments to the

[issue8155] Incompatible change to test.test_support.check_warnings behaviour

Nick Coghlan added the comment: On a quick read through, the patch looks fine to me. I actually agree it would be nice if we could keep the "quiet=True" default (since it is a better match for the feature set we want in our own tests), but I see the compatibility issue as a deal breaker for t

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Ezio Melotti added the comment: I took part of Florent latest patch, changed a few things and committed it in r79023. -- ___ Python tracker ___ _

[issue8162] logging.disable() incoherency

Changes by Brian Curtin : -- nosy: +vinay.sajip priority: -> normal versions: +Python 3.1, Python 3.2 ___ Python tracker ___ ___ Pytho

[issue8155] Incompatible change to test.test_support.check_warnings behaviour

Florent Xicluna added the comment: here come the patch. -- components: +Tests keywords: +easy, patch stage: test needed -> patch review versions: +Python 2.7 Added file: http://bugs.python.org/file16572/issue8155_check_warnings_quiet.diff ___ Python

[issue8142] libffi update to 3.0.9

Matthias Klose added the comment: no access to solaris hardware. please could you run the libffi testsuite on this machine? make sure that expect is installed. -- ___ Python tracker ___

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Florent Xicluna added the comment: > Checking the pybsddb 4.8.4devel with current trunk I still see this: It is because the "test_early_close" module calls resetwarnings(). It defeats the filter in the "threading" module. You may change the test case with a context manager: with warnings.ca

[issue3783] dbm.sqlite proof of concept

Changes by Florent Xicluna : -- nosy: +flox ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue1275] bsddb closing a DB object before all DBCursors using it are closed crashes

Changes by Jesús Cea Avión : -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue3783] dbm.sqlite proof of concept

Changes by Jesús Cea Avión : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/pytho

[issue8142] libffi update to 3.0.9

Florent Xicluna added the comment: re-opened to track the issue on Sparc Solaris -- resolution: fixed -> stage: -> needs patch status: closed -> open ___ Python tracker ___ ___

[issue8163] DictionaryServices module broken in python2.6 and later

Florent Xicluna added the comment: See also: * http://pypi.python.org/pypi/pyobjc-framework-DictionaryServices/ -- nosy: +flox ___ Python tracker ___ ___

[issue8163] DictionaryServices module broken in python2.6 and later

Senthil Kumaran added the comment: This module is not part of Python stdlib. MacOSX might have bundled it by default. Reporting it to Apple might help. -- nosy: +orsenthil resolution: -> invalid status: open -> closed ___ Python tracker

[issue8163] DictionaryServices module broken in python2.6 and later

New submission from Shashwat Anand : I am able to call DictionaryServices module from python2.5 and later. However it works correctly only on python2.5. Below is the stack-trace on using DictionaryServices on python2.5, python2.6 and python2.7 Shashwat-Anands-MacBook-Pro:PyObjCTest l0nwlf$ pyt

[issue8162] logging.disable() incoherency

New submission from Pascal Chambon : Hello I see some trouble in the semantic of logging.disable(lvl) : according to the doc (and docstrings), it's the same as a logger.setLevel(lvl) called on all logger, but in reality it doesn't act the same way : when we call logger.setLevel(lvl), log messa

[issue6541] SpooledTemporaryFile breakages

Changes by Dan : -- nosy: +danohuiginn ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/ma

[issue8161] inconsistency behavior in ctypes.c_char_p dereferencing

New submission from Jackson Yang : # Python 3.1.2rc1 (r312rc1:78742, Mar 7 2010, 07:49:40) # [MSC v.1500 32 bit (Intel)] on win32 import ctypes class T(ctypes.Structure): _fields_ = ( ('member', ctypes.c_char * 16), ) # dereference a c_char_Array variable would

[issue8153] 'set' union() fails in specific use case

Frank Rene Schaefer added the comment: Thanks, for the comments. I got it. In German we would say 'I was standing on the water hose' ... That is, something was choking the flow of my thoughts. Best Regards Frank -- ___ Python tracker