From report at bugs.python.org Sun Oct 1 17:52:17 2017 From: report at bugs.python.org (Julien Palard) Date: Sun, 01 Oct 2017 21:52:17 +0000 Subject: [docs] [issue31589] Links for French documentation pdf is broken In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1506894737.66.0.213398074469.issue31589@psf.upfronthosting.co.za> Julien Palard added the comment: Problem happen during pdflatex, I tried a local build and got: ! Package hyperref Error: Wrong DVI mode driver option `dvipdfmx', (hyperref) because pdfTeX or LuaTeX is running in PDF mode. See the hyperref package documentation for explanation. Type H for immediate help. ... l.4362 \ProcessKeyvalOptions{Hyp} ? ! Emergency stop. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 1 17:54:28 2017 From: report at bugs.python.org (Julien Palard) Date: Sun, 01 Oct 2017 21:54:28 +0000 Subject: [docs] [issue31589] Links for French documentation pdf is broken In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1506894868.18.0.912454111764.issue31589@psf.upfronthosting.co.za> Change by Julien Palard : ---------- nosy: +linkid _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 1 18:36:48 2017 From: report at bugs.python.org (Ezio Melotti) Date: Sun, 01 Oct 2017 22:36:48 +0000 Subject: [docs] [issue31589] Links for French documentation pdf is broken In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1506897408.48.0.213398074469.issue31589@psf.upfronthosting.co.za> Ezio Melotti added the comment: FWIW most of the errors I met while trying to build the pdfs of the main docs were caused by the presence of non-latin1 characters. French should be limited to the latin1 range and the error you pasted doesn't seem to be related, however that might explain while the Japanese docs are also missing (unless this issue got fixed in the meanwhile -- I haven't built the pdfs in a while). ---------- nosy: +ezio.melotti type: -> behavior _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 1 19:11:49 2017 From: report at bugs.python.org (Julien Palard) Date: Sun, 01 Oct 2017 23:11:49 +0000 Subject: [docs] [issue31589] Links for French documentation pdf is broken In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1506899509.15.0.213398074469.issue31589@psf.upfronthosting.co.za> Julien Palard added the comment: After an upgrade of my venv, the error is now: Latexmk: applying rule 'pdflatex'... Rule 'pdflatex': File changes, etc: Changed files, or newly in use since previous run(s): 'faq.aux' 'faq.out' 'faq.toc' Latexmk: Maximum runs of pdflatex reached without getting stable files Latexmk: All targets (faq.pdf) are up-to-date Latexmk: Did not finish processing file 'faq.tex': 'pdflatex' needed too many passes ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 1 19:32:45 2017 From: report at bugs.python.org (Julien Palard) Date: Sun, 01 Oct 2017 23:32:45 +0000 Subject: [docs] [issue31589] Links for French documentation pdf is broken In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1506900764.98.0.213398074469.issue31589@psf.upfronthosting.co.za> Julien Palard added the comment: One difference I see in the logs of sucessfully building the faq.tex and failing to build it is: Package hyperref Warning: Token not allowed in a PDF string (Unicode): Looks like if I remove all non-ascii characters from titles, it builds again. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 1 20:37:19 2017 From: report at bugs.python.org (Rufus V. Smith) Date: Mon, 02 Oct 2017 00:37:19 +0000 Subject: [docs] [issue27484] Some Examples in Format String Syntax are incorrect or poorly worded In-Reply-To: <1468260642.45.0.0477478332119.issue27484@psf.upfronthosting.co.za> Message-ID: <083A0A3B-598B-4399-A246-DFC4B7D31F36@gmail.com> Rufus V. Smith added the comment: I happened to run across this in my old email inbox. It's embarrassing to realize how wrong I was in submitting the report. Reading it with fresh eyes, your original makes sense. I don't know what I was thinking. > On Jul 11, 2016, at 2:10 PM, Raymond Hettinger wrote: > > > Raymond Hettinger added the comment: > > I think all of these read fine as-is though I would change "argument first" to "first argument" or just "argument". Adding the word "positional" is a distractor from what the comments are trying to communicate. > > The version numbering is normally done with a directive and outside of the examples. > > ---------- > nosy: +rhettinger > > _______________________________________ > Python tracker > > _______________________________________ ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 2 14:47:07 2017 From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=) Date: Mon, 02 Oct 2017 18:47:07 +0000 Subject: [docs] [issue31567] Inconsistent documentation around decorators In-Reply-To: <1506238290.29.0.485453330645.issue31567@psf.upfronthosting.co.za> Message-ID: <1506970027.58.0.213398074469.issue31567@psf.upfronthosting.co.za> ?ric Araujo added the comment: > What does @ mean here? If there's some meaning, the next question is, why doc for staticmethod() > (and classmethod() in the same page) does not have it? @ means that the function is meant to be used as a decorator (the markup looks like the actual code). staticmethod and classmethod are older than the decorator syntax, which is older than the special sphinx markup for decorators (they used to just use the function markup). For unittest.mock.patch, its result can be used as a decorator or as a context manager, so the current markup (no @) makes sense. If you want to update staticmethod and classmethod to use the decorator markup, please send a pull request! (more info in the devguide) ---------- nosy: +merwok _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 2 15:26:06 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Mon, 02 Oct 2017 19:26:06 +0000 Subject: [docs] [issue31665] Edit "Setting [windows] environmental variables" Message-ID: <1506972366.59.0.213398074469.issue31665@psf.upfronthosting.co.za> New submission from Terry J. Reedy : Python Setup and Usage, 3.3.1. Excursus: Setting environment variables https://docs.python.org/3/using/windows.html#excursus-setting-environment-variables The word 'excursus' is so rare and archaic that this is my first encounter with it. Could we drop it? The last paragraph starts with "To permanently modify the default environment variables, click Start and search for ?edit environment variables?,". This part is fine on Windows 10 as it brings up "Edit the system environment variables" and "Edit environmental variables for your account". Both take one to an Environmental variables dialog. The former requires than one be or become an admin user (via UAC dialog). The paragraph continues "or open System properties, Advanced system settings and click the Environment Variables button. In this dialog, you can add or modify User and System variables. To change System variables, you need non-restricted access to your machine (i.e. Administrator rights)." On Windows 10, at least, this is confusing or wrong. Control Panel has 'System' linked to the System dialog. This has 'Advanced systems settings' linked to System Properties, but one only get there by being or becoming (via UAC) an admin user. This has the Environmental Properties button mentioned above. It opens Environmental Variables for the admin user you are or are acting as. This route cannot change EVs for non-admin users. I have the impression that this has changed since Win 7. ---------- assignee: docs at python components: Documentation, Windows messages: 303560 nosy: docs at python, paul.moore, steve.dower, terry.reedy, tim.golden, zach.ware priority: normal severity: normal stage: needs patch status: open title: Edit "Setting [windows] environmental variables" type: behavior versions: Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 2 15:43:57 2017 From: report at bugs.python.org (Julien Palard) Date: Mon, 02 Oct 2017 19:43:57 +0000 Subject: [docs] [issue31589] Links for French documentation pdf is broken In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1506973437.22.0.213398074469.issue31589@psf.upfronthosting.co.za> Julien Palard added the comment: Problem looks like the utf8x package is not friend with tableofcontent: - https://tex.stackexchange.com/questions/240801/utf8x-character-fails-in-the-table-of-contents-every-second-time-i-compile - https://tex.stackexchange.com/questions/164458/pleaseinsertintopreamble-in-toc-and-header ---------- nosy: +benjamin.peterson _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 2 16:04:55 2017 From: report at bugs.python.org (linkid) Date: Mon, 02 Oct 2017 20:04:55 +0000 Subject: [docs] [issue31667] Wrong links in the gettext.NullTranslations class Message-ID: <1506974695.65.0.213398074469.issue31667@psf.upfronthosting.co.za> New submission from linkid : In gettext.NullTranslations class doc [0], links to gettext and ngettext methods are not consistent. [0] https://docs.python.org/3/library/gettext.html#the-nulltranslations-class ---------- assignee: docs at python components: Documentation messages: 303563 nosy: docs at python, linkid priority: normal severity: normal status: open title: Wrong links in the gettext.NullTranslations class type: enhancement versions: Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 2 16:17:56 2017 From: report at bugs.python.org (Eryk Sun) Date: Mon, 02 Oct 2017 20:17:56 +0000 Subject: [docs] [issue31665] Edit "Setting [windows] environmental variables" In-Reply-To: <1506972366.59.0.213398074469.issue31665@psf.upfronthosting.co.za> Message-ID: <1506975476.04.0.213398074469.issue31665@psf.upfronthosting.co.za> Eryk Sun added the comment: AFAIK, the "Advanced system settings" dialog has always required administrator access. To modify the environment for just the current user, in the control panel there's "User Accounts" => "Change my environment variables". ---------- nosy: +eryksun _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 2 17:07:57 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Mon, 02 Oct 2017 21:07:57 +0000 Subject: [docs] [issue31667] Wrong links in the gettext.NullTranslations class In-Reply-To: <1506974695.65.0.213398074469.issue31667@psf.upfronthosting.co.za> Message-ID: <1506978477.86.0.912454111764.issue31667@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- keywords: +patch pull_requests: +3840 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 2 17:09:31 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Mon, 02 Oct 2017 21:09:31 +0000 Subject: [docs] [issue31667] Wrong links in the gettext.NullTranslations class In-Reply-To: <1506974695.65.0.213398074469.issue31667@psf.upfronthosting.co.za> Message-ID: <1506978571.28.0.213398074469.issue31667@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: Good catch linkid! PR 3860 fixes these and several other gettext related links. ---------- nosy: +serhiy.storchaka versions: +Python 2.7 -Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 3 00:35:20 2017 From: report at bugs.python.org (fireattack) Date: Tue, 03 Oct 2017 04:35:20 +0000 Subject: [docs] [issue31668] "fixFirefoxAnchorBug" function in doctools.js causes navigating problem in Py3 doc in Chrome Message-ID: <1507005320.05.0.213398074469.issue31668@psf.upfronthosting.co.za> New submission from fireattack : Problem This is a regression bug/flaw in Sphinx's doctools.js, a JS file used in its base template, and therefore got inherited to Python 3's documentation website. Python 2's documentation website is not affected because it's based on an older version of Sphinx. There is a function in doctools.js: /** * workaround a firefox stupidity * see: https://bugzilla.mozilla.org/show_bug.cgi?id=645075 */ fixFirefoxAnchorBug : function() { if (document.location.hash) window.setTimeout(function() { document.location.href += ''; }, 10); } This function was supposed to fix an anchor bug in Firefox (see comment). It *used to* have a condition of $.browser outside, so it will only be applied to Firefox; but it was removed in JQuery so it was removed here as well. Therefore, this function now applies to all the browsers. Unfortunately, it causes navigating problem in Chrome now, when you use back and forward. The problem STR (Chrome only): 1. Open a link with hash (anchor), e.g. https://docs.python.org/3/library/stdtypes.html#text-sequence-type-str 2. Scroll away from the anchor position. 3. Click any external link (means the link that is not an anchor of current page). 4. Hit "back" button in the browser. What happened: When you navigating back, it doesn't go to your previous position. Instead, it goes to the anchor's location. What it should do: It should go to your previous position. Ironically, it won't cause this problem in Firefox, despite it's supposed to be a fix for (a different) anchor bug in Firefox. Comments I reported it to Sphinx as well: https://github.com/sphinx-doc/sphinx/issues/3549 but didn't get any response so far. Please keep in mind the Firefox anchor bug mentioned above will only happen if the anchor is assigned with
. From my observation we don't really use
in HTML, so I don't think this workaround function is really necessary here to begin with. ---------- assignee: docs at python components: Documentation messages: 303576 nosy: docs at python, fireattack priority: normal severity: normal status: open title: "fixFirefoxAnchorBug" function in doctools.js causes navigating problem in Py3 doc in Chrome type: behavior versions: Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 3 04:48:30 2017 From: report at bugs.python.org (Ned Deily) Date: Tue, 03 Oct 2017 08:48:30 +0000 Subject: [docs] [issue31423] Error while building PDF documentation In-Reply-To: <1505159688.48.0.695846604768.issue31423@psf.upfronthosting.co.za> Message-ID: <1507020510.55.0.912454111764.issue31423@psf.upfronthosting.co.za> Ned Deily added the comment: New changeset a74ce09c738c3e3aa89994bf31049cb914dca389 by Ned Deily (Zachary Ware) in branch '3.6': [3.6] bpo-31423: Fix building the PDF documentation (GH-3693) (GH-3699) https://github.com/python/cpython/commit/a74ce09c738c3e3aa89994bf31049cb914dca389 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 3 04:55:57 2017 From: report at bugs.python.org (Julien Palard) Date: Tue, 03 Oct 2017 08:55:57 +0000 Subject: [docs] [issue31589] Links for French documentation pdf is broken In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1507020957.39.0.213398074469.issue31589@psf.upfronthosting.co.za> Julien Palard added the comment: For the record, I can reproduce the issue with this minimal test file: mdk at windhowl$ ls -lah total 108K drwxr-xr-x 2 mdk mdk 4.0K Oct 2 21:15 . drwxrwxrwt 18 root root 96K Oct 2 21:15 .. -rw-r--r-- 1 mdk mdk 196 Oct 2 21:13 faq.tex mdk at windhowl$ cat faq.tex \documentclass[a4,10pt,french]{report} \usepackage[utf8x]{inputenc} \usepackage[T1,T2A]{fontenc} \usepackage{babel} \begin{document} \tableofcontents \chapter{FAQ sur Python ?h} \end{document} mdk at windhowl$ latexmk faq 2>&1 | tail -n 15 (/usr/share/texlive/texmf-dist/tex/latex/ucs/data/uni-0.def) [2] (./faq.aux) ) Output written on faq.dvi (2 pages, 608 bytes). Transcript written on faq.log. Latexmk: Log file says output to 'faq.dvi' Rule 'latex': File changes, etc: Changed files, or newly in use since previous run(s): 'faq.aux' 'faq.toc' Latexmk: Maximum runs of latex reached without getting stable files Latexmk: Did not finish processing file 'faq': 'latex' needed too many passes Latexmk: Use the -f option to force complete processing, unless error was exceeding maximum runs of latex/pdflatex. Latexmk: applying rule 'latex'... Latexmk: All targets (faq.dvi) are up-to-date Also, according to matrixise, it works with xelatex. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 3 05:34:49 2017 From: report at bugs.python.org (STINNER Victor) Date: Tue, 03 Oct 2017 09:34:49 +0000 Subject: [docs] [issue31589] Links for French documentation pdf is broken In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1507023289.5.0.213398074469.issue31589@psf.upfronthosting.co.za> STINNER Victor added the comment: Julien: Is there any reason why you want to use utf8x in specific? https://tex.stackexchange.com/questions/13067/utf8x-vs-utf8-inputenc """ utf8x vs. utf8 (inputenc) (...) The simple answer is that utf8x is to be avoided if possible. It loads the ucs package, which for a long time was unmaintained (although there is now a new maintainer) and breaks various other things. """ ---------- nosy: +haypo _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 3 05:35:08 2017 From: report at bugs.python.org (STINNER Victor) Date: Tue, 03 Oct 2017 09:35:08 +0000 Subject: [docs] [issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters? In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1507023308.86.0.912454111764.issue31589@psf.upfronthosting.co.za> Change by STINNER Victor : ---------- title: Links for French documentation pdf is broken -> Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters? _______________________________________ Python tracker _______________________________________ From Darren.Watson at nexusrental.co.uk Mon Oct 2 05:49:23 2017 From: Darren.Watson at nexusrental.co.uk (Darren Watson) Date: Mon, 2 Oct 2017 09:49:23 +0000 Subject: [docs] PDF Documentation Text Message-ID: <5B64B29FF1938F449E142A43F83FF0F3C22BCE52@NEXUS-MAIL.NEXUSRENTAL.local> Hi Not sure if you are aware, but the text on the PDF versions of the Python documentation is very faint. I've checked my pdf reader with documents known to be fine and everything is OK. >From what I can tell, it seems to be all Python documentation versions. Regards, Darren Watson IT DevOps Engineer Nexus Vehicle Rental Nexus House 2 Owlcotes Court 141 Richardshaw Lane Leeds, LS28 6AA www.nexusrental.co.uk [top11] [cid:image002.jpg at 01D2971F.1224D5F0] Quality & Security - We have certifications in the ISO 9001:2008 Quality Management and ISO 27001:2013 Information Security Management standards. Customer Service - Winner of the 'Best Customer Focus' award at the Best Business Awards 2017. Innovation - Winner of the 'Best Innovation' award at the Best Business Awards 2017. Professional Development - Named in the 'Centrica Top 100 Apprenticeship Employer List' 2016. This Message and any attachments are for the named recipient's use only. They may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any wrong transmission. If you are not the intended recipient or have received this message in error, please delete it and all copies of it from your system, destroy any hard copies of it and notify the sender immediately. You must not directly or indirectly, use, disclose, distribute, print or copy any part of this message or any attachments if you are not the intended recipient. Any views expressed in this message or any attachments are those of the individual sender, except where otherwise stated and the sender is authorised to state them to be the views of any such entity. Nexus Vehicle Rental is a trading name of Nexus Vehicle Management Ltd, a company registered in England and Wales. Registration. No. 03833617. Registered office: Nexus House, 2 Owlcotes Court, 141 Richardshaw Lane, Leeds, LS28 6AA. UK VAT No. 228 5101 30. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4847 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 5396 bytes Desc: image002.jpg URL: From keramatfar.a.s at gmail.com Mon Oct 2 06:16:09 2017 From: keramatfar.a.s at gmail.com (Abdalsamad Keramatfar) Date: Mon, 2 Oct 2017 13:46:09 +0330 Subject: [docs] tkinter RTL menu Message-ID: Dear Developer, I am using tkinter for GUI programming and found it well, But i wonder that it is impossible to put menu items from right to left! that is very important for RTL languages such as Persian, Arabic and et al. It can be very good to improve this library such can be used by RTL languages. -- Best regards, Abdalsamad keramatfar -------------- next part -------------- An HTML attachment was scrubbed... URL: From konstantin.ketskalo at gmail.com Tue Oct 3 04:50:30 2017 From: konstantin.ketskalo at gmail.com (Constantine Ketskalo) Date: Tue, 3 Oct 2017 11:50:30 +0300 Subject: [docs] Shortcuts bug in Python IDLE In-Reply-To: References: Message-ID: Hi, I've written this info to your forum. But is Terry Reedy even in pyhon team or is she just some troll? Saying it's impossible to fix this bug? https://bugs.python.org/issue31244 Look, here is the list of countries, that use cyrillic alphabet. This is the list of countries, that are going to be unable to use hotkeys in Python IDLE, when they are coding and switch input language to their native language to write a comment. https://en.wikipedia.org/wiki/Cyrillic_alphabets Looks like your hotkeys are bound to characters output by keys, however every key on the keyboard actually has its own id, that is independent of the language chosen for typing. So if you just bind your hotkeys to keyboard buttons id instead of characters produced by keys pressed - it's going to be easy and universal handling of this bug, that's going to work all over the world. 2017-08-21 15:05 GMT+03:00 Constantine Ketskalo < konstantin.ketskalo at gmail.com>: > Hi there. > Thank you for Python, I love this programming language. > > I've found a bug with shortcuts. I'm from Ukraine, so I'm working with > English, Ukrainian and Russian languages. But any shortcuts, where alphabet > is involved (like Ctrl+Z, Ctrl+F, Ctrl+V and so on) work only when English > is turned on. This is quite inconvenient. It's possible to work with it, > but still confusing, because you can select something in IDLE, copy it with > shortcut Ctrl+C, then try to paste it to another place and then you find > out that it wasn't copied, because active language is Ukrainian. So you > need to switch to English and repeat everything again. > > I'm currently working with Python 3.6.1, Windows 8.1 Embedded enterprize > x64. > Also I've noticed the same under Windows 7, Windows 10 in different > versions of Python. > I believe there where Python 2.7, 2.11, 3.4, 3.5. Not sure about all the > versions exectly, but for sure shortcuts worked the same in all the > versions I've ever tried to use. > > I hope this was helpful and I'm sure many developers, that work not only > with English would be really happy if you would fix this. > > Thanks again for your time and effort. > Best regards, Constantine. > > P.S. I'll right the same message to Issue tracker just in case. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From report at bugs.python.org Tue Oct 3 05:40:04 2017 From: report at bugs.python.org (Antoine Pitrou) Date: Tue, 03 Oct 2017 09:40:04 +0000 Subject: [docs] [issue22630] `concurrent.futures.Future.set_running_or_notify_cancel` does not notify cancel In-Reply-To: <1413277554.48.0.992007500484.issue22630@psf.upfronthosting.co.za> Message-ID: <1507023604.5.0.213398074469.issue22630@psf.upfronthosting.co.za> Antoine Pitrou added the comment: "change-docs-and-waiters.patch" looks reasonable on the principle, but I doubt it still applies. Also, we use Github nowadays. You may still upload patches if you prefer, but pull requests have become the recommended way to submit changes :-) ---------- nosy: +pitrou _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 3 05:47:48 2017 From: report at bugs.python.org (Julien Palard) Date: Tue, 03 Oct 2017 09:47:48 +0000 Subject: [docs] [issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters? In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1507024068.45.0.213398074469.issue31589@psf.upfronthosting.co.za> Julien Palard added the comment: I personally do not care about using utf8x, it has been introduced in: r74549 | benjamin.peterson | 2009-08-24 12:42:36 -0500 (Mon, 24 Aug 2009) | 1 line fix pdf building by teaching latex the right encoding package # Get LaTeX to handle Unicode correctly latex_elements = {'inputenc': r'\usepackage[utf8x]{inputenc}'} I tried with utf8 instead and it yielded a different set of errors, so I did not tried much. But utf8-induced bugs may be easier to fix that utf8x-induced bugs, I don't know. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 3 05:54:45 2017 From: report at bugs.python.org (STINNER Victor) Date: Tue, 03 Oct 2017 09:54:45 +0000 Subject: [docs] [issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters? In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1507024484.95.0.213398074469.issue31589@psf.upfronthosting.co.za> STINNER Victor added the comment: (Oh sorry, I misunderstand what you wrote. I understood that Python didn't use utf8x yet and you proposed to start using it.) ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 3 09:47:42 2017 From: report at bugs.python.org (=?utf-8?b?0JzQuNGF0LDQuNC7INCc0LjRgNC+0L3QvtCy?=) Date: Tue, 03 Oct 2017 13:47:42 +0000 Subject: [docs] [issue31678] Incorrect C Function name for timedelta Message-ID: <1507038462.28.0.213398074469.issue31678@psf.upfronthosting.co.za> New submission from ?????? ??????? : Documentation: PyDateTime_DELTA_GET_MICROSECOND https://docs.python.org/3/c-api/datetime.html#c.PyDateTime_DELTA_GET_MICROSECOND Should be: PyDateTime_DELTA_GET_MICROSECONDS ---------- assignee: docs at python components: Documentation messages: 303616 nosy: docs at python, ?????? ??????? priority: normal severity: normal status: open title: Incorrect C Function name for timedelta versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 3 10:35:54 2017 From: report at bugs.python.org (Henk-Jaap Wagenaar) Date: Tue, 03 Oct 2017 14:35:54 +0000 Subject: [docs] [issue31567] Inconsistent documentation around decorators In-Reply-To: <1506238290.29.0.485453330645.issue31567@psf.upfronthosting.co.za> Message-ID: <1507041354.72.0.912454111764.issue31567@psf.upfronthosting.co.za> Change by Henk-Jaap Wagenaar : ---------- nosy: +Henk-Jaap Wagenaar _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 3 11:20:06 2017 From: report at bugs.python.org (Mironov Mikhail) Date: Tue, 03 Oct 2017 15:20:06 +0000 Subject: [docs] [issue31678] Incorrect C Function name for timedelta In-Reply-To: <1507038462.28.0.213398074469.issue31678@psf.upfronthosting.co.za> Message-ID: <1507044006.9.0.912454111764.issue31678@psf.upfronthosting.co.za> Change by Mironov Mikhail : ---------- keywords: +patch pull_requests: +3850 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 3 12:39:56 2017 From: report at bugs.python.org (Mariatta Wijaya) Date: Tue, 03 Oct 2017 16:39:56 +0000 Subject: [docs] [issue31668] "fixFirefoxAnchorBug" function in doctools.js causes navigating problem in Py3 doc in Chrome In-Reply-To: <1507005320.05.0.213398074469.issue31668@psf.upfronthosting.co.za> Message-ID: <1507048796.78.0.213398074469.issue31668@psf.upfronthosting.co.za> Mariatta Wijaya added the comment: Is there anything to be done in CPython? It appears to be either a bug with the browser or Sphinx... ---------- nosy: +Mariatta _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 3 12:50:51 2017 From: report at bugs.python.org (fireattack) Date: Tue, 03 Oct 2017 16:50:51 +0000 Subject: [docs] [issue31668] "fixFirefoxAnchorBug" function in doctools.js causes navigating problem in Py3 doc in Chrome In-Reply-To: <1507005320.05.0.213398074469.issue31668@psf.upfronthosting.co.za> Message-ID: <1507049451.32.0.213398074469.issue31668@psf.upfronthosting.co.za> fireattack added the comment: Well, since it affects Python's site's functionality, I thought it's appropriate to report here (with components: documentation). I followed the instruction here: https://docs.python.org/3/bugs.html#documentation-bugs It is not Sphinx's bug per se, since it has nothing to do with its software; just an ancient problematic script in template got copied here. It is not a Chrome bug, since that script was not intended to apply to Chrome to begin with. But anyway, if anyone found it's not the right place, feel free to close it. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 4 11:13:16 2017 From: report at bugs.python.org (Barry A. Warsaw) Date: Wed, 04 Oct 2017 15:13:16 +0000 Subject: [docs] [issue28805] Add documentation for METH_FASTCALL In-Reply-To: <1480158534.61.0.510309261592.issue28805@psf.upfronthosting.co.za> Message-ID: <1507129996.17.0.213398074469.issue28805@psf.upfronthosting.co.za> Barry A. Warsaw added the comment: This and the _PyObject_FastCall* APIs really do need to be documented, especially if they're going to be used in the interpreter itself. The leading underscore signifies that it's not part of the public API (well, METH_FASTCALL doesn't have a leading underscore). When these are not documented, then they aren't discoverable, so there are cases where it may be useful but will be overlooked. It also means that folks will be inclined to cargo cult the few existing uses without perhaps understanding the full semantics. Can we please document these for Python 3.7 at least? ---------- nosy: +barry versions: +Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 4 11:13:32 2017 From: report at bugs.python.org (Barry A. Warsaw) Date: Wed, 04 Oct 2017 15:13:32 +0000 Subject: [docs] [issue28805] Add documentation for METH_FASTCALL and _PyObject_FastCall*() In-Reply-To: <1480158534.61.0.510309261592.issue28805@psf.upfronthosting.co.za> Message-ID: <1507130012.93.0.912454111764.issue28805@psf.upfronthosting.co.za> Change by Barry A. Warsaw : ---------- title: Add documentation for METH_FASTCALL -> Add documentation for METH_FASTCALL and _PyObject_FastCall*() _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 4 11:16:57 2017 From: report at bugs.python.org (STINNER Victor) Date: Wed, 04 Oct 2017 15:16:57 +0000 Subject: [docs] [issue28805] Add documentation for METH_FASTCALL and _PyObject_FastCall*() In-Reply-To: <1480158534.61.0.510309261592.issue28805@psf.upfronthosting.co.za> Message-ID: <1507130217.82.0.213398074469.issue28805@psf.upfronthosting.co.za> STINNER Victor added the comment: > Can we please document these for Python 3.7 at least? I chose to not document FASTCALL on purpose in Python 3.6, I wanted to keep everything private, until we get enough feedback and stabilize the API. Recently, the FASTCALL API changed: METH_FASTCALL doesn't support keywords anymore. You have to pass METH_FASTCALL|METH_KEYWORDS. It seems like the API became stable. I don't know if we should make the API public or not. PyPy would complain as usual that we give them more work to do :-D ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 4 11:18:55 2017 From: report at bugs.python.org (STINNER Victor) Date: Wed, 04 Oct 2017 15:18:55 +0000 Subject: [docs] [issue28805] Add documentation for METH_FASTCALL and _PyObject_FastCall*() In-Reply-To: <1480158534.61.0.510309261592.issue28805@psf.upfronthosting.co.za> Message-ID: <1507130335.27.0.213398074469.issue28805@psf.upfronthosting.co.za> STINNER Victor added the comment: I suggest to document the following 4 functions/macros: PyAPI_FUNC(PyObject *) _PyObject_FastCallDict( PyObject *callable, PyObject **args, Py_ssize_t nargs, PyObject *kwargs); PyAPI_FUNC(PyObject *) _PyObject_FastCallKeywords( PyObject *callable, PyObject **args, Py_ssize_t nargs, PyObject *kwnames); #define _PyObject_FastCall(func, args, nargs) \ _PyObject_FastCallDict((func), (args), (nargs), NULL) #define _PyObject_CallNoArg(func) \ _PyObject_FastCallDict((func), NULL, 0, NULL) And the METH_FASTCALL and METH_FASTCALL|METH_KEYWORDS calling convention. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 4 11:19:37 2017 From: report at bugs.python.org (STINNER Victor) Date: Wed, 04 Oct 2017 15:19:37 +0000 Subject: [docs] [issue28805] Add documentation for METH_FASTCALL and _PyObject_FastCall*() In-Reply-To: <1480158534.61.0.510309261592.issue28805@psf.upfronthosting.co.za> Message-ID: <1507130377.41.0.213398074469.issue28805@psf.upfronthosting.co.za> STINNER Victor added the comment: > It would also be nice if Cython could use it automatically. Cython is using FASTCALL since Python 3.6. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 4 13:28:23 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Wed, 04 Oct 2017 17:28:23 +0000 Subject: [docs] [issue31667] Wrong links in the gettext.NullTranslations class In-Reply-To: <1506974695.65.0.213398074469.issue31667@psf.upfronthosting.co.za> Message-ID: <1507138103.18.0.213398074469.issue31667@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: New changeset c02a1f4ad8fcdbffad2911c5a31c71a17a89d713 by Serhiy Storchaka in branch 'master': bpo-31667: Fix gettext related links. (#3860) https://github.com/python/cpython/commit/c02a1f4ad8fcdbffad2911c5a31c71a17a89d713 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 4 13:29:36 2017 From: report at bugs.python.org (Roundup Robot) Date: Wed, 04 Oct 2017 17:29:36 +0000 Subject: [docs] [issue31667] Wrong links in the gettext.NullTranslations class In-Reply-To: <1506974695.65.0.213398074469.issue31667@psf.upfronthosting.co.za> Message-ID: <1507138176.23.0.912454111764.issue31667@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- pull_requests: +3861 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 4 14:06:12 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Wed, 04 Oct 2017 18:06:12 +0000 Subject: [docs] [issue31667] Wrong links in the gettext.NullTranslations class In-Reply-To: <1506974695.65.0.213398074469.issue31667@psf.upfronthosting.co.za> Message-ID: <1507140372.51.0.213398074469.issue31667@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: New changeset ed77fbffa5bf81c8d16700370fe8bb63bbae1428 by Serhiy Storchaka (Miss Islington (bot)) in branch '3.6': [3.6] bpo-31667: Fix gettext related links. (GH-3860) (#3886) https://github.com/python/cpython/commit/ed77fbffa5bf81c8d16700370fe8bb63bbae1428 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 4 15:44:20 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Wed, 04 Oct 2017 19:44:20 +0000 Subject: [docs] [issue30872] Update curses docs to Python 3 In-Reply-To: <1499440453.75.0.308646182968.issue30872@psf.upfronthosting.co.za> Message-ID: <1507146259.94.0.213398074469.issue30872@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: New changeset 300dd552b15825abfe0e367ac14cec4c3e050dbc by Serhiy Storchaka in branch 'master': bpo-30872: Update the curses docs to Python 3. (#2620) https://github.com/python/cpython/commit/300dd552b15825abfe0e367ac14cec4c3e050dbc ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 4 15:45:54 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Wed, 04 Oct 2017 19:45:54 +0000 Subject: [docs] [issue30872] Update curses docs to Python 3 In-Reply-To: <1499440453.75.0.308646182968.issue30872@psf.upfronthosting.co.za> Message-ID: <1507146354.03.0.912454111764.issue30872@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- keywords: +patch pull_requests: +3862 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 5 02:35:51 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Thu, 05 Oct 2017 06:35:51 +0000 Subject: [docs] [issue30872] Update curses docs to Python 3 In-Reply-To: <1499440453.75.0.308646182968.issue30872@psf.upfronthosting.co.za> Message-ID: <1507185351.4.0.213398074469.issue30872@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: New changeset de5427a8f7ce15565d13383bc8d279bb07dda1cb by Serhiy Storchaka in branch '3.6': [3.6] bpo-30872: Update the curses docs to Python 3. (GH-2620) (#3887) https://github.com/python/cpython/commit/de5427a8f7ce15565d13383bc8d279bb07dda1cb ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 5 03:27:48 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Thu, 05 Oct 2017 07:27:48 +0000 Subject: [docs] [issue30872] Update curses docs to Python 3 In-Reply-To: <1499440453.75.0.308646182968.issue30872@psf.upfronthosting.co.za> Message-ID: <1507188468.69.0.912454111764.issue30872@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.5 _______________________________________ Python tracker _______________________________________ From 14McCoM at phs.cheshire.sch.uk Tue Oct 3 06:57:33 2017 From: 14McCoM at phs.cheshire.sch.uk (Mac McCourt) Date: Tue, 3 Oct 2017 10:57:33 +0000 Subject: [docs] (no subject) Message-ID: Help this goddamn window keeps coming up Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website. -------------- next part -------------- An HTML attachment was scrubbed... URL: From auguzun at yandex.ru Tue Oct 3 11:44:51 2017 From: auguzun at yandex.ru (=?utf-8?B?0JPRg9C30YPQvSDQkNC90LTRgNC10Lk=?=) Date: Tue, 03 Oct 2017 18:44:51 +0300 Subject: [docs] can't access ofline dowload of documentation Message-ID: <372291507045491@web4o.yandex.ru> An HTML attachment was scrubbed... URL: From mykegabu at gmail.com Wed Oct 4 09:54:35 2017 From: mykegabu at gmail.com (myke Gabu) Date: Wed, 4 Oct 2017 16:54:35 +0300 Subject: [docs] Beginers tutorial In-Reply-To: References: Message-ID: Hi python fraternity, Kindly email me a full pdf of a beginner's guide to start coding and subsequently programming with Python. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bgailer at gmail.com Thu Oct 5 10:05:06 2017 From: bgailer at gmail.com (Bob Gailer) Date: Thu, 5 Oct 2017 10:05:06 -0400 Subject: [docs] Beginers tutorial In-Reply-To: References: Message-ID: On Oct 5, 2017 8:02 AM, "myke Gabu" wrote: > > Hi python fraternity, > Kindly email me a full pdf of a beginner's guide Apologies but we don't provide that kind of service. If you go to the python.org website you will find links to tutorials. That's probably the best place to start to start coding and subsequently programming with Python. That's a wonderful ambition we're glad you're joining the community best of luck. Also be aware that this email list is primarily for the maintenance and Improvement of the Python documentation. If you need help you can email either tutor at python.org or help at python.org. Couple of requests When you run into a problem tell us as much as you can about what operating system you're using, what version of python, what you were expecting, and what you got. Avoid saying things like it doesn't work. If pertinent tell us what you did to run the program. If you get a trace back copy the entire traceback and paste it into your email. Avoid saying things like I ran this program and I got this error. Also realize that we will not write code for you but we will assist you in getting the code that you write correct. > Thank you. > > _______________________________________________ > docs mailing list > docs at python.org > https://mail.python.org/mailman/listinfo/docs > -------------- next part -------------- An HTML attachment was scrubbed... URL: From report at bugs.python.org Thu Oct 5 22:29:41 2017 From: report at bugs.python.org (Nick Coghlan) Date: Fri, 06 Oct 2017 02:29:41 +0000 Subject: [docs] [issue11205] Evaluation order of dictionary display is different from reference manual. In-Reply-To: <1297589953.69.0.371220549392.issue11205@psf.upfronthosting.co.za> Message-ID: <1507256981.34.0.213398074469.issue11205@psf.upfronthosting.co.za> Nick Coghlan added the comment: I'm unlikely to ever get to this (especially as 3.5 is now in security-fix only mode), so closing it again. ---------- nosy: +freakboy, freakboy3742 resolution: -> fixed stage: needs patch -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 6 10:22:12 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Fri, 06 Oct 2017 14:22:12 +0000 Subject: [docs] [issue31714] Improve re documentation Message-ID: <1507299732.49.0.213398074469.issue31714@psf.upfronthosting.co.za> New submission from Serhiy Storchaka : The proposed PR improves the documentation of re module and Regular Expression HOWTO. * Clarify the effect of the LOCALE flag. * Remove outdated statements. * Add an example of escaping a replacement string. * Add or correct some references. * Improve and fix a formatting. ---------- assignee: docs at python components: Documentation, Regular Expressions messages: 303822 nosy: akuchling, barry, docs at python, ezio.melotti, mrabarnett, serhiy.storchaka priority: normal severity: normal stage: patch review status: open title: Improve re documentation type: enhancement versions: Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 6 10:24:31 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Fri, 06 Oct 2017 14:24:31 +0000 Subject: [docs] [issue31714] Improve re documentation In-Reply-To: <1507299732.49.0.213398074469.issue31714@psf.upfronthosting.co.za> Message-ID: <1507299871.19.0.912454111764.issue31714@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- keywords: +patch pull_requests: +3878 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 6 11:05:28 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Fri, 06 Oct 2017 15:05:28 +0000 Subject: [docs] [issue31714] Improve re documentation In-Reply-To: <1507299732.49.0.213398074469.issue31714@psf.upfronthosting.co.za> Message-ID: <1507302328.74.0.912454111764.issue31714@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- nosy: +gregory.p.smith _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 6 11:06:26 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Fri, 06 Oct 2017 15:06:26 +0000 Subject: [docs] [issue24896] It is undocumented that re.UNICODE and re.LOCALE affect re.IGNORECASE In-Reply-To: <1439987891.31.0.547960058443.issue24896@psf.upfronthosting.co.za> Message-ID: <1507302386.54.0.213398074469.issue24896@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: I tried to correct the documentation in issue31714. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 6 11:11:22 2017 From: report at bugs.python.org (Henk-Jaap Wagenaar) Date: Fri, 06 Oct 2017 15:11:22 +0000 Subject: [docs] [issue31714] Improve re documentation In-Reply-To: <1507299732.49.0.213398074469.issue31714@psf.upfronthosting.co.za> Message-ID: <1507302682.57.0.213398074469.issue31714@psf.upfronthosting.co.za> Henk-Jaap Wagenaar added the comment: I was looking at your changes and got myself in a muddle. What is you rational for when you use ``[character or string]`` versus ``'[character or string]``? You seem to be creating consistency there, but I cannot quite see the rules you are aiming for! ---------- nosy: +Henk-Jaap Wagenaar _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 6 11:19:35 2017 From: report at bugs.python.org (Ezio Melotti) Date: Fri, 06 Oct 2017 15:19:35 +0000 Subject: [docs] [issue31714] Improve re documentation In-Reply-To: <1507299732.49.0.213398074469.issue31714@psf.upfronthosting.co.za> Message-ID: <1507303175.42.0.213398074469.issue31714@psf.upfronthosting.co.za> Ezio Melotti added the comment: ISTM that ``x`` is used when x is a regex or regex metachar, whereas ``'x'`` is used when 'x' is a string. I find this distinction reasonable. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 6 11:40:34 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Fri, 06 Oct 2017 15:40:34 +0000 Subject: [docs] [issue31714] Improve re documentation In-Reply-To: <1507299732.49.0.213398074469.issue31714@psf.upfronthosting.co.za> Message-ID: <1507304434.4.0.213398074469.issue31714@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: It is explained in the documentation: """ (In the rest of this section, we'll write RE's in ``this special style``, usually without quotes, and strings to be matched ``'in single quotes'``.) """ ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 6 11:53:09 2017 From: report at bugs.python.org (Phillip) Date: Fri, 06 Oct 2017 15:53:09 +0000 Subject: [docs] [issue31717] Socket documentation threading misstep? Message-ID: <1507305189.16.0.213398074469.issue31717@psf.upfronthosting.co.za> New submission from Phillip : Very small, but, https://docs.python.org/2/howto/sockets.html https://docs.python.org/3/howto/sockets.html have : while True: # accept connections from outside (clientsocket, address) = serversocket.accept() # now do something with the clientsocket # in this case, we'll pretend this is a threaded server ct = client_thread(clientsocket) ct.run() and for some reason I really want it to be ct.start() ---------- assignee: docs at python components: Documentation messages: 303831 nosy: apoplexy, docs at python priority: normal severity: normal status: open title: Socket documentation threading misstep? versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 6 12:00:34 2017 From: report at bugs.python.org (Brian Ward) Date: Fri, 06 Oct 2017 16:00:34 +0000 Subject: [docs] [issue31714] Improve re documentation In-Reply-To: <1507299732.49.0.213398074469.issue31714@psf.upfronthosting.co.za> Message-ID: <1507305634.02.0.213398074469.issue31714@psf.upfronthosting.co.za> Brian Ward added the comment: In re.rst, the instances of "Correcsponds the" should be "Corresponds to the" and "Doesn't have correcsponding inline flag" should be "No corresponding inline flag." ---------- nosy: +Brian Ward _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 6 12:37:18 2017 From: report at bugs.python.org (R. David Murray) Date: Fri, 06 Oct 2017 16:37:18 +0000 Subject: [docs] [issue31717] Socket documentation threading misstep? In-Reply-To: <1507305189.16.0.213398074469.issue31717@psf.upfronthosting.co.za> Message-ID: <1507307838.24.0.213398074469.issue31717@psf.upfronthosting.co.za> R. David Murray added the comment: Based on the paragraph following the example, I don't think client_thread is a threading.Thread, and 'run' is meant to be a generic representation of a possible API. Since Threads do have a 'run' method, this is certainly potentially confusing. Maybe we should change it to 'start_thread' or something like that? ---------- nosy: +r.david.murray versions: -Python 3.4, Python 3.5, Python 3.8 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 6 12:44:05 2017 From: report at bugs.python.org (R. David Murray) Date: Fri, 06 Oct 2017 16:44:05 +0000 Subject: [docs] [issue31717] Socket documentation threading misstep? In-Reply-To: <1507305189.16.0.213398074469.issue31717@psf.upfronthosting.co.za> Message-ID: <1507308245.67.0.213398074469.issue31717@psf.upfronthosting.co.za> R. David Murray added the comment: Or maybe instead of client_handler/run, it should be something like handle_client_asynchronously(clientsocket). ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 6 13:00:05 2017 From: report at bugs.python.org (Phillip) Date: Fri, 06 Oct 2017 17:00:05 +0000 Subject: [docs] [issue31717] Socket documentation threading misstep? In-Reply-To: <1507308245.67.0.213398074469.issue31717@psf.upfronthosting.co.za> Message-ID: Phillip added the comment: I could definitely understand that. After all, if it's slightly askew (or strikes some as such) it forces critical thinking, which is good. I didn't think calling run() was indicative of the three likely pathways to handle the client socket in the following paragraph. I'm indifferent, I just saw something so I said something, but ultimately I think you guys do a tremendous job keeping this documentation good. Thanks, On Fri, Oct 6, 2017 at 10:44 AM, R. David Murray wrote: > > R. David Murray added the comment: > > Or maybe instead of client_handler/run, it should be something like > handle_client_asynchronously(clientsocket). > > ---------- > > _______________________________________ > Python tracker > > _______________________________________ > ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 7 09:39:30 2017 From: report at bugs.python.org (Tzu-ping Chung) Date: Sat, 07 Oct 2017 13:39:30 +0000 Subject: [docs] [issue31720] msilib.MSIError is spelled MsiError in documentation Message-ID: <1507383570.37.0.213398074469.issue31720@psf.upfronthosting.co.za> New submission from Tzu-ping Chung : The title describes it all. ---------- assignee: docs at python components: Documentation messages: 303877 nosy: docs at python, uranusjr priority: normal severity: normal status: open title: msilib.MSIError is spelled MsiError in documentation versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 7 09:40:20 2017 From: report at bugs.python.org (Tzu-ping Chung) Date: Sat, 07 Oct 2017 13:40:20 +0000 Subject: [docs] [issue31720] msilib.MSIError is spelled MsiError in documentation In-Reply-To: <1507383570.37.0.213398074469.issue31720@psf.upfronthosting.co.za> Message-ID: <1507383620.58.0.912454111764.issue31720@psf.upfronthosting.co.za> Change by Tzu-ping Chung : ---------- keywords: +patch pull_requests: +3887 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 7 11:00:21 2017 From: report at bugs.python.org (Roundup Robot) Date: Sat, 07 Oct 2017 15:00:21 +0000 Subject: [docs] [issue31720] msilib.MSIError is spelled MsiError in documentation In-Reply-To: <1507383570.37.0.213398074469.issue31720@psf.upfronthosting.co.za> Message-ID: <1507388421.37.0.912454111764.issue31720@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- pull_requests: +3889 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 7 11:03:48 2017 From: report at bugs.python.org (Roundup Robot) Date: Sat, 07 Oct 2017 15:03:48 +0000 Subject: [docs] [issue31720] msilib.MSIError is spelled MsiError in documentation In-Reply-To: <1507383570.37.0.213398074469.issue31720@psf.upfronthosting.co.za> Message-ID: <1507388628.52.0.912454111764.issue31720@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- pull_requests: +3890 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 7 12:00:29 2017 From: report at bugs.python.org (Mariatta Wijaya) Date: Sat, 07 Oct 2017 16:00:29 +0000 Subject: [docs] [issue31720] msilib.MSIError is spelled MsiError in documentation In-Reply-To: <1507383570.37.0.213398074469.issue31720@psf.upfronthosting.co.za> Message-ID: <1507392029.87.0.213398074469.issue31720@psf.upfronthosting.co.za> Mariatta Wijaya added the comment: New changeset 5f396dba1d11356ab18e3bec130596197e741a64 by Mariatta (Miss Islington (bot)) in branch '3.6': bpo-31720: msilib documentation, change MsiError into MSIError (GH-3914) (GH-3917) https://github.com/python/cpython/commit/5f396dba1d11356ab18e3bec130596197e741a64 ---------- nosy: +Mariatta _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 7 12:01:25 2017 From: report at bugs.python.org (Mariatta Wijaya) Date: Sat, 07 Oct 2017 16:01:25 +0000 Subject: [docs] [issue31720] msilib.MSIError is spelled MsiError in documentation In-Reply-To: <1507383570.37.0.213398074469.issue31720@psf.upfronthosting.co.za> Message-ID: <1507392085.62.0.213398074469.issue31720@psf.upfronthosting.co.za> Mariatta Wijaya added the comment: Thanks! ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.4, Python 3.5, Python 3.8 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 8 22:54:14 2017 From: report at bugs.python.org (Bradley Smith) Date: Mon, 09 Oct 2017 02:54:14 +0000 Subject: [docs] [issue31537] Bug in readline module documentation example In-Reply-To: <1505938727.72.0.626220071672.issue31537@psf.upfronthosting.co.za> Message-ID: <1507517654.56.0.912454111764.issue31537@psf.upfronthosting.co.za> Change by Bradley Smith : ---------- keywords: +patch pull_requests: +3898 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 8 22:56:45 2017 From: report at bugs.python.org (Bradley Smith) Date: Mon, 09 Oct 2017 02:56:45 +0000 Subject: [docs] [issue31537] Bug in readline module documentation example In-Reply-To: <1505938727.72.0.626220071672.issue31537@psf.upfronthosting.co.za> Message-ID: <1507517805.6.0.213398074469.issue31537@psf.upfronthosting.co.za> Bradley Smith added the comment: I ran into the same bug in the documentation recently. I've opened a pull request here that fixes it: https://github.com/python/cpython/pull/3925 As I was trying to figure out why the example was broken, I wrote up a little more context to explain the current behavior and the fix: https://docs.python.org/3.7/library/readline.html#example https://docs.python.org/3.6/library/readline.html#example In the "Example" section, the second example that "supports concurrent interactive sessions, by only appending the new history" will actually *never* write any lines to a custom history file. This is conveniently masked by the fact that the file path used in the example code also happens to be the default path that readline automatically writes history to, but if you specify *any* other file path, you will see that the new file is created but never has any content written to it. The problem in this example is the use of `get_history_length` to get "previous" and "current" history lengths for determining how many lines to append to the file. Both calls to `get_history_length` always return `-1` here. Thus, when `append_history_file` is called, it always receives a first argument of `0` (because `-1 - -1 == 0`), resulting in zero lines written to the file. Instead of `get_history_length`, the example code *should* call `get_current_history_length`. Swapping that function call makes the example behave as expected, appending new lines to the file. ---------- nosy: +infinitewarp _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 9 11:04:44 2017 From: report at bugs.python.org (Paul Pinterits) Date: Mon, 09 Oct 2017 15:04:44 +0000 Subject: [docs] [issue31735] Documentation incorrectly states how descriptors are invoked Message-ID: <1507561484.86.0.213398074469.issue31735@psf.upfronthosting.co.za> New submission from Paul Pinterits : The [descriptor howto](https://docs.python.org/3/howto/descriptor.html#invoking-descriptors) states: "For example, obj.d looks up d in the dictionary of obj. If d defines the method __get__(), then d.__get__(obj) is invoked [...]" This is not true - the descriptor obtained from obj's dictionary is never invoked. If it was, the following two snippets would produce output: class Class: pass obj = Class() obj.__dict__['d'] = property(lambda: print('called')) _ = obj.d # nothing is printed. class Obj: @property def d(self): print('called') _ = Obj.d # nothing is printed. ---------- assignee: docs at python components: Documentation messages: 303968 nosy: Paul Pinterits, docs at python priority: normal severity: normal status: open title: Documentation incorrectly states how descriptors are invoked versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 9 11:50:39 2017 From: report at bugs.python.org (Henk-Jaap Wagenaar) Date: Mon, 09 Oct 2017 15:50:39 +0000 Subject: [docs] [issue31735] Documentation incorrectly states how descriptors are invoked In-Reply-To: <1507561484.86.0.213398074469.issue31735@psf.upfronthosting.co.za> Message-ID: <1507564239.8.0.213398074469.issue31735@psf.upfronthosting.co.za> Henk-Jaap Wagenaar added the comment: You get what you should get: when you print obj.d, Obj.d, you will get: which is exactly what you expect: - in the first case, you assigned a property object to the dictionary at obj.__dict__, so that's what you get back when you run obj.d. - you defined a property on a class called d, and you get it when you run Obj.d If you run print(Obj().d) you will get a TypeError: your lambda should read: lambda self: print('called') Properties should be added to the class not the instance, see https://stackoverflow.com/questions/1325673/how-to-add-property-to-a-class-dynamically and https://eev.ee/blog/2012/05/23/python-faq-descriptors/ ---------- nosy: +Henk-Jaap Wagenaar _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 9 12:47:05 2017 From: report at bugs.python.org (Paul Pinterits) Date: Mon, 09 Oct 2017 16:47:05 +0000 Subject: [docs] [issue31735] Documentation incorrectly states how descriptors are invoked In-Reply-To: <1507561484.86.0.213398074469.issue31735@psf.upfronthosting.co.za> Message-ID: <1507567625.24.0.213398074469.issue31735@psf.upfronthosting.co.za> Paul Pinterits added the comment: I'm aware that descriptors have to exist on the class in order to work. The point is that the documentation states "If d defines the method __get__(), then d.__get__(obj) is invoked" (where d is obj.d), which is simply not true. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 9 12:55:22 2017 From: report at bugs.python.org (Paul Pinterits) Date: Mon, 09 Oct 2017 16:55:22 +0000 Subject: [docs] [issue31735] Documentation incorrectly states how descriptors are invoked In-Reply-To: <1507561484.86.0.213398074469.issue31735@psf.upfronthosting.co.za> Message-ID: <1507568122.35.0.213398074469.issue31735@psf.upfronthosting.co.za> Paul Pinterits added the comment: If we take this class: class Obj: @property def d(self): print('called') And we access Obj.d: _ = Obj.d According to the docs, the following should happen: # obj.d looks up d in the dictionary of obj d = Obj.__dict__['d'] # If d defines the method __get__(), if hasattr(d, '__get__'): # then d.__get__(obj) is invoked d.__get__(Obj) We know this doesn't happen because nothing is printed to stdout. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 9 13:49:43 2017 From: report at bugs.python.org (Richard Gibson) Date: Mon, 09 Oct 2017 17:49:43 +0000 Subject: [docs] [issue31737] Documentation renders incorrectly Message-ID: <1507571383.25.0.213398074469.issue31737@psf.upfronthosting.co.za> New submission from Richard Gibson : The content at docs.python.org seems to be inserting language-dependent "smart quotes" in code blocks, which mangles backslashes and sequences like `'''`. Observed at https://docs.python.org/3/reference/lexical_analysis.html#string-and-bytes-literals , which renders longstring ::= ???? longstringitem* ???? | ????? longstringitem* ????? instead of longstring ::= "'''" longstringitem* "'''" | '"""' longstringitem* '"""' and stringescapeseq ::= ?" instead of stringescapeseq ::= "\" , and looks even worse in other languages: longstring ::= ? ?? ? longstringitem* ? ?? ? | ? ?? ?? longstringitem* ? ?? ?? longstring ::= ???? longstringitem* ???? | ????? longstringitem* ????? Running `make html` locally produces the desired output, so whatever's going on appears specific to the public site. ---------- assignee: docs at python components: Documentation messages: 303988 nosy: docs at python, gibson042 priority: normal severity: normal status: open title: Documentation renders incorrectly versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 9 13:52:27 2017 From: report at bugs.python.org (Ned Deily) Date: Mon, 09 Oct 2017 17:52:27 +0000 Subject: [docs] [issue31737] Documentation renders incorrectly In-Reply-To: <1507571383.25.0.213398074469.issue31737@psf.upfronthosting.co.za> Message-ID: <1507571547.1.0.912454111764.issue31737@psf.upfronthosting.co.za> Change by Ned Deily : ---------- nosy: +mdk _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 9 15:02:39 2017 From: report at bugs.python.org (Julien Palard) Date: Mon, 09 Oct 2017 19:02:39 +0000 Subject: [docs] [issue31737] Documentation renders incorrectly In-Reply-To: <1507571383.25.0.213398074469.issue31737@psf.upfronthosting.co.za> Message-ID: <1507575759.84.0.213398074469.issue31737@psf.upfronthosting.co.za> Julien Palard added the comment: We spotted some quoting probleme in the french translation too, and I still didn't had time to look at it, typically here: https://docs.python.org/fr/3/library/itertools.html#itertool-functions where we're getting: 10.1.1. Fonctions d?itertool? instead of: 10.1.1. Fonctions d'itertool? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 9 15:04:38 2017 From: report at bugs.python.org (Julien Palard) Date: Mon, 09 Oct 2017 19:04:38 +0000 Subject: [docs] [issue31584] Documentation Language mixed up In-Reply-To: <1506402847.94.0.987670636111.issue31584@psf.upfronthosting.co.za> Message-ID: <1507575878.15.0.213398074469.issue31584@psf.upfronthosting.co.za> Julien Palard added the comment: FTR I'm still daily monitoring the presence of mixed-up pages server side and did not spotted a single one. I'm still using my very basic: $ grep -rl 'd?finition' /srv/docs.python.org/ja/; grep -rl ? /srv/docs.python.org/{2.7,3.6,3.7} ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 9 15:10:20 2017 From: report at bugs.python.org (Julien Palard) Date: Mon, 09 Oct 2017 19:10:20 +0000 Subject: [docs] [issue26546] Provide translated french translation on docs.python.org In-Reply-To: <1457794223.79.0.618185263259.issue26546@psf.upfronthosting.co.za> Message-ID: <1507576220.5.0.213398074469.issue26546@psf.upfronthosting.co.za> Julien Palard added the comment: ? https://docs.python.org/fr/ ---------- stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 9 15:27:58 2017 From: report at bugs.python.org (Nathaniel Manista) Date: Mon, 09 Oct 2017 19:27:58 +0000 Subject: [docs] [issue31739] socket.close recommended but not demonstrated in same-page example code Message-ID: <1507577278.77.0.213398074469.issue31739@psf.upfronthosting.co.za> New submission from Nathaniel Manista : https://docs.python.org/3.7/library/socket.html#socket.socket.close says "it is recommended to close() [sockets] explicitly, or to use a with statement around them", but in the example code on the same page at https://docs.python.org/3.7/library/socket.html#example correct use of the .close() method seems to be missing. ---------- assignee: docs at python components: Documentation messages: 303993 nosy: Nathaniel Manista, docs at python priority: normal severity: normal status: open title: socket.close recommended but not demonstrated in same-page example code type: enhancement versions: Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 9 15:32:36 2017 From: report at bugs.python.org (R. David Murray) Date: Mon, 09 Oct 2017 19:32:36 +0000 Subject: [docs] [issue31739] socket.close recommended but not demonstrated in same-page example code In-Reply-To: <1507577278.77.0.213398074469.issue31739@psf.upfronthosting.co.za> Message-ID: <1507577556.08.0.213398074469.issue31739@psf.upfronthosting.co.za> R. David Murray added the comment: Which example? (It might be easiest to just generate a PR with your suggested improvement.) ---------- nosy: +r.david.murray _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 9 15:40:26 2017 From: report at bugs.python.org (Julien Palard) Date: Mon, 09 Oct 2017 19:40:26 +0000 Subject: [docs] [issue31737] Documentation renders incorrectly In-Reply-To: <1507571383.25.0.213398074469.issue31737@psf.upfronthosting.co.za> Message-ID: <1507578026.49.0.213398074469.issue31737@psf.upfronthosting.co.za> Julien Palard added the comment: Tested locally with different versions of sphinx-build: - 1.3.3 does not produce the issue - 1.6.2 (used on docs.python.org) produces the issue - 1.6.3 does not produce the issue - 1.6.4 does not produce the issue Reading the changelog between 1.6.2 and 1.6.3 lead to https://github.com/sphinx-doc/sphinx/issues/3824 itself leading to https://github.com/sphinx-doc/sphinx/commit/f99fe20e507210bd7db8665b8f234f1fe25c8100 So it looks fixed in 1.6.3 and 1.6.4, I'm running a full local build (using docsbuild-scripts) using sphinx 1.6.4 to see if we can upgrade. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 10 01:35:13 2017 From: report at bugs.python.org (INADA Naoki) Date: Tue, 10 Oct 2017 05:35:13 +0000 Subject: [docs] [issue31584] Documentation Language mixed up In-Reply-To: <1506402847.94.0.987670636111.issue31584@psf.upfronthosting.co.za> Message-ID: <1507613713.16.0.213398074469.issue31584@psf.upfronthosting.co.za> INADA Naoki added the comment: Japanese HTML has this line: I suspect this line affects CDN's cache. But I can't find document about canonical link in fastly's document. ---------- nosy: +inada.naoki _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 10 02:05:50 2017 From: report at bugs.python.org (INADA Naoki) Date: Tue, 10 Oct 2017 06:05:50 +0000 Subject: [docs] [issue31584] Documentation Language mixed up In-Reply-To: <1506402847.94.0.987670636111.issue31584@psf.upfronthosting.co.za> Message-ID: <1507615550.24.0.213398074469.issue31584@psf.upfronthosting.co.za> INADA Naoki added the comment: https://twitter.com/miyagawa/status/917629042278359040 Miyagawa-san, the member of Fastly told me they doesn't use HTML content for cache key, unless we customize VCL. But I can't find VCL for docs.python.org in github.com/python. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 10 02:10:12 2017 From: report at bugs.python.org (Julien Palard) Date: Tue, 10 Oct 2017 06:10:12 +0000 Subject: [docs] [issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters? In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1507615812.24.0.213398074469.issue31589@psf.upfronthosting.co.za> Julien Palard added the comment: Today I tried without utf8x and an up-to-date version of texlive, errors looked less mystical, so I was able to open a readable / easy to reproduce issue: https://github.com/sphinx-doc/sphinx/issues/4136 I then followed the idea of trying xetex and I was able to build english and french PDF (still not had time to try japanese). ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 10 02:14:15 2017 From: report at bugs.python.org (Roundup Robot) Date: Tue, 10 Oct 2017 06:14:15 +0000 Subject: [docs] [issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters? In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1507616055.11.0.912454111764.issue31589@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- keywords: +patch pull_requests: +3913 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 10 04:46:31 2017 From: report at bugs.python.org (Henk-Jaap Wagenaar) Date: Tue, 10 Oct 2017 08:46:31 +0000 Subject: [docs] [issue31735] Documentation incorrectly states how descriptors are invoked In-Reply-To: <1507561484.86.0.213398074469.issue31735@psf.upfronthosting.co.za> Message-ID: <1507625191.24.0.213398074469.issue31735@psf.upfronthosting.co.za> Henk-Jaap Wagenaar added the comment: "We know this doesn't happen because nothing is printed to stdout." Try running Obj().d, you will get output. Obj.d does not work because it is on a *class*, and so it runs, per the docs: 'Obj.__dict__['d'].__get__(None, Obj)' whereas you consider running it on an instance to get: b = Obj() b.d # equivalent to type(b).__dict__['d'].__get__(b, type(b)) and you will get output twice. [Note, on python2 you will get an error, I think this is because your class does not inherit from object.] ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 10 04:59:44 2017 From: report at bugs.python.org (Henk-Jaap Wagenaar) Date: Tue, 10 Oct 2017 08:59:44 +0000 Subject: [docs] [issue31735] Documentation incorrectly states how descriptors are invoked In-Reply-To: <1507561484.86.0.213398074469.issue31735@psf.upfronthosting.co.za> Message-ID: <1507625984.66.0.213398074469.issue31735@psf.upfronthosting.co.za> Henk-Jaap Wagenaar added the comment: I do think though that "If d defines the method __get__(), then d.__get__(obj) is invoked according to the precedence rules listed below." seems to contain a mistake in that it should have d.__get__(obj, type(obj)) instead of d.__get__(obj) ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 10 07:00:17 2017 From: report at bugs.python.org (=?utf-8?q?Ante_Peri=C4=87?=) Date: Tue, 10 Oct 2017 11:00:17 +0000 Subject: [docs] [issue31743] Proportional Width Font on Generated Python Docs PDFs Message-ID: <1507633217.5.0.213398074469.issue31743@psf.upfronthosting.co.za> New submission from Ante Peri? : Fonts in the generated documentation PDFs, for all Python versions, are proportional width in code blocks, unlike in HTML version, where they are fixed-width. Example https://docs.python.org/2.7/archives/python-2.7.14-docs-pdf-a4.zip ---------- assignee: docs at python components: Documentation files: Screenshot 2017-10-10 12.41.34.png messages: 304024 nosy: docs at python, synthmeat priority: normal severity: normal status: open title: Proportional Width Font on Generated Python Docs PDFs type: enhancement versions: Python 2.7 Added file: https://bugs.python.org/file47203/Screenshot 2017-10-10 12.41.34.png _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 10 09:18:16 2017 From: report at bugs.python.org (STINNER Victor) Date: Tue, 10 Oct 2017 13:18:16 +0000 Subject: [docs] [issue26546] Provide translated french translation on docs.python.org In-Reply-To: <1457794223.79.0.618185263259.issue26546@psf.upfronthosting.co.za> Message-ID: <1507641496.86.0.213398074469.issue26546@psf.upfronthosting.co.za> STINNER Victor added the comment: Since you closed the issue, Julien, I changed the status of the PEP 545 to Final: https://github.com/python/peps/commit/14092e51dea5c5c6391458da4a2ad92adad227b9 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 10 17:53:00 2017 From: report at bugs.python.org (Mariatta Wijaya) Date: Tue, 10 Oct 2017 21:53:00 +0000 Subject: [docs] [issue31537] Bug in readline module documentation example In-Reply-To: <1505938727.72.0.626220071672.issue31537@psf.upfronthosting.co.za> Message-ID: <1507672379.99.0.213398074469.issue31537@psf.upfronthosting.co.za> Mariatta Wijaya added the comment: New changeset eeb5ffd54e56dd89a99c74eb512c36d62649cfec by Mariatta (Brad Smith) in branch 'master': bpo-31537: Update readline documentation example. (GH-3925) https://github.com/python/cpython/commit/eeb5ffd54e56dd89a99c74eb512c36d62649cfec ---------- nosy: +Mariatta _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 10 17:54:12 2017 From: report at bugs.python.org (Roundup Robot) Date: Tue, 10 Oct 2017 21:54:12 +0000 Subject: [docs] [issue31537] Bug in readline module documentation example In-Reply-To: <1505938727.72.0.626220071672.issue31537@psf.upfronthosting.co.za> Message-ID: <1507672452.18.0.912454111764.issue31537@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- pull_requests: +3923 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 10 18:03:16 2017 From: report at bugs.python.org (Mariatta Wijaya) Date: Tue, 10 Oct 2017 22:03:16 +0000 Subject: [docs] [issue31537] Bug in readline module documentation example In-Reply-To: <1505938727.72.0.626220071672.issue31537@psf.upfronthosting.co.za> Message-ID: <1507672996.81.0.213398074469.issue31537@psf.upfronthosting.co.za> Mariatta Wijaya added the comment: New changeset 10eb14e2c5fe08c4193668530eaef156e07c3674 by Mariatta (Miss Islington (bot)) in branch '3.6': bpo-31537: Update readline documentation example. (GH-3925) (GH-3948) https://github.com/python/cpython/commit/10eb14e2c5fe08c4193668530eaef156e07c3674 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 10 18:04:12 2017 From: report at bugs.python.org (Mariatta Wijaya) Date: Tue, 10 Oct 2017 22:04:12 +0000 Subject: [docs] [issue31537] Bug in readline module documentation example In-Reply-To: <1505938727.72.0.626220071672.issue31537@psf.upfronthosting.co.za> Message-ID: <1507673052.51.0.213398074469.issue31537@psf.upfronthosting.co.za> Mariatta Wijaya added the comment: Fixed. Thanks! ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 10 20:18:47 2017 From: report at bugs.python.org (Robert Snoeberger) Date: Wed, 11 Oct 2017 00:18:47 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. Message-ID: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> New submission from Robert Snoeberger : The signature for PyBuffer_FillContiguousStrides in the documentation shows that the type of parameter 'itemsize' is Py_ssize_t [1]. This is different from the signature in Include/abstract.h which shows that the type as int [2]. [1] https://docs.python.org/3/c-api/buffer.html#c.PyBuffer_FillContiguousStrides [2] https://github.com/python/cpython/blob/49b2734bf12dc1cda80fd73d3ec8896ae3e362f2/Include/abstract.h#L559-L563 ---------- assignee: docs at python components: Documentation messages: 304096 nosy: docs at python, snoeberger priority: normal severity: normal status: open title: Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 04:45:47 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Wed, 11 Oct 2017 08:45:47 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. In-Reply-To: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> Message-ID: <1507711547.42.0.912454111764.issue31754@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- keywords: +easy stage: -> needs patch versions: +Python 2.7, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 10:40:20 2017 From: report at bugs.python.org (Heinrich Schnermann) Date: Wed, 11 Oct 2017 14:40:20 +0000 Subject: [docs] [issue31757] Tutorial: Fibonacci numbers start with 1, 1 Message-ID: <1507732819.98.0.213398074469.issue31757@psf.upfronthosting.co.za> New submission from Heinrich Schnermann : In https://docs.python.org/3/tutorial/controlflow.html#defining-functions both examples produce fibonacci numbers starting with 0. They should start with 1, as in the example in https://docs.python.org/3/tutorial/introduction.html#first-steps-towards-programming The first example should change the lines while a < n: print(a, end=' ') to while b < n: print(b, end=' ') and the second example should change the lines while a < n: result.append(a) # see below to while b < n: result.append(b) # see below ---------- assignee: docs at python components: Documentation messages: 304144 nosy: docs at python, skyhein priority: normal severity: normal status: open title: Tutorial: Fibonacci numbers start with 1, 1 type: behavior versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 10:46:48 2017 From: report at bugs.python.org (Berker Peksag) Date: Wed, 11 Oct 2017 14:46:48 +0000 Subject: [docs] [issue23532] add example of 'first match wins' to regex "|" documentation? In-Reply-To: <1424991623.26.0.907615110662.issue23532@psf.upfronthosting.co.za> Message-ID: <1507733208.65.0.912454111764.issue23532@psf.upfronthosting.co.za> Change by Berker Peksag : ---------- stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 12:07:56 2017 From: report at bugs.python.org (Mark Dickinson) Date: Wed, 11 Oct 2017 16:07:56 +0000 Subject: [docs] [issue31757] Tutorial: Fibonacci numbers start with 1, 1 In-Reply-To: <1507732819.98.0.213398074469.issue31757@psf.upfronthosting.co.za> Message-ID: <1507738076.46.0.213398074469.issue31757@psf.upfronthosting.co.za> Mark Dickinson added the comment: Is there any particular reason you want to start with 1? While not universal, it's standard to define `Fib(0) = 0`, and to start the sequence at `0`. (And note that Python usually starts indexing things from 0, so it makes sense to start with `Fib(0)` rather than `Fib(1)`.) In principle, one could define `Fib(0)=1`, `Fib(1)=1`, `Fib(1)=2`, and so on, but there's a strong reason not to do so: it breaks (or at least uglifies) many nice number-theoretic properties, like `gcd(Fib(m), Fib(n)) == Fib(gcd(m, n))`. ---------- nosy: +mark.dickinson _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 12:14:21 2017 From: report at bugs.python.org (Mark Dickinson) Date: Wed, 11 Oct 2017 16:14:21 +0000 Subject: [docs] [issue31757] Tutorial: Fibonacci numbers start with 1, 1 In-Reply-To: <1507732819.98.0.213398074469.issue31757@psf.upfronthosting.co.za> Message-ID: <1507738461.72.0.213398074469.issue31757@psf.upfronthosting.co.za> Mark Dickinson added the comment: A nice response to the question of whether to start with 0 or 1 here: https://stackoverflow.com/a/5901955 > The definition with Fib(0) = 1 is known as the combinatorial > definition, and Fib(0) = 0 is the classical definition. Both > are used in the Fibonacci Quarterly, though authors that use > the combinatorial definition need to add a sentence of > explanation. I confess that I hadn't heard of the Fibonacci Quarterly before. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 12:22:20 2017 From: report at bugs.python.org (Tim Peters) Date: Wed, 11 Oct 2017 16:22:20 +0000 Subject: [docs] [issue31327] bug in dateutil\tz\tz.py In-Reply-To: <1504286649.82.0.482783873664.issue31327@psf.upfronthosting.co.za> Message-ID: <1507738940.53.0.213398074469.issue31327@psf.upfronthosting.co.za> Tim Peters added the comment: Since this is a pretty common gotcha, I'd prefer to add it as an example to the text I already quoted; e.g., add: """ For example, the native Windows C libraries do not support times before the epoch, and `localtime(n)` for negative `n` raises `OSError` on Windows. """ ---------- assignee: -> docs at python components: +Documentation -Library (Lib) nosy: +docs at python type: crash -> enhancement _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 12:24:17 2017 From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=) Date: Wed, 11 Oct 2017 16:24:17 +0000 Subject: [docs] [issue31327] bug in dateutil\tz\tz.py In-Reply-To: <1504286649.82.0.482783873664.issue31327@psf.upfronthosting.co.za> Message-ID: <1507739057.19.0.213398074469.issue31327@psf.upfronthosting.co.za> St?phane Wirtel added the comment: Thank you, I will provide a PR for this issue and close it once it's over. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 12:33:41 2017 From: report at bugs.python.org (Tim Peters) Date: Wed, 11 Oct 2017 16:33:41 +0000 Subject: [docs] [issue31327] bug in dateutil\tz\tz.py In-Reply-To: <1504286649.82.0.482783873664.issue31327@psf.upfronthosting.co.za> Message-ID: <1507739621.37.0.213398074469.issue31327@psf.upfronthosting.co.za> Tim Peters added the comment: I'll just add that it may be a different issue to argue about how `_naive_is_dst()` is implemented. ---------- nosy: +belopolsky _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 12:52:47 2017 From: report at bugs.python.org (Alexander Belopolsky) Date: Wed, 11 Oct 2017 16:52:47 +0000 Subject: [docs] [issue31327] bug in dateutil\tz\tz.py In-Reply-To: <1504286649.82.0.482783873664.issue31327@psf.upfronthosting.co.za> Message-ID: <1507740767.66.0.213398074469.issue31327@psf.upfronthosting.co.za> Alexander Belopolsky added the comment: Is this similar to issue 29097? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 12:55:04 2017 From: report at bugs.python.org (Denis Osipov) Date: Wed, 11 Oct 2017 16:55:04 +0000 Subject: [docs] [issue31761] Possible error in devguide part about tests Message-ID: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> New submission from Denis Osipov : In Developer Guide says: "If you don?t have easy access to a command line, you can run the test suite from a Python or IDLE shell: >>> from test import autotest" But I can't run test from IDLE: Traceback (most recent call last): File "", line 1, in from test import autotest File "D:\repos\cpython\Lib\test\autotest.py", line 5, in main() File "D:\repos\cpython\Lib\test\libregrtest\main.py", line 585, in main Regrtest().main(tests=tests, **kwargs) File "D:\repos\cpython\Lib\test\libregrtest\main.py", line 510, in main self._main(tests, kwargs) File "D:\repos\cpython\Lib\test\libregrtest\main.py", line 524, in _main setup_tests(self.ns) File "D:\repos\cpython\Lib\test\libregrtest\setup.py", line 18, in setup_tests faulthandler.enable(all_threads=True) io.UnsupportedOperation: fileno If I understand it correct, this behavior is reasonable (issues 3003 and 25588). Maybe it's worth to remove words about running from IDLE. Or in case if it's possible to run such tests add some words about it. ---------- assignee: docs at python components: Documentation messages: 304163 nosy: denis-osipov, docs at python priority: normal severity: normal status: open title: Possible error in devguide part about tests type: behavior versions: Python 3.7, Python 3.8 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 13:18:50 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Wed, 11 Oct 2017 17:18:50 +0000 Subject: [docs] [issue31761] Possible error in devguide part about tests In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1507742330.24.0.912454111764.issue31761@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- nosy: +haypo _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 14:00:28 2017 From: report at bugs.python.org (Heinrich Schnermann) Date: Wed, 11 Oct 2017 18:00:28 +0000 Subject: [docs] [issue31757] Tutorial: Fibonacci numbers start with 1, 1 In-Reply-To: <1507732819.98.0.213398074469.issue31757@psf.upfronthosting.co.za> Message-ID: <1507744828.32.0.213398074469.issue31757@psf.upfronthosting.co.za> Heinrich Schnermann added the comment: I would not insist of starting with 1 instead of 0 (I follow your arguments here), but perhaps it would be nice if it would behave the same way in both chapters. The first fibonacci number examples in https://docs.python.org/3/tutorial/introduction.html#first-steps-towards-programming start with 1. There are three examples here, in the first, while b < 10: print(b) should change to while a < 10: print(a) The output of this first example would have an additional 0: 0 1 1 ... And in the third example while b < 1000: print(b, end=',') should change to while a < 1000: print(a, end=',') where the output of this third example would change from 1,1,2,3,5,8,13,21,34,55,89,144,233,377,610,987, to 0,1,1,2,3,5,8,13,21,34,55,89,144,233,377,610,987, ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 15:18:19 2017 From: report at bugs.python.org (Mark Dickinson) Date: Wed, 11 Oct 2017 19:18:19 +0000 Subject: [docs] [issue31757] Tutorial: Fibonacci numbers start with 1, 1 In-Reply-To: <1507732819.98.0.213398074469.issue31757@psf.upfronthosting.co.za> Message-ID: <1507749499.42.0.213398074469.issue31757@psf.upfronthosting.co.za> Mark Dickinson added the comment: I agree it would be good to be consistent. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 17:18:38 2017 From: report at bugs.python.org (Anthony Flury) Date: Wed, 11 Oct 2017 21:18:38 +0000 Subject: [docs] [issue31766] Python 3.5 missing from documentation Message-ID: <1507756717.96.0.213398074469.issue31766@psf.upfronthosting.co.za> New submission from Anthony Flury : In the Python version pull down list on docs.python.org, Python3.5 used to be listed, but has now been removed; the list only contains 2.7, 3.6 & 3.7. Python 3.5 is still the official Python 3.5 release in the Ubuntu repository, and still a supported release in other parts of python.org, so to see it disappearing from the drop-down was surprising. To note - if you pick a particular page - say : https://docs.python.org/3/tutorial/index.html and change the url to : https://docs.python.org/3.5/tutorial/index.html The pull down now does contain 3.5 (along side 2.7, 3.63 & 3.7) ---------- assignee: docs at python components: Documentation messages: 304181 nosy: anthony-flury, docs at python priority: normal severity: normal status: open title: Python 3.5 missing from documentation type: behavior versions: Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 17:55:25 2017 From: report at bugs.python.org (Ned Deily) Date: Wed, 11 Oct 2017 21:55:25 +0000 Subject: [docs] [issue31766] Python 3.5 missing from documentation In-Reply-To: <1507756717.96.0.213398074469.issue31766@psf.upfronthosting.co.za> Message-ID: <1507758925.38.0.213398074469.issue31766@psf.upfronthosting.co.za> Ned Deily added the comment: The documentation for 3.5 was deliberated removed from the pull down lists of current docsets as 3.5 is now in security-fix-only mode; the 3.5 documentation is only updated when a new security release is made and general doc changes to it are no longer made. You can find a link to the docsets for 3.5.x and all Python releases on the Python Documentation By Version page (https://www.python.org/doc/versions/) which is linked to from a number of places, including the index page of the current and past Python versions docsets (e.g. https://docs.python.org/3/) and from the main python.org doc page (https://www.python.org/doc/). ---------- nosy: +larry, ned.deily resolution: -> not a bug status: open -> pending _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 19:50:27 2017 From: report at bugs.python.org (Steven D'Aprano) Date: Wed, 11 Oct 2017 23:50:27 +0000 Subject: [docs] [issue31757] Tutorial: Fibonacci numbers start with 1, 1 In-Reply-To: <1507732819.98.0.213398074469.issue31757@psf.upfronthosting.co.za> Message-ID: <1507765827.11.0.912454111764.issue31757@psf.upfronthosting.co.za> Change by Steven D'Aprano : ---------- nosy: +steven.daprano _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 11 21:38:32 2017 From: report at bugs.python.org (Daisuke Miyakawa) Date: Thu, 12 Oct 2017 01:38:32 +0000 Subject: [docs] [issue31567] Inconsistent documentation around decorators In-Reply-To: <1506238290.29.0.485453330645.issue31567@psf.upfronthosting.co.za> Message-ID: <1507772312.67.0.912454111764.issue31567@psf.upfronthosting.co.za> Change by Daisuke Miyakawa : ---------- keywords: +patch pull_requests: +3935 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 05:16:23 2017 From: report at bugs.python.org (STINNER Victor) Date: Thu, 12 Oct 2017 09:16:23 +0000 Subject: [docs] [issue31761] regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1507799783.79.0.912454111764.issue31761@psf.upfronthosting.co.za> Change by STINNER Victor : ---------- components: +Tests -Documentation title: Possible error in devguide part about tests -> regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 05:51:16 2017 From: report at bugs.python.org (STINNER Victor) Date: Thu, 12 Oct 2017 09:51:16 +0000 Subject: [docs] [issue31761] regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1507801876.5.0.213398074469.issue31761@psf.upfronthosting.co.za> STINNER Victor added the comment: > "If you don?t have easy access to a command line, you can run the test suite from a Python or IDLE shell: The devguide is wrong. You should not run the Python test suite in IDLE. It doesn't work and many tests fail just because of IDLE. Please run the test suite in a command line (like "cmd.exe" on Windows). ---------- _______________________________________ Python tracker _______________________________________ From miganosiris8 at gmail.com Mon Oct 9 15:45:14 2017 From: miganosiris8 at gmail.com (Osiris Migan) Date: Mon, 9 Oct 2017 21:45:14 +0200 Subject: [docs] =?utf-8?q?Demande_de_la_version_fran=C3=A7aise_de_la_docu?= =?utf-8?q?mentation_3=2E6=2E3_de_python?= In-Reply-To: References: Message-ID: Bonjour monsieur. Je suis un d?butant en programmation et je ne ma?trise que le fran?ais tr?s bien. Voulez-vous bien m'envoyer la version fran?aise de ce livre?merci pour votre compr?hension -------------- next part -------------- An HTML attachment was scrubbed... URL: From report at bugs.python.org Thu Oct 12 09:37:55 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Thu, 12 Oct 2017 13:37:55 +0000 Subject: [docs] [issue31771] tkinter geometry string +- when window ovelaps left or top of screen In-Reply-To: <1507814776.62.0.213398074469.issue31771@psf.upfronthosting.co.za> Message-ID: <1507815475.67.0.213398074469.issue31771@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: Tkinter is just a wrapper around the Tk library. It returns what Tk returns. See Tk documentation: https://www.tcl.tk/man/tcl8.6/TkCmd/winfo.htm#M15 https://www.tcl.tk/man/tcl8.6/TkCmd/wm.htm#M42 If you want to improve Tkinter documentation, patches are welcome. ---------- assignee: -> docs at python components: +Documentation nosy: +docs at python, serhiy.storchaka type: behavior -> enhancement versions: +Python 2.7, Python 3.6, Python 3.7 -Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 10:39:46 2017 From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=) Date: Thu, 12 Oct 2017 14:39:46 +0000 Subject: [docs] [issue31567] Inconsistent documentation around decorators In-Reply-To: <1506238290.29.0.485453330645.issue31567@psf.upfronthosting.co.za> Message-ID: <1507819185.9.0.213398074469.issue31567@psf.upfronthosting.co.za> ?ric Araujo added the comment: New changeset 0e61e67a57deb4abc677808201d7cf3c38138e02 by ?ric Araujo (Daisuke Miyakawa) in branch 'master': bpo-31567: add or fix decorator markup in docs (#3959) https://github.com/python/cpython/commit/0e61e67a57deb4abc677808201d7cf3c38138e02 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 10:40:40 2017 From: report at bugs.python.org (Roundup Robot) Date: Thu, 12 Oct 2017 14:40:40 +0000 Subject: [docs] [issue31567] Inconsistent documentation around decorators In-Reply-To: <1506238290.29.0.485453330645.issue31567@psf.upfronthosting.co.za> Message-ID: <1507819240.28.0.912454111764.issue31567@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- pull_requests: +3944 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 10:41:24 2017 From: report at bugs.python.org (Denis Osipov) Date: Thu, 12 Oct 2017 14:41:24 +0000 Subject: [docs] [issue31761] regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1507819284.42.0.213398074469.issue31761@psf.upfronthosting.co.za> Denis Osipov added the comment: Got it. Thank you for your help. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 10:48:33 2017 From: report at bugs.python.org (Berker Peksag) Date: Thu, 12 Oct 2017 14:48:33 +0000 Subject: [docs] [issue31567] Inconsistent documentation around decorators In-Reply-To: <1506238290.29.0.485453330645.issue31567@psf.upfronthosting.co.za> Message-ID: <1507819713.32.0.213398074469.issue31567@psf.upfronthosting.co.za> Berker Peksag added the comment: Use of classmethod and staticmethod decorators as functions is still a valid use case. I think the old signatures should be kept. It should be possible to document both uses in same place: .. function:: classmethod(function) .. decorator:: classmethod Documentation body. ---------- nosy: +berker.peksag _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 11:10:13 2017 From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=) Date: Thu, 12 Oct 2017 15:10:13 +0000 Subject: [docs] [issue31567] Inconsistent documentation around decorators In-Reply-To: <1506238290.29.0.485453330645.issue31567@psf.upfronthosting.co.za> Message-ID: <1507821013.23.0.912454111764.issue31567@psf.upfronthosting.co.za> Change by ?ric Araujo : ---------- pull_requests: +3945 _______________________________________ Python tracker _______________________________________ From berker.peksag at gmail.com Thu Oct 12 11:27:55 2017 From: berker.peksag at gmail.com (=?UTF-8?Q?Berker_Peksa=C4=9F?=) Date: Thu, 12 Oct 2017 18:27:55 +0300 Subject: [docs] (minor issue) Missing string `_widget` in example code of unittest In-Reply-To: References: Message-ID: On Fri, Jun 9, 2017 at 12:26 PM, John Gamboa wrote: > TL;DR: instead of `test_default_size` and `test_resize`, the strings should > be `test_default_widget_size` and `test_default_resize` in the snippet > explaining how to create a test suite (defining the function `suite()`) in > the documentation of Python 3. Hi John, Thank you for the report. I've opened https://github.com/python/cpython/pull/3967 to fix this. --Berker From report at bugs.python.org Thu Oct 12 11:29:25 2017 From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=) Date: Thu, 12 Oct 2017 15:29:25 +0000 Subject: [docs] [issue31567] Inconsistent documentation around decorators In-Reply-To: <1506238290.29.0.485453330645.issue31567@psf.upfronthosting.co.za> Message-ID: <1507822165.67.0.213398074469.issue31567@psf.upfronthosting.co.za> ?ric Araujo added the comment: I think existing uses of the decorator markup rely on the reader?s understanding that it?s syntactic sugar for a call and an assignment, and they don?t have decorator+function markup. The PRs for this ticket follow that. That said, staticmethod as a non-decorator has an important use case for function injection in tests (using self.func in TestCase classes that work with a C module and an equivalent Python version). Maybe this deserves an extra example? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 11:46:54 2017 From: report at bugs.python.org (Berker Peksag) Date: Thu, 12 Oct 2017 15:46:54 +0000 Subject: [docs] [issue31567] Inconsistent documentation around decorators In-Reply-To: <1506238290.29.0.485453330645.issue31567@psf.upfronthosting.co.za> Message-ID: <1507823214.33.0.213398074469.issue31567@psf.upfronthosting.co.za> Berker Peksag added the comment: > That said, staticmethod as a non-decorator has an important use case for > function injection in tests (using self.func in TestCase classes that work with > a C module and an equivalent Python version). Maybe this deserves an extra > example? Yes, that would be nice. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 12:28:59 2017 From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=) Date: Thu, 12 Oct 2017 16:28:59 +0000 Subject: [docs] [issue31567] Inconsistent documentation around decorators In-Reply-To: <1506238290.29.0.485453330645.issue31567@psf.upfronthosting.co.za> Message-ID: <1507825739.13.0.213398074469.issue31567@psf.upfronthosting.co.za> ?ric Araujo added the comment: New changeset 03b9537dc515d10528f83c920d38910b95755aff by ?ric Araujo in branch 'master': bpo-31567: more decorator markup fixes in docs (GH-3959) (#3966) https://github.com/python/cpython/commit/03b9537dc515d10528f83c920d38910b95755aff ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 12:33:07 2017 From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=) Date: Thu, 12 Oct 2017 16:33:07 +0000 Subject: [docs] [issue31567] Inconsistent documentation around decorators In-Reply-To: <1506238290.29.0.485453330645.issue31567@psf.upfronthosting.co.za> Message-ID: <1507825987.6.0.213398074469.issue31567@psf.upfronthosting.co.za> ?ric Araujo added the comment: New changeset 205dd4e14de77f9c8ed2903ddebbcf9968bbb6a9 by ?ric Araujo (Miss Islington (bot)) in branch '3.6': [3.6] bpo-31567: add or fix decorator markup in docs (GH-3959) (GH-3966) https://github.com/python/cpython/commit/205dd4e14de77f9c8ed2903ddebbcf9968bbb6a9 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 12:34:21 2017 From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=) Date: Thu, 12 Oct 2017 16:34:21 +0000 Subject: [docs] [issue31567] Inconsistent documentation around decorators In-Reply-To: <1506238290.29.0.485453330645.issue31567@psf.upfronthosting.co.za> Message-ID: <1507826061.21.0.213398074469.issue31567@psf.upfronthosting.co.za> ?ric Araujo added the comment: Cheers! ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 13:10:46 2017 From: report at bugs.python.org (Mariatta Wijaya) Date: Thu, 12 Oct 2017 17:10:46 +0000 Subject: [docs] [issue31761] regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1507828246.53.0.213398074469.issue31761@psf.upfronthosting.co.za> Mariatta Wijaya added the comment: Closing this issue, I opened https://github.com/python/devguide/issues/280 so that Dev Guide can be updated. Thanks! ---------- nosy: +Mariatta resolution: -> not a bug stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 13:39:57 2017 From: report at bugs.python.org (Anthony Flury) Date: Thu, 12 Oct 2017 17:39:57 +0000 Subject: [docs] [issue31766] Python 3.5 missing from documentation In-Reply-To: <1507756717.96.0.213398074469.issue31766@psf.upfronthosting.co.za> Message-ID: <1507829997.48.0.213398074469.issue31766@psf.upfronthosting.co.za> Anthony Flury added the comment: Isn't Python 2.7 in Security Fix only as well ? It seems strange; Python 3.5 probably the most heavily installed Python 3 release (every Ubuntu installation has Python 3.5 installed by default - and neither Python 3.6 or 3.7 are available from the standard ubuntu repository); the docs.python.org site is the normal place people are directed to for help - and the implication of the removal will be for many people is that Python 3.5 is obsolete which isn't the case at all. ---------- status: pending -> open _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 13:43:27 2017 From: report at bugs.python.org (Fred L. Drake, Jr.) Date: Thu, 12 Oct 2017 17:43:27 +0000 Subject: [docs] [issue31766] Python 3.5 missing from documentation In-Reply-To: <1507756717.96.0.213398074469.issue31766@psf.upfronthosting.co.za> Message-ID: <1507830207.45.0.213398074469.issue31766@psf.upfronthosting.co.za> Fred L. Drake, Jr. added the comment: The 3.5 docs should really remain in the main docs UI via the pulldown as long as it's so widely used. The fact that it won't be changing much just means it can be served efficiently. ---------- nosy: +fdrake _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 13:49:05 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Thu, 12 Oct 2017 17:49:05 +0000 Subject: [docs] [issue31761] regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1507830545.39.0.213398074469.issue31761@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: See issue25588. Currently running tests from IDLE doesn't work, but it worked in the past and maybe we can make it working again. ---------- nosy: +serhiy.storchaka _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 14:04:19 2017 From: report at bugs.python.org (Ned Deily) Date: Thu, 12 Oct 2017 18:04:19 +0000 Subject: [docs] [issue31766] Python 3.5 missing from documentation In-Reply-To: <1507756717.96.0.213398074469.issue31766@psf.upfronthosting.co.za> Message-ID: <1507831459.9.0.912454111764.issue31766@psf.upfronthosting.co.za> Change by Ned Deily : ---------- keywords: +patch pull_requests: +3947 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 14:08:45 2017 From: report at bugs.python.org (Ned Deily) Date: Thu, 12 Oct 2017 18:08:45 +0000 Subject: [docs] [issue31766] Python 3.5 missing from documentation In-Reply-To: <1507756717.96.0.213398074469.issue31766@psf.upfronthosting.co.za> Message-ID: <1507831725.8.0.213398074469.issue31766@psf.upfronthosting.co.za> Ned Deily added the comment: New changeset b7cbfe49e39a7bbd7da20b937735a8a60bbf1872 by Ned Deily in branch 'master': bpo-31766: restore 3.5 to docs version switchers (#3969) https://github.com/python/cpython/commit/b7cbfe49e39a7bbd7da20b937735a8a60bbf1872 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 14:12:22 2017 From: report at bugs.python.org (Ned Deily) Date: Thu, 12 Oct 2017 18:12:22 +0000 Subject: [docs] [issue31766] Python 3.5 missing from documentation In-Reply-To: <1507756717.96.0.213398074469.issue31766@psf.upfronthosting.co.za> Message-ID: <1507831942.33.0.912454111764.issue31766@psf.upfronthosting.co.za> Change by Ned Deily : ---------- pull_requests: +3948 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 14:19:09 2017 From: report at bugs.python.org (Ned Deily) Date: Thu, 12 Oct 2017 18:19:09 +0000 Subject: [docs] [issue31766] Python 3.5 missing from documentation In-Reply-To: <1507756717.96.0.213398074469.issue31766@psf.upfronthosting.co.za> Message-ID: <1507832349.46.0.213398074469.issue31766@psf.upfronthosting.co.za> Ned Deily added the comment: New changeset f8d42ea0e4341b270f1de71b4ff40cfa18420eed by Ned Deily in branch '3.6': bpo-31766: restore 3.5 to docs version switchers (#3970) https://github.com/python/cpython/commit/f8d42ea0e4341b270f1de71b4ff40cfa18420eed ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 14:20:47 2017 From: report at bugs.python.org (Ned Deily) Date: Thu, 12 Oct 2017 18:20:47 +0000 Subject: [docs] [issue31766] Python 3.5 missing from documentation In-Reply-To: <1507756717.96.0.213398074469.issue31766@psf.upfronthosting.co.za> Message-ID: <1507832447.2.0.912454111764.issue31766@psf.upfronthosting.co.za> Change by Ned Deily : ---------- pull_requests: +3949 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 14:24:25 2017 From: report at bugs.python.org (Ned Deily) Date: Thu, 12 Oct 2017 18:24:25 +0000 Subject: [docs] [issue31766] Python 3.5 missing from documentation In-Reply-To: <1507756717.96.0.213398074469.issue31766@psf.upfronthosting.co.za> Message-ID: <1507832665.54.0.213398074469.issue31766@psf.upfronthosting.co.za> Ned Deily added the comment: New changeset 356b68023d6fee5e30d25a4a680ac5b9e4f8dd65 by Ned Deily in branch '2.7': bpo-31766: restore 3.5 to docs version switchers (#3971) https://github.com/python/cpython/commit/356b68023d6fee5e30d25a4a680ac5b9e4f8dd65 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 14:31:21 2017 From: report at bugs.python.org (Ned Deily) Date: Thu, 12 Oct 2017 18:31:21 +0000 Subject: [docs] [issue31766] Python 3.5 missing from documentation In-Reply-To: <1507756717.96.0.213398074469.issue31766@psf.upfronthosting.co.za> Message-ID: <1507833081.1.0.213398074469.issue31766@psf.upfronthosting.co.za> Ned Deily added the comment: > Isn't Python 2.7 in Security Fix only as well ? No, 2.7 is still being actively maintained (until 2020). (https://devguide.python.org/#status-of-python-branches) But, bowing to popular demand, I've restored 3.5 to the switchers for 3.7, 3.6, and 2.7. It should appear again in the on-line docs shortly. Thanks for all of your comments! ---------- resolution: not a bug -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 2.7, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 15:19:21 2017 From: report at bugs.python.org (paul j3) Date: Thu, 12 Oct 2017 19:19:21 +0000 Subject: [docs] [issue31640] Document exit() from parse_args In-Reply-To: <1506704042.9.0.213398074469.issue31640@psf.upfronthosting.co.za> Message-ID: <1507835961.61.0.213398074469.issue31640@psf.upfronthosting.co.za> paul j3 added the comment: And the actual exit is via `parse.error` and `parse.exit`, which are documented in 16.4.5.9. When run interactively in Ipython, exits (including the help) are captured and displayed with: In [896]: parser.parse_args() usage: ipython3 [-h] [--one | --two | --six] ipython3: error: unrecognized arguments: --pylab --nosep --term-title --InteractiveShellApp.pylab_import_all=False An exception has occurred, use %tb to see the full traceback. SystemExit: 2 The exit makes unittesting a challenge. 'test_argparse.py' resolves this by using a subclassed parser, one that changes the error/exit, and also redirects output. ---------- nosy: +paul.j3 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 19:18:26 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Thu, 12 Oct 2017 23:18:26 +0000 Subject: [docs] [issue31761] regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1507850306.31.0.213398074469.issue31761@psf.upfronthosting.co.za> Terry J. Reedy added the comment: Victor, what is your opinion of running 'from test import autotest' in a standard python shell window, opened from an icon, as opposed to IDLE's shell? > many tests fail just because of IDLE. We cannot know what to blame on IDLE without a proper control experiment. I updated my Win10 repository, rebuilt python 3.7, ran the tests from the command line, and all passed (thank you for making this routine). I ran autotest in a Python console and saw a new resource warning from one of the async tests and 3 failures. I cannot say what they were because when the test finished, the window closed (crashed), which is a metafailure. I will rerun and try to identify the error as they occur. Should we reopen this issue or open a new issue, to fix problems not due to IDLE, or remove the entire suggestion to use autotest, and remove autotest itself? ---------- nosy: +terry.reedy _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 19:42:47 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Thu, 12 Oct 2017 23:42:47 +0000 Subject: [docs] [issue31761] regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1507851767.03.0.213398074469.issue31761@psf.upfronthosting.co.za> Terry J. Reedy added the comment: 0:00:28 [ 25/407] test_asyncio F:\dev\3x\lib\asyncio\sslproto.py:330: ResourceWarning: unclosed transport source=self) test_code_module - multiple errors test test_importlib failed -- Traceback (most recent call last): File "F:\dev\3x\lib\test\test_importlib\test_locks.py", line 134, in test_all_locks self.bootstrap._module_locks) AssertionError: 0 != 1 : {'test.autotest': } test_warnings failed - multiple errors crash after summary printed. I am rerunning in python started from command to see if there is any message printed. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 20:34:15 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Fri, 13 Oct 2017 00:34:15 +0000 Subject: [docs] [issue31761] regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1507854855.23.0.213398074469.issue31761@psf.upfronthosting.co.za> Terry J. Reedy added the comment: The Python console exits because test.libregrtest.main.Regrtest._main calls sys.exit. test.autotest consists of from test.libregrtest import main main() The main call should be wrapped with try:...except sys.exit: pass The output also has this variance from the command line result. 0:15:47 [319/407/2] test_subprocess minkernel\crts\ucrt\src\appcrt\lowio\write.cpp(49) : Assertion failed: (_osfile(fh) & FOPEN) minkernel\crts\ucrt\src\appcrt\lowio\close.cpp(49) : Assertion failed: (_osfile(fh) & FOPEN) minkernel\crts\ucrt\src\appcrt\lowio\close.cpp(49) : Assertion failed: (_osfile(fh) & FOPEN) The list of tests skipped seems to be the same. By setting sys.argv before importing autotest, I got ====================================================================== FAIL: test_ps1 (test.test_code_module.TestInteractiveConsole) ---------------------------------------------------------------------- Traceback (most recent call last): File "F:\dev\3x\lib\test\test_code_module.py", line 35, in test_ps1 self.assertEqual(self.sysmod.ps1, '>>> ') AssertionError: != '>>> ' ====================================================================== FAIL: test_ps2 (test.test_code_module.TestInteractiveConsole) ---------------------------------------------------------------------- Traceback (most recent call last): File "F:\dev\3x\lib\test\test_code_module.py", line 40, in test_ps2 self.assertEqual(self.sysmod.ps2, '... ') AssertionError: != '... ' ---------------------------------------------------------------------- ====================================================================== FAIL: test_missing_filename_main_with_argv (test.test_warnings.CWarnTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "F:\dev\3x\lib\test\test_warnings\__init__.py", line 446, in test_missing_filename_main_with_argv self.assertEqual(w[-1].filename, sys.argv[0]) AssertionError: '__main__' != '' - __main__ + and ====================================================================== FAIL: test_missing_filename_main_with_argv (test.test_warnings.PyWarnTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "F:\dev\3x\lib\test\test_warnings\__init__.py", line 446, in test_missing_filename_main_with_argv self.assertEqual(w[-1].filename, sys.argv[0]) AssertionError: '__main__' != '' - __main__ Wneh I start python with python.bat, sys.argv = [''], not ['__main__']. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 12 21:05:02 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Fri, 13 Oct 2017 01:05:02 +0000 Subject: [docs] [issue31761] regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1507856701.95.0.213398074469.issue31761@psf.upfronthosting.co.za> Terry J. Reedy added the comment: When I import autotest in IDLE's shell, test_code_module fails, test_importlib and test_warnings fail, as without IDLE, and test_gc and test_logging are new failures. (Results are easy to see because SystemExit is caught and ignored.) test test_gc failed -- Traceback (most recent call last): File "F:\dev\3x\lib\test\support\__init__.py", line 1855, in wrapper return func(*args, **kwargs) File "F:\dev\3x\lib\test\test_gc.py", line 290, in test_get_count self.assertLess(a, 5) AssertionError: 8 not less than 5 test test_logging failed -- Traceback (most recent call last): File "F:\dev\3x\lib\test\test_logging.py", line 1960, in test_warnings "dummy.py:42: UserWarning: Explicit\n Dummy line\n") AssertionError: '\nWarning (from warnings module):\n File[57 chars]it\n' != 'dummy.py:42: UserWarning: Explicit\n Dummy line\n' + dummy.py:42: UserWarning: Explicit - - Warning (from warnings module): - File "dummy.py", line 42 - Dummy line ? -- + Dummy line - UserWarning: Explicit IDLE replaces warnings.show_warnings. In any case, there are 3 failures in Python's shell versus 4 in IDLE's shell. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 13 04:33:08 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Fri, 13 Oct 2017 08:33:08 +0000 Subject: [docs] [issue31761] regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1507883588.61.0.213398074469.issue31761@psf.upfronthosting.co.za> Terry J. Reedy added the comment: After starting Python from a command line instead of an icon, importing/running autotest results in the same three failures. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 13 16:23:19 2017 From: report at bugs.python.org (Aniket Vyas) Date: Fri, 13 Oct 2017 20:23:19 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. In-Reply-To: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> Message-ID: <1507926199.83.0.213398074469.issue31754@psf.upfronthosting.co.za> Aniket Vyas added the comment: Hello ! I am new to the community and would love to start my contribution here. Can I take up this bug ? In order to do so I am going through the following links: https://docs.python.org/devguide/docquality.html https://docs.python.org/devguide/pullrequest.html Is the list exhaustive for this particular issue ? Thanks ! ---------- nosy: +Aniket Vyas _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 13 16:54:50 2017 From: report at bugs.python.org (Mariatta Wijaya) Date: Fri, 13 Oct 2017 20:54:50 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. In-Reply-To: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> Message-ID: <1507928090.39.0.213398074469.issue31754@psf.upfronthosting.co.za> Mariatta Wijaya added the comment: Welcome Aniket. Yes those two links are good starting points. Please propose a PR with the fix. ---------- nosy: +Mariatta _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 13 17:24:28 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Fri, 13 Oct 2017 21:24:28 +0000 Subject: [docs] [issue31757] Tutorial: Fibonacci numbers start with 1, 1 In-Reply-To: <1507732819.98.0.213398074469.issue31757@psf.upfronthosting.co.za> Message-ID: <1507929868.51.0.213398074469.issue31757@psf.upfronthosting.co.za> Terry J. Reedy added the comment: I agree that we should be consistent -- with the current standard definition -- with the changes suggested above. Heinrich, can you, and do you want to, submit a patch? If so, please also sign the contributor agreement. See https://www.python.org/psf/contrib/ The Fibonacci numbers start with 1 if there is no F(0), as in Fibonacci's rabbit model. Before 0 was accepted as a number, the series had to start with F(1) = F(2) = 1. See https://en.wikipedia.org/wiki/Fibonacci_number ---------- nosy: +terry.reedy _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 01:05:42 2017 From: report at bugs.python.org (Nick Coghlan) Date: Sat, 14 Oct 2017 05:05:42 +0000 Subject: [docs] [issue31778] ast.literal_eval supports non-literals in Python 3 In-Reply-To: <1507847478.46.0.213398074469.issue31778@psf.upfronthosting.co.za> Message-ID: <1507957542.17.0.213398074469.issue31778@psf.upfronthosting.co.za> Nick Coghlan added the comment: I'm marking this as documentation issue for now, as the operators that literal_eval allows are solely those where constant folding support is needed to correctly handle complex and negative numbers (as noted in the original post): ``` >>> dis.dis("+1") 1 0 LOAD_CONST 1 (1) 2 RETURN_VALUE >>> dis.dis("-1") 1 0 LOAD_CONST 1 (-1) 2 RETURN_VALUE >>> dis.dis("1+1") 1 0 LOAD_CONST 1 (2) 2 RETURN_VALUE >>> dis.dis("1+1j") 1 0 LOAD_CONST 2 ((1+1j)) 2 RETURN_VALUE >>> dis.dis("2017-10-10") 1 0 LOAD_CONST 3 (1997) 2 RETURN_VALUE ``` So the key promise that literal_eval makes is that it will not permit arbitrary code execution, but the docs should make it clearer that it *does* permit constant folding for addition and subtraction in order to handle the full range of numeric literals. If folks want to ensure that the input string *doesn't* include a binary operator, then that currently needs to be checked separately with ast.parse: ``` >>> type(ast.parse("2+3").body[0].value) is ast.BinOp True >>> type(ast.parse("2017-10-10").body[0].value) is ast.BinOp True ``` For 3.7+, that check could potentially be encapsulated as an "allow_folding=True" keyword-only parameter (where the default gives the current behaviour, while "allow_folding=False" disables processing of UnaryOp and BinOp), but the docs update is the more immediate need. ---------- assignee: -> docs at python components: +Documentation nosy: +docs at python versions: +Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 01:14:32 2017 From: report at bugs.python.org (Raymond Hettinger) Date: Sat, 14 Oct 2017 05:14:32 +0000 Subject: [docs] [issue31757] Tutorial: Fibonacci numbers start with 1, 1 In-Reply-To: <1507732819.98.0.213398074469.issue31757@psf.upfronthosting.co.za> Message-ID: <1507958072.6.0.912454111764.issue31757@psf.upfronthosting.co.za> Change by Raymond Hettinger : ---------- assignee: docs at python -> rhettinger nosy: +rhettinger versions: +Python 3.7 -Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 01:19:47 2017 From: report at bugs.python.org (Raymond Hettinger) Date: Sat, 14 Oct 2017 05:19:47 +0000 Subject: [docs] [issue31757] Tutorial: Fibonacci numbers start with 1, 1 In-Reply-To: <1507732819.98.0.213398074469.issue31757@psf.upfronthosting.co.za> Message-ID: <1507958387.83.0.213398074469.issue31757@psf.upfronthosting.co.za> Raymond Hettinger added the comment: I update the example in "First Steps Towards Programming" to match the one in "Defining Functions" (which is also shown on the home page at www.python.org. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 01:48:37 2017 From: report at bugs.python.org (Raymond Hettinger) Date: Sat, 14 Oct 2017 05:48:37 +0000 Subject: [docs] [issue31757] Tutorial: Fibonacci numbers start with 1, 1 In-Reply-To: <1507732819.98.0.213398074469.issue31757@psf.upfronthosting.co.za> Message-ID: <1507960117.09.0.912454111764.issue31757@psf.upfronthosting.co.za> Change by Raymond Hettinger : ---------- keywords: +patch pull_requests: +3967 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 02:08:21 2017 From: report at bugs.python.org (David Bieber) Date: Sat, 14 Oct 2017 06:08:21 +0000 Subject: [docs] [issue31778] ast.literal_eval supports non-literals in Python 3 In-Reply-To: <1507847478.46.0.213398074469.issue31778@psf.upfronthosting.co.za> Message-ID: <1507961300.86.0.213398074469.issue31778@psf.upfronthosting.co.za> David Bieber added the comment: # Replies > Rolling back previous enhancements would break existing code. I sympathize completely with the need to maintain backward compatibility. And if this is the reason that this issue gets treated only as a documentation issue, rather than as a behavior issue, I can appreciate that. If that is the case and literal_eval is not going to only evaluate literals, then for my use case I'll need a way to determine from a string whether it represents a literal. I can implement this myself using ast.parse and walking the resulting tree, looking for non-literal AST nodes. Would such an "is_literal" function would be more appropriate in the ast module than as a one-off function in Python Fire? > The key promise that literal_eval makes is that it will not permit arbitrary code execution. I disagree that this is the only key promise, and here's my reasoning. The docstring has two sentences, and each one makes a promise: 1. "Safely evaluate an expression node or a string containing a Python expression." 2. "The string or node provided may only consist of the following Python literal structures: strings, bytes, numbers, tuples, lists, dicts, sets, booleans, and None." (1) says that evaluation is safe -- this is the key promise that you reference. (2) is also a promise though, that only certain types are allowed. While one could argue that the behavior of the function is not specified for inputs violating that criteria, I think the clear correct thing to do is to raise a ValueError if the value doesn't meet the criteria. This is what was done in Python 2, where the docstring for literal_eval is these same two sentences (modulo the inclusion of bytes and sets). It's my opinion that Python 2's behavior better matches the docstring as well as the behavior implied by the function's name. # Additional observations 1. Python 2 _does_ support parsing complex literals, but does not support treating e.g. '1+1' as a literal. ast.literal_eval('1+1j') # works in both Python 2 and Python 3 ast.literal_eval('1j+1') # raises a ValueError in Python 2, returns 1+1j in Python 3 ast.literal_eval('1+1') # raises a ValueError in Python 2, returns 2 in Python 3 2. Python 3 supports parsing addition and subtraction at any level of nesting. ast.literal_eval('(1, (0, 1+1+1))') # raises a ValueError in Python 2, returns (1, (0, 3)) in Python 3 In my opinion, Python 2's behavior is correct in these situations since it matches the documentation and only evals literals as defined in the documentation. # Source The relevant code in Python 2.7.3 is [here](https://github.com/enthought/Python-2.7.3/blob/69fe0ffd2d85b4002cacae1f28ef2eb0f25e16ae/Lib/ast.py#L67). It explicitly allows NUM +/- COMPLEX, but not even COMPLEX +/- NUM. The corresponding code for Python 3 is [here](https://github.com/python/cpython/blob/ef611c96eab0ab667ebb43fdf429b319f6d99890/Lib/ast.py#L76). You'll notice it supports adding and subtracting arbitrary numeric types (int, float, complex). --- Thanks for your replies and for hearing me out on this issue. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 03:17:49 2017 From: report at bugs.python.org (Aniket Vyas) Date: Sat, 14 Oct 2017 07:17:49 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. In-Reply-To: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> Message-ID: <1507965469.76.0.912454111764.issue31754@psf.upfronthosting.co.za> Change by Aniket Vyas : ---------- keywords: +patch pull_requests: +3969 stage: needs patch -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 03:29:47 2017 From: report at bugs.python.org (Aniket Vyas) Date: Sat, 14 Oct 2017 07:29:47 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. In-Reply-To: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> Message-ID: <1507966187.19.0.213398074469.issue31754@psf.upfronthosting.co.za> Aniket Vyas added the comment: Thanks Mariatta. I have initiated a PR for the issue. https://github.com/python/cpython/pull/3993 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 04:14:32 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Sat, 14 Oct 2017 08:14:32 +0000 Subject: [docs] [issue31714] Improve re documentation In-Reply-To: <1507299732.49.0.213398074469.issue31714@psf.upfronthosting.co.za> Message-ID: <1507968872.46.0.213398074469.issue31714@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: New changeset cd195e2a7ac5c9b2574d5462752b7939641de4a9 by Serhiy Storchaka in branch 'master': bpo-31714: Improved regular expression documentation. (#3907) https://github.com/python/cpython/commit/cd195e2a7ac5c9b2574d5462752b7939641de4a9 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 04:42:46 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Sat, 14 Oct 2017 08:42:46 +0000 Subject: [docs] [issue31714] Improve re documentation In-Reply-To: <1507299732.49.0.213398074469.issue31714@psf.upfronthosting.co.za> Message-ID: <1507970566.74.0.912454111764.issue31714@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- pull_requests: +3970 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 05:17:21 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Sat, 14 Oct 2017 09:17:21 +0000 Subject: [docs] [issue31714] Improve re documentation In-Reply-To: <1507299732.49.0.213398074469.issue31714@psf.upfronthosting.co.za> Message-ID: <1507972641.13.0.213398074469.issue31714@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: New changeset 69ed5b61e7d2bdaf2dc6684061f737adc24a96ae by Serhiy Storchaka in branch '3.6': [3.6] bpo-31714: Improved regular expression documentation. (GH-3907). (#3994) https://github.com/python/cpython/commit/69ed5b61e7d2bdaf2dc6684061f737adc24a96ae ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 05:26:57 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Sat, 14 Oct 2017 09:26:57 +0000 Subject: [docs] [issue31714] Improve re documentation In-Reply-To: <1507299732.49.0.213398074469.issue31714@psf.upfronthosting.co.za> Message-ID: <1507973217.83.0.912454111764.issue31714@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 10:36:11 2017 From: report at bugs.python.org (Raymond Hettinger) Date: Sat, 14 Oct 2017 14:36:11 +0000 Subject: [docs] [issue31757] Tutorial: Fibonacci numbers start with 1, 1 In-Reply-To: <1507732819.98.0.213398074469.issue31757@psf.upfronthosting.co.za> Message-ID: <1507991771.54.0.213398074469.issue31757@psf.upfronthosting.co.za> Raymond Hettinger added the comment: New changeset 8c26a34f93db7ae96b42bcce6b557437436c7721 by Raymond Hettinger in branch 'master': bpo-31757: Make Fibonacci examples consistent (#3991) https://github.com/python/cpython/commit/8c26a34f93db7ae96b42bcce6b557437436c7721 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 10:36:58 2017 From: report at bugs.python.org (Raymond Hettinger) Date: Sat, 14 Oct 2017 14:36:58 +0000 Subject: [docs] [issue31757] Tutorial: Fibonacci numbers start with 1, 1 In-Reply-To: <1507732819.98.0.213398074469.issue31757@psf.upfronthosting.co.za> Message-ID: <1507991818.12.0.912454111764.issue31757@psf.upfronthosting.co.za> Change by Raymond Hettinger : ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 15:43:08 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Sat, 14 Oct 2017 19:43:08 +0000 Subject: [docs] [issue31778] ast.literal_eval supports non-literals in Python 3 In-Reply-To: <1507847478.46.0.213398074469.issue31778@psf.upfronthosting.co.za> Message-ID: <1508010188.71.0.213398074469.issue31778@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: The support of parsing addition and subtraction at any level of nesting was added by bc95973b51abadc84960e7836ce313f12cf515cf. The commit message and NEWS entry don't contain an issue number, thus the rationale of this change is not known. Raymond, could you please explain? ---------- nosy: +rhettinger, serhiy.storchaka _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 14 19:55:59 2017 From: report at bugs.python.org (Semen Zhydenko) Date: Sat, 14 Oct 2017 23:55:59 +0000 Subject: [docs] [issue31788] Typo in comments Modules/_ssl.c Message-ID: <1508025359.26.0.213398074469.issue31788@psf.upfronthosting.co.za> New submission from Semen Zhydenko : completly must be changed to completely ---------- assignee: docs at python components: Documentation messages: 304405 nosy: Semen Zhydenko, docs at python priority: normal severity: normal status: open title: Typo in comments Modules/_ssl.c versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 03:31:39 2017 From: report at bugs.python.org (Berker Peksag) Date: Sun, 15 Oct 2017 07:31:39 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. In-Reply-To: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> Message-ID: <1508052698.92.0.213398074469.issue31754@psf.upfronthosting.co.za> Berker Peksag added the comment: New changeset 1b9e76ed3a055a53ca67397e928e1b408461900b by Berker Peksag (vyas45) in branch 'master': bpo-31754: Fix type of 'itemsize' in PyBuffer_FillContiguousStrides (GH-3993) https://github.com/python/cpython/commit/1b9e76ed3a055a53ca67397e928e1b408461900b ---------- nosy: +berker.peksag _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 03:31:45 2017 From: report at bugs.python.org (Roundup Robot) Date: Sun, 15 Oct 2017 07:31:45 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. In-Reply-To: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> Message-ID: <1508052705.94.0.912454111764.issue31754@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- pull_requests: +3978 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 03:34:44 2017 From: report at bugs.python.org (Berker Peksag) Date: Sun, 15 Oct 2017 07:34:44 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. In-Reply-To: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> Message-ID: <1508052884.75.0.912454111764.issue31754@psf.upfronthosting.co.za> Change by Berker Peksag : ---------- type: -> behavior _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 03:37:09 2017 From: report at bugs.python.org (Berker Peksag) Date: Sun, 15 Oct 2017 07:37:09 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. In-Reply-To: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> Message-ID: <1508053029.85.0.213398074469.issue31754@psf.upfronthosting.co.za> Berker Peksag added the comment: New changeset e881302b70ab36bafcf37e3917be118bbec97763 by Berker Peksag (Miss Islington (bot)) in branch '3.6': [3.6] bpo-31754: Fix type of 'itemsize' in PyBuffer_FillContiguousStrides (GH-3993) https://github.com/python/cpython/commit/e881302b70ab36bafcf37e3917be118bbec97763 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 03:47:26 2017 From: report at bugs.python.org (Berker Peksag) Date: Sun, 15 Oct 2017 07:47:26 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. In-Reply-To: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> Message-ID: <1508053646.32.0.912454111764.issue31754@psf.upfronthosting.co.za> Change by Berker Peksag : ---------- stage: patch review -> backport needed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 03:54:07 2017 From: report at bugs.python.org (Berker Peksag) Date: Sun, 15 Oct 2017 07:54:07 +0000 Subject: [docs] [issue31788] Typo in comments Modules/_ssl.c In-Reply-To: <1508025359.26.0.213398074469.issue31788@psf.upfronthosting.co.za> Message-ID: <1508054047.3.0.912454111764.issue31788@psf.upfronthosting.co.za> Change by Berker Peksag : ---------- keywords: +easy stage: -> needs patch type: -> behavior versions: -Python 3.4, Python 3.5, Python 3.8 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 03:55:50 2017 From: report at bugs.python.org (Berker Peksag) Date: Sun, 15 Oct 2017 07:55:50 +0000 Subject: [docs] [issue31788] Typo in comments Modules/_ssl.c In-Reply-To: <1508025359.26.0.213398074469.issue31788@psf.upfronthosting.co.za> Message-ID: <1508054150.82.0.912454111764.issue31788@psf.upfronthosting.co.za> Change by Berker Peksag : ---------- versions: -Python 2.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 04:18:48 2017 From: report at bugs.python.org (Roundup Robot) Date: Sun, 15 Oct 2017 08:18:48 +0000 Subject: [docs] [issue31788] Typo in comments Modules/_ssl.c In-Reply-To: <1508025359.26.0.213398074469.issue31788@psf.upfronthosting.co.za> Message-ID: <1508055528.12.0.912454111764.issue31788@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- keywords: +patch pull_requests: +3979 stage: needs patch -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 05:49:49 2017 From: report at bugs.python.org (Julien Palard) Date: Sun, 15 Oct 2017 09:49:49 +0000 Subject: [docs] [issue31793] Allow to specialize smart quotes in documentation translations Message-ID: <1508060988.99.0.213398074469.issue31793@psf.upfronthosting.co.za> New submission from Julien Palard : It would be great to allow each translation to specify their smart-quotes configuration, typically Japanese prefer no smart-quotes: - https://github.com/python/docsbuild-scripts/issues/32 It's easily done by adding a Doc/docutils.conf file, I'm opening a PR. ---------- assignee: docs at python components: Documentation messages: 304429 nosy: docs at python, mdk priority: normal severity: normal status: open title: Allow to specialize smart quotes in documentation translations versions: Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 05:55:25 2017 From: report at bugs.python.org (Roundup Robot) Date: Sun, 15 Oct 2017 09:55:25 +0000 Subject: [docs] [issue31793] Allow to specialize smart quotes in documentation translations In-Reply-To: <1508060988.99.0.213398074469.issue31793@psf.upfronthosting.co.za> Message-ID: <1508061325.05.0.912454111764.issue31793@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- keywords: +patch pull_requests: +3980 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 14:06:37 2017 From: report at bugs.python.org (Aniket Vyas) Date: Sun, 15 Oct 2017 18:06:37 +0000 Subject: [docs] [issue31788] Typo in comments Modules/_ssl.c In-Reply-To: <1508025359.26.0.213398074469.issue31788@psf.upfronthosting.co.za> Message-ID: <1508090797.8.0.213398074469.issue31788@psf.upfronthosting.co.za> Aniket Vyas added the comment: I can pick this up if it's okay. ---------- nosy: +vyas45 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 14:07:33 2017 From: report at bugs.python.org (Aniket Vyas) Date: Sun, 15 Oct 2017 18:07:33 +0000 Subject: [docs] [issue31788] Typo in comments Modules/_ssl.c In-Reply-To: <1508025359.26.0.213398074469.issue31788@psf.upfronthosting.co.za> Message-ID: <1508090853.51.0.213398074469.issue31788@psf.upfronthosting.co.za> Aniket Vyas added the comment: My bad, didn't notice the PR already existing. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 15:28:33 2017 From: report at bugs.python.org (Benjamin Peterson) Date: Sun, 15 Oct 2017 19:28:33 +0000 Subject: [docs] [issue31788] Typo in comments Modules/_ssl.c In-Reply-To: <1508025359.26.0.213398074469.issue31788@psf.upfronthosting.co.za> Message-ID: <1508095713.91.0.213398074469.issue31788@psf.upfronthosting.co.za> Benjamin Peterson added the comment: New changeset 1295e11d397c6138427296d5f9653a9e7dd69062 by Benjamin Peterson (Semen Zhydenko) in branch 'master': completly -> completely (#3999) (closes bpo-31788) https://github.com/python/cpython/commit/1295e11d397c6138427296d5f9653a9e7dd69062 ---------- nosy: +benjamin.peterson resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 15:29:49 2017 From: report at bugs.python.org (Roundup Robot) Date: Sun, 15 Oct 2017 19:29:49 +0000 Subject: [docs] [issue31788] Typo in comments Modules/_ssl.c In-Reply-To: <1508025359.26.0.213398074469.issue31788@psf.upfronthosting.co.za> Message-ID: <1508095789.77.0.912454111764.issue31788@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- pull_requests: +3982 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 15:48:54 2017 From: report at bugs.python.org (Benjamin Peterson) Date: Sun, 15 Oct 2017 19:48:54 +0000 Subject: [docs] [issue31788] Typo in comments Modules/_ssl.c In-Reply-To: <1508025359.26.0.213398074469.issue31788@psf.upfronthosting.co.za> Message-ID: <1508096934.59.0.213398074469.issue31788@psf.upfronthosting.co.za> Benjamin Peterson added the comment: New changeset cfc604722ff5ad64de96ddeb944661f1e94d8cd0 by Benjamin Peterson (Miss Islington (bot)) in branch '3.6': [3.6] completly -> completely (GH-3999) (closes bpo-31788) (#4008) https://github.com/python/cpython/commit/cfc604722ff5ad64de96ddeb944661f1e94d8cd0 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 18:45:56 2017 From: report at bugs.python.org (Nitish) Date: Sun, 15 Oct 2017 22:45:56 +0000 Subject: [docs] [issue31795] Slicings documentation doesn't mention Ellipsis Message-ID: <1508107556.27.0.213398074469.issue31795@psf.upfronthosting.co.za> New submission from Nitish : Ellipsis object documentation[1] specifies that Ellipsis is mainly used by Slicings. But Slicing's documentation[2] doesn't mention anything about Ellipsis. Consequently - it is not immediately clear from Ellipsis documentation what it's used for. [1] https://docs.python.org/3/library/stdtypes.html?highlight=ellipsis#the-ellipsis-object [2] https://docs.python.org/3/reference/expressions.html#slicings ---------- assignee: docs at python components: Documentation messages: 304449 nosy: docs at python, nitishch priority: normal severity: normal status: open title: Slicings documentation doesn't mention Ellipsis type: enhancement _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 15 23:24:25 2017 From: report at bugs.python.org (Raymond Hettinger) Date: Mon, 16 Oct 2017 03:24:25 +0000 Subject: [docs] [issue31795] Slicings documentation doesn't mention Ellipsis In-Reply-To: <1508107556.27.0.213398074469.issue31795@psf.upfronthosting.co.za> Message-ID: <1508124265.63.0.213398074469.issue31795@psf.upfronthosting.co.za> Raymond Hettinger added the comment: In regular Python, the ellipsis isn't used for slicing. It does have special meaning for numpy. So, I think the docs may be correct as is. ---------- nosy: +rhettinger _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 16 02:30:31 2017 From: report at bugs.python.org (Nitish) Date: Mon, 16 Oct 2017 06:30:31 +0000 Subject: [docs] [issue31795] Slicings documentation doesn't mention Ellipsis In-Reply-To: <1508107556.27.0.213398074469.issue31795@psf.upfronthosting.co.za> Message-ID: <1508135431.4.0.213398074469.issue31795@psf.upfronthosting.co.za> Nitish added the comment: The problem is that while documentation for other objects like Null object, NotImplemented object make it clear what they are used for, documentation for Ellipsis object only says that it's used in slicings and the slicings documentation doesn't cover Ellipsis. Can we add an example of its usage in Numpy to the docs? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 16 08:06:43 2017 From: report at bugs.python.org (Raymond Hettinger) Date: Mon, 16 Oct 2017 12:06:43 +0000 Subject: [docs] [issue31795] Slicings documentation doesn't mention Ellipsis In-Reply-To: <1508107556.27.0.213398074469.issue31795@psf.upfronthosting.co.za> Message-ID: <1508155603.85.0.213398074469.issue31795@psf.upfronthosting.co.za> Raymond Hettinger added the comment: > Can we add an example of its usage in Numpy to the docs? I don't think we should. In CPython, the ellipsis has no interesting semantics. It is something that third-party modules can use however they wish. It doesn't make sense for CPython docs to cover their usage. ---------- resolution: -> not a bug stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 16 13:21:03 2017 From: report at bugs.python.org (Aniket Vyas) Date: Mon, 16 Oct 2017 17:21:03 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. In-Reply-To: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> Message-ID: <1508174463.8.0.912454111764.issue31754@psf.upfronthosting.co.za> Change by Aniket Vyas : ---------- pull_requests: +3985 stage: backport needed -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 16 14:15:20 2017 From: report at bugs.python.org (Aniket Vyas) Date: Mon, 16 Oct 2017 18:15:20 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. In-Reply-To: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> Message-ID: <1508177720.79.0.912454111764.issue31754@psf.upfronthosting.co.za> Change by Aniket Vyas : ---------- pull_requests: +3986 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 16 14:23:46 2017 From: report at bugs.python.org (Berker Peksag) Date: Mon, 16 Oct 2017 18:23:46 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. In-Reply-To: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> Message-ID: <1508178226.56.0.213398074469.issue31754@psf.upfronthosting.co.za> Berker Peksag added the comment: New changeset 50cef52372381a9e2f3d760497d8db76254cffef by Berker Peksag (vyas45) in branch '2.7': [2.7] bpo-31754: Fix type of 'itemsize' in PyBuffer_FillContiguousStrides (GH-3993) https://github.com/python/cpython/commit/50cef52372381a9e2f3d760497d8db76254cffef ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 16 14:26:06 2017 From: report at bugs.python.org (Berker Peksag) Date: Mon, 16 Oct 2017 18:26:06 +0000 Subject: [docs] [issue31754] Documented type of parameter 'itemsize' to PyBuffer_FillContiguousStrides is incorrect. In-Reply-To: <1507681127.43.0.213398074469.issue31754@psf.upfronthosting.co.za> Message-ID: <1508178366.13.0.213398074469.issue31754@psf.upfronthosting.co.za> Berker Peksag added the comment: Thank you for the report, Robert and thank you for the patches, Aniket. ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 17 07:58:28 2017 From: report at bugs.python.org (Julien Palard) Date: Tue, 17 Oct 2017 11:58:28 +0000 Subject: [docs] [issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters? In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1508241508.04.0.213398074469.issue31589@psf.upfronthosting.co.za> Julien Palard added the comment: Finally have a combination of latex engines that work for every cases, did a PR on docsbuild-scripts: https://github.com/python/docsbuild-scripts/pull/34/ I already pulled xelatex on docs.iad1.psf.io via https://github.com/python/psf-salt/commit/989a7715c4a452b5af13baf9a33535bab0af822b#diff-6fb01fe8bbc22a54d234a57ad58e291e Also opened a few related issue sphinx-doc side to track my thoughts: - https://github.com/sphinx-doc/sphinx/issues/4150 (Ask if there is a better way to set the latex engine than giving it from docsbuild-scripts) - https://github.com/sphinx-doc/sphinx/issues/4159 (Choose unicode-enabled default latex engines) - https://github.com/sphinx-doc/sphinx/issues/4149 (Be more explicit on documentation about how to choose a latex engine) ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 17 15:03:04 2017 From: report at bugs.python.org (Nathaniel Manista) Date: Tue, 17 Oct 2017 19:03:04 +0000 Subject: [docs] [issue31739] socket.close recommended but not demonstrated in same-page example code In-Reply-To: <1507577278.77.0.213398074469.issue31739@psf.upfronthosting.co.za> Message-ID: <1508266984.73.0.213398074469.issue31739@psf.upfronthosting.co.za> Nathaniel Manista added the comment: As I am learning from the examples, I don't have the confidence to propose a fix to them. :-P For the IPv4-and-IPv6 "Echo server program": should s be closed at some point after "conn, addr = s.accept()"? Should s be closed on the line immediately after "conn, addr = s.accept()", should it be closed on the last line (after the "with conn:" context is exited), or is either acceptable? Should the "very simple network sniffer with raw sockets on Windows" have a with statement or "s.close()"? Should the "communicate to a CAN network using the raw socket protocol" example have a with statement or "s.close()"? Of course it's possible that I'm misunderstanding one or more things. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 17 22:05:13 2017 From: report at bugs.python.org (R. David Murray) Date: Wed, 18 Oct 2017 02:05:13 +0000 Subject: [docs] [issue31739] socket.close recommended but not demonstrated in same-page example code In-Reply-To: <1508266984.73.0.213398074469.issue31739@psf.upfronthosting.co.za> Message-ID: <20171018020508.BD18B1B10002@webabinitio.net> R. David Murray added the comment: I think in the echo examples the 'with conn' block should be indented and a 'with s:' added around it. The network sniffer should probably use a with statement with the created socket. The CAN example ends only on ctrl-C, and could go into a fast spin loop on error, so it probably needs a more extensive rewrite. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 17 22:12:55 2017 From: report at bugs.python.org (R. David Murray) Date: Wed, 18 Oct 2017 02:12:55 +0000 Subject: [docs] [issue31739] socket.close recommended but not demonstrated in same-page example code In-Reply-To: <1507577278.77.0.213398074469.issue31739@psf.upfronthosting.co.za> Message-ID: <1508292775.18.0.213398074469.issue31739@psf.upfronthosting.co.za> R. David Murray added the comment: Heh, of course the socket server also only ends with ctl-C. And I misread the CAN example, it won't spin because the read isn't wrapped in a try/except. So yes, that should use a with on the socket as well, since the with will close the socket on a ctl-C, unlike a close statement after the loop which will never be reached. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 18 07:54:54 2017 From: report at bugs.python.org (R. David Murray) Date: Wed, 18 Oct 2017 11:54:54 +0000 Subject: [docs] [issue31778] ast.literal_eval supports non-literals in Python 3 In-Reply-To: <1507847478.46.0.213398074469.issue31778@psf.upfronthosting.co.za> Message-ID: <1508327694.66.0.213398074469.issue31778@psf.upfronthosting.co.za> R. David Murray added the comment: "Safely evaluate an expression node or a string containing a Python expression." The behavior you are citing matches that documentation, as far as I can see. 1+1 is an expression involving supported literals. ---------- nosy: +r.david.murray _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 18 08:01:29 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Wed, 18 Oct 2017 12:01:29 +0000 Subject: [docs] [issue31778] ast.literal_eval supports non-literals in Python 3 In-Reply-To: <1507847478.46.0.213398074469.issue31778@psf.upfronthosting.co.za> Message-ID: <1508328089.66.0.213398074469.issue31778@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: """ The string or node provided may only consist of the following Python literal structures: strings, bytes, numbers, tuples, lists, dicts, sets, booleans, and None. """ 1+1 is not a literal number. """ It is not capable of evaluating arbitrarily complex expressions, for example involving operators or indexing. """ ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 18 10:34:06 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Wed, 18 Oct 2017 14:34:06 +0000 Subject: [docs] [issue31778] ast.literal_eval supports non-literals in Python 3 In-Reply-To: <1507847478.46.0.213398074469.issue31778@psf.upfronthosting.co.za> Message-ID: <1508337246.86.0.912454111764.issue31778@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- keywords: +patch pull_requests: +4009 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 18 10:35:31 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Wed, 18 Oct 2017 14:35:31 +0000 Subject: [docs] [issue31778] ast.literal_eval supports non-literals in Python 3 In-Reply-To: <1507847478.46.0.213398074469.issue31778@psf.upfronthosting.co.za> Message-ID: <1508337331.27.0.213398074469.issue31778@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: PR 4035 makes ast.literal_eval() more strict. ---------- versions: -Python 3.6, Python 3.8 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 18 11:32:03 2017 From: report at bugs.python.org (Colin Dunklau) Date: Wed, 18 Oct 2017 15:32:03 +0000 Subject: [docs] [issue31811] async and await missing from keyword list in lexical analysis doc Message-ID: <1508340723.02.0.213398074469.issue31811@psf.upfronthosting.co.za> New submission from Colin Dunklau : I see that code making async/await real keywords has been merged, but it looks like Doc/reference/lexical_analysis.rst doesn't have those added https://github.com/python/cpython/blob/4a2d00c/Doc/reference/lexical_analysis.rst#keywords Is that list autogenerated somehow or was it just overlooked? ---------- assignee: docs at python components: Documentation messages: 304583 nosy: Colin Dunklau, docs at python priority: normal severity: normal status: open title: async and await missing from keyword list in lexical analysis doc type: enhancement versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 18 11:42:17 2017 From: report at bugs.python.org (STINNER Victor) Date: Wed, 18 Oct 2017 15:42:17 +0000 Subject: [docs] [issue31812] Document PEP 545 (documentation translation) in What's New in Python 3.7 Message-ID: <1508341337.17.0.213398074469.issue31812@psf.upfronthosting.co.za> New submission from STINNER Victor : The PEP 545 should be documented in What's New in Python 3.7: mention that the Python documentation is now *officially* translated to french and japanese. ---------- assignee: docs at python components: Documentation messages: 304584 nosy: docs at python, haypo, inada.naoki, mdk priority: normal severity: normal status: open title: Document PEP 545 (documentation translation) in What's New in Python 3.7 versions: Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 18 13:18:46 2017 From: report at bugs.python.org (Yury Selivanov) Date: Wed, 18 Oct 2017 17:18:46 +0000 Subject: [docs] [issue31778] ast.literal_eval supports non-literals in Python 3 In-Reply-To: <1507847478.46.0.213398074469.issue31778@psf.upfronthosting.co.za> Message-ID: <1508347126.32.0.912454111764.issue31778@psf.upfronthosting.co.za> Change by Yury Selivanov : ---------- nosy: -yselivanov _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 18 17:29:05 2017 From: report at bugs.python.org (Mario Corchero) Date: Wed, 18 Oct 2017 21:29:05 +0000 Subject: [docs] [issue31454] Include "import as" in tutorial In-Reply-To: <1505317940.24.0.986048971751.issue31454@psf.upfronthosting.co.za> Message-ID: <1508362145.55.0.912454111764.issue31454@psf.upfronthosting.co.za> Change by Mario Corchero : ---------- nosy: +mariocj89 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 18 17:38:12 2017 From: report at bugs.python.org (Mario Corchero) Date: Wed, 18 Oct 2017 21:38:12 +0000 Subject: [docs] [issue31454] Include "import as" in tutorial In-Reply-To: <1505317940.24.0.986048971751.issue31454@psf.upfronthosting.co.za> Message-ID: <1508362692.62.0.912454111764.issue31454@psf.upfronthosting.co.za> Change by Mario Corchero : ---------- keywords: +patch pull_requests: +4012 stage: needs patch -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 19 05:27:26 2017 From: report at bugs.python.org (raylu) Date: Thu, 19 Oct 2017 09:27:26 +0000 Subject: [docs] [issue17799] settrace docs are wrong about "c_call" events In-Reply-To: <1366428980.14.0.538502026896.issue17799@psf.upfronthosting.co.za> Message-ID: <1508405246.16.0.912454111764.issue17799@psf.upfronthosting.co.za> Change by raylu : ---------- nosy: +raylu _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 19 08:58:41 2017 From: report at bugs.python.org (F. Lamar) Date: Thu, 19 Oct 2017 12:58:41 +0000 Subject: [docs] [issue31811] async and await missing from keyword list in lexical analysis doc In-Reply-To: <1508340723.02.0.213398074469.issue31811@psf.upfronthosting.co.za> Message-ID: <1508417921.63.0.213398074469.issue31811@psf.upfronthosting.co.za> F. Lamar added the comment: I a new contributor. This seems like a simple fix. I'd be happy to work on it. I will submit ar PR on or before 10-22-17 ---------- nosy: +F. Lamar _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 19 14:54:33 2017 From: report at bugs.python.org (Allen Li) Date: Thu, 19 Oct 2017 18:54:33 +0000 Subject: [docs] [issue31822] Document that urllib.parse.{Defrag, Split, Parse}Result are namedtuples Message-ID: <1508439273.05.0.213398074469.issue31822@psf.upfronthosting.co.za> New submission from Allen Li : It would be useful to document that urllib.parse.{Defrag,Split,Parse}Result are namedtuples, and make that API officially public if it was not otherwise. These classes are implemented as namedtuples in Python 2 and 3, and I am not aware of a reason that that would need to change in the future. In particular, the namedtuple _replace() method is very useful for modifying parts of a URL, a common use case. u = urllib.parse.urlsplit(some_url) u = u._replace(netloc=other_netloc) urllib.parse.urlunsplit(u) # Alternatives not depending on namedtuple API parts = list(u) parts[1] = other_netloc # Using a magic index urllib.parse.urlunsplit(u) u = urllib.parse.SplitResult( # Very ugly scheme=u.scheme, netloc=other_netloc, path=u.path, query=u.query, fragment=u.fragment) ---------- assignee: docs at python components: Documentation messages: 304637 nosy: Allen Li, docs at python priority: normal severity: normal status: open title: Document that urllib.parse.{Defrag,Split,Parse}Result are namedtuples type: enhancement versions: Python 2.7, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 19 15:24:20 2017 From: report at bugs.python.org (Mike Frysinger) Date: Thu, 19 Oct 2017 19:24:20 +0000 Subject: [docs] [issue31822] Document that urllib.parse.{Defrag, Split, Parse}Result are namedtuples In-Reply-To: <1508439273.05.0.213398074469.issue31822@psf.upfronthosting.co.za> Message-ID: <1508441060.2.0.213398074469.issue31822@psf.upfronthosting.co.za> Mike Frysinger added the comment: specifically, the docs for these classes: https://docs.python.org/2/library/urlparse.html#results-of-urlparse-and-urlsplit https://docs.python.org/3/library/urllib.parse.html#urlparse-result-object > The result objects from the urlparse() and urlsplit() functions are subclasses > of the tuple type. These subclasses add the attributes described in those > functions, as well as provide an additional method: > ... > class urlparse.SplitResult(scheme, netloc, path, query, fragment) > Concrete class for urlsplit() results. changing "subclasses of the tuple type" to "subclasses of collections.namedtuples" would be great. also adding hints to use _replace to update values would be great :). ---------- nosy: +vapier _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 19 19:17:42 2017 From: report at bugs.python.org (Peter Lovett) Date: Thu, 19 Oct 2017 23:17:42 +0000 Subject: [docs] [issue31824] Missing default argument detail in documentation of StreamReaderWriter Message-ID: <1508455062.42.0.213398074469.issue31824@psf.upfronthosting.co.za> New submission from Peter Lovett : Documentation of StreamReaderWriter at https://docs.python.org/3/library/codecs.html#codecs.StreamReaderWriter section 7.2.1.4.3 is missing the default value on the errors argument. Should change from: class codecs.StreamReaderWriter(stream, Reader, Writer, errors) to be: class codecs.StreamReaderWriter(stream, Reader, Writer, errors='strict') ---------- assignee: docs at python components: Documentation messages: 304646 nosy: PeterLovett, docs at python priority: normal severity: normal status: open title: Missing default argument detail in documentation of StreamReaderWriter type: behavior versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 19 20:27:58 2017 From: report at bugs.python.org (Janko Krstic) Date: Fri, 20 Oct 2017 00:27:58 +0000 Subject: [docs] [issue31163] Return destination path in Path.rename and Path.replace In-Reply-To: <1502292744.48.0.627996317333.issue31163@psf.upfronthosting.co.za> Message-ID: <1508459278.48.0.912454111764.issue31163@psf.upfronthosting.co.za> Change by Janko Krstic : ---------- keywords: +patch pull_requests: +4024 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 19 22:22:14 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Fri, 20 Oct 2017 02:22:14 +0000 Subject: [docs] [issue31761] Failures and crashes when running tests by import. In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1508466134.51.0.213398074469.issue31761@psf.upfronthosting.co.za> Terry J. Reedy added the comment: I am re-opening because there is a bug, a conflict between doc and code comment and actual behavior, and one which has nothing to do with IDLE. The question is whether to fix it or to delete the invitation to invoke the bug. The reason the devguide gives an alternative for running tests is so that someone with only installed Python and no command line could still test their installation and even contribute a patch on the tracker. On 2000-08-23, Tim Peters add the following comment to test.autotest: # This should be equivalent to running regrtest.py from the cmdline. # It can be especially handy if you're in an interactive shell, e.g., # from test import autotest. The autotest code was later copied into test.__main__, and both are now: from test.libregrtest import main main() So 'from test import __main__' is the same as importing autotest, and should be the same as importing and running libregrtest To test the equivalence in the setting where either import might be useful, I opened both python and IDLE from the 3.7.0a2 Windows start icons and imported autotest. The test deterministicly crashes after test_marshal. I call the stoppage a crash because wrapping the import in try: ... except BaseException has no effect. The Python console just vanishes. IDLE restarts. ... 0:05:51 [207/407/5] test_marshal =============================== RESTART: Shell ========================= >>> So the claimed equivalence in worse than just not true. There were, I believe, 3 failures in the Python console. The extra 2 in IDLE are due to the #25588 fix guarding against sys.stderr being None is needed in a couple of other places. In any case, either running tests by importing should be made to work (again, presuming it once did) or deprecated and autotest removed. ---------- resolution: not a bug -> stage: resolved -> status: closed -> open title: regrtest: faulthandler.enable() fails with io.UnsupportedOperation: fileno when run from IDLE -> Failures and crashes when running tests by import. versions: -Python 3.8 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 20 05:04:12 2017 From: report at bugs.python.org (Pablo Galindo Salgado) Date: Fri, 20 Oct 2017 09:04:12 +0000 Subject: [docs] [issue17799] settrace docs are wrong about "c_call" events In-Reply-To: <1366428980.14.0.538502026896.issue17799@psf.upfronthosting.co.za> Message-ID: <1508490252.26.0.912454111764.issue17799@psf.upfronthosting.co.za> Change by Pablo Galindo Salgado : ---------- keywords: +patch pull_requests: +4025 stage: -> patch review _______________________________________ Python tracker _______________________________________ From andregirol at gmail.com Mon Oct 16 12:19:10 2017 From: andregirol at gmail.com (=?UTF-8?B?QW5kcsOpIEdpcm9s?=) Date: Mon, 16 Oct 2017 14:19:10 -0200 Subject: [docs] Portuguese Brazilian Transtlation Message-ID: Hello folks! My name is Andr? (aka Girol). I'm new in Python Community and fell in love with the language and the people. I noticed that the main documentation is not yet translated to Portuguese (or not fully translated for a major release). I would be honored to help with the documentation. If I can join the translators' team, I would like to know how to start. I also found a github repo with the brazilian translation, but it is empty. I helped in the translation of other open source projects such as Pro Git book (small contribution) and with phpmyadmin core translation and revision of fuzzy sentences. Thank you all for your attention and for your amazing work. Best Regards, -- Andr? Luiz Girol -------------- next part -------------- An HTML attachment was scrubbed... URL: From barclata at gmail.com Fri Oct 20 02:20:27 2017 From: barclata at gmail.com (Tj Barclay) Date: Fri, 20 Oct 2017 01:20:27 -0500 Subject: [docs] Clarity for curses.wrapper Message-ID: MAJOR DISCLAIMER: I'm 7.4ish beers deep In the documentation for the curses library of Python 3.6 it mentions that curses.wrapper(*function*) will do some common curses initializations before running *function*. Then it will run *function* waiting for a thrown exception or the end before doing some cleanup. It does not however explicitly state that the return value of curses.initscr() is passed into that function. It is only implicitly shown through the code example. For the sake of future drunk programmers, please make that more clear. I super understand this is stupid and minor and I could be mistaken (SEE DISCLAIMER) Best, TJ -- TJ Barclay Electrcial Engineering &Computer Science, University of Kansas tjbarclay at ku.edu +1 316 259 2250 -------------- next part -------------- An HTML attachment was scrubbed... URL: From barclata at gmail.com Fri Oct 20 02:40:30 2017 From: barclata at gmail.com (Tj Barclay) Date: Fri, 20 Oct 2017 01:40:30 -0500 Subject: [docs] Fwd: Clarity for curses.wrapper In-Reply-To: References: Message-ID: ---------- Forwarded message ---------- From: Tj Barclay Date: Fri, Oct 20, 2017 at 1:20 AM Subject: Clarity for curses.wrapper To: docs at python.org MAJOR DISCLAIMER: I'm 7.4ish beers deep In the documentation for the curses library of Python 3.6 it mentions that curses.wrapper(*function*) will do some common curses initializations before running *function*. Then it will run *function* waiting for a thrown exception or the end before doing some cleanup. It does not however explicitly state that the return value of curses.initscr() is passed into that function. It is only implicitly shown through the code example. For the sake of future drunk programmers, please make that more clear. I super understand this is stupid and minor and I could be mistaken (SEE DISCLAIMER) Best, TJ -- TJ Barclay Electrcial Engineering &Computer Science, University of Kansas tjbarclay at ku.edu +1 316 259 2250 <(316)%20259-2250> Yes, I am a moron. My complaint is blown up by the 'real' curses documentation. I was looking at the curses HOWTO which is why I was confused. I apologize for the mistake. Best, TJ -- TJ Barclay Electrcial Engineering &Computer Science, University of Kansas tjbarclay at ku.edu +1 316 259 2250 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Darren.Watson at nexusrental.co.uk Mon Oct 16 11:01:25 2017 From: Darren.Watson at nexusrental.co.uk (Darren Watson) Date: Mon, 16 Oct 2017 15:01:25 +0000 Subject: [docs] Python Documentation PDFs Message-ID: <5B64B29FF1938F449E142A43F83FF0F3C22E68D3@NEXUS-MAIL.NEXUSRENTAL.local> Hi The text on the PDF downloads is very faint: [cid:image001.png at 01D34698.04CE2B30] All other PDFs work fine in my Adobe Reader. Could this be looked into? Many Thanks, Darren Watson IT DevOps Engineer Nexus Vehicle Rental Nexus House 2 Owlcotes Court 141 Richardshaw Lane Leeds, LS28 6AA www.nexusrental.co.uk [top11] [cid:image002.jpg at 01D2971F.1224D5F0] Quality & Security - We have certifications in the ISO 9001:2008 Quality Management and ISO 27001:2013 Information Security Management standards. Customer Service - Winner of the 'Best Customer Focus' award at the Best Business Awards 2017. Innovation - Winner of the 'Best Innovation' award at the Best Business Awards 2017. Professional Development - Named in the 'Centrica Top 100 Apprenticeship Employer List' 2016. This Message and any attachments are for the named recipient's use only. They may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any wrong transmission. If you are not the intended recipient or have received this message in error, please delete it and all copies of it from your system, destroy any hard copies of it and notify the sender immediately. You must not directly or indirectly, use, disclose, distribute, print or copy any part of this message or any attachments if you are not the intended recipient. Any views expressed in this message or any attachments are those of the individual sender, except where otherwise stated and the sender is authorised to state them to be the views of any such entity. Nexus Vehicle Rental is a trading name of Nexus Vehicle Management Ltd, a company registered in England and Wales. Registration. No. 03833617. Registered office: Nexus House, 2 Owlcotes Court, 141 Richardshaw Lane, Leeds, LS28 6AA. UK VAT No. 228 5101 30. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 57391 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 4847 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 5396 bytes Desc: image003.jpg URL: From erik at q32.com Wed Oct 18 11:44:06 2017 From: erik at q32.com (Erik Aronesty) Date: Wed, 18 Oct 2017 11:44:06 -0400 Subject: [docs] asyncio on windows: WinError 995 spew in logs during load tests Message-ID: This error intermittently occurs when I close a server and wait for it to be closed. I seem to get all of the messages I expect in my tests, and my server seems to work fine on windows or linux otherwise, so it's not urgent for me. It seems (to me) that there is no way to catch an exception during accept(). The coroutine is coming directly from windows a overlapped i/o call: (ov = _overlapped.Overlapped(NULL)) Again, this exception only occurs intermittently and usually during my "1K connections tests" and similar load tests. DEBUG:root:waiting.... DEBUG:asyncio:taking long time to close proactor ERROR:asyncio:Task exception was never retrieved future: .accept_coro() done, defined at C:\Python36\lib\asyncio\windows_events.py:485> exception=OSError(22, 'The I/O operation has been aborted because of either a thread exit or an application request', None, 995, None)> Traceback (most recent call last): File "C:\Python36\lib\asyncio\windows_events.py", line 489, in accept_coro yield from future File "C:\Python36\lib\asyncio\proactor_events.py", line 504, in loop conn, addr = f.result() File "C:\Python36\lib\asyncio\windows_events.py", line 702, in _poll value = callback(transferred, key, ov) File "C:\Python36\lib\asyncio\windows_events.py", line 477, in finish_accept ov.getresult() OSError: [WinError 995] The I/O operation has been aborted because of either a thread exit or an application request DEBUG:root:finished.... DEBUG:root:loop dropped out -------------- next part -------------- An HTML attachment was scrubbed... URL: From report at bugs.python.org Fri Oct 20 08:35:25 2017 From: report at bugs.python.org (STINNER Victor) Date: Fri, 20 Oct 2017 12:35:25 +0000 Subject: [docs] [issue31761] Failures and crashes when running tests by import in IDLE In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1508502925.97.0.912454111764.issue31761@psf.upfronthosting.co.za> Change by STINNER Victor : ---------- title: Failures and crashes when running tests by import. -> Failures and crashes when running tests by import in IDLE _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 20 13:34:29 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Fri, 20 Oct 2017 17:34:29 +0000 Subject: [docs] [issue31793] Allow to specialize smart quotes in documentation translations In-Reply-To: <1508060988.99.0.213398074469.issue31793@psf.upfronthosting.co.za> Message-ID: <1508520869.52.0.213398074469.issue31793@psf.upfronthosting.co.za> Terry J. Reedy added the comment: Patch is trivial two lines but needs review and merge from someone familiar with Sphinx stuff. [?ric, https://docs.python.org/devguide/experts.html contains the invalid Eric.Araujo] ---------- nosy: +ezio.melotti, merwok, terry.reedy, willingc _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 20 14:53:35 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Fri, 20 Oct 2017 18:53:35 +0000 Subject: [docs] [issue31811] async and await missing from keyword list in lexical analysis doc In-Reply-To: <1508340723.02.0.213398074469.issue31811@psf.upfronthosting.co.za> Message-ID: <1508525615.7.0.912454111764.issue31811@psf.upfronthosting.co.za> Change by Terry J. Reedy : ---------- nosy: +yselivanov _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 20 15:15:44 2017 From: report at bugs.python.org (Yury Selivanov) Date: Fri, 20 Oct 2017 19:15:44 +0000 Subject: [docs] [issue31811] async and await missing from keyword list in lexical analysis doc In-Reply-To: <1508340723.02.0.213398074469.issue31811@psf.upfronthosting.co.za> Message-ID: <1508526944.52.0.213398074469.issue31811@psf.upfronthosting.co.za> Yury Selivanov added the comment: They are covered here: https://github.com/python/cpython/blob/4a2d00cb4525fcb3209f04531472ba6a359ed418/Doc/reference/compound_stmts.rst#coroutines ---------- resolution: -> not a bug stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 20 15:39:56 2017 From: report at bugs.python.org (Terry J. Reedy) Date: Fri, 20 Oct 2017 19:39:56 +0000 Subject: [docs] [issue31761] Failures and crashes when running tests by import In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1508528396.91.0.213398074469.issue31761@psf.upfronthosting.co.za> Terry J. Reedy added the comment: Victor, why do you persist in the nearly irrelevant focus on IDLE? As I reported above, failures and crashes happen ***without*** involving IDLE. Serhiy appears to report the same in #31794. ---------- title: Failures and crashes when running tests by import in IDLE -> Failures and crashes when running tests by import _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 20 16:09:07 2017 From: report at bugs.python.org (Pablo Galindo Salgado) Date: Fri, 20 Oct 2017 20:09:07 +0000 Subject: [docs] [issue9842] Document ... used in recursive repr of containers In-Reply-To: <1284336324.93.0.400210409006.issue9842@psf.upfronthosting.co.za> Message-ID: <1508530147.59.0.912454111764.issue9842@psf.upfronthosting.co.za> Change by Pablo Galindo Salgado : ---------- keywords: +patch pull_requests: +4033 stage: needs patch -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 20 16:17:13 2017 From: report at bugs.python.org (Roundup Robot) Date: Fri, 20 Oct 2017 20:17:13 +0000 Subject: [docs] [issue31812] Document PEP 545 (documentation translation) in What's New in Python 3.7 In-Reply-To: <1508341337.17.0.213398074469.issue31812@psf.upfronthosting.co.za> Message-ID: <1508530633.49.0.912454111764.issue31812@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- keywords: +patch pull_requests: +4034 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 20 16:40:43 2017 From: report at bugs.python.org (STINNER Victor) Date: Fri, 20 Oct 2017 20:40:43 +0000 Subject: [docs] [issue31761] Failures and crashes when running tests by import In-Reply-To: <1508528396.91.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: STINNER Victor added the comment: Sorry, I didn't read you comment. I just saw IDLE, I missed that you wrote that the bug is unrelated to IDLE. Ooops ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 20 16:46:32 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Fri, 20 Oct 2017 20:46:32 +0000 Subject: [docs] [issue31761] Failures and crashes when running tests by import In-Reply-To: <1507740904.59.0.213398074469.issue31761@psf.upfronthosting.co.za> Message-ID: <1508532392.5.0.213398074469.issue31761@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: Perhaps there are issues specific to IDLE, but we should first fix issues not related to IDLE in #31794. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 20 18:37:05 2017 From: report at bugs.python.org (Colin Dunklau) Date: Fri, 20 Oct 2017 22:37:05 +0000 Subject: [docs] [issue31811] async and await missing from keyword list in lexical analysis doc In-Reply-To: <1508340723.02.0.213398074469.issue31811@psf.upfronthosting.co.za> Message-ID: <1508539025.71.0.213398074469.issue31811@psf.upfronthosting.co.za> Colin Dunklau added the comment: Hi Yury, perhaps I've misinterpreted PEP 492, and I can't claim to understand how the parser works and thus how the changes in https://github.com/python/cpython/pull/1669 affect things, but it seems to me that async and await are truly reserved words now, not just only reserved in certain contexts. If that's true, shouldn't they also appear in the list in the lexical analysis doc? I'd appreciate any clarification you (or anyone else) can offer. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 20 18:52:34 2017 From: report at bugs.python.org (Yury Selivanov) Date: Fri, 20 Oct 2017 22:52:34 +0000 Subject: [docs] [issue31811] async and await missing from keyword list in lexical analysis doc In-Reply-To: <1508340723.02.0.213398074469.issue31811@psf.upfronthosting.co.za> Message-ID: <1508539954.6.0.213398074469.issue31811@psf.upfronthosting.co.za> Yury Selivanov added the comment: Ah, you mean this list: https://docs.python.org/3/reference/lexical_analysis.html#keywords ? Your original link was a bit hard to read as it shows rest markup and not the actual list of keywords. So I missed it, sorry. I'll reopen the issue, please feel free to submit a PR! ---------- resolution: not a bug -> stage: resolved -> needs patch status: closed -> open _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 21 14:07:39 2017 From: report at bugs.python.org (jfbu) Date: Sat, 21 Oct 2017 18:07:39 +0000 Subject: [docs] [issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters? In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1508609259.19.0.912454111764.issue31589@psf.upfronthosting.co.za> Change by jfbu : ---------- pull_requests: +4040 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 21 14:44:41 2017 From: report at bugs.python.org (jfbu) Date: Sat, 21 Oct 2017 18:44:41 +0000 Subject: [docs] [issue31589] Links for French documentation PDF is broken: LaTeX issue with non-ASCII characters? In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za> Message-ID: <1508611480.95.0.213398074469.issue31589@psf.upfronthosting.co.za> jfbu added the comment: I have made a PR at https://github.com/python/cpython/pull/4069 which enhances `conf.py` with some pdflatex extra Unicode configuration. I tested it with building PDF English documentation at master (at https://github.com/python/cpython/tree/db60a5bfa5d5f7a6f1538cc1fe76f0fda57b524e) and at 3.6 branch (at https://github.com/python/cpython/tree/1e78ed6825701029aa45a68f9e62dd3bb8d4e928) and also French documentation at 3.6 (at https://github.com/python/python-docs-fr/commit/76b522b79c3caa26658920c714acf8fac0c20eeb). The changes are only for ``pdflatex`` builds: if `latex_engine` is set to `xelatex`, `lualatex`, or `platex` (automatic if language is `ja`), nothing is modified. ---------- nosy: +jfbu _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 22 03:40:26 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Sun, 22 Oct 2017 07:40:26 +0000 Subject: [docs] [issue16700] Document that bytes OS API can returns unusable results on Windows In-Reply-To: <1355677117.39.0.191453655217.issue16700@psf.upfronthosting.co.za> Message-ID: <1508658026.78.0.912454111764.issue16700@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- versions: -Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 22 03:52:54 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Sun, 22 Oct 2017 07:52:54 +0000 Subject: [docs] [issue16700] Document that bytes OS API can returns unusable results on Windows In-Reply-To: <1355677117.39.0.191453655217.issue16700@psf.upfronthosting.co.za> Message-ID: <1508658774.67.0.213398074469.issue16700@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: This is now 2.7 only issue. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 22 04:11:31 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Sun, 22 Oct 2017 08:11:31 +0000 Subject: [docs] [issue28197] range.index mismatch with documentation In-Reply-To: <1474231832.91.0.157673750963.issue28197@psf.upfronthosting.co.za> Message-ID: <1508659891.01.0.912454111764.issue28197@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- stage: -> needs patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 22 17:18:51 2017 From: report at bugs.python.org (Raymond Hettinger) Date: Sun, 22 Oct 2017 21:18:51 +0000 Subject: [docs] [issue9842] Document ... used in recursive repr of containers In-Reply-To: <1284336324.93.0.400210409006.issue9842@psf.upfronthosting.co.za> Message-ID: <1508707130.95.0.213398074469.issue9842@psf.upfronthosting.co.za> Raymond Hettinger added the comment: Since the appearance of reprs is not guaranteed. I don't think this should be documented (because doing so makes it a guaranteed behavior). In fact, the appearance has changed over time from ... to [...] in and may change at some point to <...> so that it can't be confused with an actual Ellipsis object. At best this should be a FAQ entry or we can defer to behaviors that are documented and guaranteed (such as reprlib.recursive_repr() and its default fillvalue). I concur with David Murray that the Ellipsis object should be indexed and cross-referenced. ---------- nosy: +rhettinger _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 22 17:28:01 2017 From: report at bugs.python.org (Raymond Hettinger) Date: Sun, 22 Oct 2017 21:28:01 +0000 Subject: [docs] [issue31739] socket.close recommended but not demonstrated in same-page example code In-Reply-To: <1507577278.77.0.213398074469.issue31739@psf.upfronthosting.co.za> Message-ID: <1508707681.39.0.213398074469.issue31739@psf.upfronthosting.co.za> Raymond Hettinger added the comment: Lisa, would you care to wrap this one up? ---------- assignee: docs at python -> lisroach nosy: +lisroach, rhettinger _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 22 17:28:55 2017 From: report at bugs.python.org (Raymond Hettinger) Date: Sun, 22 Oct 2017 21:28:55 +0000 Subject: [docs] [issue31822] Document that urllib.parse.{Defrag, Split, Parse}Result are namedtuples In-Reply-To: <1508439273.05.0.213398074469.issue31822@psf.upfronthosting.co.za> Message-ID: <1508707735.25.0.912454111764.issue31822@psf.upfronthosting.co.za> Change by Raymond Hettinger : ---------- assignee: docs at python -> lisroach nosy: +lisroach _______________________________________ Python tracker _______________________________________ From smeng9 at illinois.edu Sun Oct 22 02:37:44 2017 From: smeng9 at illinois.edu (Shaoyu Meng) Date: Sun, 22 Oct 2017 01:37:44 -0500 Subject: [docs] Improvement of explanation of Mersenne Twister in 9.6 random section Message-ID: Hi, In section 9.6 the reason of not to use Mersenne Twister for the cryptographic purpose is overly generalized. "The Mersenne Twister is one of the most extensively tested random number generators in existence. However, being completely deterministic, it is not suitable for all purposes, and is completely unsuitable for cryptographic purposes" We should not use Mersenne Twister for the cryptographic purpose not because it is completely deterministic (PRGs are deterministic once given a seed) but because it cannot pass the "next bit test". "Next bit test" means that the next bits cannot be determined *even after seeing all the previous bits*, and even if the function is indeed deterministic. The problem with Mersenne Twister is that after seeing enough samples, it may be possible to learn some information about the seed and guess some of the next bits. What we need to analyze are two concepts: the generator function itself, and the process for choosing the seed. All random number generators, including Mersenne Twister, but also including the provably-secure constructions, are deterministic functions of the seed. If "completely deterministic" means unsuitable for cryptographic use, then we've gotten nowhere. A deterministic function can be used for cryptography. These two sentences should be better changed to "The Mersenne Twister is one of the most extensively tested random number generators in existence. However, it is not suitable for all purposes and is completely unsuitable for cryptographic purpose because after observing the previous bits generated for a long time, next bit may be guessed correctly with chance larger than 1/2" Best, Shaoyu -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.crul at coreye.fr Mon Oct 23 04:13:42 2017 From: sebastien.crul at coreye.fr (=?iso-8859-1?Q?Crul=2C_S=E9bastien?=) Date: Mon, 23 Oct 2017 08:13:42 +0000 Subject: [docs] Links download documentation in French Translation on 3.6.3 version are KO (404 Error) Message-ID: Hello, I have a problem for download documentation files in French Translation. [cid:image001.png at 01D34BE7.09F9A2C0] >From : https://docs.python.org/fr/3.6/download.html [cid:image002.png at 01D34BE7.09F9A2C0] This urls are down (404 Error) : https://docs.python.org/fr/3.6/archives/python-3.6.3-docs-pdf-a4.zip => 404 Error https://docs.python.org/fr/3.6/archives/python-3.6.3-docs-html.zip => 404 Error I checked with this version 3.5.4 : [cid:image003.png at 01D34BE7.09F9A2C0] But dead : https://docs.python.org/fr/3.5/archives/python-3.5.4-docs-pdf-a4.zip => 404 Error https://docs.python.org/fr/3.5/archives/python-3.5.4-docs-html.zip => 404 Error I download a version English version (3.6.3) and it's OK. Best regards. M. CRUL S?bastien. Email : sebastien.crul at coreye.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3827 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 42297 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 2949 bytes Desc: image003.png URL: From report at bugs.python.org Mon Oct 23 13:56:55 2017 From: report at bugs.python.org (Cheryl Sabella) Date: Mon, 23 Oct 2017 17:56:55 +0000 Subject: [docs] [issue25041] document AF_PACKET socket address format In-Reply-To: <1441804077.41.0.782475265278.issue25041@psf.upfronthosting.co.za> Message-ID: <1508781415.89.0.912454111764.issue25041@psf.upfronthosting.co.za> Change by Cheryl Sabella : ---------- pull_requests: +4062 stage: needs patch -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 23 14:07:59 2017 From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=) Date: Mon, 23 Oct 2017 18:07:59 +0000 Subject: [docs] [issue31822] Document that urllib.parse.{Defrag, Split, Parse}Result are namedtuples In-Reply-To: <1508439273.05.0.213398074469.issue31822@psf.upfronthosting.co.za> Message-ID: <1508782079.17.0.912454111764.issue31822@psf.upfronthosting.co.za> Change by ?ric Araujo : ---------- keywords: +easy nosy: +eric.araujo stage: -> needs patch versions: +Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 23 15:05:32 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Mon, 23 Oct 2017 19:05:32 +0000 Subject: [docs] [issue31822] Document that urllib.parse.{Defrag, Split, Parse}Result are namedtuples In-Reply-To: <1508439273.05.0.213398074469.issue31822@psf.upfronthosting.co.za> Message-ID: <1508785532.42.0.213398074469.issue31822@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: collections.namedtuples is not a class. ---------- nosy: +serhiy.storchaka _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 23 15:08:43 2017 From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=) Date: Mon, 23 Oct 2017 19:08:43 +0000 Subject: [docs] [issue31822] Document that urllib.parse.{Defrag, Split, Parse}Result are namedtuples In-Reply-To: <1508439273.05.0.213398074469.issue31822@psf.upfronthosting.co.za> Message-ID: <1508785723.09.0.213398074469.issue31822@psf.upfronthosting.co.za> ?ric Araujo added the comment: I suggest using :term:`named tuple` for the link (+ an example of using _replace as Mike said) ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 24 03:26:35 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Tue, 24 Oct 2017 07:26:35 +0000 Subject: [docs] [issue31667] Wrong links in the gettext.NullTranslations class In-Reply-To: <1506974695.65.0.213398074469.issue31667@psf.upfronthosting.co.za> Message-ID: <1508829995.3.0.912454111764.issue31667@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- pull_requests: +4070 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 24 03:59:24 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Tue, 24 Oct 2017 07:59:24 +0000 Subject: [docs] [issue31667] Wrong links in the gettext.NullTranslations class In-Reply-To: <1506974695.65.0.213398074469.issue31667@psf.upfronthosting.co.za> Message-ID: <1508831964.03.0.213398074469.issue31667@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: New changeset ef346a2473376c888ff160db9623eaa9871db2ac by Serhiy Storchaka in branch '2.7': [2.7] bpo-31667: Fix gettext related links. (GH-3860) (#4100) https://github.com/python/cpython/commit/ef346a2473376c888ff160db9623eaa9871db2ac ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 24 04:01:17 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Tue, 24 Oct 2017 08:01:17 +0000 Subject: [docs] [issue31667] Wrong links in the gettext.NullTranslations class In-Reply-To: <1506974695.65.0.213398074469.issue31667@psf.upfronthosting.co.za> Message-ID: <1508832077.25.0.912454111764.issue31667@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 24 05:22:24 2017 From: report at bugs.python.org (STINNER Victor) Date: Tue, 24 Oct 2017 09:22:24 +0000 Subject: [docs] [issue31812] Document PEP 545 (documentation translation) in What's New in Python 3.7 In-Reply-To: <1508341337.17.0.213398074469.issue31812@psf.upfronthosting.co.za> Message-ID: <1508836944.15.0.213398074469.issue31812@psf.upfronthosting.co.za> STINNER Victor added the comment: New changeset 809d173c2005ed76f5b6cb178a0cce3f88121883 by Victor Stinner (Julien Palard) in branch 'master': bpo-31812: Add documentation translations to What's New in Python 3.7. (GH-4064) https://github.com/python/cpython/commit/809d173c2005ed76f5b6cb178a0cce3f88121883 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 24 05:22:53 2017 From: report at bugs.python.org (STINNER Victor) Date: Tue, 24 Oct 2017 09:22:53 +0000 Subject: [docs] [issue31812] Document PEP 545 (documentation translation) in What's New in Python 3.7 In-Reply-To: <1508341337.17.0.213398074469.issue31812@psf.upfronthosting.co.za> Message-ID: <1508836973.42.0.912454111764.issue31812@psf.upfronthosting.co.za> Change by STINNER Victor : ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 24 14:38:20 2017 From: report at bugs.python.org (Cheryl Sabella) Date: Tue, 24 Oct 2017 18:38:20 +0000 Subject: [docs] [issue9305] Don't use east/west of UTC in date/time documentation In-Reply-To: <1279556505.28.0.814004588201.issue9305@psf.upfronthosting.co.za> Message-ID: <1508870300.25.0.213398074469.issue9305@psf.upfronthosting.co.za> Cheryl Sabella added the comment: Would one of the original authors of the patches like to create a GitHub pull request for this issue? ---------- nosy: +csabella _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 24 22:46:46 2017 From: report at bugs.python.org (Jun Hui Lee) Date: Wed, 25 Oct 2017 02:46:46 +0000 Subject: [docs] [issue31865] html.unescape does not work as per documentation Message-ID: <1508899606.23.0.213398074469.issue31865@psf.upfronthosting.co.za> New submission from Jun Hui Lee : html.unescape(s) Convert all named and numeric character references (e.g. >, >, &x3e;) But running this gives: >>> html.unescape('>, >, &x3e;') '>, >, &x3e;' ---------- assignee: docs at python components: Documentation messages: 304957 nosy: Jun Hui Lee, docs at python priority: normal severity: normal status: open title: html.unescape does not work as per documentation type: behavior versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 25 12:01:35 2017 From: report at bugs.python.org (J Sloot) Date: Wed, 25 Oct 2017 16:01:35 +0000 Subject: [docs] [issue31869] commentary on ssl.PROTOCOL_TLS Message-ID: <1508947295.4.0.213398074469.issue31869@psf.upfronthosting.co.za> New submission from J Sloot : on https://docs.python.org/2/library/ssl.html#ssl.PROTOCOL_TLS for ssl.PROTOCOL_TLS When the commentary from ssl.PRTOCOL_TLS moved from PROTOCOL_SSLv23 to PROTOCOL_TLS the note {Despite the name, this option can select "TLS" protocols as well as "SSL"} didn't change. Suggested new wording {Despite the name, this option can select "SSL" protocols as well as "TLS"} ---------- assignee: docs at python components: Documentation messages: 304996 nosy: J Sloot, docs at python priority: normal severity: normal status: open title: commentary on ssl.PROTOCOL_TLS versions: Python 2.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Oct 25 19:00:11 2017 From: report at bugs.python.org (Berker Peksag) Date: Wed, 25 Oct 2017 23:00:11 +0000 Subject: [docs] [issue29933] asyncio: set_write_buffer_limits() doc doesn't specify unit of the parameters In-Reply-To: <1490707139.27.0.838851028066.issue29933@psf.upfronthosting.co.za> Message-ID: <1508972411.42.0.213398074469.issue29933@psf.upfronthosting.co.za> Berker Peksag added the comment: PR 2262 has been merged and backported to bugfix branches so I think this issue can be closed now. ---------- nosy: +berker.peksag resolution: -> fixed stage: needs patch -> resolved status: open -> closed type: -> enhancement _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 01:33:13 2017 From: report at bugs.python.org (Mateusz Kurek) Date: Thu, 26 Oct 2017 05:33:13 +0000 Subject: [docs] [issue31871] Support for file descriptor params in os.path Message-ID: <1508995993.41.0.213398074469.issue31871@psf.upfronthosting.co.za> New submission from Mateusz Kurek : Since Python 3.3, some os module functions, like os.stat (https://docs.python.org/3/library/os.html#os.stat), support passing file descriptor instead of a path. os.path functions, on the other hand (like os.path.exists - https://docs.python.org/3/library/os.path.html#os.path.exists - or os.path.samefile - https://docs.python.org/3/library/os.path.html#os.path.samefile) mention using os.stat underneath, but according to documentation, does not support passing file descriptor instead of a path (at least it's not mentioned in the docs that this feature is supported). Is this intentional (os.path functions should not take file descriptor params) or this feature is officialy supported, but it's ommited in the docs? ---------- assignee: docs at python components: Documentation messages: 305023 nosy: Mateusz Kurek, docs at python priority: normal severity: normal status: open title: Support for file descriptor params in os.path type: enhancement versions: Python 3.4, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 04:27:49 2017 From: report at bugs.python.org (Berker Peksag) Date: Thu, 26 Oct 2017 08:27:49 +0000 Subject: [docs] [issue30937] csv module examples miss newline='' when opening files In-Reply-To: <1500130085.47.0.354601054193.issue30937@psf.upfronthosting.co.za> Message-ID: <1509006468.88.0.213398074469.issue30937@psf.upfronthosting.co.za> Berker Peksag added the comment: New changeset 275d2d9c4663a1ea8d1f7c8778567a735b0372c1 by Berker Peksag (Ammar Askar) in branch 'master': bpo-30937: Make usage of newline='' consistent in csv docs (GH-2730) https://github.com/python/cpython/commit/275d2d9c4663a1ea8d1f7c8778567a735b0372c1 ---------- nosy: +berker.peksag _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 04:27:54 2017 From: report at bugs.python.org (Roundup Robot) Date: Thu, 26 Oct 2017 08:27:54 +0000 Subject: [docs] [issue30937] csv module examples miss newline='' when opening files In-Reply-To: <1500130085.47.0.354601054193.issue30937@psf.upfronthosting.co.za> Message-ID: <1509006474.84.0.912454111764.issue30937@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- pull_requests: +4094 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 04:38:19 2017 From: report at bugs.python.org (Berker Peksag) Date: Thu, 26 Oct 2017 08:38:19 +0000 Subject: [docs] [issue30937] csv module examples miss newline='' when opening files In-Reply-To: <1500130085.47.0.354601054193.issue30937@psf.upfronthosting.co.za> Message-ID: <1509007099.77.0.213398074469.issue30937@psf.upfronthosting.co.za> Berker Peksag added the comment: New changeset 614ea48986f80d361043510ac3945f3dcd666c31 by Berker Peksag (Miss Islington (bot)) in branch '3.6': bpo-30937: Make usage of newline='' consistent in csv docs (GH-2730) https://github.com/python/cpython/commit/614ea48986f80d361043510ac3945f3dcd666c31 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 04:39:50 2017 From: report at bugs.python.org (Berker Peksag) Date: Thu, 26 Oct 2017 08:39:50 +0000 Subject: [docs] [issue30937] csv module examples miss newline='' when opening files In-Reply-To: <1500130085.47.0.354601054193.issue30937@psf.upfronthosting.co.za> Message-ID: <1509007190.04.0.213398074469.issue30937@psf.upfronthosting.co.za> Berker Peksag added the comment: Good catch, Pavel. Thanks! This is now fixed in 3.6 and 3.7 docs. Thanks for the patch, Ammar. ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed type: enhancement -> behavior versions: +Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 09:09:44 2017 From: report at bugs.python.org (Tom Floyer) Date: Thu, 26 Oct 2017 13:09:44 +0000 Subject: [docs] [issue31811] async and await missing from keyword list in lexical analysis doc In-Reply-To: <1508340723.02.0.213398074469.issue31811@psf.upfronthosting.co.za> Message-ID: <1509023384.12.0.912454111764.issue31811@psf.upfronthosting.co.za> Change by Tom Floyer : ---------- keywords: +patch pull_requests: +4095 stage: needs patch -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 09:15:32 2017 From: report at bugs.python.org (David Antonini) Date: Thu, 26 Oct 2017 13:15:32 +0000 Subject: [docs] [issue31873] Inconsistent capitalization of proper noun - Unicode. Message-ID: <1509023732.92.0.213398074469.issue31873@psf.upfronthosting.co.za> New submission from David Antonini : Make 'unicode'/'Unicode' capitalization consistent. 'Unicode' is a proper noun, and as such should be capitalized. I submitted a pull request correcting the inconsistent capitalization in the Unicode page of the Documentation - Doc/c-api/unicode.rst - capitalizing 12 errant instances to reflect the correct capitalization in most of the document. I was then requested to open an issue here for discussion. ---------- assignee: docs at python components: Documentation messages: 305050 nosy: docs at python, toonarmycaptain priority: normal pull_requests: 4096 severity: normal status: open title: Inconsistent capitalization of proper noun - Unicode. type: enhancement _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 09:41:52 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Thu, 26 Oct 2017 13:41:52 +0000 Subject: [docs] [issue31873] Inconsistent capitalization of proper noun - Unicode. In-Reply-To: <1509023732.92.0.213398074469.issue31873@psf.upfronthosting.co.za> Message-ID: <1509025312.89.0.213398074469.issue31873@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: I agree that the inconsistency should be fixed. But I'm not sure that we should use the words "an Unicode object" in Python 3. In many similar cases ("a bytes object", "a type object", "a module object") the name of Python type is used. "unicode" was a name of Python type in Python 2. In Python 3 it is "str". The term "Unicode string" also is widely used. Should not we use "a str object", "a string object", "a Unicode string" or "a Unicode string object" in the C API documentation? ---------- components: +Unicode nosy: +benjamin.peterson, ezio.melotti, haypo, lemburg, martin.panter, r.david.murray, serhiy.storchaka stage: -> patch review versions: +Python 3.6, Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 09:50:27 2017 From: report at bugs.python.org (R. David Murray) Date: Thu, 26 Oct 2017 13:50:27 +0000 Subject: [docs] [issue31873] Inconsistent capitalization of proper noun - Unicode. In-Reply-To: <1509023732.92.0.213398074469.issue31873@psf.upfronthosting.co.za> Message-ID: <1509025827.16.0.213398074469.issue31873@psf.upfronthosting.co.za> R. David Murray added the comment: It may be a proper noun, but it is conventionally spelled with a lowercase letter when referring to the type/object. It would be spelled with an upper case letter when referring to the *standard*. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 10:21:36 2017 From: report at bugs.python.org (Hery) Date: Thu, 26 Oct 2017 14:21:36 +0000 Subject: [docs] [issue31876] python363.chm includes gibberish Message-ID: <1509027696.53.0.213398074469.issue31876@psf.upfronthosting.co.za> New submission from Hery : Just Open https://www.python.org/ftp/python/3.6.3/python363.chm And click the first page, it says "What? New in Python". And most of pages the chm file include some gibberish. ---------- assignee: docs at python components: Documentation messages: 305059 nosy: Nim, docs at python priority: normal severity: normal status: open title: python363.chm includes gibberish type: behavior versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 10:59:10 2017 From: report at bugs.python.org (David Antonini) Date: Thu, 26 Oct 2017 14:59:10 +0000 Subject: [docs] [issue31873] Inconsistent capitalization of proper noun - Unicode. In-Reply-To: <1509023732.92.0.213398074469.issue31873@psf.upfronthosting.co.za> Message-ID: <1509029950.19.0.213398074469.issue31873@psf.upfronthosting.co.za> David Antonini added the comment: Does the Unicode documentation currently conform to that convention, or does it require editing? It appears to me that a lot of cases where reference to "Unicode object" is currently capitalised (most of them, in fact) may need to be modified. However, it would seem that there is a grey area in making a distinction between reference to the unicode type as implemented in Python and reference to the standard as a descriptor of the format of an object? The way I read there a lot of the cases are in essence a reference to both. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 11:55:51 2017 From: report at bugs.python.org (R. David Murray) Date: Thu, 26 Oct 2017 15:55:51 +0000 Subject: [docs] [issue31873] Inconsistent capitalization of proper noun - Unicode. In-Reply-To: <1509023732.92.0.213398074469.issue31873@psf.upfronthosting.co.za> Message-ID: <1509033351.62.0.213398074469.issue31873@psf.upfronthosting.co.za> R. David Murray added the comment: In this case I think the cost of editing for consistency may be higher than the value, especially since as you say there are ambiguous cases. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 14:07:17 2017 From: report at bugs.python.org (Tom Floyer) Date: Thu, 26 Oct 2017 18:07:17 +0000 Subject: [docs] [issue31811] async and await missing from keyword list in lexical analysis doc In-Reply-To: <1508340723.02.0.213398074469.issue31811@psf.upfronthosting.co.za> Message-ID: <1509041237.02.0.213398074469.issue31811@psf.upfronthosting.co.za> Tom Floyer added the comment: I've added those keywords to documentation master branch. ---------- nosy: +tomfloyer pull_requests: +4104 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 18:49:01 2017 From: report at bugs.python.org (Berker Peksag) Date: Thu, 26 Oct 2017 22:49:01 +0000 Subject: [docs] [issue24459] Mention PYTHONFAULTHANDLER in the man page In-Reply-To: <1434487895.85.0.561507121326.issue24459@psf.upfronthosting.co.za> Message-ID: <1509058141.29.0.912454111764.issue24459@psf.upfronthosting.co.za> Change by Berker Peksag : ---------- pull_requests: +4106 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Oct 26 18:51:07 2017 From: report at bugs.python.org (Berker Peksag) Date: Thu, 26 Oct 2017 22:51:07 +0000 Subject: [docs] [issue24459] Mention PYTHONFAULTHANDLER in the man page In-Reply-To: <1434487895.85.0.561507121326.issue24459@psf.upfronthosting.co.za> Message-ID: <1509058267.6.0.912454111764.issue24459@psf.upfronthosting.co.za> Change by Berker Peksag : ---------- versions: -Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 27 00:42:19 2017 From: report at bugs.python.org (Berker Peksag) Date: Fri, 27 Oct 2017 04:42:19 +0000 Subject: [docs] [issue31053] Unnecessary argument in command example In-Reply-To: <1501118256.7.0.957994269182.issue31053@psf.upfronthosting.co.za> Message-ID: <1509079338.97.0.213398074469.issue31053@psf.upfronthosting.co.za> Berker Peksag added the comment: New changeset d609b0c24ebdb748cabcc6c062dfc86f9000e6c4 by Berker Peksag (cocoatomo) in branch 'master': bpo-31053: Remove redundant 'venv' argument in venv example (GH-2907) https://github.com/python/cpython/commit/d609b0c24ebdb748cabcc6c062dfc86f9000e6c4 ---------- nosy: +berker.peksag _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 27 00:42:33 2017 From: report at bugs.python.org (Roundup Robot) Date: Fri, 27 Oct 2017 04:42:33 +0000 Subject: [docs] [issue31053] Unnecessary argument in command example In-Reply-To: <1501118256.7.0.957994269182.issue31053@psf.upfronthosting.co.za> Message-ID: <1509079353.67.0.912454111764.issue31053@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- keywords: +patch pull_requests: +4110 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 27 00:47:02 2017 From: report at bugs.python.org (Berker Peksag) Date: Fri, 27 Oct 2017 04:47:02 +0000 Subject: [docs] [issue31053] Unnecessary argument in command example In-Reply-To: <1501118256.7.0.957994269182.issue31053@psf.upfronthosting.co.za> Message-ID: <1509079622.77.0.213398074469.issue31053@psf.upfronthosting.co.za> Berker Peksag added the comment: New changeset 37d1d967eed4018ef397dd9d1515683e5b6b55e7 by Berker Peksag (Miss Islington (bot)) in branch '3.6': bpo-31053: Remove redundant 'venv' argument in venv example (GH-2907) https://github.com/python/cpython/commit/37d1d967eed4018ef397dd9d1515683e5b6b55e7 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 27 00:47:45 2017 From: report at bugs.python.org (Berker Peksag) Date: Fri, 27 Oct 2017 04:47:45 +0000 Subject: [docs] [issue31053] Unnecessary argument in command example In-Reply-To: <1501118256.7.0.957994269182.issue31053@psf.upfronthosting.co.za> Message-ID: <1509079665.22.0.213398074469.issue31053@psf.upfronthosting.co.za> Berker Peksag added the comment: Thank you! ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed type: -> behavior _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 27 07:25:21 2017 From: report at bugs.python.org (Berker Peksag) Date: Fri, 27 Oct 2017 11:25:21 +0000 Subject: [docs] [issue31545] Fixing documentation for timedelta. In-Reply-To: <1506010165.72.0.788430347114.issue31545@psf.upfronthosting.co.za> Message-ID: <1509103521.84.0.213398074469.issue31545@psf.upfronthosting.co.za> Berker Peksag added the comment: New changeset 843ea47a034307c7b1ca642dd70f0269255b289a by Berker Peksag (Utkarsh Upadhyay) in branch 'master': bpo-31545: Update documentation containing timedelta repr. (GH-3687) https://github.com/python/cpython/commit/843ea47a034307c7b1ca642dd70f0269255b289a ---------- nosy: +berker.peksag _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 27 07:25:48 2017 From: report at bugs.python.org (Berker Peksag) Date: Fri, 27 Oct 2017 11:25:48 +0000 Subject: [docs] [issue31545] Fixing documentation for timedelta. In-Reply-To: <1506010165.72.0.788430347114.issue31545@psf.upfronthosting.co.za> Message-ID: <1509103548.01.0.213398074469.issue31545@psf.upfronthosting.co.za> Berker Peksag added the comment: Thanks! ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed type: -> enhancement _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 27 08:29:22 2017 From: report at bugs.python.org (STINNER Victor) Date: Fri, 27 Oct 2017 12:29:22 +0000 Subject: [docs] [issue31545] Fixing documentation for timedelta. In-Reply-To: <1506010165.72.0.788430347114.issue31545@psf.upfronthosting.co.za> Message-ID: <1509107362.91.0.213398074469.issue31545@psf.upfronthosting.co.za> STINNER Victor added the comment: Thank you Utkarsh Upadhyay for finishing the change up to the documentation ;-) ---------- nosy: +haypo _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 27 10:13:51 2017 From: report at bugs.python.org (Utkarsh Upadhyay) Date: Fri, 27 Oct 2017 14:13:51 +0000 Subject: [docs] [issue31545] Fixing documentation for timedelta. In-Reply-To: <1506010165.72.0.788430347114.issue31545@psf.upfronthosting.co.za> Message-ID: <1509113631.88.0.213398074469.issue31545@psf.upfronthosting.co.za> Utkarsh Upadhyay added the comment: :) There's still a lot of room for improvement on documentation front, esp. the inline __doc__s. I'll be working on that next. ~ ut ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Oct 27 13:52:42 2017 From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=) Date: Fri, 27 Oct 2017 17:52:42 +0000 Subject: [docs] [issue31871] Support for file descriptor params in os.path In-Reply-To: <1508995993.41.0.213398074469.issue31871@psf.upfronthosting.co.za> Message-ID: <1509126761.99.0.213398074469.issue31871@psf.upfronthosting.co.za> ?ric Araujo added the comment: > support passing file descriptor instead of a path. os.path functions Are you sure about that? The docs for os.stat show the dir_fd parameter, used to avoid directory renaming issues or attacks, but it doesn?t say that the *path* argument can be an int file descriptor instead of a str file path. ---------- nosy: +eric.araujo _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 28 05:49:54 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Sat, 28 Oct 2017 09:49:54 +0000 Subject: [docs] [issue31871] Support for file descriptor params in os.path In-Reply-To: <1508995993.41.0.213398074469.issue31871@psf.upfronthosting.co.za> Message-ID: <1509184194.41.0.213398074469.issue31871@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: ?ric, see https://docs.python.org/3/library/os.html#files-and-directories. Yes, now some os.path functions can accept a file descriptor as a path. I don't think this is intentional. And this may not work on all platforms. >>> os.path.isdir(1) False >>> os.path.islink(1) Traceback (most recent call last): File "", line 1, in File "/home/serhiy/py/cpython/Lib/posixpath.py", line 169, in islink st = os.lstat(path) TypeError: lstat: path should be string, bytes or os.PathLike, not int ---------- nosy: +serhiy.storchaka _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 28 07:49:45 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Sat, 28 Oct 2017 11:49:45 +0000 Subject: [docs] [issue15606] re.VERBOSE whitespace behavior not completely documented In-Reply-To: <1344534617.67.0.49137100671.issue15606@psf.upfronthosting.co.za> Message-ID: <1509191385.3.0.213398074469.issue15606@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: Steven, would you mind to update your patch according to review comments and create a pull request on GitHub? ---------- stage: patch review -> needs patch versions: +Python 2.7, Python 3.6, Python 3.7 -Python 3.3 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 28 08:06:46 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Sat, 28 Oct 2017 12:06:46 +0000 Subject: [docs] [issue17418] Documentation links for io.open In-Reply-To: <1363273361.29.0.0702686905061.issue17418@psf.upfronthosting.co.za> Message-ID: <1509192406.07.0.912454111764.issue17418@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- status: open -> pending _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 28 08:09:10 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Sat, 28 Oct 2017 12:09:10 +0000 Subject: [docs] [issue22671] Typo in class io.BufferedIOBase docs In-Reply-To: <1413711352.27.0.0253692424247.issue22671@psf.upfronthosting.co.za> Message-ID: <1509192550.0.0.213398074469.issue22671@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: Do you mind to create a PR Martin? ---------- assignee: docs at python -> martin.panter nosy: +serhiy.storchaka versions: +Python 3.6, Python 3.7 -Python 3.4, Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 28 08:27:04 2017 From: report at bugs.python.org (Serhiy Storchaka) Date: Sat, 28 Oct 2017 12:27:04 +0000 Subject: [docs] [issue18534] State clearly that open() 'file' param is "name" attr of the result In-Reply-To: <1374556018.34.0.468152457131.issue18534@psf.upfronthosting.co.za> Message-ID: <1509193624.82.0.912454111764.issue18534@psf.upfronthosting.co.za> Change by Serhiy Storchaka : ---------- status: open -> pending _______________________________________ Python tracker _______________________________________ From alan.co at free.fr Thu Oct 26 09:11:42 2017 From: alan.co at free.fr (Alain) Date: Thu, 26 Oct 2017 15:11:42 +0200 Subject: [docs] DOCUMENTATION PYTHON Message-ID: <38398FCA-79EB-4174-B4AF-E64FCBD84477@free.fr> Hello, I would like to start programing with Python but I canut find the right link to download it. The official I found doesn?t work and tells Error 404 ! Could you please send me this documentation in French if available. Thank ypu for your help. Kindest regards, Alain From jean.jacques.dervain.bosson at gmail.com Wed Oct 25 09:28:03 2017 From: jean.jacques.dervain.bosson at gmail.com (Dervain Bosson) Date: Wed, 25 Oct 2017 13:28:03 +0000 Subject: [docs] french documentation Message-ID: Hello ! (apologize me for my bad english ^_^' ) I am a beginner programming with python. And unfortunately i am not yet very comfortable with documentation in English. So i wanted to download (french version), but unfortunately it is not available. Online yes but locally no (yes i know i'm just repeating myselft :) ). Is there any possibility to obtaining a french doc in local please ? Sincerely Jean Jacques Bosson African Developer. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ktalovmorx at gmail.com Fri Oct 27 16:06:12 2017 From: ktalovmorx at gmail.com (Ktalov Morx) Date: Fri, 27 Oct 2017 16:06:12 -0400 Subject: [docs] Hacer copia de una lista que contiene listas Message-ID: Si, a = [ [1,2,3] ] b = a[:] b[0][0] = 7 Entonces resulta que el elemento 0 de A resulta afectado tambien, b = [ [7,2,3] ] a = [ [7,2,3]] ] -------------- next part -------------- An HTML attachment was scrubbed... URL: From martin.leginus at falcon.io Thu Oct 26 04:43:33 2017 From: martin.leginus at falcon.io (Martin Leginus) Date: Thu, 26 Oct 2017 10:43:33 +0200 Subject: [docs] Incorrect order on list(keys) in the documentation Message-ID: Hi guys, [image: Inline image 1] Looking at the documentation at: https://docs.python.org/3.7/library/stdtypes.html#dictionary-view-objects It seems that order of list(keys) is incorrect in the documentation. Best wishes, martin Martin Leginus Data scientist +45 2693 5851 <+4526935851> Copenhagen Falcon.io Aps H.C. Andersens Blvd. 27 1553 Copenhagen CVR no.: 33362226 [image: Falcon Social] Meet Your Customers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 50560 bytes Desc: not available URL: From t_haiqiang at hotmail.com Fri Oct 27 02:24:52 2017 From: t_haiqiang at hotmail.com (tang haiqiang) Date: Fri, 27 Oct 2017 06:24:52 +0000 Subject: [docs] A Primary user from China Message-ID: Hi, as a primary user learning python without few months, I love python so much. It?s really helpful for me(us) if there?s a documentation for Python in Chinese. But there?s only three versions including English, Japanese and French on the website. It?s a huge number of Chinese people who use python in job and studying, and it?s must be great information for them if you gays can release a Chinese edition. As you can see how poor my English is which might know our desire for it. Looking forward to you soon. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim_ewing at boulder.swri.edu Thu Oct 26 14:03:17 2017 From: tim_ewing at boulder.swri.edu (Tim) Date: Thu, 26 Oct 2017 12:03:17 -0600 Subject: [docs] Bug Report - Scrolling Interaction with Table of Contents Message-ID: On Windows 7, Mozilla Firefox 53.0.3 (64-bit) When using links within the table of contents and scrolling back to the top of a page, the table sometimes clips through the top of the page. It seems to be dependent on scroll speed; you need to scroll slow enough that the table doesn't reset itself. See attached screenshots (mostly bug2.png) for examples of error. Apologies if this isn't the right place to report this, but the tracker looked to be for Python code issues, not issues with the doc. - Tim Ewing -------------- next part -------------- A non-text attachment was scrubbed... Name: bug1.PNG Type: image/png Size: 100421 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bug2.PNG Type: image/png Size: 95132 bytes Desc: not available URL: From report at bugs.python.org Sat Oct 28 20:59:29 2017 From: report at bugs.python.org (Raymond Hettinger) Date: Sun, 29 Oct 2017 00:59:29 +0000 Subject: [docs] [issue28197] range.index mismatch with documentation In-Reply-To: <1474231832.91.0.157673750963.issue28197@psf.upfronthosting.co.za> Message-ID: <1509238769.55.0.912454111764.issue28197@psf.upfronthosting.co.za> Change by Raymond Hettinger : ---------- assignee: rhettinger -> _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Oct 28 23:06:50 2017 From: report at bugs.python.org (Martin Panter) Date: Sun, 29 Oct 2017 03:06:50 +0000 Subject: [docs] [issue22671] Typo in class io.BufferedIOBase docs In-Reply-To: <1413711352.27.0.0253692424247.issue22671@psf.upfronthosting.co.za> Message-ID: <1509246410.43.0.213398074469.issue22671@psf.upfronthosting.co.za> Martin Panter added the comment: I?m unlikely to soon, but I don?t mind if someone else uses my patch. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 29 00:00:17 2017 From: report at bugs.python.org (Berker Peksag) Date: Sun, 29 Oct 2017 04:00:17 +0000 Subject: [docs] [issue31065] Documentation for Popen.poll is unclear In-Reply-To: <1501237857.05.0.15004204926.issue31065@psf.upfronthosting.co.za> Message-ID: <1509249617.94.0.912454111764.issue31065@psf.upfronthosting.co.za> Change by Berker Peksag : ---------- pull_requests: +4130 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 29 00:06:51 2017 From: report at bugs.python.org (Berker Peksag) Date: Sun, 29 Oct 2017 04:06:51 +0000 Subject: [docs] [issue31065] Documentation for Popen.poll is unclear In-Reply-To: <1501237857.05.0.15004204926.issue31065@psf.upfronthosting.co.za> Message-ID: <1509250011.29.0.213398074469.issue31065@psf.upfronthosting.co.za> Berker Peksag added the comment: New changeset 0f1973d06e2116deafb19bbb9443b138187803c7 by Berker Peksag in branch '3.6': bpo-31065: Add doc about Popen.poll returning None. (GH-3169) https://github.com/python/cpython/commit/0f1973d06e2116deafb19bbb9443b138187803c7 ---------- nosy: +berker.peksag _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 29 00:07:46 2017 From: report at bugs.python.org (Berker Peksag) Date: Sun, 29 Oct 2017 04:07:46 +0000 Subject: [docs] [issue31065] Documentation for Popen.poll is unclear In-Reply-To: <1501237857.05.0.15004204926.issue31065@psf.upfronthosting.co.za> Message-ID: <1509250066.19.0.213398074469.issue31065@psf.upfronthosting.co.za> Berker Peksag added the comment: I've backported 006617ff7d6df3fdedcfe53e94ee2c52cc796437 to 3.6. I think this can be closed now, thank you! ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed type: -> enhancement versions: -Python 2.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 29 00:10:02 2017 From: report at bugs.python.org (Berker Peksag) Date: Sun, 29 Oct 2017 04:10:02 +0000 Subject: [docs] [issue31304] Update doc for starmap_async error_back kwarg In-Reply-To: <1504037611.28.0.102125644209.issue31304@psf.upfronthosting.co.za> Message-ID: <1509250202.53.0.912454111764.issue31304@psf.upfronthosting.co.za> Change by Berker Peksag : ---------- keywords: +easy stage: -> needs patch versions: +Python 3.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Oct 29 14:33:02 2017 From: report at bugs.python.org (Pablo Galindo Salgado) Date: Sun, 29 Oct 2017 18:33:02 +0000 Subject: [docs] [issue31304] Update doc for starmap_async error_back kwarg In-Reply-To: <1504037611.28.0.102125644209.issue31304@psf.upfronthosting.co.za> Message-ID: <1509301982.78.0.912454111764.issue31304@psf.upfronthosting.co.za> Change by Pablo Galindo Salgado : ---------- keywords: +patch pull_requests: +4137 stage: needs patch -> patch review _______________________________________ Python tracker _______________________________________ From songofacandy at gmail.com Mon Oct 30 08:13:59 2017 From: songofacandy at gmail.com (INADA Naoki) Date: Mon, 30 Oct 2017 21:13:59 +0900 Subject: [docs] Portuguese Brazilian Transtlation In-Reply-To: References: Message-ID: Hi, Andr?. See https://www.python.org/dev/peps/pep-0545/#language-team about what you need to translate Python doc. If you want to be coordinator of Portuguese translation team, I'll assign you as coordinator on Transifex. Please give me your Transifex user name. INADA Naoki On Tue, Oct 17, 2017 at 1:19 AM, Andr? Girol wrote: > Hello folks! > > My name is Andr? (aka Girol). I'm new in Python Community and fell in love > with the language and the people. > > I noticed that the main documentation is not yet translated to Portuguese > (or not fully translated for a major release). > > I would be honored to help with the documentation. If I can join the > translators' team, I would like to know how to start. I also found a github > repo with the brazilian translation, but it is empty. > > I helped in the translation of other open source projects such as Pro Git > book (small contribution) and with phpmyadmin core translation and revision > of fuzzy sentences. > > Thank you all for your attention and for your amazing work. > > Best Regards, > > -- > Andr? Luiz Girol > > > _______________________________________________ > docs mailing list > docs at python.org > https://mail.python.org/mailman/listinfo/docs > From report at bugs.python.org Mon Oct 30 14:39:31 2017 From: report at bugs.python.org (Mariatta Wijaya) Date: Mon, 30 Oct 2017 18:39:31 +0000 Subject: [docs] [issue31304] Update doc for starmap_async error_back kwarg In-Reply-To: <1504037611.28.0.102125644209.issue31304@psf.upfronthosting.co.za> Message-ID: <1509388771.23.0.213398074469.issue31304@psf.upfronthosting.co.za> Mariatta Wijaya added the comment: New changeset 11225753a89c2907bb717e6c050fe907e5e11829 by Mariatta (Pablo Galindo) in branch 'master': bpo-31304: Update starmap_async documentation. (GH-4168) https://github.com/python/cpython/commit/11225753a89c2907bb717e6c050fe907e5e11829 ---------- nosy: +Mariatta _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 30 14:39:40 2017 From: report at bugs.python.org (Roundup Robot) Date: Mon, 30 Oct 2017 18:39:40 +0000 Subject: [docs] [issue31304] Update doc for starmap_async error_back kwarg In-Reply-To: <1504037611.28.0.102125644209.issue31304@psf.upfronthosting.co.za> Message-ID: <1509388780.96.0.912454111764.issue31304@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- pull_requests: +4147 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 30 14:47:41 2017 From: report at bugs.python.org (Mariatta Wijaya) Date: Mon, 30 Oct 2017 18:47:41 +0000 Subject: [docs] [issue31304] Update doc for starmap_async error_back kwarg In-Reply-To: <1504037611.28.0.102125644209.issue31304@psf.upfronthosting.co.za> Message-ID: <1509389261.49.0.213398074469.issue31304@psf.upfronthosting.co.za> Mariatta Wijaya added the comment: New changeset 2702380870b63ebe0161dfa29a2d0a3de02401b4 by Mariatta (Miss Islington (bot)) in branch '3.6': bpo-31304: Update starmap_async documentation. (GH-4168) (GH-4177) https://github.com/python/cpython/commit/2702380870b63ebe0161dfa29a2d0a3de02401b4 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 30 14:48:42 2017 From: report at bugs.python.org (Mariatta Wijaya) Date: Mon, 30 Oct 2017 18:48:42 +0000 Subject: [docs] [issue31304] Update doc for starmap_async error_back kwarg In-Reply-To: <1504037611.28.0.102125644209.issue31304@psf.upfronthosting.co.za> Message-ID: <1509389322.8.0.213398074469.issue31304@psf.upfronthosting.co.za> Mariatta Wijaya added the comment: This has been fixed. Thanks! ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 30 19:05:47 2017 From: report at bugs.python.org (Roundup Robot) Date: Mon, 30 Oct 2017 23:05:47 +0000 Subject: [docs] [issue31739] socket.close recommended but not demonstrated in same-page example code In-Reply-To: <1507577278.77.0.213398074469.issue31739@psf.upfronthosting.co.za> Message-ID: <1509404747.95.0.912454111764.issue31739@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- keywords: +patch pull_requests: +4152 stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 30 19:26:09 2017 From: report at bugs.python.org (Adam Mitchell) Date: Mon, 30 Oct 2017 23:26:09 +0000 Subject: [docs] [issue31739] socket.close recommended but not demonstrated in same-page example code In-Reply-To: <1507577278.77.0.213398074469.issue31739@psf.upfronthosting.co.za> Message-ID: <1509405969.21.0.213398074469.issue31739@psf.upfronthosting.co.za> Adam Mitchell added the comment: I submitted a pull request, #4181, to fix this issue. I am now waiting for my contributor agreement to be approved. ---------- nosy: +AdamMitchell _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Oct 30 19:28:16 2017 From: report at bugs.python.org (Todd Rovito) Date: Mon, 30 Oct 2017 23:28:16 +0000 Subject: [docs] [issue31739] socket.close recommended but not demonstrated in same-page example code In-Reply-To: <1507577278.77.0.213398074469.issue31739@psf.upfronthosting.co.za> Message-ID: <1509406096.03.0.912454111764.issue31739@psf.upfronthosting.co.za> Change by Todd Rovito : ---------- nosy: +Todd.Rovito _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 31 09:21:07 2017 From: report at bugs.python.org (Roundup Robot) Date: Tue, 31 Oct 2017 13:21:07 +0000 Subject: [docs] [issue31454] Include "import as" in tutorial In-Reply-To: <1505317940.24.0.986048971751.issue31454@psf.upfronthosting.co.za> Message-ID: <1509456067.82.0.912454111764.issue31454@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- pull_requests: +4165 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 31 12:08:44 2017 From: report at bugs.python.org (STINNER Victor) Date: Tue, 31 Oct 2017 16:08:44 +0000 Subject: [docs] [issue20064] PyObject_Malloc is not documented In-Reply-To: <1387913960.58.0.680621486861.issue20064@psf.upfronthosting.co.za> Message-ID: <1509466124.58.0.912454111764.issue20064@psf.upfronthosting.co.za> Change by STINNER Victor : ---------- pull_requests: +4167 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 31 12:20:03 2017 From: report at bugs.python.org (STINNER Victor) Date: Tue, 31 Oct 2017 16:20:03 +0000 Subject: [docs] [issue20064] PyObject_Malloc is not documented In-Reply-To: <1387913960.58.0.680621486861.issue20064@psf.upfronthosting.co.za> Message-ID: <1509466803.02.0.912454111764.issue20064@psf.upfronthosting.co.za> Change by STINNER Victor : ---------- pull_requests: +4170 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 31 12:37:30 2017 From: report at bugs.python.org (STINNER Victor) Date: Tue, 31 Oct 2017 16:37:30 +0000 Subject: [docs] [issue20064] PyObject_Malloc is not documented In-Reply-To: <1387913960.58.0.680621486861.issue20064@psf.upfronthosting.co.za> Message-ID: <1509467850.2.0.213398074469.issue20064@psf.upfronthosting.co.za> STINNER Victor added the comment: New changeset ec2cbdd1dff2c51788136480b2085e77506ebf34 by Victor Stinner in branch 'master': bpo-20064: Document PyObject_Malloc() (#4199) https://github.com/python/cpython/commit/ec2cbdd1dff2c51788136480b2085e77506ebf34 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 31 12:38:42 2017 From: report at bugs.python.org (Roundup Robot) Date: Tue, 31 Oct 2017 16:38:42 +0000 Subject: [docs] [issue20064] PyObject_Malloc is not documented In-Reply-To: <1387913960.58.0.680621486861.issue20064@psf.upfronthosting.co.za> Message-ID: <1509467922.11.0.912454111764.issue20064@psf.upfronthosting.co.za> Change by Roundup Robot : ---------- pull_requests: +4172 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 31 12:55:51 2017 From: report at bugs.python.org (STINNER Victor) Date: Tue, 31 Oct 2017 16:55:51 +0000 Subject: [docs] [issue20064] PyObject_Malloc is not documented In-Reply-To: <1387913960.58.0.680621486861.issue20064@psf.upfronthosting.co.za> Message-ID: <1509468951.51.0.912454111764.issue20064@psf.upfronthosting.co.za> Change by STINNER Victor : ---------- pull_requests: +4173 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 31 12:56:17 2017 From: report at bugs.python.org (STINNER Victor) Date: Tue, 31 Oct 2017 16:56:17 +0000 Subject: [docs] [issue20064] PyObject_Malloc is not documented In-Reply-To: <1387913960.58.0.680621486861.issue20064@psf.upfronthosting.co.za> Message-ID: <1509468977.89.0.213398074469.issue20064@psf.upfronthosting.co.za> STINNER Victor added the comment: New changeset 8543ce8ffd57d770b57fe653e0ab7fada1a4c343 by Victor Stinner (Miss Islington (bot)) in branch '3.6': bpo-20064: Document PyObject_Malloc() (GH-4199) (#4203) https://github.com/python/cpython/commit/8543ce8ffd57d770b57fe653e0ab7fada1a4c343 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 31 13:05:57 2017 From: report at bugs.python.org (STINNER Victor) Date: Tue, 31 Oct 2017 17:05:57 +0000 Subject: [docs] [issue20064] PyObject_Malloc is not documented In-Reply-To: <1387913960.58.0.680621486861.issue20064@psf.upfronthosting.co.za> Message-ID: <1509469557.55.0.912454111764.issue20064@psf.upfronthosting.co.za> Change by STINNER Victor : ---------- pull_requests: -4170 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 31 13:08:31 2017 From: report at bugs.python.org (STINNER Victor) Date: Tue, 31 Oct 2017 17:08:31 +0000 Subject: [docs] [issue20064] PyObject_Malloc is not documented In-Reply-To: <1387913960.58.0.680621486861.issue20064@psf.upfronthosting.co.za> Message-ID: <1509469711.0.0.213398074469.issue20064@psf.upfronthosting.co.za> STINNER Victor added the comment: New changeset 52ba7b447f41dad2754ddbc50ed97413b557bbe1 by Victor Stinner in branch '2.7': bpo-20064: Document PyObject_Malloc() (#4204) https://github.com/python/cpython/commit/52ba7b447f41dad2754ddbc50ed97413b557bbe1 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 31 13:09:18 2017 From: report at bugs.python.org (STINNER Victor) Date: Tue, 31 Oct 2017 17:09:18 +0000 Subject: [docs] [issue20064] PyObject_Malloc is not documented In-Reply-To: <1387913960.58.0.680621486861.issue20064@psf.upfronthosting.co.za> Message-ID: <1509469758.37.0.213398074469.issue20064@psf.upfronthosting.co.za> STINNER Victor added the comment: It took a while, but PyObject_Malloc() & cie are now documented :-) I even backported and *adapted* the doc to Python 2.7 ;-) ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.6, Python 3.7 -Python 3.4, Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 31 16:45:13 2017 From: report at bugs.python.org (=?utf-8?b?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?=) Date: Tue, 31 Oct 2017 20:45:13 +0000 Subject: [docs] [issue31914] Document Pool.(star)map return type Message-ID: <1509482713.68.0.213398074469.issue31914@psf.upfronthosting.co.za> New submission from ????? ???????? : https://docs.python.org/3/library/multiprocessing.html#multiprocessing.pool.Pool.starmap says: starmap(func, iterable[, chunksize]) Like map() except that the elements of the iterable are expected to be iterables that are unpacked as arguments. Hence an iterable of [(1,2), (3, 4)] results in [func(1,2), func(3,4)]. If it was like map() then it would have returned an iterator. Please clarify, that Pool.map and Pool.starmap return list. ---------- assignee: docs at python components: Documentation messages: 305337 nosy: dilyan.palauzov, docs at python priority: normal severity: normal status: open title: Document Pool.(star)map return type type: enhancement versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 31 16:48:05 2017 From: report at bugs.python.org (=?utf-8?b?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?=) Date: Tue, 31 Oct 2017 20:48:05 +0000 Subject: [docs] [issue31914] Document Pool.(star)map return type In-Reply-To: <1509482713.68.0.213398074469.issue31914@psf.upfronthosting.co.za> Message-ID: <1509482885.78.0.213398074469.issue31914@psf.upfronthosting.co.za> ????? ???????? added the comment: Pool.starmap is not like map from the standard library, as the hyperlinking on the word map() suggests, but like Pool.map(). The latter talks about the chunksize parameter, but the former and Pool.starmap don't. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Oct 31 23:14:33 2017 From: report at bugs.python.org (Guido van Rossum) Date: Wed, 01 Nov 2017 03:14:33 +0000 Subject: [docs] [issue18534] State clearly that open() 'file' param is "name" attr of the result In-Reply-To: <1374556018.34.0.468152457131.issue18534@psf.upfronthosting.co.za> Message-ID: <1509506072.95.0.213398074469.issue18534@psf.upfronthosting.co.za> Guido van Rossum added the comment: Agreed it's too subtle to change the behavior. > We may also want to explicitly point out that using os.fsdecode(name) before passing it to open() will ensure that the name attribute is set to a string rather than a bytes object. Not sure. Are there cases where os.fsdecode() fails even if the binary syscall would succeed? (The docs claim that on Windows it uses 'strict'.) If it doesn't, maybe we can add a new attribute that gives the name as Text? It could be '' if name is an int. ---------- nosy: +gvanrossum status: pending -> open _______________________________________ Python tracker _______________________________________ From ojkoorde at gmail.com Tue Oct 31 05:31:58 2017 From: ojkoorde at gmail.com (Artur Kowalczyk) Date: Tue, 31 Oct 2017 10:31:58 +0100 Subject: [docs] (no subject) Message-ID: https://docs.python.org/3/whatsnew/2.2.html#pep-238-changing-the-division-operator Above documentation is not correct in this sentence: *Currently Python?s division operator, /, behaves like C?s division operator when presented with two integer arguments: it returns an integer result that?s truncated down when there would be a fractional part.* Even below in the same paragraph it says sth different. In C/C++ result of integer division is truncated (ie. truncated toward zero). In python / operator when given integer operands performs floor division. Trunc operation is equal to ceil for negative numbers and floor for positive. It is not the same as floor for al reals. in Python 2: -7/3=-3 which is floor of -2.(3) not trunc So Python's integer division is far from being the same as in C or C++. Regards, Artur -------------- next part -------------- An HTML attachment was scrubbed... URL: From os.appertet at gmail.com Tue Oct 31 13:15:26 2017 From: os.appertet at gmail.com (Oscar Appertet) Date: Tue, 31 Oct 2017 18:15:26 +0100 Subject: [docs] problem to dowload "info's package" Message-ID: <2F610653-9285-4CC5-A2C4-E0A07756D3D9@gmail.com> Hi, I'm in your website (https://docs.python.org/3.6/#) and I'm trying to download your whole instructions. I want to have them offline and when I go to the download page it shows me 'Error 404 page not found". Could you please send me these documents to learn this beautiful language that's Python ? Thank you for everything ! Have a nice evening Oscar os.appertet at gmail.com From robsantad44 at gmail.com Mon Oct 30 12:53:21 2017 From: robsantad44 at gmail.com (Robsan Tadesse) Date: Mon, 30 Oct 2017 19:53:21 +0300 Subject: [docs] (no subject) In-Reply-To: References: Message-ID: I Need to learn pyton -------------- next part -------------- An HTML attachment was scrubbed... URL: