[issue17390] display python version on idle title bar
Changes by Kent Johnson : -- nosy: -kjohnson ___ Python tracker <http://bugs.python.org/issue17390> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17719] IDLE help text refers to incorrect Python version
Kent Johnson added the comment: Note: this text does not appear in Doc/library/idle.rst so it does not have to be corrected there. -- ___ Python tracker <http://bugs.python.org/issue17719> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17719] IDLE help text refers to incorrect Python version
New submission from Kent Johnson: The IDLE help text says, "Running without a subprocess: (DEPRECATED in Python 3.5 see Issue 16123)." According to the referenced issue, this feature is scheduled to be deprecated in *3.4* and *removed* in 3.5. The attached patch corrects the help text. -- assignee: docs@python components: Documentation files: deprecated_in_3.4.patch keywords: patch messages: 186769 nosy: docs@python, kjohnson priority: normal severity: normal status: open title: IDLE help text refers to incorrect Python version type: behavior versions: Python 3.4 Added file: http://bugs.python.org/file29808/deprecated_in_3.4.patch ___ Python tracker <http://bugs.python.org/issue17719> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17390] display python version on idle title bar
Kent Johnson added the comment: issue17390_editor_title.patch is not correct, it changes the title on any window that inherits from EditorWindow, including the shell window. Here is a new patch that changes short_title() instead of saved_change_hook(), so it can be overridden by derived classes. This is the same method used to change the title of the shell window. Derived classes of EditorWindow are PyShellEditorWindow and OutputWindow. OutputWindow overrides short_title() and IIUC PyShellEditorWindow should use the same title as a normal editor window. -- nosy: +kjohnson Added file: http://bugs.python.org/file29804/issue17390_editor_title_rev2.patch ___ Python tracker <http://bugs.python.org/issue17390> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10303] small inconsistency in tutorial
Kent Johnson added the comment: Attached patch deletes the referenced sentence. -- keywords: +patch nosy: +kjohnson Added file: http://bugs.python.org/file19536/issue10303.diff ___ Python tracker <http://bugs.python.org/issue10303> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7935] Cross-reference ast.literal_eval() from eval() docs
New submission from Kent Johnson : eval() is a known security hole. Since Python 2.6 ast.literal_eval() provides a better alternative in many cases. literal_eval() is not as well known as eval() and not easy to find even if you know it exists (but don't remember the name). eval() comes up over and over in the Python-tutor list and the attendant warnings are repeated ad nauseum; literal_eval() is rarely mentioned as an alternative. Suggestion: in the docs for eval(), put a warning about security risks and a cross-reference to literal_eval(). For example: Warning: eval() executes any expression and should be used only with trusted input. ast.literal_eval() is a safe alternative for evaluating expressions containing only Python literals. Thanks! -- assignee: georg.brandl components: Documentation messages: 99363 nosy: georg.brandl, kjohnson severity: normal status: open title: Cross-reference ast.literal_eval() from eval() docs type: feature request versions: Python 2.6 ___ Python tracker <http://bugs.python.org/issue7935> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7310] Unhelpful __repr__() in os.environ
New submission from Kent Johnson : In Python 2.x, os.environ extends UserDict.IterableUserDict and therefore os.environ.__repr__() shows the environment. This makes it easy and intuitive to view the entire environment in the interactive interpreter. In Python 3.1, os.environ extends _abcoll.MutableMapping and uses object.__repr__(). This is a much less useful representation. I suggest adding this __repr__() method to class os._Environ (os.py line 380): def __repr__(self): return repr(self.data) -- components: Library (Lib) messages: 95160 nosy: kjohnson severity: normal status: open title: Unhelpful __repr__() in os.environ type: behavior versions: Python 3.1 ___ Python tracker <http://bugs.python.org/issue7310> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4156] Docs for BaseHandler.protocol_xxx methods are unclear
New submission from Kent Johnson <[EMAIL PROTECTED]>: In the docs for urllib2.BaseHandler previous to Python 2.6, the names of the protocol_xxx() methods were spelled with 'protocol' in italics to indicate that it is a placeholder; the actual method name is e.g. http_opener(). http://www.python.org/doc/2.5.2/lib/base-handler-objects.html In the Python 2.6 docs this typographic distinction has been lost http://docs.python.org/library/urllib2.html#basehandler-objects so it is not so clear that e.g. protocol_open() is not an actual method. I suggest either restoring the italics or using a spelling such as _open() for the method names. If this is difficult then the body of the descriptions should be rewritten to make it clear that the 'given protocol' is indicated by the name of the method. -- assignee: georg.brandl components: Documentation messages: 75023 nosy: georg.brandl, kjohnson severity: normal status: open title: Docs for BaseHandler.protocol_xxx methods are unclear versions: Python 2.6 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4156> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4017] IDLE 2.6 broken on OSX (Leopard)
Changes by Kent Johnson <[EMAIL PROTECTED]>: -- nosy: +kjohnson ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4017> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4012] Minor errors in multiprocessing docs
Kent Johnson <[EMAIL PROTECTED]> added the comment: On Thu, Oct 2, 2008 at 1:07 PM, Jesse Noller <[EMAIL PROTECTED]> wrote: > > Jesse Noller <[EMAIL PROTECTED]> added the comment: > > Which examples are you talking about Georg? I think you mean me, not Georg...I was referring to the example that immediately follows http://docs.python.org/library/multiprocessing.html#multiprocessing.pool.AsyncResult.successful ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4012> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4012] Minor errors in multiprocessing docs
New submission from Kent Johnson <[EMAIL PROTECTED]>: In the docs for AsyncResult http://docs.python.org/dev/library/multiprocessing.html#multiprocessing.pool.AsyncResult "get([timeout)" is missing a ] In the example following, it refers to pool.applyAsync() in two places; the docs spell this apply_async(), one of them must be wrong :-) -- assignee: georg.brandl components: Documentation messages: 74150 nosy: georg.brandl, kjohnson severity: normal status: open title: Minor errors in multiprocessing docs versions: Python 2.6 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4012> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3866] int() doesn't 'guess'
New submission from Kent Johnson <[EMAIL PROTECTED]>: The library reference for int() says, "If radix is zero, the proper radix is guessed based on the contents of string; the interpretation is the same as for integer literals." The use of the word 'guess' implies that there is some heuristic used here, that somehow the function will look at an arbitrary number and figure out the correct radix. This can confuse newbies: http://mail.python.org/pipermail/tutor/2008-September/064268.html 'determined' might be a better word. For bonus points link to the Language Reference page on integer literals: http://docs.python.org/ref/integers.html -- assignee: georg.brandl components: Documentation messages: 73214 nosy: georg.brandl, kjohnson severity: normal status: open title: int() doesn't 'guess' versions: Python 2.6 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3866> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3671] What's New in 2.6 - corrections
Kent Johnson <[EMAIL PROTECTED]> added the comment: For the itertools examples, perhaps you could remove the [ ] from the result text so it doesn't look like a list. For example: itertools.izip_longest([1,2,3], [1,2,3,4,5]) -> (1, 1), (2, 2), (3, 3), (None, 4), (None, 5) ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3671> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3670] Reporting bugs - no such sections
Kent Johnson <[EMAIL PROTECTED]> added the comment: You should add something like the old "About this document" footer. AFAICT there is no information in the new docs about how to report a problem with the docs. ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3670> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3671] What's New in 2.6 - corrections
New submission from Kent Johnson <[EMAIL PROTECTED]>: These are minor corrections to the What's New in Python 2.6[b3] doc. Note: the PEP references are to the headers in What's New, not the actual PEPs - PEP 371: The multiprocessing Package - "apply() or apply_async, adding a single request, and map() or map_async()" All four function names should link to the Pool docs. Currently apply and map link to the docs for the builtins of the same name; the other two don't link. - PEP 3101: Advanced String Formatting - In the first example, "uid = 'root'" is not needed - PEP 3112: Byte Literals - In the second example, the value of b should not have a space in the middle, i.e. bytearray(b'\xe2\x87\xaf\xe3\x89\x84') instead of bytearray(b'\xe2\x87\xaf \xe3\x89\x84') - Other Language Changes - next(*iterator*, [*default*]) - the asterisks are not needed - "letting complex(repr(cmplx)) will now round-trip values" -> so complex(repr(cmplx)) will now round-trip values - Interpreter Changes - "**encoding** or **encoding**:**errorhandler**" - Are the ** truly part of the syntax? - New, Improved, and Deprecated Modules - heapq.merge() returns a generator; the example should be list(heapq.merge([1, 3, 5, 9], [2, 8, 16])) - All the new itertools functions return iterators, not lists; their examples should also be wrapped in list() - itertools.product([1,2], repeat=3)) <- extra ) - shutil - "ignore_patterns() takes an arbitrary number of glob-style patterns and will ignore any files and directories that match this pattern." -> ignore_patterns() takes an arbitrary number of glob-style patterns and returns a callable which will ignore any files and directories that match this pattern. - The future_builtins module - I think all the ** are extraneous. -- assignee: georg.brandl components: Documentation messages: 71888 nosy: georg.brandl, kjohnson severity: normal status: open title: What's New in 2.6 - corrections versions: Python 2.6 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3671> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3670] Reporting bugs - no such sections
New submission from Kent Johnson <[EMAIL PROTECTED]>: The "Reporting Bugs" section of the Python 2.6b3 docs http://docs.python.org/dev/bugs.html says, please use either the “Add a comment” or the “Suggest a change” features of the relevant page in the most recent online documentation at http://docs.python.org/. I don't see either of these features in the 2.6 docs or the 2.5 docs at the link. -- assignee: georg.brandl components: Documentation messages: 71885 nosy: georg.brandl, kjohnson severity: normal status: open title: Reporting bugs - no such sections versions: Python 2.6 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3670> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1163367] correct/clarify documentation for super
Kent Johnson <[EMAIL PROTECTED]> added the comment: This issue seems to have foundered on finding an explanation for the finer points of super(). Perhaps the glaring errors could at least be corrected, or the fine points could be omitted or glossed over? For example change the first sentence of the docs to "Returns a proxy for the type following 'type' in the method resolution order of 'object-or-type'." Perhaps link to these? http://chandlerproject.org/bin/view/Projects/UsingSuper http://fuhm.net/super-harmful/ -- nosy: +kjohnson _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1163367> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1463] Minor error in mimetypes docs
New submission from Kent Johnson: In the mimetypes module docs http://docs.python.org/lib/module-mimetypes.html the section on add_type() should read "When strict is *true (the default)* the mapping". -- components: Documentation messages: 57636 nosy: kjohnson severity: minor status: open title: Minor error in mimetypes docs __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1463> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1462] About this document refers to SourceForge tracker
New submission from Kent Johnson: "About this document" http://docs.python.org/lib/about.html still refers to "the Python Bug Tracker at SourceForge". The bug tracker link is incorrect (should be the new tracker) and the SF reference is obsolete. -- components: Documentation messages: 57635 nosy: kjohnson severity: normal status: open title: About this document refers to SourceForge tracker __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1462> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
