[issue7467] The zipfile module does not check files' CRCs, including in ZipFile.testzip

New submission from Douglas Turk : The zipfile module does not calculate the CRC of files in a zipfile as they are read as of Python 2.6. The old ZipFile.read function in Python 2.5 used to do this, and ZipFile.testzip appears to rely on ZipFile.read to check the CRC. This means that ZipFile.test

[issue6692] asyncore kqueue support

Changes by Antoine Pitrou : -- assignee: -> josiahcarlson nosy: +josiahcarlson priority: -> normal stage: -> needs patch ___ Python tracker ___

[issue7465] Call to another class's constructor in unittest.TestCase.setUp returns the same instance multiple times

R. David Murray added the comment: Heh, that first b = baseClass(); del b wasn't supposed to be there and doesn't change the result, just in case you were wondering. -- ___ Python tracker __

[issue7465] Call to another class's constructor in unittest.TestCase.setUp returns the same instance multiple times

R. David Murray added the comment: Yes, this working as intended. Consider: Python 2.7a1+ (trunk:76725, Dec 9 2009, 09:26:36) [GCC 4.4.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> class baseClass(object): ... def __init__(self, testList=[]): ...

[issue7466] Segmentation fault after about 20 seconds on lenovo T500

David W. Lambert added the comment: Further isolation, following change removes segmentation fault: digital_roots = tuple(map(digital_root,factorization)) becomes digital_roots = [digital_root(factor) for factor in factorization] --

[issue7465] Call to another class's constructor in unittest.TestCase.setUp returns the same instance multiple times

Changes by Aaron Altman : -- title: Call to another class's constructor in unittest.TestCase.setUp returns the same instance -> Call to another class's constructor in unittest.TestCase.setUp returns the same instance multiple times ___ Python tracke

[issue7466] Segmentation fault after about 20 seconds on lenovo T500

New submission from David W. Lambert : ''' This brute [possibly a] solution to http://projecteuler.net/index.php?section=problems&id=159 causes segmentation fault. $ p3 # an AMD 64 bit build. Python 3.1.1 (r311:74480, Oct 2 2009, 12:29:57) [GCC 4.3.3] on linux2 T

[issue7465] Call to another class's constructor in unittest.TestCase.setUp returns the same instance

New submission from Aaron Altman : Not sure if this is intended behavior. I have a baseClass I'm writing tests for. My test architecture has an instance of this baseClass assigned as a member of TestBaseClass(unittest.TestCase) in TestBaseClass.setUp. The problem occurs when tests in TestBaseC

[issue7459] Magic word incorrect in Python 3

Benjamin Peterson added the comment: Fixed in r76731. Thanks. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue5949] IMAP4_SSL spin because of SSLSocket.suppress_ragged_eofs

R. David Murray added the comment: Committed to py3k in r76730 with the suggested additional test. -- ___ Python tracker ___ ___ Pytho

[issue5949] IMAP4_SSL spin because of SSLSocket.suppress_ragged_eofs

R. David Murray added the comment: Unfortunately, the SocketServer patches introduced other issues (see for example issue 6381). So I'm reluctant to backport those changes, since as you say no one had reported problems. It seems like the chance of inadvertently breaking someone's working 2.6 c

[issue1123727] gensuitemodule.processfile fails

Changes by Ronald Oussoren : -- priority: normal -> low ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue6692] asyncore kqueue support

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue7154] urllib.request system proxy configuration lookup broken for OS X in Python 3

Ronald Oussoren added the comment: I agree that _scproxy should be ported to the 3.x trees. Such a port should be fairly straightforward, but is harder than just copying files over due to the str/unicode changes in the 3.x tree. -- ___ Python track

[issue6834] use different mechanism for pythonw on osx

Ronald Oussoren added the comment: FWIW: I now have a 2.7 tree with the new pythonw on my machine, open issues are: * Ensure IDLE.app gets build in such a way that the GUI works for all supported universal binaries (including a 4-way build on 10.5, where the system Tk doesn't work in 64-b

[issue7452] Invalid mnemonic 'fnstcw'

Ronald Oussoren added the comment: BTW. Am I correct when I state that this issue has been fixed and can be closed? -- ___ Python tracker ___ ___

[issue7452] Invalid mnemonic 'fnstcw'

Ronald Oussoren added the comment: Ned: the best way to ensure universal builds don't get broken is through the buildbots. AFAIK there are no buildbots that create universal binaries at the moment. Sadly enough I don't have the resources to provide one. Mark: Mac/README explains how to build

[issue6472] Inconsistent use of "iterator" in ElementTree doc & diff between Py and C modules

flox added the comment: Patch for the documentation. (source: upstream documentation) -- Added file: http://bugs.python.org/file15513/issue6472_upstream_docs.diff ___ Python tracker

[issue6911] Document changes in asynchat

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue5949] IMAP4_SSL spin because of SSLSocket.suppress_ragged_eofs

Scott Dial added the comment: It seems that on the py3k branch, the EOF situation is handled roughly in the same manner (the broken line is returned) and ultimately the IMAP4.abort exception is raised because b'* ' is an invalid response (the 'OK' having been dropped). IOW, it passes the EOF tes

[issue5949] IMAP4_SSL spin because of SSLSocket.suppress_ragged_eofs

R. David Murray added the comment: I'll take a look at the socketserver issue, but probably not today. In the meantime, can you take a look at this port of the tests to py3k when you get a chance? The tests pass without changes to imaplib, but the imaplib code is a bit different in py3k. I'd

[issue5949] IMAP4_SSL spin because of SSLSocket.suppress_ragged_eofs

Scott Dial added the comment: I've revised my opinion. If you extract out only the changes to SocketServer and ignore the others, then I would consider it a good backport (fixes bugs only). I have attached such a patch. BTW, with this patch, you can remove the shutdown() call in the test_imapli

[issue5949] IMAP4_SSL spin because of SSLSocket.suppress_ragged_eofs

Scott Dial added the comment: I tracked the necessary change to r73638 and issue6267. However, I am not sure it is in scope to backport all of that. The only changed actually needed from this set to make SocketServer behave correctly with a SSLSocket is: def close_request(self, request):

[issue5949] IMAP4_SSL spin because of SSLSocket.suppress_ragged_eofs

R. David Murray added the comment: Do you know which patches? It's possible they just haven't been evaluated for backport yet, and if that's so I'll see if I can take care of it. -- ___ Python tracker

[issue7464] circular reference in HTTPResponse by urllib2

New submission from Kristján Valur Jónsson : in urllib2, you will find these lines: # Wrap the HTTPResponse object in socket's file object adapter # for Windows. That adapter calls recv(), so delegate recv() # to read(). This weird wrapping allows the returned object to

[issue5949] IMAP4_SSL spin because of SSLSocket.suppress_ragged_eofs

Changes by Scott Dial : Removed file: http://bugs.python.org/file15509/test_imaplib_issue5949-py26.patch ___ Python tracker ___ ___ Python-bugs

[issue5949] IMAP4_SSL spin because of SSLSocket.suppress_ragged_eofs

Scott Dial added the comment: I have attached a proper backport for the 2.6 maintenance branch. There were some features (not bugfixes) of the trunk that the tests depended on, which are not backported. However, the tests still hang, because there are changes to SocketServer.py that were not ba

[issue5949] IMAP4_SSL spin because of SSLSocket.suppress_ragged_eofs

Changes by Scott Dial : Removed file: http://bugs.python.org/file15508/test_imaplib_issue5949-py26.patch ___ Python tracker ___ ___ Python-bugs

[issue5949] IMAP4_SSL spin because of SSLSocket.suppress_ragged_eofs

Changes by Scott Dial : Added file: http://bugs.python.org/file15509/test_imaplib_issue5949-py26.patch ___ Python tracker ___ ___ Python-bugs-l

[issue7316] Add a timeout functionality to common locking operations

Changes by Antoine Pitrou : -- assignee: -> pitrou stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue7452] Invalid mnemonic 'fnstcw'

Ned Deily added the comment: Mark, I wasn't ranting at you or Ronald or anyone in particular. It's no secret that Python's build system is complex and fragile in some areas. On the other hand, the build system is ambitious, covering a wide variety of platforms and variants, and is largely s

[issue5949] IMAP4_SSL spin because of SSLSocket.suppress_ragged_eofs

Changes by Scott Dial : Added file: http://bugs.python.org/file15508/test_imaplib_issue5949-py26.patch ___ Python tracker ___ ___ Python-bugs-l

[issue5949] IMAP4_SSL spin because of SSLSocket.suppress_ragged_eofs

R. David Murray added the comment: Added skipping of the SSL tests if ssl is not available in r76727. -- ___ Python tracker ___ ___ Py

[issue7459] Magic word incorrect in Python 3

Changes by Benjamin Peterson : -- assignee: -> benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7451] improve json decoding performance

Antoine Pitrou added the comment: > I wonder if you can make a patch for 2.6 python branch. No, 2.6 doesn't have the same C accelerator in the first place. -- ___ Python tracker ___

[issue5949] IMAP4_SSL spin because of SSLSocket.suppress_ragged_eofs

R. David Murray added the comment: Applied to trunk in r76276. However, when I tried to backport it to 2.6, the tests hang in test_connect for the SSL version. The hang isn't interruptible by ctl-C. Perhaps there's some SSL fix that hasn't been backported, and if so it would be nice to figure

[issue7451] improve json decoding performance

Valentin Kuznetsov added the comment: I wonder if you can make a patch for 2.6 python branch. -- ___ Python tracker ___ ___ Python-bug

[issue7452] Invalid mnemonic 'fnstcw'

Mark Dickinson added the comment: A reply to Ned from the person who introduced this bug in the first place (sorry, folks): [Ned] > 1. How to make core developers and patch contributors more aware of the > special requirements of multi-architecture builds? I guess I was already aware of this,

[issue7459] Magic word incorrect in Python 3

Changes by Antoine Pitrou : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue7459] Magic word incorrect in Python 3

Antoine Pitrou added the comment: I think the point is more of self-documentation not being deceiving. Here someone tries to use import.c 's embedded documentation about existing magic numbers and he/she gets mystified because the actual magic number doesn't seem to correspond. Also, it's true

[issue7463] PyDateTime_IMPORT() causes compiler warnings

New submission from Murray Cumming : At least in Python 2.5 and 2.6 (I haven't checked newer versions), the PyDateTime_IMPORT() macro passes string literals to a function that takes non-const char* parameters: #define PyDateTime_IMPORT \ PyDateTimeAPI = (PyDateTime_CAPI*) PyCObject_Impo

[issue7452] Invalid mnemonic 'fnstcw'

Ned Deily added the comment: I agree that adding the definitions of HAVE_GCC_ASM_FOR_X87 to pymacconfig.h solves the problem. [mini-rant on] This problem is another illustration of how easy it is to inadvertently introduce significant bugs in the OS X multi-architecture support, bugs which c