Mailman 3 January 2017 - docs

[issue26355] Emit major version based canonical URLs for docs
by Manuel Krebber 27 Jan '17

27 Jan '17

Changes by Manuel Krebber <admin(a)wheerd.de>: Removed file: http://bugs.python.org/file46428/slot-wrapper-types.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26355> _______________________________________

1 0

[issue26355] Emit major version based canonical URLs for docs
by Manuel Krebber 27 Jan '17

27 Jan '17

Manuel Krebber added the comment: I create the last diff without creating a commit, so maybe this one works better. ---------- nosy: +Wheerd Added file: http://bugs.python.org/file46428/slot-wrapper-types.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26355> _______________________________________

1 0

[issue26355] Emit major version based canonical URLs for docs
by Matthias Bussonnier 27 Jan '17

27 Jan '17

Matthias Bussonnier added the comment: Here is a patch that add a canonical link to the current documentation that should apply cleanly to 3.4 and above. I can do similar for older versions. ---------- keywords: +patch Added file: http://bugs.python.org/file46426/cannonical-doc-for-3.4plus.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26355> _______________________________________

1 0

[issue26355] Emit major version based canonical URLs for docs
by Matthias Bussonnier 26 Jan '17

26 Jan '17

Matthias Bussonnier added the comment: Does this have to be implemented on the doc build of EOL pythons versions (like 2.6), or can it be a script which is ran once on these old docs ? One of the issues I had trying to implement that on other projects was that you don't know in advance what the future pages will be or if it will be gone. So you can go this route[1], in which case it's a 10 line fix that I'm happy to contribute also here. Typically `https://docs.python.org/2/c-api/string.html` has no cannonical on 3 whouch you can't know while building with sphinx. Or I though about injecting an html comment with a html comment that you search and replace once you publish the "new" version and only if the target page exists on the new version. So : - is that ok to have non existing cannonical ? - is that ok if adding <rel>s on docs is (or requires) a post-sphinx script ? 1: https://github.com/xonsh/xonsh/pull/1914/files Thanks ---------- nosy: +mbussonn _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26355> _______________________________________

1 0

[issue26355] Emit major version based canonical URLs for docs
by Nick Coghlan 26 Jan '17

26 Jan '17

Nick Coghlan added the comment: Belatedly following up on this, yeah, the RTFD page indicates that the header link should look like: <link rel="canonical" href="http://docs.python.org/3/<path>"> ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26355> _______________________________________

1 0

[issue22651] Open file in a+ mode reads from end of file in Python 3.4
by STINNER Victor 26 Jan '17

26 Jan '17

STINNER Victor added the comment: On Python 2, it's easy to workaround the issue, just always go the end explicitly: f = open(filename, "a+") f.seek(0, os.SEEK_END) Or use the io module which doesn't use the stdio of the C library and has a portable and reliable behaviour: f = io.open(filename, "a+") Georg Brandl: "This is a somewhat unfortunate difference between the major C libs and Python's new IO, but probably too late to change." Since it's easy to workaround the issue and only one user complained lat 2 years (3 years?), sorry, I close now the issue. I add this bug to my long list of bugs in the C stdio which won't be fixed in Python 2... http://haypo-notes.readthedocs.io/python.html#bugs-in-the-c-stdio-used-by-t… ---------- resolution: -> wont fix status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22651> _______________________________________

1 0

[issue22651] Open file in a+ mode reads from end of file in Python 3.4
by STINNER Victor 26 Jan '17

26 Jan '17

Changes by STINNER Victor <victor.stinner(a)gmail.com>: ---------- Removed message: http://bugs.python.org/msg286294 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22651> _______________________________________

1 0

[issue22651] Open file in a+ mode reads from end of file in Python 3.4
by Caitlin 26 Jan '17

26 Jan '17

Caitlin added the comment: Yeah, the workaround seemed to work for me when trying to open file on http://buywebsitetrafficreviews.org/, but this should be fixed somehow anyway. ---------- nosy: +caitlinwalker37 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22651> _______________________________________

1 0

Suggested Edit of re Doc
by Douglas Morris 25 Jan '17

25 Jan '17

Dear Python volunteers, Thanks for you work. I am learning Python (a newbie) and have a suggestion. The FAQ has an explanation on the syntactical requirement of raw strings, which is nice enough when you are looking at it or remember looking at it. Newbies who read the re documentation first may have a different experience. The Standard Library Documentation for module re reads in section 6.2 (the beginning of the re documentation):The solution is to use Python’s raw string notation for regular expressionpatterns; backslashes are not handled in any special way in a string literalprefixed with 'r'. I suggest changing that to: The solution is to use Python’s raw string notation for regular expressionpatterns. Backslash escapes are not actually replaced in raw strings, but the backslashes are still required to syntactically permit such replacement in subsequent processing. Consequently, the content of string literals with the 'r' prefix have exactly one syntactic requirement: the total number of consecutive backslashes at the end must be even (possibly zero). Douglas Morris

1 0

[issue26149] Suggest PyCharm Community as an editor for Unix platforms
by John Hagen 25 Jan '17

25 Jan '17

New submission from John Hagen: The Python documentation recommends editors that can be used on Unix: https://docs.python.org/3.5/using/unix.html#editors If the intent is to advertise very excellent IDEs (as Geany and Komodo Edit are listed), I suggest that PyCharm Community Edition (https://www.jetbrains.com/pycharm/download/) be added to the list. It is free, has a very powerful static analyzer, comes with PEP8 checking installed by default, supports type hinting, ... (https://www.jetbrains.com/pycharm/features/) ---------- assignee: docs@python components: Documentation messages: 258551 nosy: John Hagen, docs@python priority: normal severity: normal status: open title: Suggest PyCharm Community as an editor for Unix platforms type: enhancement versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26149> _______________________________________

11 19