[issue45511] Batch-mode input() limited to 4095 characters on *NIX

2021-10-25 Thread Romuald Brunet
Romuald Brunet added the comment: This does not seems to be a copypaste issue. I've re-tested using xdotool to "manually" type 5000 characters in to a X terminal (gnome-terminal and xterm, to be sure) and got the same result. I also have 4 read(0, "...") with the last o

[issue45544] Close 2to3 issues and list them here

2021-10-20 Thread Romuald Brunet
Change by Romuald Brunet : -- nosy: +Romuald nosy_count: 3.0 -> 4.0 pull_requests: +27383 pull_request: https://github.com/python/cpython/pull/16826 ___ Python tracker <https://bugs.python.org/issu

[issue45511] input() method limited to 4095 characters on *NIX

2021-10-18 Thread Romuald Brunet
New submission from Romuald Brunet : When run in non-interactive mode and with a TTY stdin, the input() method will not read more than 4095 characters Simple example: >>> foo = input() # paste a 5000 character pasteboard (one line) >>> print(le

[issue42524] [doc] pdb access to return value

2021-08-05 Thread Romuald Brunet
Change by Romuald Brunet : -- pull_requests: +26106 pull_request: https://github.com/python/cpython/pull/27612 ___ Python tracker <https://bugs.python.org/issue42

[issue42524] [doc] pdb access to return value

2021-08-04 Thread Romuald Brunet
Romuald Brunet added the comment: I'm not sure I follow. You wish to "simply" update the doc? (and not update the retval to allow storing it into a varible. I'm OK with that) But if we choose this, I'm not sure what needs changing in the doctests :-? Another interrogation:

[issue26779] pdb continue followed by an exception in the same frame shows incorrect frame linenumber

2021-04-19 Thread Romuald Brunet
Romuald Brunet added the comment: I meant: this issue is fixed in 3.10 -- ___ Python tracker <https://bugs.python.org/issue26779> ___ ___ Python-bugs-list mailin

[issue26779] pdb continue followed by an exception in the same frame shows incorrect frame linenumber

2021-04-19 Thread Romuald Brunet
Romuald Brunet added the comment: Ran into a similar issue today This issue (and mine is fixed) in python 3.10. Most probaly related to #24565 fix -- nosy: +Romuald versions: +Python 3.7, Python 3.8, Python 3.9 ___ Python tracker <ht

[issue43703] xml.etree parser does not accept valid control characters

2021-04-02 Thread Romuald Brunet
Romuald Brunet added the comment: Thanks for the quick reply We're getting data from about a hundred different providers around the world; some of them not really keen on standards, so we already have some hacks to fix invalid XML. We'll add one to the list In that particular case, the XML

[issue43703] xml.etree parser does not accept valid control characters

