[issue6489] Documentation of ElementTree.Element.getiterator implies element will always be included

Changes by Ezio Melotti : -- assignee: georg.brandl -> effbot nosy: +effbot priority: -> low ___ Python tracker ___ ___ Python-bugs-li

[issue6489] Documentation of ElementTree.Element.getiterator implies element will always be included

New submission from Mitchell Model : Documentation of ElementTree.Element.getiterator implies element will always be included, but it is only included if it matches. (It says "creates a tree iterator with the current element as the root" and also says, ambiguously, "iterates over this element and

[issue6488] ElementTree documentation refers to "path" with no explanation, and inconsistently

Changes by Ezio Melotti : -- assignee: georg.brandl -> effbot nosy: +effbot priority: -> low ___ Python tracker ___ ___ Python-bugs-li

[issue6488] ElementTree documentation refers to "path" with no explanation, and inconsistently

New submission from Mitchell Model : The documentation of ElementTree mentions "path" in describing the arguments to certain methods. However, "path" is never defined. I realize that a "path" is (at least a partial implementation of) an XPath, but there's nothing in the documentation to suggest t

[issue6486] Library doc introduction strangely points to "Built-in Objects" as a starting point

Ezio Melotti added the comment: I agree, the built-in functions page [1] is a good place where to start and indeed it's the page that follows the introduction [2]. The built-in object page/section [3] should be probably included/integrated with one of the other pages (and possibly rephrased too

[issue3341] "Suggest a change" link

Ezio Melotti added the comment: An easier approach would be to open the "create a new issue" page of the tracker when the user clicks on "suggest a change". The title can be set automatically to something like "Doc suggestion on Page XYZ". The "Documentation" component and the version could be s

[issue6487] Some index entries appear in black

Changes by Amaury Forgeot d'Arc : -- assignee: -> georg.brandl nosy: +georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing

[issue6487] Some index entries appear in black

New submission from Mitchell Model : Some index entries appear in black. I think this happens only with top-level entries. I can't find any pattern to which ones are in black, so it doesn't look like black has any actual significance. The C general index page is rich with examples. -- me

[issue6486] Library doc introduction strangely points to "Built-in Objects" as a starting point

New submission from Mitchell Model : At the end of the introduction page of the library documentation there is a strange suggestion to begin with "Built-in Objects" as a starting point. The "Built-in Objects" page consists of two paragraphs that will surely mystify people new to Python. I'm not

[issue5210] zlib does not indicate end of compressed stream properly

Ezio Melotti added the comment: Thanks for the patch! Can you provide tests too? -- nosy: +ezio.melotti priority: -> normal stage: -> test needed versions: +Python 2.7, Python 3.2 -Python 3.0 ___ Python tracker _

[issue6485] is_finished not exported by zlib

Changes by Ezio Melotti : -- resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> zlib does not indicate end of compressed stream properly ___ Python tracker ___

[issue6485] is_finished not exported by zlib

Jean-Paul Calderone added the comment: This is a duplicate of #5210, which has a patch attached. -- nosy: +exarkun ___ Python tracker ___

[issue6485] is_finished not exported by zlib

New submission from Travis H. : The zlib C library has the capability to indicate the end of a compressed stream by returning a Z_STREAM_END from a call to inflate. This allows uncompressed data to follow some compressed data. It is necessary to know when the end of the compressed stream has be

[issue6480] code.runsource() parsing bug

Sean added the comment: Seems to me it's probably an issue with the newlines, but from help(code.compile_command): Compile a command and determine whether it is incomplete. Arguments: source -- the source string; may contain \n characters filename -- optional filename

[issue6484] No unit test for mailcap module

Martin v. Löwis added the comment: Please also identify yourself with your full name. -- nosy: +loewis ___ Python tracker ___ ___ Pyth

[issue6449] Improve/update python.org/dev/

Ezio Melotti added the comment: Thanks for taking care of it. There's also a typo ("thissmall") in the first line of http://www.python.org/dev/faq/#why-should-i-use-svn-switch -- ___ Python tracker

[issue6484] No unit test for mailcap module

R. David Murray added the comment: Welcome! Please read the material at http://www.python.org/dev if you haven't already, especially the dev FAQ. At the moment the case can't be assigned to you in the tracker interface, but your claiming it in the text is sufficient. Please write the tests an

[issue6484] No unit test for mailcap module

New submission from Greg : There is currently no test_mailcap or any other standalone unit test for the mailcap module. The only existing test is a self-test at the end of the module. I would like to be assigned to work on this patch. (Why am I assigning myself to write tests for a small, older

[issue6418] unittest.TestProgram change breaks nose

Michael Foord added the comment: Committed to trunk in revision 74007. -- assignee: -> michael.foord resolution: -> accepted status: open -> closed ___ Python tracker ___ _

[issue5672] Implement a way to change the python process name

Changes by Floris Bruynooghe : -- nosy: +flub ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue6483] Modules are not deallocated correctly if m_size = -1

Changes by Benjamin Peterson : -- assignee: -> loewis nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue6483] Modules are not deallocated correctly if m_size = -1

New submission from Julian Andres Klode : The documentation states that m_size should be -1 if no additional memory is needed. But this causes the objects inside the module to not be deallocated at all. The attached module (test) stores an object of a type 'Test', which prints "Deallocation is h