[issue19045] Make on Solaris 11 x64 with OracleStudio12.3 failed

Changes by Ned Deily : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue19054] Descriptors howto

Changes by Ned Deily : -- nosy: +rhettinger versions: -Python 2.6, Python 3.1, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list

[issue19052] Python's CGIHTTPServer does not handle Expect: 100-continue gracefully which results in some Post requests being handled slowly.

R. David Murray added the comment: No need to apologize for missing the issue. I missed it too, and I was looking for it because I thought I remembered something...but only found the one I referenced and assumed that that was what I was remembering. -- stage: -> committed/rejected ty

[issue19055] Regular expressions: * does not match as many repetitions as possible.

R. David Murray added the comment: The documentation is correct and unambiguous. Regular expressions just aren't very intuitive. The documentation says "Causes the resulting RE to match 0 or more repetitions of the preceding RE, as many repetitions as are possible." "as many repetitions of

[issue18990] Remove unnecessary API inconsistency from ElementTree.XMLPullParser.close()

Stefan Behnel added the comment: Inviting some more people to get this patch reviewed in a timely fashion. Given that it's a cleanup of a newly introduced API, it must go in before the first beta release of 3.4. The even wider cleanup would be to make XMLPullParser inherit from XMLParser and

[issue18990] Return root element from ElementTree.XMLPullParser.close() to match ElementTree.XMLParser

Nick Coghlan added the comment: I clarified the issue title to actually explain the concern and the proposed fix (i.e. close() on XMLPullParser doesn't currently return the root, which is inconsistent with the XMLParser API). This sounds like a reasonable change to me, but the docs also need t

[issue18990] Return root element from ElementTree.XMLPullParser.close() to match ElementTree.XMLParser

Stefan Behnel added the comment: I'm not entirely happy about the docs anyway. Most people just want to loop over iterparse() and be done (use case being to save memory). The new parser class is a rather special and more complex thing that we shouldn't let innocent users run into that easily.

[issue19048] itertools.tee doesn't have a __sizeof__ method

Martin v. Löwis added the comment: Antoine: in (my experience of) memory analysis, the size of a single object is mostly irrelevant. If you need to know how much memory something consumes, you typically want to know the memory of a set of objects. So this is the case that really must be suppor

<    1   2