[issue36620] Documentation missing parameter for Itertools.zip_longest

2019-04-12 Thread Charles Merriam
Charles Merriam added the comment: Hi Cheryl, No. I've dealt with the Team Python long cycles for random pull requests before. Charles On Fri, Apr 12, 2019 at 2:27 PM Cheryl Sabella wrote: > > Cheryl Sabella added the comment: > > Good catch! In the same section

[issue36620] Documentation missing parameter for Itertools.zip_longest

2019-04-12 Thread Charles Merriam
New submission from Charles Merriam : On page: https://docs.python.org/3.8/library/itertools.html In the heading summary, in the "Iterators terminating on the shortest input sequence:" section, in the "zip_longest()" table row, in the "Arguments" column, the te

[issue31640] Document exit() from parse_args

2017-09-29 Thread Charles Merriam
New submission from Charles Merriam : It is unexpected to testers and users to ArgParse that it terminates the process; one usually expects an error code. Fix by modifying documentation to section 16.4.4 The parse_args() Method. Change the words "Return the populated namespace."

[issue8243] curses writing to window's bottom right position raises: `_curses.error: addstr() returned ERR'

2014-05-23 Thread Charles Merriam
Charles Merriam added the comment: My typo. Documentation verbiage was included in the bug report. Submitting a patch to the documentation is a harder than just rewriting the library. I speak English, MarkDown, HTML, JavaScript, and even RST. I don't speak Sphinx, DocBook, or TeX. O

[issue21562] curses getsxy() should be curses getxy() in https://docs.python.org/3/library/curses.html#curses.cursxy

2014-05-23 Thread Charles Merriam
New submission from Charles Merriam: https://docs.python.org/3/library/curses.html#curses.cursxy The symbol 'getsxy' does not exist in the curses library. The correct symbol is 'getxy'. -- assignee: docs@python components: Documentation messages: 218986 nosy: C

[issue8243] curses writing to window's bottom right position raises: `_curses.error: addstr() returned ERR'

2014-05-23 Thread Charles Merriam
Charles Merriam added the comment: Some more information to just nail this thing that's been here forever. 1. This has been an issue in Python since at least 2001. 2. It is a duplicate of the item 441129 which was closed as won't fix. 3. It is bug in curses implementations. 4. T

[issue2684] Logging Module still failing for %(filename)s, __init__

2008-04-25 Thread Charles Merriam
Charles Merriam <[EMAIL PROTECTED]> added the comment: In my installation, line 1327 is within the logging.debug() function, specifically at the call to apply(root.debug, (msg,)+args, kwargs) [EMAIL PROTECTED]:~/py$ rm *.pyc [EMAIL PROTECTED]:~/py$ python x.py DEBUG:logging/__init__.p

[issue2684] Logging Module still failing for %(filename)s, __init__

2008-04-24 Thread Charles Merriam
Charles Merriam <[EMAIL PROTECTED]> added the comment: oops, last line should be "exits the stack frames for the logging module. This should be a once-per-program-execution event" Hmm.. tracker should have a preview button. __ Tracker <[EMAI

[issue2684] Logging Module still failing for %(filename)s, __init__

2008-04-24 Thread Charles Merriam
New submission from Charles Merriam <[EMAIL PROTECTED]>: About same as problem in 2.4 Issue1470422 closed without a test case on MacOS X/Python 2.4. Also same as http://mail.python.org/pipermail/python-bugs-list/2004-July/024111.html and so on back for years. What happens: [EMAIL PRO