[issue26107] PEP 511: code.co_lnotab: use signed line number delta to support moving instructions in an optimizer

Roundup Robot added the comment: New changeset 16f60cd918e0 by Victor Stinner in branch 'default': PEP 511 https://hg.python.org/peps/rev/16f60cd918e0 -- ___ Python tracker ___ _

[issue26146] PEP 511: Add ast.Constant to allow AST optimizer to emit constants

Roundup Robot added the comment: New changeset 16f60cd918e0 by Victor Stinner in branch 'default': PEP 511 https://hg.python.org/peps/rev/16f60cd918e0 -- ___ Python tracker ___ _

[issue24841] Some test_ssl network tests fail if svn.python.org is not accessible.

Martin Panter added the comment: The two changes to test_ssl.py look okay to me, although they will need updating since the Issue 24841 changeover to pythontest.net. But I don’t think it is a good idea to add ENOTCONN to the list of errors ignored by all transient_internet() tests. In most cas

[issue26215] remove gc from CPython

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue26215] remove gc from CPython

New submission from yuriy_levchenko: I permanently use gc.disable() but CPython create object with GC_Head. it's use big memory. I suggest add define to a few file that remove use GC_Head and allocate extra memory. -- messages: 259013 nosy: yuriy_levchenko priority: normal severity: nor

[issue26098] PEP 510: Specialize functions with guards

STINNER Victor added the comment: Patch version 5: implement PyFunction_RemoveSpecialized() and PyFunction_RemoveAllSpecialized() functions (with unit tests!). I'm not sure that PyFunction_RemoveSpecialized() must return 0 (success) if the removed specialized code doesn't exist (invalid index)

[issue26210] `HTMLParser.handle_data` may be invoked although `HTMLParser.reset` was invoked

Changes by Yannick Duchêne : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue26210] `HTMLParser.handle_data` may be invoked although `HTMLParser.reset` was invoked

Yannick Duchêne added the comment: > And I don't see how to stop the process either. I just did it with `raise StopIteration`, caught at a proper place (in the procedure which invokes `feed` and `close`), and it seems to be fine, I have no more strange behaviours. At least, I cannot see a clea

[issue9694] argparse required arguments displayed under "optional arguments"

Changes by tony gaetani : -- nosy: +tonygaetani ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue26194] Undefined behavior for deque.insert() when len(d) == maxlen

STINNER Victor added the comment: > -1 is the position before the last element ('C'). After popping-off extra > element the result can be ['A', 'B', None] or ['B', None, 'C']. Oh ok :-) Now I'm confused, I don't know what is the expected behaviour :-) -- __

[issue26210] `HTMLParser.handle_data` may be invoked although `HTMLParser.reset` was invoked

Xiang Zhang added the comment: Hmm, I don't know whether I am right or not. Let's wait for a core member to clarify. If I am wrong, I am quite sorry. I don't think invoking reset when parsing should raise an error(and I don't know how to achieve that). When to invoke a subroutine is determined

[issue26206] test_socket.testRecvmsgPeek() timeout on "AMD64 Debian root 3.x" buildbot

Martin Panter added the comment: A few more details from : * Affects Python 3 but not 2.7. * Offending test case: RecvmsgUDP6Test.testRecvmsgPeek() * Seems to correspond with the buildbot VM’s config recently being rebuilt

[issue26194] Undefined behavior for deque.insert() when len(d) == maxlen

Serhiy Storchaka added the comment: -1 is the position before the last element ('C'). After popping-off extra element the result can be ['A', 'B', None] or ['B', None, 'C']. -- ___ Python tracker _

[issue26211] HTMLParser: “AssertionError: we should not get here!”

Yannick Duchêne added the comment: I'm closing this issue, as the the issue http://bugs.python.org/issue26210 is the real one and this one seems to be a variant of the former. -- status: open -> closed ___ Python tracker

[issue26194] Undefined behavior for deque.insert() when len(d) == maxlen

STINNER Victor added the comment: > I would expected ['A', 'B', None]. Hum, it seems consistent with list behaviour, no? >>> x=list("abc") >>> x.insert(-1, "X") >>> x ['a', 'b', 'X', 'c'] -1 is the same than len(x)-1 (2 in this example). deque(['A', None, 'B'], maxlen=3) seems correct to me.

[issue26194] Undefined behavior for deque.insert() when len(d) == maxlen

Serhiy Storchaka added the comment: But the postcondition d[i] == newitem is broken if i is negative. >>> d = deque('ABC', maxlen=3) >>> d.insert(-1, None) >>> d deque(['A', None, 'B'], maxlen=3) I would expected ['A', 'B', None]. -- resolution: fixed -> status: closed -> open __

[issue26210] `HTMLParser.handle_data` may be invoked although `HTMLParser.reset` was invoked

Yannick Duchêne added the comment: Thanks Xiang, for the clear explanations. So an error should be triggered when `reset` is invoked while it should not. And remains the issue about how to stop the parser: should an exception be raised and caught at an outer invocation level? Something like ra

[issue26210] `HTMLParser.handle_data` may be invoked although `HTMLParser.reset` was invoked

Xiang Zhang added the comment: Actually it does move forward since in goahead, it first store a "copy" of the initial self.rawdata and use it to control the flow. If you make some change to self.rawdata when parsing, for example call reset, goahead can not feel it. But methods parse_* can. So

[issue17394] Add slicing support to collections.deque

Raymond Hettinger added the comment: Thank you for doing this work. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue26210] `HTMLParser.handle_data` may be invoked although `HTMLParser.reset` was invoked

Yannick Duchêne added the comment: The documentation says: > Reset the instance. Loses all unprocessed data. How can parsing go ahead with all unprocessed data lost? This is the “Loses all unprocessed data” which made me believe it is to stop it. May be the documentation is unclear. By the wa

[issue26214] textwrap should minimize number of breaks in extra long words

Changes by SilentGhost : -- nosy: +georg.brandl versions: +Python 3.6 -Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue26214] textwrap should minimize number of breaks in extra long words

Changes by Tuomas Salo : -- title: textwrap should minimize breaks -> textwrap should minimize number of breaks in extra long words ___ Python tracker ___ __

[issue26214] textwrap should minimize breaks

New submission from Tuomas Salo: This code: import textwrap textwrap.wrap("123 123 1234567", width=5) currently* produces this output: ['123', '123 1', '23456', '7'] I would expect the textwrap module to only break words when absolutely necessary. That is, I would have expected i

[issue26211] HTMLParser: “AssertionError: we should not get here!”

Yannick Duchêne added the comment: `reset` is called to stop the parser. If really `reset` should not be called during parser hooks execution, then the documentation should says so and an error should be raised when `reset` is invoked. -- ___ Pytho

<    1   2