2021-04-02 Thread Romuald Brunet
New submission from Romuald Brunet : Python XML parser (xml.etree) does not seems to allow control characters that are invalid in XML 1.0, but valid in XML 1.1 [1] [2] Considering the following sample: import xml.etree.ElementTree as ET bad = 'bar baz' print(ET.fromstring(bad

[issue42524] pdb access to return value

2020-12-01 Thread Romuald Brunet
Change by Romuald Brunet : -- keywords: +patch pull_requests: +22470 stage: -> patch review pull_request: https://github.com/python/cpython/pull/23601 ___ Python tracker <https://bugs.python.org/issu

[issue42524] pdb access to return value

2020-12-01 Thread Romuald Brunet
New submission from Romuald Brunet : When using the pdb module, there is currently no way to easy access the current return value of the stack This return value is accessed by the 'retval command' I propose using the currently unused argument to allow storing the return value in the local

[issue17393] stdlib import mistaken for local by import_fixer

2019-10-16 Thread Romuald Brunet
Change by Romuald Brunet : -- keywords: +patch pull_requests: +16376 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16826 ___ Python tracker <https://bugs.python.org/issu

[issue17393] stdlib import mistaken for local by import_fixer

2019-10-16 Thread Romuald Brunet
Romuald Brunet added the comment: Confirming that this issue is still present on 3.8 (and working on a fix) -- ___ Python tracker <https://bugs.python.org/issue17

[issue17393] stdlib import mistaken for local by import_fixer

2019-10-16 Thread Romuald Brunet
Change by Romuald Brunet : -- nosy: +Romuald ___ Python tracker <https://bugs.python.org/issue17393> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34307] NullHandler init refusing arguments

2018-08-01 Thread Romuald Brunet
Change by Romuald Brunet : -- keywords: +patch pull_requests: +8111 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34307> ___ ___ Py

[issue34307] NullHandler init refusing arguments

2018-08-01 Thread Romuald Brunet
New submission from Romuald Brunet : Context: I'm using a custom Handler that relies on a third-party library that may not be present try: from acme.logging import CustomHandler as BaseHandler except ImportError: import logging.NullHandler as BaseHandler class MoreCustomHandler

[issue32680] smtplib SMTP instances missing a default sock attribute

2018-01-26 Thread Romuald Brunet
Romuald Brunet <romuald.bru...@gmail.com> added the comment: My use case: try: s = SMTP('myhost') s.do_some_sending() finaly: if s is not None and s.sock is not None: s.quit() But I realize just now that in that case, if s was initialized correctly, its sock was inevitab

[issue32680] smtplib SMTP instances missing a default sock attribute

2018-01-26 Thread Romuald Brunet
Change by Romuald Brunet <romuald.bru...@gmail.com>: -- keywords: +patch pull_requests: +5192 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.pyt

[issue32680] smtplib SMTP instances missing a default sock attribute

2018-01-26 Thread Romuald Brunet
New submission from Romuald Brunet <romuald.bru...@gmail.com>: SMTP instances from the smtplib module are not creating their sock attribute consistently after __init__ When host is sent as parameter a sock object is created (and hopefully, connected) When the host is not sent, th

[issue24084] pstats: sub-millisecond display

2017-10-09 Thread Romuald Brunet
Romuald Brunet <romuald.bru...@gmail.com> added the comment: I figured we didn't want to change the size of the columns (+12 COL), but this could easily be done yes -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python

[issue31443] Possibly out of date C extension documentation

2017-09-17 Thread Romuald Brunet
Romuald Brunet added the comment: I'm not sure this is relevant, but I've just made a simple test on Windows (7) with my C extension using { … .tp_new = PyType_GenericNew } and the compiler did not complain (also the code worked as expected

[issue31443] Possibly out of date C extension documentation

2017-09-13 Thread Romuald Brunet
New submission from Romuald Brunet: In the "Defining New Types documentation" basics about tp_new -> PyType_GenericNew, the doc states: > We’d like to just assign this to the tp_new slot, but we can’t, for > portability sake, On some platforms or compilers, we can’t stat

[issue27558] SystemError inside multiprocessing.dummy Pool.map

2016-07-18 Thread Romuald Brunet
New submission from Romuald Brunet: Raising without a previous exception inside a method called from multiprocessing.dummy.Pool.map will trigger a SystemError. SystemError: PyEval_EvalFrameEx returned NULL without setting an error Traceback (most recent call last): File "example.py&q

[issue24084] pstats: sub-millisecond display

2015-04-30 Thread Romuald Brunet
New submission from Romuald Brunet: When running pstats with functions that take less than 0.5 millisecond (per call for example), the value shown is '0.000, which isn't really helpful. This patch aims to show the value in microseconds instead of seconds for values that would otherwise

[issue7980] time.strptime not thread safe

2014-03-18 Thread Romuald Brunet
Changes by Romuald Brunet romuald.bru...@gmail.com: -- nosy: +Romuald ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7980 ___ ___ Python-bugs-list

[issue7980] time.strptime not thread safe

2014-03-18 Thread Romuald Brunet
Romuald Brunet added the comment: This is a patch attempt to fix issue: import the _strptime module at time / datetime module load instead of method call. Please note that the test is not fully reliable: it may pass without the patch / on current version, since threaded execution isn't