From report at bugs.python.org Mon Aug 1 04:48:00 2016 From: report at bugs.python.org (Hynek Schlawack) Date: Mon, 01 Aug 2016 08:48:00 +0000 Subject: [docs] [issue27589] asyncio doc: issue in as_completed() doc In-Reply-To: <1469182105.52.0.303554063448.issue27589@psf.upfronthosting.co.za> Message-ID: <1470041280.53.0.294848472175.issue27589@psf.upfronthosting.co.za> Hynek Schlawack added the comment: More explicitly: The doc sells the function short. If you have a bunch of futures and want to know as soon as one of them is ready: this is the function for you. The only hint that this is the actual behavior comes from the *name* of the function; not the documentation. ---------- nosy: +hynek _______________________________________ Python tracker _______________________________________ From i.safiulin at innopolis.ru Mon Aug 1 07:19:05 2016 From: i.safiulin at innopolis.ru (Ilshat Safiulin) Date: Mon, 1 Aug 2016 11:19:05 +0000 Subject: [docs] Python 3.4.5 docs Message-ID: $null Hi! I was trying to download documentations for Python 3.4.5 but the links are going nowhere https://docs.python.org/3.4/download.html https://www.python.org/ftp/python/doc/3.4.5/python-3.4.5-docs-html.tar.bz2 Could you please fix it? _____ ?????? ????????, ??? ?? "??????????? ?????????" -------------- next part -------------- An HTML attachment was scrubbed... URL: From man0fs0rr0w at protonmail.ch Tue Aug 2 05:12:49 2016 From: man0fs0rr0w at protonmail.ch (man0fS0rr0w) Date: Tue, 02 Aug 2016 05:12:49 -0400 Subject: [docs] Documentation Python 3.4.5 Message-ID: <5waWtPHpfGrNUVfL_KgXQLh6iWyYBPhVyPL1t4FcYzWIT6U0-Wr88jXjsDAuruxp60EFlM41UqZEjdhcUYiEZfuiOZYwt6bOAMZya3sBB9M=@protonmail.ch> Hi. I'm trying to download the tar.bz2 files containing the documentation of Python 3.4.5. But I get a 404 on every links (html, txt...) I've checked for Python 3.5 and it works. French here: excuse me for spelling or grammar errors. Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. -------------- next part -------------- An HTML attachment was scrubbed... URL: From report at bugs.python.org Tue Aug 2 10:10:08 2016 From: report at bugs.python.org (Emanuel Barry) Date: Tue, 02 Aug 2016 14:10:08 +0000 Subject: [docs] [issue27242] Make the docs for NotImplemented & NotImplementedError unambiguous In-Reply-To: <1465239567.69.0.773832868585.issue27242@psf.upfronthosting.co.za> Message-ID: <1470147007.83.0.818239744678.issue27242@psf.upfronthosting.co.za> Emanuel Barry added the comment: Obligatory monthly ping. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 2 12:25:49 2016 From: report at bugs.python.org (Berker Peksag) Date: Tue, 02 Aug 2016 16:25:49 +0000 Subject: [docs] [issue24637] locals dictionary in PyRun_String In-Reply-To: <1436966586.07.0.0153968460371.issue24637@psf.upfronthosting.co.za> Message-ID: <1470155149.18.0.304241110369.issue24637@psf.upfronthosting.co.za> Changes by Berker Peksag : ---------- nosy: +berker.peksag stage: -> patch review versions: -Python 2.7, Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker _______________________________________ From stephane at wirtel.be Tue Aug 2 12:31:31 2016 From: stephane at wirtel.be (stephane at wirtel.be) Date: Tue, 02 Aug 2016 16:31:31 -0000 Subject: [docs] locals dictionary in PyRun_String (issue 24637) Message-ID: <20160802163131.4972.85222@psf.upfronthosting.co.za> it's ok for me. http://bugs.python.org/review/24637/ From report at bugs.python.org Tue Aug 2 12:32:54 2016 From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=) Date: Tue, 02 Aug 2016 16:32:54 +0000 Subject: [docs] [issue24637] locals dictionary in PyRun_String In-Reply-To: <1436966586.07.0.0153968460371.issue24637@psf.upfronthosting.co.za> Message-ID: <1470155574.04.0.831767539916.issue24637@psf.upfronthosting.co.za> St?phane Wirtel added the comment: the patch makes sense for me. ---------- nosy: +matrixise _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 2 12:40:11 2016 From: report at bugs.python.org (Ethan Furman) Date: Tue, 02 Aug 2016 16:40:11 +0000 Subject: [docs] [issue27242] Make the docs for NotImplemented & NotImplementedError unambiguous In-Reply-To: <1465239567.69.0.773832868585.issue27242@psf.upfronthosting.co.za> Message-ID: <1470156011.54.0.997268317737.issue27242@psf.upfronthosting.co.za> Ethan Furman added the comment: Did a little rewording and trimming (and formatting). Tried to keep the ideas while not being so verbose. ---------- Added file: http://bugs.python.org/file43977/issue27242.stoneleaf.01.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 2 12:42:23 2016 From: report at bugs.python.org (Ezio Melotti) Date: Tue, 02 Aug 2016 16:42:23 +0000 Subject: [docs] [issue27242] Make the docs for NotImplemented & NotImplementedError unambiguous In-Reply-To: <1465239567.69.0.773832868585.issue27242@psf.upfronthosting.co.za> Message-ID: <1470156143.95.0.214411467469.issue27242@psf.upfronthosting.co.za> Changes by Ezio Melotti : ---------- nosy: +ezio.melotti _______________________________________ Python tracker _______________________________________ From ghost.adh at runbox.com Tue Aug 2 10:16:18 2016 From: ghost.adh at runbox.com (ghost.adh at runbox.com) Date: Tue, 02 Aug 2016 14:16:18 -0000 Subject: [docs] Clarify the use cases of NotImplemented in the docs (issue 27242) Message-ID: <20160802141618.14289.30242@psf.upfronthosting.co.za> https://bugs.python.org/review/27242/diff/17812/Doc/library/constants.rst File Doc/library/constants.rst (right): https://bugs.python.org/review/27242/diff/17812/Doc/library/constants.rst#newcode38 Doc/library/constants.rst:38: When ``NotImplemented`` is returned, the interpreter will then try the Please, wrap everything to 80 columns. https://bugs.python.org/review/27242/diff/17812/Doc/library/constants.rst#newcode44 Doc/library/constants.rst:44: :meth:`__lt__` or :meth:`__add__`. The appropriate way to signal that an Sentences should be separated by two spaces. Here and everywhere below. https://bugs.python.org/review/27242/diff/17812/Doc/library/constants.rst#newcode47 Doc/library/constants.rst:47: calling the superclass' method with :func:`super`) or raising an exception superclass's https://bugs.python.org/review/27242/ From barry at dadadata.net Tue Aug 2 12:58:38 2016 From: barry at dadadata.net (barry at dadadata.net) Date: Tue, 02 Aug 2016 16:58:38 -0000 Subject: [docs] Clarify the use cases of NotImplemented in the docs (issue 27242) Message-ID: <20160802165838.21841.6919@psf.upfronthosting.co.za> Reviewers: gvanrossum, stoneleaf, Jelle Zijlstra, SilentGhost, Message: A few typos and some nits. Mostly good otherwise. http://bugs.python.org/review/27242/diff/18040/Doc/library/constants.rst File Doc/library/constants.rst (right): http://bugs.python.org/review/27242/diff/18040/Doc/library/constants.rst#newcode50 Doc/library/constants.rst:50: even though they have similar purposes. See :exc:`NotImplementedError` Typo: Implented. Otherwise I'd use :exc:`NotImplementedError` on the above line instead of ``NotImplementedError`` Also s/similar purposes/similar names/ here too. http://bugs.python.org/review/27242/diff/18040/Doc/library/exceptions.rst File Doc/library/exceptions.rst (right): http://bugs.python.org/review/27242/diff/18040/Doc/library/exceptions.rst#newcode244 Doc/library/exceptions.rst:244: even though they have similar purposes. See :data:`NotImplemented` for s/similar purposes/similar names/ IMO. I'd also use :data:`NotImplemented` instead of ``NotImplemented`` on the above line. Also, there's not really a need to reference NotImplementedError from within its own block; but if you do it, please also do this in NotImplemented. Typo: "Implented" on the above line. Please review this at http://bugs.python.org/review/27242/ Affected files: Doc/library/constants.rst Doc/library/exceptions.rst diff --git a/Doc/library/constants.rst b/Doc/library/constants.rst --- a/Doc/library/constants.rst +++ b/Doc/library/constants.rst @@ -26,30 +26,36 @@ A small number of constants live in the .. data:: NotImplemented Special value which should be returned by the binary special methods (e.g. :meth:`__eq__`, :meth:`__lt__`, :meth:`__add__`, :meth:`__rsub__`, etc.) to indicate that the operation is not implemented with respect to the other type; may be returned by the in-place binary special methods (e.g. :meth:`__imul__`, :meth:`__iand__`, etc.) for the same purpose. Its truth value is true. -.. note:: + .. note:: - When ``NotImplemented`` is returned, the interpreter will then try the - reflected operation on the other type, or some other fallback, depending - on the operator. If all attempted operations return ``NotImplemented``, the - interpreter will raise an appropriate exception. + When a binary (or in-place) method returns ``NotImplemented`` the + interpreter will try the reflected operation on the other type (or some + other fallback, depending on the operator). If all attempts return + ``NotImplemented``, the interpreter will raise an appropriate exception. + Incorrectly returning `NotImplemented` will result in a misleading + error message or the ``NotImplemented`` value being returned to Python code. - See - :ref:`implementing-the-arithmetic-operations` - for more details. + See :ref:`implementing-the-arithmetic-operations` for examples. + + .. note:: + + ``NotImplentedError`` and ``NotImplemented`` are not interchangeable, + even though they have similar purposes. See :exc:`NotImplementedError` + for details on when to use it. .. data:: Ellipsis The same as ``...``. Special value used mostly in conjunction with extended slicing syntax for user-defined container data types. .. data:: __debug__ diff --git a/Doc/library/exceptions.rst b/Doc/library/exceptions.rst --- a/Doc/library/exceptions.rst +++ b/Doc/library/exceptions.rst @@ -221,23 +221,35 @@ The following exceptions are the excepti .. exception:: NameError Raised when a local or global name is not found. This applies only to unqualified names. The associated value is an error message that includes the name that could not be found. .. exception:: NotImplementedError This exception is derived from :exc:`RuntimeError`. In user defined base - classes, abstract methods should raise this exception when they require derived - classes to override the method. + classes, abstract methods should raise this exception when they require + derived classes to override the method, or while the class is being + developed to indicate that the real implementation still needs to be added. + .. note:: + + It should not be used to indicate that an operater or method is not + meant to be supported at all -- in that case either leave the operator / + method undefined or, if a subclass, set it to :data:`None`. + + .. note:: + + :exc:`NotImplentedError` and ``NotImplemented`` are not interchangeable, + even though they have similar purposes. See :data:`NotImplemented` for + details on when to use it. .. exception:: OSError([arg]) OSError(errno, strerror[, filename[, winerror[, filename2]]]) .. index:: module: errno This exception is raised when a system function returns a system-related error, including I/O failures such as "file not found" or "disk full" (not for illegal argument types or other incidental errors). @@ -429,20 +441,29 @@ The following exceptions are the excepti The exit status or error message that is passed to the constructor. (Defaults to ``None``.) .. exception:: TypeError Raised when an operation or function is applied to an object of inappropriate type. The associated value is a string giving details about the type mismatch. + This exception may be raised by user code to indicate that an attempted + operation on an object is not supported, and is not meant to. If an object + is meant to support a given operation but has not yet provided an + implementation, :exc:`NotImplementedError` is the proper exception to raise. + + Passing arguments of the wrong type (e.g. passing a :class:`list` when an + :class:`int` is expected) should result in a :exc:`TypeError`, but passing + arguments with the wrong value (e.g. a number outside expected boundaries) + should be a :exc:`ValueError`. .. exception:: UnboundLocalError Raised when a reference is made to a local variable in a function or method, but no value has been bound to that variable. This is a subclass of :exc:`NameError`. .. exception:: UnicodeError From report at bugs.python.org Tue Aug 2 13:00:25 2016 From: report at bugs.python.org (Emanuel Barry) Date: Tue, 02 Aug 2016 17:00:25 +0000 Subject: [docs] [issue27242] Make the docs for NotImplemented & NotImplementedError unambiguous In-Reply-To: <1465239567.69.0.773832868585.issue27242@psf.upfronthosting.co.za> Message-ID: <1470157225.59.0.499050592743.issue27242@psf.upfronthosting.co.za> Emanuel Barry added the comment: Thanks Ethan for the improved patch! Pointed out a typo and some nits, but other than that it's mostly good. I'm not that good at brevity, and I think your patch is much better on that regard :) ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 2 13:19:37 2016 From: report at bugs.python.org (Ethan Furman) Date: Tue, 02 Aug 2016 17:19:37 +0000 Subject: [docs] [issue27242] Make the docs for NotImplemented & NotImplementedError unambiguous In-Reply-To: <1465239567.69.0.773832868585.issue27242@psf.upfronthosting.co.za> Message-ID: <1470158377.12.0.78036952568.issue27242@psf.upfronthosting.co.za> Ethan Furman added the comment: Fixed the typos (thanks!), removed the self-reference, and went with "similar names and purposes". ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 2 15:20:59 2016 From: report at bugs.python.org (Berker Peksag) Date: Tue, 02 Aug 2016 19:20:59 +0000 Subject: [docs] [issue24082] Obsolete note in argument parsing (c-api/arg.rst) In-Reply-To: <1430403570.61.0.800757161817.issue24082@psf.upfronthosting.co.za> Message-ID: <1470165659.9.0.741359389349.issue24082@psf.upfronthosting.co.za> Berker Peksag added the comment: The patch looks good to me. Note that the patch in issue 24278 also removes the same note. ---------- nosy: +berker.peksag stage: -> patch review type: -> behavior versions: +Python 3.5, Python 3.6 -Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 2 17:45:04 2016 From: report at bugs.python.org (Evelyn Mitchell) Date: Tue, 02 Aug 2016 21:45:04 +0000 Subject: [docs] [issue23710] C API doc for PyObject_HEAD is outdated In-Reply-To: <1426776099.01.0.644113037586.issue23710@psf.upfronthosting.co.za> Message-ID: <1470174304.78.0.981363300512.issue23710@psf.upfronthosting.co.za> Evelyn Mitchell added the comment: There is a patch, and it looks good to me. This should be moved into 'commit review' state. ---------- nosy: +Evelyn Mitchell _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 2 17:58:27 2016 From: report at bugs.python.org (Evelyn Mitchell) Date: Tue, 02 Aug 2016 21:58:27 +0000 Subject: [docs] [issue23710] C API doc for PyObject_HEAD is outdated In-Reply-To: <1426776099.01.0.644113037586.issue23710@psf.upfronthosting.co.za> Message-ID: <1470175107.64.0.876070986953.issue23710@psf.upfronthosting.co.za> Evelyn Mitchell added the comment: Changed to commit review. ---------- stage: needs patch -> commit review _______________________________________ Python tracker _______________________________________ From efmphone at gmail.com Tue Aug 2 18:02:12 2016 From: efmphone at gmail.com (efmphone at gmail.com) Date: Tue, 02 Aug 2016 22:02:12 -0000 Subject: [docs] UUID docs should say how to get "standard form" (issue 26267) Message-ID: <20160802220212.14289.6058@psf.upfronthosting.co.za> str() does not return the uuid within {}, line 53 should be changed to show that. http://bugs.python.org/review/26267/ From report at bugs.python.org Tue Aug 2 18:20:08 2016 From: report at bugs.python.org (Ammar Askar) Date: Tue, 02 Aug 2016 22:20:08 +0000 Subject: [docs] [issue26267] UUID docs should say how to get "standard form" In-Reply-To: <1454438589.41.0.991764109365.issue26267@psf.upfronthosting.co.za> Message-ID: <1470176408.2.0.144763289635.issue26267@psf.upfronthosting.co.za> Ammar Askar added the comment: Fixed the str() representation as per Evelyn's comment. ---------- Added file: http://bugs.python.org/file43979/uuiddocs.diff2 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 2 18:31:06 2016 From: report at bugs.python.org (Ammar Askar) Date: Tue, 02 Aug 2016 22:31:06 +0000 Subject: [docs] [issue26267] UUID docs should say how to get "standard form" In-Reply-To: <1454438589.41.0.991764109365.issue26267@psf.upfronthosting.co.za> Message-ID: <1470177066.26.0.275225890016.issue26267@psf.upfronthosting.co.za> Ammar Askar added the comment: Whoops, didn't export the patch properly there so it didn't get picked up by the review tool, this should fix it. ---------- Added file: http://bugs.python.org/file43980/uuiddocs.diff3 _______________________________________ Python tracker _______________________________________ From efmphone at gmail.com Tue Aug 2 18:34:58 2016 From: efmphone at gmail.com (efmphone at gmail.com) Date: Tue, 02 Aug 2016 22:34:58 -0000 Subject: [docs] UUID docs should say how to get "standard form" (issue 26267) Message-ID: <20160802223458.4972.6944@psf.upfronthosting.co.za> Thanks for adding the comparison at 56:58, that's a significant thing to know. http://bugs.python.org/review/26267/ From report at bugs.python.org Tue Aug 2 18:55:10 2016 From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=) Date: Tue, 02 Aug 2016 22:55:10 +0000 Subject: [docs] [issue23710] C API doc for PyObject_HEAD is outdated In-Reply-To: <1426776099.01.0.644113037586.issue23710@psf.upfronthosting.co.za> Message-ID: <1470178510.79.0.700648380796.issue23710@psf.upfronthosting.co.za> Changes by St?phane Wirtel : ---------- nosy: +matrixise _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 02:32:59 2016 From: report at bugs.python.org (Martin Panter) Date: Wed, 03 Aug 2016 06:32:59 +0000 Subject: [docs] [issue24278] Docs on Parsing arguments should say something about mem mgmt for formatters returning C strings In-Reply-To: <1432481258.46.0.49462668629.issue24278@psf.upfronthosting.co.za> Message-ID: <1470205978.92.0.673606296669.issue24278@psf.upfronthosting.co.za> Martin Panter added the comment: Will commit this soon, apart from dropping ?such as bytearray? for s#, which I don?t remember the reasoning. ---------- stage: patch review -> commit review versions: -Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 02:59:06 2016 From: report at bugs.python.org (Berker Peksag) Date: Wed, 03 Aug 2016 06:59:06 +0000 Subject: [docs] [issue26267] UUID docs should say how to get "standard form" In-Reply-To: <1454438589.41.0.991764109365.issue26267@psf.upfronthosting.co.za> Message-ID: <1470207546.02.0.845168046795.issue26267@psf.upfronthosting.co.za> Berker Peksag added the comment: > It also indents the attributes and descriptions to emphasize that they are part of the UUID instance, not the uuid module. Thanks for the patch, but please revert unrelated changes. ---------- nosy: +berker.peksag stage: needs patch -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 03:17:01 2016 From: report at bugs.python.org (Roundup Robot) Date: Wed, 03 Aug 2016 07:17:01 +0000 Subject: [docs] [issue26576] Tweak wording of decorator docos In-Reply-To: <1458196198.66.0.0478952577579.issue26576@psf.upfronthosting.co.za> Message-ID: <20160803071653.23913.52276.160B728A@psf.io> Roundup Robot added the comment: New changeset e0f9f8be7963 by Berker Peksag in branch '3.5': Issue #26576: Clarify that the @deco syntax is not always an equivalent of f = deco(f) https://hg.python.org/cpython/rev/e0f9f8be7963 New changeset 08359651815e by Berker Peksag in branch 'default': Issue #26576: Merge from 3.5 https://hg.python.org/cpython/rev/08359651815e ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 03:19:15 2016 From: report at bugs.python.org (Berker Peksag) Date: Wed, 03 Aug 2016 07:19:15 +0000 Subject: [docs] [issue26576] Tweak wording of decorator docos In-Reply-To: <1458196198.66.0.0478952577579.issue26576@psf.upfronthosting.co.za> Message-ID: <1470208755.36.0.864105818231.issue26576@psf.upfronthosting.co.za> Berker Peksag added the comment: Thanks for the patch, Chris. I've only changed `func` to ``func`` (we don't use single backtick in reST.) ---------- nosy: +berker.peksag resolution: -> fixed stage: -> resolved status: open -> closed type: -> enhancement versions: +Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 03:21:57 2016 From: report at bugs.python.org (Ammar Askar) Date: Wed, 03 Aug 2016 07:21:57 +0000 Subject: [docs] [issue26267] UUID docs should say how to get "standard form" In-Reply-To: <1454438589.41.0.991764109365.issue26267@psf.upfronthosting.co.za> Message-ID: <1470208917.5.0.602071458937.issue26267@psf.upfronthosting.co.za> Ammar Askar added the comment: Done. As a side question, are changes like those indentation problems tracked somewhere else/merged in bulk like spelling changes? ---------- Added file: http://bugs.python.org/file43988/uuiddocs.diff4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 03:49:27 2016 From: report at bugs.python.org (Berker Peksag) Date: Wed, 03 Aug 2016 07:49:27 +0000 Subject: [docs] [issue26267] UUID docs should say how to get "standard form" In-Reply-To: <1454438589.41.0.991764109365.issue26267@psf.upfronthosting.co.za> Message-ID: <1470210567.5.0.440624362853.issue26267@psf.upfronthosting.co.za> Berker Peksag added the comment: I wouldn't consider it a problem since both forms are supported. Also note that you don't need to specify the "UUID." prefix when you use the indented form: .. class:: UUID(...) .. attribute:: bytes I don't think the benefit here is worth the amount of code churn. ---------- _______________________________________ Python tracker _______________________________________ From berker.peksag at gmail.com Wed Aug 3 04:09:25 2016 From: berker.peksag at gmail.com (berker.peksag at gmail.com) Date: Wed, 03 Aug 2016 08:09:25 -0000 Subject: [docs] UUID docs should say how to get "standard form" (issue 26267) Message-ID: <20160803080925.4972.8176@psf.upfronthosting.co.za> http://bugs.python.org/review/26267/diff/18046/Doc/library/uuid.rst File Doc/library/uuid.rst (right): http://bugs.python.org/review/26267/diff/18046/Doc/library/uuid.rst#newcode51 Doc/library/uuid.rst:51: .. describe:: str(uuid) It would be better to be less verbose here. This can go after the "Exactly one of hex, bytes, bytes_le, fields [...]" paragraph in the uuid.UUID() documentation. http://bugs.python.org/review/26267/diff/18046/Doc/library/uuid.rst#newcode56 Doc/library/uuid.rst:56: .. describe:: uuid1 == uuid2 Same as above. See datetime or decimal documentations for an example of how to document comparison operations. http://bugs.python.org/review/26267/ From report at bugs.python.org Wed Aug 3 05:01:26 2016 From: report at bugs.python.org (INADA Naoki) Date: Wed, 03 Aug 2016 09:01:26 +0000 Subject: [docs] [issue27671] FAQ: len() is still function for good reason. Message-ID: <1470214886.13.0.870924776007.issue27671@psf.upfronthosting.co.za> New submission from INADA Naoki: https://docs.python.org/3/faq/design.html#why-does-python-use-methods-for-some-functionality-e-g-list-index-but-functions-for-other-e-g-len-list > The major reason is history. ... > but it?s a part of Python, and it?s too late to make such fundamental changes now. The functions have to remain to avoid massive code breakage. People seeing this answer may think "it's bad design, but remains for historical reason." But there is more positive reason why len is still function. http://effbot.org/pyfaq/why-does-python-use-methods-for-some-functionality-e-g-list-index-but-functions-for-other-e-g-len-list.htm ---------- assignee: docs at python components: Documentation messages: 271881 nosy: docs at python, methane priority: normal severity: normal status: open title: FAQ: len() is still function for good reason. _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 05:58:20 2016 From: report at bugs.python.org (Roundup Robot) Date: Wed, 03 Aug 2016 09:58:20 +0000 Subject: [docs] [issue23710] C API doc for PyObject_HEAD is outdated In-Reply-To: <1426776099.01.0.644113037586.issue23710@psf.upfronthosting.co.za> Message-ID: <20160803095817.19472.9736.0E9E3F8C@psf.io> Roundup Robot added the comment: New changeset 92b468020e07 by Berker Peksag in branch '3.5': Issue #23710: Update PyObject_HEAD documentation https://hg.python.org/cpython/rev/92b468020e07 New changeset 26dd6e7f1733 by Berker Peksag in branch 'default': Issue #23710: Merge from 3.5 https://hg.python.org/cpython/rev/26dd6e7f1733 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 05:59:23 2016 From: report at bugs.python.org (Berker Peksag) Date: Wed, 03 Aug 2016 09:59:23 +0000 Subject: [docs] [issue23710] C API doc for PyObject_HEAD is outdated In-Reply-To: <1426776099.01.0.644113037586.issue23710@psf.upfronthosting.co.za> Message-ID: <1470218363.45.0.932882975159.issue23710@psf.upfronthosting.co.za> Berker Peksag added the comment: Thanks for the patch. Committed capidocs.diff-2 with some tweaks. ---------- resolution: -> fixed stage: commit review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 11:12:05 2016 From: report at bugs.python.org (Berker Peksag) Date: Wed, 03 Aug 2016 15:12:05 +0000 Subject: [docs] [issue18334] type(name, bases, dict) does not call metaclass' __prepare__ attribute In-Reply-To: <1372641138.46.0.644775856541.issue18334@psf.upfronthosting.co.za> Message-ID: <1470237125.12.0.964222853611.issue18334@psf.upfronthosting.co.za> Changes by Berker Peksag : ---------- nosy: +berker.peksag stage: -> patch review versions: +Python 3.5, Python 3.6 -Python 3.3, Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 14:05:48 2016 From: report at bugs.python.org (Zachary Ware) Date: Wed, 03 Aug 2016 18:05:48 +0000 Subject: [docs] [issue19489] move quick search box above TOC In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za> Message-ID: <1470247548.71.0.678053314271.issue19489@psf.upfronthosting.co.za> Zachary Ware added the comment: This LGTM. If it's simple enough, I'd like to see a shot at putting the search box in the top bar, but it's not necessary :) I'll commit this in the near future unless somebody beats me to it. ---------- stage: needs patch -> commit review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 16:19:09 2016 From: report at bugs.python.org (Ammar Askar) Date: Wed, 03 Aug 2016 20:19:09 +0000 Subject: [docs] [issue19489] move quick search box above TOC In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za> Message-ID: <1470255549.79.0.47680954048.issue19489@psf.upfronthosting.co.za> Ammar Askar added the comment: This patch adds the search bar to the navigation/header area on the right. ---------- Added file: http://bugs.python.org/file43994/searchbar_in_header.diff _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 16:39:10 2016 From: report at bugs.python.org (Ammar Askar) Date: Wed, 03 Aug 2016 20:39:10 +0000 Subject: [docs] [issue19489] move quick search box above TOC In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za> Message-ID: <1470256750.76.0.37192785927.issue19489@psf.upfronthosting.co.za> Ammar Askar added the comment: Amended the navigation bar patch to add back a change that only shows the searchbar if javascript is enabled. ---------- Added file: http://bugs.python.org/file43995/searchbar_in_header.diff2 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 16:51:37 2016 From: report at bugs.python.org (Zachary Ware) Date: Wed, 03 Aug 2016 20:51:37 +0000 Subject: [docs] [issue19489] move quick search box above TOC In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za> Message-ID: <1470257497.43.0.582063440094.issue19489@psf.upfronthosting.co.za> Zachary Ware added the comment: I really like the search box in the header/footer. I can't really speak for the actual content of the patch since my Sphinx/HTML/CSS/Jinja/whatever else knowledge is severely limited, but it looks pretty straightforward and the result is very nice. I'd appreciate a review from someone who's better-versed in all things Sphinx (Georg, if you have a chance, you'd be ideal). If there are no objections within about a week, though, I'll just go ahead and commit it. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 16:56:19 2016 From: report at bugs.python.org (Zachary Ware) Date: Wed, 03 Aug 2016 20:56:19 +0000 Subject: [docs] [issue19489] move quick search box above TOC In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za> Message-ID: <1470257779.97.0.901036555946.issue19489@psf.upfronthosting.co.za> Changes by Zachary Ware : ---------- versions: -Python 2.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 21:56:08 2016 From: report at bugs.python.org (Roundup Robot) Date: Thu, 04 Aug 2016 01:56:08 +0000 Subject: [docs] [issue24278] Docs on Parsing arguments should say something about mem mgmt for formatters returning C strings In-Reply-To: <1432481258.46.0.49462668629.issue24278@psf.upfronthosting.co.za> Message-ID: <20160804015604.130636.90642.76BC6F85@psf.io> Roundup Robot added the comment: New changeset ad7da726bea6 by Martin Panter in branch '3.5': Issue #24278: Explain how argument parsing output buffers are managed https://hg.python.org/cpython/rev/ad7da726bea6 New changeset 49c318c6294e by Martin Panter in branch 'default': Issue #24278: Merge argument parsing docs from 3.5 https://hg.python.org/cpython/rev/49c318c6294e ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 22:53:17 2016 From: report at bugs.python.org (Martin Panter) Date: Thu, 04 Aug 2016 02:53:17 +0000 Subject: [docs] [issue24278] Docs on Parsing arguments should say something about mem mgmt for formatters returning C strings In-Reply-To: <1432481258.46.0.49462668629.issue24278@psf.upfronthosting.co.za> Message-ID: <1470279197.07.0.131263464637.issue24278@psf.upfronthosting.co.za> Changes by Martin Panter : ---------- resolution: -> fixed stage: commit review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 3 22:55:03 2016 From: report at bugs.python.org (Martin Panter) Date: Thu, 04 Aug 2016 02:55:03 +0000 Subject: [docs] [issue24082] Obsolete note in argument parsing (c-api/arg.rst) In-Reply-To: <1430403570.61.0.800757161817.issue24082@psf.upfronthosting.co.za> Message-ID: <1470279303.2.0.198533081711.issue24082@psf.upfronthosting.co.za> Martin Panter added the comment: I committed my patch for Issue 24278 (revision ad7da726bea6), so this notice is now removed ---------- nosy: +martin.panter resolution: -> fixed stage: patch review -> resolved status: open -> closed superseder: -> Docs on Parsing arguments should say something about mem mgmt for formatters returning C strings _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 4 04:51:15 2016 From: report at bugs.python.org (Steve Holden) Date: Thu, 04 Aug 2016 08:51:15 +0000 Subject: [docs] [issue27680] Reduce Github pull request rate Message-ID: <1470300675.44.0.889172442592.issue27680@psf.upfronthosting.co.za> New submission from Steve Holden: I have seen a relatively large number of pull requests via the Github mirror repository, because would-be contributors presumably just look on Github and, having found Python there, assume this is the place for contributions. The standard README file gives no clue that the Github repository should not be used as the basis for contributory pull requests, and neither should it. Fortunately Github will display a README.md file in preference to REAMDE when one is found. This patch adds a message, highly visible to Github users, that they are in the wrong place. For an indication of how the Github page will then look, visit https://github.com/holdenweb/python/tree/README where the patch is already installed. ---------- assignee: docs at python components: Documentation files: README.patch keywords: needs review, patch messages: 271958 nosy: docs at python, holdenweb priority: normal severity: normal stage: patch review status: open title: Reduce Github pull request rate type: enhancement Added file: http://bugs.python.org/file44004/README.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 4 05:27:07 2016 From: report at bugs.python.org (Steve Holden) Date: Thu, 04 Aug 2016 09:27:07 +0000 Subject: [docs] [issue27680] Reduce Github pull request rate In-Reply-To: <1470300675.44.0.889172442592.issue27680@psf.upfronthosting.co.za> Message-ID: <1470302827.53.0.351182813702.issue27680@psf.upfronthosting.co.za> Steve Holden added the comment: Hmm, not sure I quite understand how to interact with this tracker. So here's an updated patch that I thought I had already submitted ... ---------- Added file: http://bugs.python.org/file44006/README2.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 4 05:47:19 2016 From: report at bugs.python.org (Berker Peksag) Date: Thu, 04 Aug 2016 09:47:19 +0000 Subject: [docs] [issue27680] Reduce Github pull request rate In-Reply-To: <1470300675.44.0.889172442592.issue27680@psf.upfronthosting.co.za> Message-ID: <1470304039.62.0.415103457787.issue27680@psf.upfronthosting.co.za> Berker Peksag added the comment: I find pull requests templates more useful: https://github.com/blog/2111-issue-and-pull-request-templates and we already have a template to warn users: https://github.com/python/cpython/blob/master/.github/PULL_REQUEST_TEMPLATE.md ---------- nosy: +berker.peksag _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 4 07:57:36 2016 From: report at bugs.python.org (Steve Holden) Date: Thu, 04 Aug 2016 11:57:36 +0000 Subject: [docs] [issue27680] Reduce Github pull request rate In-Reply-To: <1470300675.44.0.889172442592.issue27680@psf.upfronthosting.co.za> Message-ID: <1470311856.77.0.882860420257.issue27680@psf.upfronthosting.co.za> Steve Holden added the comment: I don't seem to be able to activate the PR template, but if you are happy it works then I guess this would be a belt-and-braces change. If nobody merges it and it gets closed that's fine, but if it obviates just a few pull requests it will save both the core devs and the contributors some time. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 4 09:05:06 2016 From: report at bugs.python.org (R. David Murray) Date: Thu, 04 Aug 2016 13:05:06 +0000 Subject: [docs] [issue27680] Reduce Github pull request rate In-Reply-To: <1470300675.44.0.889172442592.issue27680@psf.upfronthosting.co.za> Message-ID: <1470315906.79.0.70251926629.issue27680@psf.upfronthosting.co.za> R. David Murray added the comment: Just FYI Steve, the pull request template is relatively recent addition (within the last two months). ---------- nosy: +r.david.murray _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 4 10:21:21 2016 From: report at bugs.python.org (Steve Holden) Date: Thu, 04 Aug 2016 14:21:21 +0000 Subject: [docs] [issue27680] Reduce Github pull request rate In-Reply-To: <1470300675.44.0.889172442592.issue27680@psf.upfronthosting.co.za> Message-ID: <1470320481.19.0.488309520756.issue27680@psf.upfronthosting.co.za> Steve Holden added the comment: Hmm. Tried making a PR to a forked copy and didn't see it. Probably just incompetence on my part. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 4 10:33:43 2016 From: report at bugs.python.org (Berker Peksag) Date: Thu, 04 Aug 2016 14:33:43 +0000 Subject: [docs] [issue27680] Reduce Github pull request rate In-Reply-To: <1470300675.44.0.889172442592.issue27680@psf.upfronthosting.co.za> Message-ID: <1470321223.51.0.160679035018.issue27680@psf.upfronthosting.co.za> Berker Peksag added the comment: Sorry, I forgot to share a screenshot in my earlier message: https://dl.dropboxusercontent.com/u/166024/pr-template.png ---------- _______________________________________ Python tracker _______________________________________ From zachary.ware+pydocs at gmail.com Thu Aug 4 13:15:55 2016 From: zachary.ware+pydocs at gmail.com (Zachary Ware) Date: Thu, 4 Aug 2016 12:15:55 -0500 Subject: [docs] Word missing In-Reply-To: <746938434.3229025.1469123503230.JavaMail.yahoo@mail.yahoo.com> References: <746938434.3229025.1469123503230.JavaMail.yahoo.ref@mail.yahoo.com> <746938434.3229025.1469123503230.JavaMail.yahoo@mail.yahoo.com> Message-ID: On Thu, Jul 21, 2016 at 12:51 PM, Linda Pescatore via docs wrote: > Section 3.3.2, there is a word missing at the end of this sentence: > > This allows you to type python to run the interpreter, and pip or . Thanks for the report! This has now been fixed. -- Zach From report at bugs.python.org Thu Aug 4 22:16:08 2016 From: report at bugs.python.org (Roundup Robot) Date: Fri, 05 Aug 2016 02:16:08 +0000 Subject: [docs] [issue26462] Patch to enhance literal block language declaration In-Reply-To: <1456790330.71.0.936150839602.issue26462@psf.upfronthosting.co.za> Message-ID: <20160805021605.26446.61705.52C718C9@psf.io> Roundup Robot added the comment: New changeset 6e9a040a993f by Martin Panter in branch '2.7': Issue #26462: Doc: avoid literal_block warnings, fix syntax highlighting. https://hg.python.org/cpython/rev/6e9a040a993f ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 4 23:37:04 2016 From: report at bugs.python.org (Michael Lee) Date: Fri, 05 Aug 2016 03:37:04 +0000 Subject: [docs] [issue27688] Expand documentation about Any in the typing module Message-ID: <1470368224.56.0.159287783102.issue27688@psf.upfronthosting.co.za> New submission from Michael Lee: This patch updates the section about `Any` in the typing module. Previously, that section was relatively sparse and didn't seem to do a very good job of helping the reader understand what the distinction between `Any` and `object` is. This patch expands that section and adds several examples borrowed from the mypy docs and PEP 484. ---------- assignee: docs at python components: Documentation files: object-vs-any.patch keywords: patch messages: 272009 nosy: docs at python, gvanrossum, michael0x2a priority: normal severity: normal status: open title: Expand documentation about Any in the typing module versions: Python 3.5, Python 3.6 Added file: http://bugs.python.org/file44012/object-vs-any.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 00:09:00 2016 From: report at bugs.python.org (Michael Lee) Date: Fri, 05 Aug 2016 04:09:00 +0000 Subject: [docs] [issue27689] Add documentation for typing.Generator Message-ID: <1470370140.25.0.341729775697.issue27689@psf.upfronthosting.co.za> New submission from Michael Lee: This patch adds (previously missing) documentation for `typing.Generator`. ---------- assignee: docs at python components: Documentation files: document-generators.patch keywords: patch messages: 272010 nosy: docs at python, gvanrossum, michael0x2a priority: normal severity: normal status: open title: Add documentation for typing.Generator versions: Python 3.5, Python 3.6 Added file: http://bugs.python.org/file44013/document-generators.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 03:59:58 2016 From: report at bugs.python.org (Ivan Levkivskyi) Date: Fri, 05 Aug 2016 07:59:58 +0000 Subject: [docs] [issue27688] Expand documentation about Any in the typing module In-Reply-To: <1470368224.56.0.159287783102.issue27688@psf.upfronthosting.co.za> Message-ID: <1470383998.38.0.144592301132.issue27688@psf.upfronthosting.co.za> Changes by Ivan Levkivskyi : ---------- nosy: +levkivskyi _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 04:47:32 2016 From: report at bugs.python.org (Martin Panter) Date: Fri, 05 Aug 2016 08:47:32 +0000 Subject: [docs] [issue26462] Patch to enhance literal block language declaration In-Reply-To: <1456790330.71.0.936150839602.issue26462@psf.upfronthosting.co.za> Message-ID: <1470386852.28.0.680973112661.issue26462@psf.upfronthosting.co.za> Martin Panter added the comment: I backported the patch to 2.7. Now I get no warnings about syntax highlighting from 2.7 (there were only a few reported before). ---------- resolution: -> fixed stage: needs patch -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 11:07:03 2016 From: report at bugs.python.org (Mathieu Dupuy) Date: Fri, 05 Aug 2016 15:07:03 +0000 Subject: [docs] [issue20004] csv.DictReader classic class has a property with setter In-Reply-To: <1387278593.92.0.0717442259637.issue20004@psf.upfronthosting.co.za> Message-ID: <1470409623.86.0.391008623376.issue20004@psf.upfronthosting.co.za> Mathieu Dupuy added the comment: The comment is still present in python 3 sources at the moment. Shouldn't we remove it in python 3 ? ---------- nosy: +deronnax _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 12:18:31 2016 From: report at bugs.python.org (Guido van Rossum) Date: Fri, 05 Aug 2016 16:18:31 +0000 Subject: [docs] [issue27689] Add documentation for typing.Generator In-Reply-To: <1470370140.25.0.341729775697.issue27689@psf.upfronthosting.co.za> Message-ID: <1470413911.88.0.102464808994.issue27689@psf.upfronthosting.co.za> Guido van Rossum added the comment: Patch LGTM. I'll apply and merge once your other patches are final. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 12:18:42 2016 From: report at bugs.python.org (Guido van Rossum) Date: Fri, 05 Aug 2016 16:18:42 +0000 Subject: [docs] [issue27689] Add documentation for typing.Generator In-Reply-To: <1470370140.25.0.341729775697.issue27689@psf.upfronthosting.co.za> Message-ID: <1470413922.87.0.785378783702.issue27689@psf.upfronthosting.co.za> Changes by Guido van Rossum : ---------- assignee: docs at python -> gvanrossum _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 12:22:45 2016 From: report at bugs.python.org (Ivan Levkivskyi) Date: Fri, 05 Aug 2016 16:22:45 +0000 Subject: [docs] [issue27689] Add documentation for typing.Generator In-Reply-To: <1470370140.25.0.341729775697.issue27689@psf.upfronthosting.co.za> Message-ID: <1470414165.54.0.730943363059.issue27689@psf.upfronthosting.co.za> Ivan Levkivskyi added the comment: Michael, thank you for the patch. I have only one comment. Generator is one of the few types in typing.py that behaves contravariantly. Maybe you could emphasize that it is contravariant in send type in your patch? ---------- nosy: +levkivskyi _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 13:29:04 2016 From: report at bugs.python.org (Michael Lee) Date: Fri, 05 Aug 2016 17:29:04 +0000 Subject: [docs] [issue27688] Expand documentation about Any in the typing module In-Reply-To: <1470368224.56.0.159287783102.issue27688@psf.upfronthosting.co.za> Message-ID: <1470418144.27.0.21253537329.issue27688@psf.upfronthosting.co.za> Michael Lee added the comment: Here's revision two. The only change I didn't make was the one about the isinstance check. It isn't included in PEP 484, and after talking to Guido, he decided it wouldn't be appropriate to document it here. ---------- Added file: http://bugs.python.org/file44025/object-vs-any-v2.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 14:01:32 2016 From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=) Date: Fri, 05 Aug 2016 18:01:32 +0000 Subject: [docs] [issue27688] Expand documentation about Any in the typing module In-Reply-To: <1470368224.56.0.159287783102.issue27688@psf.upfronthosting.co.za> Message-ID: <1470420092.83.0.311111888721.issue27688@psf.upfronthosting.co.za> St?phane Wirtel added the comment: I have reviewed your patch, and it compiles with sphinx. no issue with the content, but I am not a native speaker and not an expert of the type hinting of python 3.5 ---------- nosy: +matrixise _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 14:08:40 2016 From: report at bugs.python.org (Michael Lee) Date: Fri, 05 Aug 2016 18:08:40 +0000 Subject: [docs] [issue27689] Add documentation for typing.Generator In-Reply-To: <1470370140.25.0.341729775697.issue27689@psf.upfronthosting.co.za> Message-ID: <1470420520.87.0.696892498296.issue27689@psf.upfronthosting.co.za> Michael Lee added the comment: Revision two -- I added a brief note mentioning that SendType is contravariant, as Ivan suggested. ---------- Added file: http://bugs.python.org/file44026/document-generators-v2.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 14:53:42 2016 From: report at bugs.python.org (Terry J. Reedy) Date: Fri, 05 Aug 2016 18:53:42 +0000 Subject: [docs] [issue27671] FAQ: len() is still function for good reason. In-Reply-To: <1470214886.13.0.870924776007.issue27671@psf.upfronthosting.co.za> Message-ID: <1470423222.08.0.140384702158.issue27671@psf.upfronthosting.co.za> Terry J. Reedy added the comment: I agree. We do not need to semi-apologize for having generic functions be builtin generic functions. ---------- nosy: +terry.reedy _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 15:38:19 2016 From: report at bugs.python.org (Michael Lee) Date: Fri, 05 Aug 2016 19:38:19 +0000 Subject: [docs] [issue27689] Add documentation for typing.Generator In-Reply-To: <1470370140.25.0.341729775697.issue27689@psf.upfronthosting.co.za> Message-ID: <1470425899.4.0.886111670813.issue27689@psf.upfronthosting.co.za> Michael Lee added the comment: Revision 3 -- I changed the protocol for the example so that you stop the generator by sending in a negative number as a sentinel rather then None. ---------- Added file: http://bugs.python.org/file44027/document-generators-v3.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 15:58:33 2016 From: report at bugs.python.org (Guido van Rossum) Date: Fri, 05 Aug 2016 19:58:33 +0000 Subject: [docs] [issue27689] Add documentation for typing.Generator In-Reply-To: <1470370140.25.0.341729775697.issue27689@psf.upfronthosting.co.za> Message-ID: <1470427113.45.0.00448943707929.issue27689@psf.upfronthosting.co.za> Guido van Rossum added the comment: changeset: 102542:f10029fea6ee tag: tip parent: 102540:fe189b8bd3ab parent: 102541:b5403f416836 user: Guido van Rossum date: Fri Aug 05 12:57:38 2016 -0700 summary: Add typing.Generator docs, by Michael Lee. (Merge 3.5->3.6) changeset: 102541:b5403f416836 branch: 3.5 parent: 102539:42d84513c3f0 user: Guido van Rossum date: Fri Aug 05 12:56:09 2016 -0700 summary: Add typing.Generator docs, by Michael Lee. ---------- resolution: -> fixed status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 16:32:27 2016 From: report at bugs.python.org (Ned Deily) Date: Fri, 05 Aug 2016 20:32:27 +0000 Subject: [docs] [issue8243] curses writing to window's bottom right position raises: `_curses.error: addstr() returned ERR' In-Reply-To: <1352121880.55.0.191535515397.issue8243@psf.upfronthosting.co.za> Message-ID: <1470429147.09.0.396293947839.issue8243@psf.upfronthosting.co.za> Ned Deily added the comment: See also Issue27693 which documents a similar issue using curses.textpad. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 18:10:34 2016 From: report at bugs.python.org (Roundup Robot) Date: Fri, 05 Aug 2016 22:10:34 +0000 Subject: [docs] [issue27242] Make the docs for NotImplemented & NotImplementedError unambiguous In-Reply-To: <1465239567.69.0.773832868585.issue27242@psf.upfronthosting.co.za> Message-ID: <20160805221031.10605.55539.B3867A1A@psf.io> Roundup Robot added the comment: New changeset 142f5325af06 by Ethan Furman in branch 'default': Clarify NotImplemented vs NotImplementedError. Initial patch by Emmanuel Barry. Closes issue 27242. https://hg.python.org/cpython/rev/142f5325af06 ---------- nosy: +python-dev resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 18:34:27 2016 From: report at bugs.python.org (Berker Peksag) Date: Fri, 05 Aug 2016 22:34:27 +0000 Subject: [docs] [issue12276] 3.x ignores sys.tracebacklimit=0 In-Reply-To: <1307436501.83.0.59684150491.issue12276@psf.upfronthosting.co.za> Message-ID: <1470436467.02.0.691834412241.issue12276@psf.upfronthosting.co.za> Changes by Berker Peksag : ---------- keywords: +easy stage: -> needs patch type: -> behavior versions: +Python 3.5, Python 3.6 -Python 3.1, Python 3.2 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 18:45:56 2016 From: report at bugs.python.org (Berker Peksag) Date: Fri, 05 Aug 2016 22:45:56 +0000 Subject: [docs] [issue3216] Scarce msilib documentation In-Reply-To: <1214577470.61.0.590067451474.issue3216@psf.upfronthosting.co.za> Message-ID: <1470437156.02.0.0112932162576.issue3216@psf.upfronthosting.co.za> Berker Peksag added the comment: All obvious bugs have already been fixed. ---------- nosy: +berker.peksag resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 18:55:47 2016 From: report at bugs.python.org (Berker Peksag) Date: Fri, 05 Aug 2016 22:55:47 +0000 Subject: [docs] [issue14594] document imp.load_dynamic() In-Reply-To: <1334576684.12.0.825511182603.issue14594@psf.upfronthosting.co.za> Message-ID: <1470437747.67.0.615575041114.issue14594@psf.upfronthosting.co.za> Berker Peksag added the comment: The imp module has been deprecated long time ago and the importlib module itself doesn't it anymore. However, Cython still use it: https://github.com/cython/cython/blob/master/pyximport/pyximport.py#L217 I'm inclined to close this as 'out of date' but feel free to reopen it :) ---------- nosy: +berker.peksag resolution: -> out of date stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 19:40:54 2016 From: report at bugs.python.org (Berker Peksag) Date: Fri, 05 Aug 2016 23:40:54 +0000 Subject: [docs] [issue15639] csv.Error description is incorrectly broad In-Reply-To: <1344861900.41.0.500081964818.issue15639@psf.upfronthosting.co.za> Message-ID: <1470440454.23.0.712629302276.issue15639@psf.upfronthosting.co.za> Berker Peksag added the comment: Thanks for the report. Most of the csv.Error usages are in Modules/_csv.c. You can search for "_csvstate_global->error_obj" in the module's source code. I think the documentation is correct as is. ---------- nosy: +berker.peksag resolution: -> not a bug stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 19:59:34 2016 From: report at bugs.python.org (Roundup Robot) Date: Fri, 05 Aug 2016 23:59:34 +0000 Subject: [docs] [issue18548] In unittest doc change WidgetTestCase to SimpleWidgetTestCase in suite() In-Reply-To: <1374691721.34.0.862188774104.issue18548@psf.upfronthosting.co.za> Message-ID: <20160805235928.71977.76082.B824D85C@psf.io> Roundup Robot added the comment: New changeset d0402caa0ef5 by Berker Peksag in branch '3.5': Issue #18548: Fix unittest.TestSuite() example https://hg.python.org/cpython/rev/d0402caa0ef5 New changeset e17e3f620709 by Berker Peksag in branch 'default': Issue #18548: Merge from 3.5 https://hg.python.org/cpython/rev/e17e3f620709 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 20:00:56 2016 From: report at bugs.python.org (Berker Peksag) Date: Sat, 06 Aug 2016 00:00:56 +0000 Subject: [docs] [issue18548] In unittest doc change WidgetTestCase to SimpleWidgetTestCase in suite() In-Reply-To: <1374691721.34.0.862188774104.issue18548@psf.upfronthosting.co.za> Message-ID: <1470441656.52.0.599518250088.issue18548@psf.upfronthosting.co.za> Berker Peksag added the comment: Good catch, thanks! I went with Ezio's suggestion but left 2.7 documentation as is. ---------- nosy: +berker.peksag resolution: -> fixed stage: patch review -> resolved status: open -> closed type: enhancement -> behavior versions: +Python 3.5, Python 3.6 -Python 3.3, Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 5 20:07:35 2016 From: report at bugs.python.org (Berker Peksag) Date: Sat, 06 Aug 2016 00:07:35 +0000 Subject: [docs] [issue21056] csv documentation is incorrect In-Reply-To: <1395720703.0.0.19592596057.issue21056@psf.upfronthosting.co.za> Message-ID: <1470442055.81.0.159713735783.issue21056@psf.upfronthosting.co.za> Changes by Berker Peksag : ---------- keywords: +easy stage: -> needs patch versions: +Python 3.5, Python 3.6 -Python 3.4 _______________________________________ Python tracker _______________________________________ From ammar at ammaraskar.com Fri Aug 5 23:20:16 2016 From: ammar at ammaraskar.com (ammar at ammaraskar.com) Date: Sat, 06 Aug 2016 03:20:16 -0000 Subject: [docs] UUID docs should say how to get "standard form" (issue 26267) Message-ID: <20160806032016.12558.61768@psf.upfronthosting.co.za> https://bugs.python.org/review/26267/diff/18046/Doc/library/uuid.rst File Doc/library/uuid.rst (right): https://bugs.python.org/review/26267/diff/18046/Doc/library/uuid.rst#newcode56 Doc/library/uuid.rst:56: .. describe:: uuid1 == uuid2 On 2016/08/03 10:09:25, berkerpeksag wrote: > Same as above. See datetime or decimal documentations for an example of how to > document comparison operations. So datetime takes the approach of documenting operators in a table (presumably because it has a lot of ops) https://docs.python.org/3/library/datetime.html#datetime.date.day decimal seems to do it in this way https://docs.python.org/3/library/decimal.html#decimal.Decimal.compare The style I used here is from https://docs.python.org/3/library/stdtypes.html#set but now that I look at it, within the stdtypes there's also the datetime style operator documentation for numbers. https://docs.python.org/3/library/stdtypes.html#numeric-types-int-float-complex Is there a preferred style for documenting operators? Which one should I use here? (apparently I forgot to click the publish button on Rietveld, I wrote this day before yesterday) https://bugs.python.org/review/26267/ From report at bugs.python.org Sat Aug 6 06:22:35 2016 From: report at bugs.python.org (Berker Peksag) Date: Sat, 06 Aug 2016 10:22:35 +0000 Subject: [docs] [issue12946] PyModule_GetDict() claims it can never fail, but it can In-Reply-To: <1315585192.34.0.742122652176.issue12946@psf.upfronthosting.co.za> Message-ID: <1470478955.08.0.0807761307423.issue12946@psf.upfronthosting.co.za> Berker Peksag added the comment: I've changed the dead code to assert(d != NULL); and added the following sentence to PyModule_GetDict documentation: If *module* is not a module object (or a subtype of a module object), :exc:`SystemError` is raised and *NULL* is returned. ---------- keywords: +patch nosy: +berker.peksag stage: -> patch review versions: +Python 3.6 -Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4 Added file: http://bugs.python.org/file44030/issue12946.diff _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 6 06:41:35 2016 From: report at bugs.python.org (Berker Peksag) Date: Sat, 06 Aug 2016 10:41:35 +0000 Subject: [docs] [issue23105] os.O_SHLOCK and os.O_EXLOCK are not available on Linux In-Reply-To: <1419345535.42.0.312768269587.issue23105@psf.upfronthosting.co.za> Message-ID: <1470480095.51.0.343520661864.issue23105@psf.upfronthosting.co.za> Changes by Berker Peksag : ---------- keywords: +easy stage: -> needs patch versions: +Python 3.6 -Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 6 07:03:10 2016 From: report at bugs.python.org (Berker Peksag) Date: Sat, 06 Aug 2016 11:03:10 +0000 Subject: [docs] [issue23542] Update PEP 476 for using urllib2.build_opener() In-Reply-To: <1425069828.0.0.476725699175.issue23542@psf.upfronthosting.co.za> Message-ID: <1470481390.82.0.842979803851.issue23542@psf.upfronthosting.co.za> Berker Peksag added the comment: Thanks for the patch, but I prefer keeping the section shorter. Also, note that disabling verification globally is discouraged in the PEP. ---------- nosy: +berker.peksag resolution: -> rejected stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 6 07:04:25 2016 From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=) Date: Sat, 06 Aug 2016 11:04:25 +0000 Subject: [docs] [issue23105] os.O_SHLOCK and os.O_EXLOCK are not available on Linux In-Reply-To: <1419345535.42.0.312768269587.issue23105@psf.upfronthosting.co.za> Message-ID: <1470481465.94.0.822310462332.issue23105@psf.upfronthosting.co.za> St?phane Wirtel added the comment: If you read the documentation from glibc-2.24, these options are only available on BSD and not on Linux. """ The remaining operating modes are BSD extensions. They exist only on some systems. On other systems, these macros are not defined. Macro: int O_SHLOCK Acquire a shared lock on the file, as with flock. See File Locks. If O_CREAT is specified, the locking is done atomically when creating the file. You are guaranteed that no other process will get the lock on the new file first. Macro: int O_EXLOCK Acquire an exclusive lock on the file, as with flock. See File Locks. This is atomic like O_SHLOCK. """ With my fedora 24, and glibc 2.23 I don't find any reference to these macros. ---------- nosy: +matrixise _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 6 07:04:46 2016 From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=) Date: Sat, 06 Aug 2016 11:04:46 +0000 Subject: [docs] [issue23105] os.O_SHLOCK and os.O_EXLOCK are not available on Linux In-Reply-To: <1419345535.42.0.312768269587.issue23105@psf.upfronthosting.co.za> Message-ID: <1470481486.63.0.609953257253.issue23105@psf.upfronthosting.co.za> St?phane Wirtel added the comment: Link to the documentation of glibc: http://www.gnu.org/software/libc/manual/html_node/Open_002dtime-Flags.html ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 6 07:19:58 2016 From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=) Date: Sat, 06 Aug 2016 11:19:58 +0000 Subject: [docs] [issue23105] os.O_SHLOCK and os.O_EXLOCK are not available on Linux In-Reply-To: <1419345535.42.0.312768269587.issue23105@psf.upfronthosting.co.za> Message-ID: <1470482398.48.0.406533273134.issue23105@psf.upfronthosting.co.za> St?phane Wirtel added the comment: I am working on it. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 6 07:47:16 2016 From: report at bugs.python.org (Berker Peksag) Date: Sat, 06 Aug 2016 11:47:16 +0000 Subject: [docs] [issue24626] please sync cgi.parse document In-Reply-To: <1436757548.2.0.774685113457.issue24626@psf.upfronthosting.co.za> Message-ID: <1470484036.68.0.473529168853.issue24626@psf.upfronthosting.co.za> Berker Peksag added the comment: Thanks for the report! The default values of fp and environ parameters are already documented in the function signature in Python 3: cgi.parse(fp=None, environ=os.environ, keep_blank_values=False, strict_parsing=False) In Python 2, the function signature is: cgi.parse(fp[, environ[, keep_blank_values[, strict_parsing]]]) Since the default values cannot be documented in the latter form, we need to specify them separately in plain text. The reason why "(the file defaults to ``sys.stdin``)" is still in Python 3 documentation is because of the following two lines in cgi.parse() implementation: if fp is None: fp = sys.stdin So if you invoke cgi.parse() (which means fp is None) it will be replaced with sys.stdin. ---------- resolution: -> not a bug stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 6 08:38:26 2016 From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=) Date: Sat, 06 Aug 2016 12:38:26 +0000 Subject: [docs] [issue23105] os.O_SHLOCK and os.O_EXLOCK are not available on Linux In-Reply-To: <1419345535.42.0.312768269587.issue23105@psf.upfronthosting.co.za> Message-ID: <1470487105.98.0.0288839829471.issue23105@psf.upfronthosting.co.za> St?phane Wirtel added the comment: patch for 3.6 with the comment of Sworddragon. ---------- keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file44032/issue23105.diff _______________________________________ Python tracker _______________________________________ From stephane at wirtel.be Sat Aug 6 09:47:10 2016 From: stephane at wirtel.be (stephane at wirtel.be) Date: Sat, 06 Aug 2016 13:47:10 -0000 Subject: [docs] PyModule_GetDict() claims it can never fail, but it can (issue 12946) Message-ID: <20160806134710.4972.66800@psf.upfronthosting.co.za> http://bugs.python.org/review/12946/diff/18078/Doc/c-api/module.rst File Doc/c-api/module.rst (right): http://bugs.python.org/review/12946/diff/18078/Doc/c-api/module.rst#newcode64 Doc/c-api/module.rst:64: :exc:`SystemError` is raised and *NULL* is returned. The assert will raise a SystemError ? http://bugs.python.org/review/12946/ From berker.peksag at gmail.com Sat Aug 6 11:34:30 2016 From: berker.peksag at gmail.com (berker.peksag at gmail.com) Date: Sat, 06 Aug 2016 15:34:30 -0000 Subject: [docs] PyModule_GetDict() claims it can never fail, but it can (issue 12946) Message-ID: <20160806153430.18363.78718@psf.upfronthosting.co.za> http://bugs.python.org/review/12946/diff/18078/Doc/c-api/module.rst File Doc/c-api/module.rst (right): http://bugs.python.org/review/12946/diff/18078/Doc/c-api/module.rst#newcode64 Doc/c-api/module.rst:64: :exc:`SystemError` is raised and *NULL* is returned. On 2016/08/06 15:47:10, matrixise wrote: > The assert will raise a SystemError ? No, the following branch will raise SystemError: if (!PyModule_Check(m)) { PyErr_BadInternalCall(); return NULL; } I added the assert statement as a sanity check. http://bugs.python.org/review/12946/ From ferry.boender at electricmonk.nl Wed Aug 3 10:59:41 2016 From: ferry.boender at electricmonk.nl (Ferry Boender) Date: Wed, 3 Aug 2016 16:59:41 +0200 Subject: [docs] Downloads for Python 3.4.5 not working Message-ID: Hello, FYI: The downloads for Python documentation 3.4.5 ( https://docs.python.org/3.4/download.html) don't seem to be working: https://www.python.org/ftp/python/doc/3.4.5/python-3.4.5-docs-pdf-a4.zip results in: 404 Not Found nginx I don't really need them, but I thought you might like to know! With kind regards, Ferry -------------- next part -------------- An HTML attachment was scrubbed... URL: From ghost.adh at runbox.com Thu Aug 4 05:07:19 2016 From: ghost.adh at runbox.com (ghost.adh at runbox.com) Date: Thu, 04 Aug 2016 09:07:19 -0000 Subject: [docs] Reduce Github pull request rate (issue 27680) Message-ID: <20160804090719.18363.71929@psf.upfronthosting.co.za> https://bugs.python.org/review/27680/diff/18057/README.md File README.md (right): https://bugs.python.org/review/27680/diff/18057/README.md#newcode16 README.md:16: at https://hg.python.org/, updated daily as a service to those who are already using perhaps link to https://hg.python.org/cpython ? https://bugs.python.org/review/27680/diff/18057/README.md#newcode23 README.md:23: explains all you need you know to join the Python developers. If you are all you need to know https://bugs.python.org/review/27680/diff/18057/README.md#newcode24 README.md:24: interested in contributring then we especially recommend that you read contributing https://bugs.python.org/review/27680/diff/18057/README.md#newcode27 README.md:27: Thanks for taking time to visit the Python repository, and for yout interest in Python. your https://bugs.python.org/review/27680/ From guido at python.org Thu Aug 4 23:58:12 2016 From: guido at python.org (guido at python.org) Date: Fri, 05 Aug 2016 03:58:12 -0000 Subject: [docs] Expand documentation about Any in the typing module (issue 27688) Message-ID: <20160805035812.12558.22266@psf.upfronthosting.co.za> http://bugs.python.org/review/27688/diff/18064/Doc/library/typing.rst File Doc/library/typing.rst (right): http://bugs.python.org/review/27688/diff/18064/Doc/library/typing.rst#newcode187 Doc/library/typing.rst:187: A special kind of type is :class:`Any`. The static type checker will treat Maybe "a static type checker"? http://bugs.python.org/review/27688/diff/18064/Doc/library/typing.rst#newcode188 Doc/library/typing.rst:188: every type as a subclass of :class:`Any` and :class:`Any` as a subtype of Could you avoid "subclass" and instead say something like "compatible with"? (My apologies if PEP 484 isn't always politically correct on this yet.) http://bugs.python.org/review/27688/diff/18064/Doc/library/typing.rst#newcode211 Doc/library/typing.rst:211: not throw an error when assigning ``a`` to ``s`` even though ``s`` was throw -> report http://bugs.python.org/review/27688/diff/18064/Doc/library/typing.rst#newcode241 Doc/library/typing.rst:241: # Fails; an object does not have a `magic` method. Maybe also show that hash(42) *does* type-check? http://bugs.python.org/review/27688/diff/18064/Doc/library/typing.rst#newcode251 Doc/library/typing.rst:251: manner. Use :class:`Any` to indicate that a value is dynamically typed. Maybe add that you have to use isinstance() to be able to use the value if its type is object? http://bugs.python.org/review/27688/ From guido at python.org Fri Aug 5 14:25:14 2016 From: guido at python.org (guido at python.org) Date: Fri, 05 Aug 2016 18:25:14 -0000 Subject: [docs] Add documentation for typing.Generator (issue 27689) Message-ID: <20160805182514.4972.12895@psf.upfronthosting.co.za> http://bugs.python.org/review/27689/diff/18074/Doc/library/typing.rst File Doc/library/typing.rst (right): http://bugs.python.org/review/27689/diff/18074/Doc/library/typing.rst#newcode474 Doc/library/typing.rst:474: while sent is not None: On 2016/08/05 20:15:15, levkivskyi wrote: > One more comment: One might be confused why send type is float and not > Optional[float], maybe you could add an explanation that one anyway can only > send None as a first value, so that Optional is redundant. Hm, that initial None is not given to yield (it just starts execution of the generator body). This code really needs Optional[float] in the signature, if that's used as the sentinel (once we have strict optional checking). http://bugs.python.org/review/27689/ From johnsonabraham0812 at gmail.com Fri Aug 5 03:33:19 2016 From: johnsonabraham0812 at gmail.com (Johnson Abraham) Date: Fri, 5 Aug 2016 13:03:19 +0530 Subject: [docs] Python 3.4.4 Message-ID: Hi, I couldn't download documentation of Python 3.4.4. I've attached the screenshot for your reference. Thank you! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot_2016-08-05-13-01-41.png Type: image/png Size: 22037 bytes Desc: not available URL: From levkivskyi at gmail.com Fri Aug 5 03:57:01 2016 From: levkivskyi at gmail.com (levkivskyi at gmail.com) Date: Fri, 05 Aug 2016 07:57:01 -0000 Subject: [docs] Expand documentation about Any in the typing module (issue 27688) Message-ID: <20160805075701.18363.95727@psf.upfronthosting.co.za> Two minor comments. http://bugs.python.org/review/27688/diff/18064/Doc/library/typing.rst File Doc/library/typing.rst (right): http://bugs.python.org/review/27688/diff/18064/Doc/library/typing.rst#newcode222 Doc/library/typing.rst:222: # The static type checker treats the above Maybe "A static type checker" here too? http://bugs.python.org/review/27688/diff/18064/Doc/library/typing.rst#newcode236 Doc/library/typing.rst:236: That means when the type of a value is :class:`object`, the type checker will same here "a type checker" http://bugs.python.org/review/27688/ From levkivskyi at gmail.com Fri Aug 5 14:15:15 2016 From: levkivskyi at gmail.com (levkivskyi at gmail.com) Date: Fri, 05 Aug 2016 18:15:15 -0000 Subject: [docs] Add documentation for typing.Generator (issue 27689) Message-ID: <20160805181515.12558.5136@psf.upfronthosting.co.za> http://bugs.python.org/review/27689/diff/18074/Doc/library/typing.rst File Doc/library/typing.rst (right): http://bugs.python.org/review/27689/diff/18074/Doc/library/typing.rst#newcode474 Doc/library/typing.rst:474: while sent is not None: One more comment: One might be confused why send type is float and not Optional[float], maybe you could add an explanation that one anyway can only send None as a first value, so that Optional is redundant. http://bugs.python.org/review/27689/ From patrickwayodi at gmail.com Wed Aug 3 10:56:13 2016 From: patrickwayodi at gmail.com (Patrick Wayodi) Date: Wed, 3 Aug 2016 17:56:13 +0300 Subject: [docs] Missing archives for Python 3.4.5 Docs Message-ID: I am unable to download any of the docs on the Python 3.4.5 Documentation page: https://docs.python.org/3.4/download.html From Perry.Rothenbaum at onsemi.com Thu Aug 4 21:37:48 2016 From: Perry.Rothenbaum at onsemi.com (Perry Rothenbaum) Date: Fri, 5 Aug 2016 01:37:48 +0000 Subject: [docs] Your print statement in the tutorial is misisng parethesis Message-ID: <030CA89F208D374486F026F538D16EDB6AE52B93@ONWATER52M.ad.onsemi.com> I am learning Python 3.5. I'm following your examples in section 3 "An informal introduction to Python" tutorial. The "print" statement is shown without parenthesis in the tutorial and in Python 3.5 it only works with parenthesis. In fact, if I try to type it as you have it shown, I get an error and am being told to add parenthesis. When I add parenthesis it works. Regards, Perry Rothenbaum ON Semiconductor Field Applications System Engineering (Continental Automotive) 1515 Woodfield Road, Suite 745 Schaumburg, IL 60173 Cell 312 805 9456 perry.rothenbaum at onsemi.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane at wirtel.be Fri Aug 5 13:59:56 2016 From: stephane at wirtel.be (stephane at wirtel.be) Date: Fri, 05 Aug 2016 17:59:56 -0000 Subject: [docs] Expand documentation about Any in the typing module (issue 27688) Message-ID: <20160805175956.12558.87258@psf.upfronthosting.co.za> it's ok for me, but I am not an expert with the type hinting of 3.5. http://bugs.python.org/review/27688/ From steve at holdenweb.com Thu Aug 4 05:18:52 2016 From: steve at holdenweb.com (steve at holdenweb.com) Date: Thu, 04 Aug 2016 09:18:52 -0000 Subject: [docs] Reduce Github pull request rate (issue 27680) Message-ID: <20160804091852.21841.77026@psf.upfronthosting.co.za> Reviewers: SilentGhost, Message: Submitting a new patch remedying the dyslexia-induced errors pointed out by SilentGhost. Thank! https://bugs.python.org/review/27680/diff/18057/README.md File README.md (right): https://bugs.python.org/review/27680/diff/18057/README.md#newcode16 README.md:16: at https://hg.python.org/, updated daily as a service to those who are already using On 2016/08/04 11:07:19, SilentGhost wrote: > perhaps link to https://hg.python.org/cpython ? Done. https://bugs.python.org/review/27680/diff/18057/README.md#newcode23 README.md:23: explains all you need you know to join the Python developers. If you are On 2016/08/04 11:07:19, SilentGhost wrote: > all you need to know Done. https://bugs.python.org/review/27680/diff/18057/README.md#newcode24 README.md:24: interested in contributring then we especially recommend that you read On 2016/08/04 11:07:19, SilentGhost wrote: > contributing Done. https://bugs.python.org/review/27680/diff/18057/README.md#newcode27 README.md:27: Thanks for taking time to visit the Python repository, and for yout interest in Python. On 2016/08/04 11:07:19, SilentGhost wrote: > your Done. Please review this at https://bugs.python.org/review/27680/ Affected files: README.md diff -r b04560c3ce69 README.md --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/README.md Thu Aug 04 09:40:23 2016 +0100 @@ -0,0 +1,32 @@ +# This Is Not the Official Python Project Repository! + +### Though it will be, some time fairly soon + +You may have read announcements that Python developers have decided to move to git. +That hasn't happened yet. + +## No Pull Requests, Please + +At present the move to Github is still being planned, and so pull requests +to this repository will not be actioned. We try to inform people of this by responding to +pull requests, but the time spent doing that would really be better spent developing the +Python language! + +This site is currently a mirror of Python's official repository, which lives +at https://hg.python.org/, updated daily as a service to those who are already using +Github and find it a more convenient distribution channel. + +## Yes, Contributions Are Welcome + +The official Python source code repository is currently implemented on Mercurial. +The Python Developers' Guide is at https://docs.python.org/devguide/, and it +explains all you need you know to join the Python developers. If you are +interested in contributring then we especially recommend that you read +https://docs.python.org/devguide/#contributing. + +Thanks for taking time to visit the Python repository, and for yout interest in Python. + +----------------------------------------------------------------------- + +This file has been added to assist during the Mercurial-to-Github transition period, +and will be replaced by the traditional README file when the transition is complete. From weihnachtsmann97 at gmx.net Fri Aug 5 15:58:14 2016 From: weihnachtsmann97 at gmx.net (Thomas Roethenbacher) Date: Fri, 5 Aug 2016 21:58:14 +0200 Subject: [docs] Redundancy in Docs Message-ID: An HTML attachment was scrubbed... URL: From report at bugs.python.org Sat Aug 6 16:36:11 2016 From: report at bugs.python.org (Sworddragon) Date: Sat, 06 Aug 2016 20:36:11 +0000 Subject: [docs] [issue23105] os.O_SHLOCK and os.O_EXLOCK are not available on Linux In-Reply-To: <1419345535.42.0.312768269587.issue23105@psf.upfronthosting.co.za> Message-ID: <1470515771.25.0.304981488973.issue23105@psf.upfronthosting.co.za> Sworddragon added the comment: If we decide to word it this way eventually the sentence for "Windows only" needs to be updated too. Not sure about the other sentences as they sound a bit if they would guarantee what they say. Maybe somebody else knows more. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 6 16:48:25 2016 From: report at bugs.python.org (Roundup Robot) Date: Sat, 06 Aug 2016 20:48:25 +0000 Subject: [docs] [issue27688] Expand documentation about Any in the typing module In-Reply-To: <1470368224.56.0.159287783102.issue27688@psf.upfronthosting.co.za> Message-ID: <20160806204822.10718.42483.097D85AE@psf.io> Roundup Robot added the comment: New changeset cbcab1fb1b8a by Guido van Rossum in branch '3.5': Better docs for typing.Any by Michael Lee. Fixes issue #27688. https://hg.python.org/cpython/rev/cbcab1fb1b8a New changeset f60e16663f6e by Guido van Rossum in branch 'default': Better docs for typing.Any by Michael Lee. Fixes issue #27688. (Merge 3.5->3.6) https://hg.python.org/cpython/rev/f60e16663f6e ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 6 16:48:57 2016 From: report at bugs.python.org (Guido van Rossum) Date: Sat, 06 Aug 2016 20:48:57 +0000 Subject: [docs] [issue27688] Expand documentation about Any in the typing module In-Reply-To: <1470368224.56.0.159287783102.issue27688@psf.upfronthosting.co.za> Message-ID: <1470516537.65.0.137891030387.issue27688@psf.upfronthosting.co.za> Changes by Guido van Rossum : ---------- resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 7 00:18:46 2016 From: report at bugs.python.org (Martin Blais) Date: Sun, 07 Aug 2016 04:18:46 +0000 Subject: [docs] [issue24278] Docs on Parsing arguments should say something about mem mgmt for formatters returning C strings In-Reply-To: <1432481258.46.0.49462668629.issue24278@psf.upfronthosting.co.za> Message-ID: <1470543525.82.0.519949524756.issue24278@psf.upfronthosting.co.za> Martin Blais added the comment: Thank you Martin! ---------- _______________________________________ Python tracker _______________________________________ From georg at python.org Sun Aug 7 02:38:24 2016 From: georg at python.org (Georg Brandl) Date: Sun, 7 Aug 2016 08:38:24 +0200 Subject: [docs] Your print statement in the tutorial is misisng parethesis In-Reply-To: <030CA89F208D374486F026F538D16EDB6AE52B93@ONWATER52M.ad.onsemi.com> References: <030CA89F208D374486F026F538D16EDB6AE52B93@ONWATER52M.ad.onsemi.com> Message-ID: <15319990-59b3-78b4-f102-bee7279ae052@python.org> On 08/05/2016 03:37 AM, Perry Rothenbaum wrote: > I am learning Python 3.5. I?m following your examples in section 3 ?An > informal introduction to Python? tutorial. The ?print? statement is shown > without parenthesis in the tutorial and in Python 3.5 it only works with > parenthesis. In fact, if I try to type it as you have it shown, I get an error > and am being told to add parenthesis. When I add parenthesis it works. Hi Perry, please take care which version of the tutorial you're reading: there are separate versions for Python 2 (where "print" is a statement that doesn't require parens) and Python 3 (where it does, as you noticed). The links are https://docs.python.org/2/tutorial/ and https://docs.python.org/3/tutorial/ cheers, Georg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From report at bugs.python.org Sun Aug 7 03:32:49 2016 From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=) Date: Sun, 07 Aug 2016 07:32:49 +0000 Subject: [docs] [issue23105] os.O_SHLOCK and os.O_EXLOCK are not available on Linux In-Reply-To: <1419345535.42.0.312768269587.issue23105@psf.upfronthosting.co.za> Message-ID: <1470555169.06.0.683930545007.issue23105@psf.upfronthosting.co.za> St?phane Wirtel added the comment: Which sentence with "Windows only" ? Thanks ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 7 03:39:06 2016 From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=) Date: Sun, 07 Aug 2016 07:39:06 +0000 Subject: [docs] [issue12946] PyModule_GetDict() claims it can never fail, but it can In-Reply-To: <1315585192.34.0.742122652176.issue12946@psf.upfronthosting.co.za> Message-ID: <1470555546.3.0.75802462617.issue12946@psf.upfronthosting.co.za> St?phane Wirtel added the comment: you can merge the patch. ---------- nosy: +matrixise _______________________________________ Python tracker _______________________________________ From stephane at wirtel.be Sun Aug 7 03:40:06 2016 From: stephane at wirtel.be (stephane at wirtel.be) Date: Sun, 07 Aug 2016 07:40:06 -0000 Subject: [docs] PyModule_GetDict() claims it can never fail, but it can (issue 12946) Message-ID: <20160807074006.22036.72437@psf.upfronthosting.co.za> http://bugs.python.org/review/12946/diff/18078/Doc/c-api/module.rst File Doc/c-api/module.rst (right): http://bugs.python.org/review/12946/diff/18078/Doc/c-api/module.rst#newcode64 Doc/c-api/module.rst:64: :exc:`SystemError` is raised and *NULL* is returned. ok in this case, sorry, I was on my phone and not on my laptop for the review. thanks for the copy/paste. I have checked the code. On 2016/08/06 17:34:30, berkerpeksag wrote: > On 2016/08/06 15:47:10, matrixise wrote: > > The assert will raise a SystemError ? > > No, the following branch will raise SystemError: > > if (!PyModule_Check(m)) { > PyErr_BadInternalCall(); > return NULL; > } > > I added the assert statement as a sanity check. Done. http://bugs.python.org/review/12946/ From report at bugs.python.org Sun Aug 7 17:02:29 2016 From: report at bugs.python.org (Terry J. Reedy) Date: Sun, 07 Aug 2016 21:02:29 +0000 Subject: [docs] [issue27705] Updating old C:/Windows/System32/ucrtbased.dll Message-ID: <1470603749.52.0.375133152623.issue27705@psf.upfronthosting.co.za> New submission from Terry J. Reedy: This is a continuation of msg269741 from #26624, summarizing how to resolve this message. C:\WINDOWS\SYSTEM32\ucrtbased.dll is version 10.0.10240.16384 WARN: ucrtbased contains known issues. Please update Visual Studio or the Windows SDK. See: http://bugs.python.org/issue26624 F:\Python\dev\36\PCbuild\python.vcxproj(91,5): warning MSB3073: The command ""F:\Python\dev\36\PCBuild\win32\python_d.exe" "F:\Python\dev\36\PC\validate_ucrtbase.py" ucrtbased" exited with code 1. Merely updating Visual Studio is not enough. One must update the Windows SDK either directly or while updating Visual Studio by making sure that the new SDK is requested under Features. [X] Windows and Web Development [X] Universal Windows App Development Tools [X] Tools (1.4.1) and Windows 10 SDK (10.0.14393) (Versions and even the menu may change in the future.) The best way to update Visual Studio is probably to uninstall it first via Control Panel / Programs and Features / Microsoft Visual Studio Community 2015 (or whichever version you have). I did not. After downloading the current installer vs_community__9c4d694197656e43997d069a0ead2003.exe I just ran without uninstalling. It automatically installs in the current vs2015 directory, Instead of a clean install, it updated and ended with the same 'bad hash' message as reported in msg269741. I then went to Programs and Features and chose 'Repair'. The first time it failed because it did not like the existing Microsoft Visual C++ 2015 Redistributable (x86 or x64) files being present. With those removed, and the SDK feature checked, Repair worked and Python builds without the warning. The current SDK is not listed as 'Microsoft Windows SDK...' but as Windows Software Development Kit - Windows 10.0.14393 Steve: my suggestion is that "Please update Visual Studio or the Windows SDK." be changed to "Please update the Windows SDK, possibly by updating Visual Studio with the Windows SDK feature selected." Also change the issue number from 26624 to whatever this one gets. ---------- assignee: docs at python components: Build, Documentation, Windows messages: 272132 nosy: docs at python, paul.moore, steve.dower, terry.reedy, tim.golden, zach.ware priority: normal severity: normal stage: needs patch status: open title: Updating old C:/Windows/System32/ucrtbased.dll type: behavior versions: Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 7 19:14:22 2016 From: report at bugs.python.org (Sworddragon) Date: Sun, 07 Aug 2016 23:14:22 +0000 Subject: [docs] [issue23105] os.O_SHLOCK and os.O_EXLOCK are not available on Linux In-Reply-To: <1419345535.42.0.312768269587.issue23105@psf.upfronthosting.co.za> Message-ID: <1470611662.17.0.591025829349.issue23105@psf.upfronthosting.co.za> Sworddragon added the comment: Maybe it sounded a bit confusing but this text was not to be meant as a direct match against the documentation. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 8 02:01:57 2016 From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=) Date: Mon, 08 Aug 2016 06:01:57 +0000 Subject: [docs] [issue12276] 3.x ignores sys.tracebacklimit=0 In-Reply-To: <1307436501.83.0.59684150491.issue12276@psf.upfronthosting.co.za> Message-ID: <1470636117.62.0.402675719449.issue12276@psf.upfronthosting.co.za> Changes by St?phane Wirtel : ---------- nosy: +matrixise _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 8 02:06:07 2016 From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=) Date: Mon, 08 Aug 2016 06:06:07 +0000 Subject: [docs] [issue23746] sysconfg.is_python_build() is buggy In-Reply-To: <1427101982.73.0.589713060591.issue23746@psf.upfronthosting.co.za> Message-ID: <1470636367.64.0.802599561217.issue23746@psf.upfronthosting.co.za> Changes by St?phane Wirtel : ---------- nosy: +matrixise _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 8 02:08:36 2016 From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=) Date: Mon, 08 Aug 2016 06:08:36 +0000 Subject: [docs] [issue24459] Mention PYTHONFAULTHANDLER in the man page In-Reply-To: <1434487895.85.0.561507121326.issue24459@psf.upfronthosting.co.za> Message-ID: <1470636516.36.0.136919933509.issue24459@psf.upfronthosting.co.za> Changes by St?phane Wirtel : ---------- nosy: +matrixise _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 8 04:31:53 2016 From: report at bugs.python.org (Oren Milman) Date: Mon, 08 Aug 2016 08:31:53 +0000 Subject: [docs] [issue20842] pkgutil docs should reference glossary terms not PEP 302 In-Reply-To: <1393846400.67.0.723549613222.issue20842@psf.upfronthosting.co.za> Message-ID: <1470645112.91.0.961080879025.issue20842@psf.upfronthosting.co.za> Oren Milman added the comment: ImpImporter was first added in changeset 37808 (https://hg.python.org/cpython/rev/ccc0b5412799) and updated a day later in changeset 37821 (https://hg.python.org/cpython/rev/3135648026c4). Both of these commits were introduced to support PEP 302. Since then, ImpImporter remained quite the same, and was never changed to suit later relevant PEPs (e.g. PEP 420 and PEP 451). Thus, IMHO, we should go with your second option, Martin, and retain the PEP 302 reference in ImpImporter documentation. With regard to the accuracy of Python's 'finder' glossary entry, it was updated recently, in changeset 99434 (https://hg.python.org/cpython/rev/88cee7d16ccb), to suit PEP 302, PEP 420 and PEP 451, so ISTM there is no need to adjust it. ---------- _______________________________________ Python tracker _______________________________________ From arbautjc at gmail.com Sat Aug 6 18:30:04 2016 From: arbautjc at gmail.com (Jean-Claude Arbaut) Date: Sun, 7 Aug 2016 00:30:04 +0200 Subject: [docs] missing downloads for Python 3.4.4 documentation Message-ID: Hello, This is not really a documentation bug, but I didn't know where to ask. The download files for the Python 3.4.4 documentation are missing, both from the old links I kept (https://docs.python.org/3.4/archives/python-3.4.4-docs-html.zip or maybe https://docs.python.org/3/archives/python-3.4.4-docs-html.zip) and from the recently changed links on the site (no 3.4.4 folder at https://www.python.org/ftp/python/doc/). I don't know if they have been removed on purpose, however it's strange to have dead links on the site. And all previous downloads seem to be available at https://www.python.org/ftp/python/doc/. Are they lost for good ? Best regards, Jean-Claude Arbaut From huitikho at hotmail.com Sun Aug 7 02:24:26 2016 From: huitikho at hotmail.com (Hui Tik Ho) Date: Sun, 7 Aug 2016 06:24:26 +0000 Subject: [docs] About the calculation of Technical Analysis (ie. RSI, MACD) Message-ID: Dear Sir/Madam, If I wish to download Python for Financial Calculation, ie. Technical Indicators (MACD, RSI), in which documents can I refer to ? Thanks & Regards ! Hui Tik Ho -------------- next part -------------- An HTML attachment was scrubbed... URL: From pwb at twitoftheyear.com Sun Aug 7 17:17:33 2016 From: pwb at twitoftheyear.com (pwb at twitoftheyear.com) Date: Sun, 7 Aug 2016 17:17:33 -0400 Subject: [docs] Broken links for documentation download Message-ID: on the page https://docs.python.org/3.4/download.html are several links for downloading Python 3.4 documentation. For ALL of the links, I am getting 404 Error (Not Found) ? as of today, 8/7/2016. -------------- next part -------------- An HTML attachment was scrubbed... URL: From report at bugs.python.org Mon Aug 8 05:42:41 2016 From: report at bugs.python.org (Ram Vallury) Date: Mon, 08 Aug 2016 09:42:41 +0000 Subject: [docs] [issue26209] TypeError in smtpd module with string arguments In-Reply-To: <1453840478.59.0.371405366995.issue26209@psf.upfronthosting.co.za> Message-ID: <1470649361.08.0.9681418577.issue26209@psf.upfronthosting.co.za> Ram Vallury added the comment: Updated the documentation of smtpd. https://docs.python.org/3/library/smtpd.html#smtpserver-objects * this is my first patch, please revert back to me or make learn if I do any mistake* ---------- keywords: +patch nosy: +rvallury Added file: http://bugs.python.org/file44045/smtpd_doc_updated.patch _______________________________________ Python tracker _______________________________________ From stephane at wirtel.be Mon Aug 8 05:48:16 2016 From: stephane at wirtel.be (stephane at wirtel.be) Date: Mon, 08 Aug 2016 09:48:16 -0000 Subject: [docs] TypeError in smtpd module with string arguments (issue 26209) Message-ID: <20160808094816.5373.96385@psf.upfronthosting.co.za> http://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst File Doc/library/smtpd.rst (right): http://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst#newcode36 Doc/library/smtpd.rst:36: the parameters localaddr and remoteaddr should a tuple in form ``("host",portnumber)``, should be a tuple http://bugs.python.org/review/26209/ From ghost.adh at runbox.com Mon Aug 8 05:49:18 2016 From: ghost.adh at runbox.com (ghost.adh at runbox.com) Date: Mon, 08 Aug 2016 09:49:18 -0000 Subject: [docs] TypeError in smtpd module with string arguments (issue 26209) Message-ID: <20160808094918.5318.53572@psf.upfronthosting.co.za> https://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst File Doc/library/smtpd.rst (right): https://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst#newcode35 Doc/library/smtpd.rst:35: *localaddr*. It will treat *remoteaddr* as an upstream SMTP relayer. Both Two spaces between the sentences are required. https://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst#newcode36 Doc/library/smtpd.rst:36: the parameters localaddr and remoteaddr should a tuple in form ``("host",portnumber)``, Please make sure that each line fits into 80 columns. https://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst#newcode36 Doc/library/smtpd.rst:36: the parameters localaddr and remoteaddr should a tuple in form ``("host",portnumber)``, How about this wording: "Both *localaddr* and *remoteaddr* should be a two-tuple in the form ``('host', portnumber)``... https://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst#newcode37 Doc/library/smtpd.rst:37: where *host* is a valid IP/FQDN. It inherits from :class:`asyncore.dispatcher`, Only single space between words. https://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst#newcode37 Doc/library/smtpd.rst:37: where *host* is a valid IP/FQDN. It inherits from :class:`asyncore.dispatcher`, I'd suggest replacing "It" with "The object". https://bugs.python.org/review/26209/ From report at bugs.python.org Mon Aug 8 06:06:13 2016 From: report at bugs.python.org (Roundup Robot) Date: Mon, 08 Aug 2016 10:06:13 +0000 Subject: [docs] [issue23322] parser module docs missing second example In-Reply-To: <1422257477.04.0.712021667077.issue23322@psf.upfronthosting.co.za> Message-ID: <20160808100610.108680.54111.69867AA1@psf.io> Roundup Robot added the comment: New changeset b479e74f7706 by Berker Peksag in branch '3.5': Issue #23322: Remove outdated reference to an example in parser docs https://hg.python.org/cpython/rev/b479e74f7706 New changeset 099fd7954941 by Berker Peksag in branch 'default': Issue #23322: Merge from 3.5 https://hg.python.org/cpython/rev/099fd7954941 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 8 06:06:50 2016 From: report at bugs.python.org (Berker Peksag) Date: Mon, 08 Aug 2016 10:06:50 +0000 Subject: [docs] [issue23322] parser module docs missing second example In-Reply-To: <1422257477.04.0.712021667077.issue23322@psf.upfronthosting.co.za> Message-ID: <1470650810.87.0.825466768969.issue23322@psf.upfronthosting.co.za> Berker Peksag added the comment: Thanks, Sahil. ---------- resolution: -> fixed stage: needs patch -> resolved status: open -> closed type: -> behavior versions: +Python 3.6 -Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 8 06:42:27 2016 From: report at bugs.python.org (Ram Vallury) Date: Mon, 08 Aug 2016 10:42:27 +0000 Subject: [docs] [issue26209] TypeError in smtpd module with string arguments In-Reply-To: <1453840478.59.0.371405366995.issue26209@psf.upfronthosting.co.za> Message-ID: <1470652947.49.0.594516790218.issue26209@psf.upfronthosting.co.za> Ram Vallury added the comment: Submitting patch 2 for smtpd doc changes ---------- Added file: http://bugs.python.org/file44047/smtpd_doc_updated_2.patch _______________________________________ Python tracker _______________________________________ From ram.pydev at gmail.com Mon Aug 8 06:44:24 2016 From: ram.pydev at gmail.com (ram.pydev at gmail.com) Date: Mon, 08 Aug 2016 10:44:24 -0000 Subject: [docs] TypeError in smtpd module with string arguments (issue 26209) Message-ID: <20160808104424.5373.40043@psf.upfronthosting.co.za> http://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst File Doc/library/smtpd.rst (right): http://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst#newcode35 Doc/library/smtpd.rst:35: *localaddr*. It will treat *remoteaddr* as an upstream SMTP relayer. Both On 2016/08/08 11:49:18, SilentGhost wrote: > Two spaces between the sentences are required. Done. http://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst#newcode35 Doc/library/smtpd.rst:35: *localaddr*. It will treat *remoteaddr* as an upstream SMTP relayer. Both On 2016/08/08 11:49:18, SilentGhost wrote: > Two spaces between the sentences are required. Done. http://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst#newcode36 Doc/library/smtpd.rst:36: the parameters localaddr and remoteaddr should a tuple in form ``("host",portnumber)``, On 2016/08/08 11:48:16, matrixise wrote: > should be a tuple Done. http://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst#newcode36 Doc/library/smtpd.rst:36: the parameters localaddr and remoteaddr should a tuple in form ``("host",portnumber)``, On 2016/08/08 11:49:18, SilentGhost wrote: > Please make sure that each line fits into 80 columns. Done. http://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst#newcode36 Doc/library/smtpd.rst:36: the parameters localaddr and remoteaddr should a tuple in form ``("host",portnumber)``, On 2016/08/08 11:49:18, SilentGhost wrote: > How about this wording: "Both *localaddr* and *remoteaddr* should be a two-tuple > in the form ``('host', portnumber)``... mentioning two-tuple would be confusing added this way "Both *localaddr* and *remoteaddr* should be a tuple... http://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst#newcode37 Doc/library/smtpd.rst:37: where *host* is a valid IP/FQDN. It inherits from :class:`asyncore.dispatcher`, On 2016/08/08 11:49:18, SilentGhost wrote: > Only single space between words. Done. http://bugs.python.org/review/26209/diff/18091/Doc/library/smtpd.rst#newcode37 Doc/library/smtpd.rst:37: where *host* is a valid IP/FQDN. It inherits from :class:`asyncore.dispatcher`, On 2016/08/08 11:49:18, SilentGhost wrote: > I'd suggest replacing "It" with "The object". Done. http://bugs.python.org/review/26209/ From report at bugs.python.org Mon Aug 8 06:45:41 2016 From: report at bugs.python.org (Berker Peksag) Date: Mon, 08 Aug 2016 10:45:41 +0000 Subject: [docs] [issue26209] TypeError in smtpd module with string arguments In-Reply-To: <1453840478.59.0.371405366995.issue26209@psf.upfronthosting.co.za> Message-ID: <1470653141.03.0.561438464589.issue26209@psf.upfronthosting.co.za> Changes by Berker Peksag : ---------- stage: needs patch -> patch review _______________________________________ Python tracker _______________________________________ From ghost.adh at runbox.com Mon Aug 8 08:29:08 2016 From: ghost.adh at runbox.com (ghost.adh at runbox.com) Date: Mon, 08 Aug 2016 12:29:08 -0000 Subject: [docs] TypeError in smtpd module with string arguments (issue 26209) Message-ID: <20160808122908.5318.83952@psf.upfronthosting.co.za> https://bugs.python.org/review/26209/diff/18092/Doc/library/smtpd.rst File Doc/library/smtpd.rst (right): https://bugs.python.org/review/26209/diff/18092/Doc/library/smtpd.rst#newcode36 Doc/library/smtpd.rst:36: the parameters *localaddr* and *remoteaddr* should be a tuple in form ``("host",portnumber)``, The lines are still wider than 80 columns. Also, please add a space before word portnumber. https://bugs.python.org/review/26209/ From report at bugs.python.org Mon Aug 8 10:39:14 2016 From: report at bugs.python.org (R. David Murray) Date: Mon, 08 Aug 2016 14:39:14 +0000 Subject: [docs] [issue20004] csv.DictReader classic class has a property with setter In-Reply-To: <1387278593.92.0.0717442259637.issue20004@psf.upfronthosting.co.za> Message-ID: <1470667154.09.0.513682239766.issue20004@psf.upfronthosting.co.za> R. David Murray added the comment: I don't believe it was ever committed to 3.x, nor do I see it there. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 8 10:42:47 2016 From: report at bugs.python.org (Mathieu Dupuy) Date: Mon, 08 Aug 2016 14:42:47 +0000 Subject: [docs] [issue20004] csv.DictReader classic class has a property with setter In-Reply-To: <1470667154.09.0.513682239766.issue20004@psf.upfronthosting.co.za> Message-ID: Mathieu Dupuy added the comment: Yeah, it turned out I was actually browsing Python 2.7 sources. My bad. 2016-08-08 16:39 GMT+02:00 R. David Murray : > > R. David Murray added the comment: > > I don't believe it was ever committed to 3.x, nor do I see it there. > > ---------- > > _______________________________________ > Python tracker > > _______________________________________ ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 8 12:23:52 2016 From: report at bugs.python.org (Xiang Zhang) Date: Mon, 08 Aug 2016 16:23:52 +0000 Subject: [docs] [issue27712] Tiny typos in import.rst Message-ID: <1470673432.73.0.0437634567698.issue27712@psf.upfronthosting.co.za> Changes by Xiang Zhang : ---------- assignee: docs at python components: Documentation files: import_doc.patch keywords: patch nosy: docs at python, xiang.zhang priority: normal severity: normal status: open title: Tiny typos in import.rst type: behavior versions: Python 3.6 Added file: http://bugs.python.org/file44050/import_doc.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 05:45:00 2016 From: report at bugs.python.org (Ram Vallury) Date: Tue, 09 Aug 2016 09:45:00 +0000 Subject: [docs] [issue26209] TypeError in smtpd module with string arguments In-Reply-To: <1453840478.59.0.371405366995.issue26209@psf.upfronthosting.co.za> Message-ID: <1470735900.07.0.238881821809.issue26209@psf.upfronthosting.co.za> Ram Vallury added the comment: added space before word portnumber. column space adjusted ---------- Added file: http://bugs.python.org/file44055/smtpd_doc_updated_3.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 08:29:35 2016 From: report at bugs.python.org (Eyal Mor) Date: Tue, 09 Aug 2016 12:29:35 +0000 Subject: [docs] [issue27717] sqlite documentation bug Message-ID: <1470745775.08.0.0704550754852.issue27717@psf.upfronthosting.co.za> New submission from Eyal Mor: In the SQlite module documentation there a code section showing how to securely use the sqlite.execute method. The problem with this code section is that just from a glance, without reading the paragraph before, or the comments in the section, users could use the insecure version. It would be better if only a secure example would be in the code section. https://docs.python.org/2/library/sqlite3.html Section: # Never do this -- insecure! symbol = 'RHAT' c.execute("SELECT * FROM stocks WHERE symbol = '%s'" % symbol) # Do this instead t = ('RHAT',) c.execute('SELECT * FROM stocks WHERE symbol=?', t) print c.fetchone() # Larger example that inserts many records at a time purchases = [('2006-03-28', 'BUY', 'IBM', 1000, 45.00), ('2006-04-05', 'BUY', 'MSFT', 1000, 72.00), ('2006-04-06', 'SELL', 'IBM', 500, 53.00), ] c.executemany('INSERT INTO stocks VALUES (?,?,?,?,?)', purchases) ---------- assignee: docs at python components: Documentation files: Screen Shot 2016-08-09 at 3.28.05 PM.png messages: 272238 nosy: Eyal Mor, docs at python priority: normal severity: normal status: open title: sqlite documentation bug type: security versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6 Added file: http://bugs.python.org/file44056/Screen Shot 2016-08-09 at 3.28.05 PM.png _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 08:41:19 2016 From: report at bugs.python.org (Gabriel Pettier (Tshirtman)) Date: Tue, 09 Aug 2016 12:41:19 +0000 Subject: [docs] [issue27718] help('signal') incomplete (e.g: signal.signal not visible) Message-ID: <1470746479.88.0.0919609545752.issue27718@psf.upfronthosting.co.za> New submission from Gabriel Pettier (Tshirtman): Up to apparently python 3.5, using help('signal') used to show the 'signal.signal' function among others, now it's not in the list, while of course help('signal.signal') does work, it was reported to me to still be the case in 3.6a1. ---------- assignee: docs at python components: Documentation messages: 272240 nosy: Gabriel Pettier (Tshirtman), docs at python priority: normal severity: normal status: open title: help('signal') incomplete (e.g: signal.signal not visible) type: behavior versions: Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 09:33:07 2016 From: report at bugs.python.org (Serhiy Storchaka) Date: Tue, 09 Aug 2016 13:33:07 +0000 Subject: [docs] [issue27718] help('signal') incomplete (e.g: signal.signal not visible) In-Reply-To: <1470746479.88.0.0919609545752.issue27718@psf.upfronthosting.co.za> Message-ID: <1470749587.28.0.643021263657.issue27718@psf.upfronthosting.co.za> Changes by Serhiy Storchaka : ---------- nosy: +ethan.furman, giampaolo.rodola _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 09:39:59 2016 From: report at bugs.python.org (R. David Murray) Date: Tue, 09 Aug 2016 13:39:59 +0000 Subject: [docs] [issue27717] sqlite documentation bug In-Reply-To: <1470745775.08.0.0704550754852.issue27717@psf.upfronthosting.co.za> Message-ID: <1470749999.7.0.999570194389.issue27717@psf.upfronthosting.co.za> R. David Murray added the comment: I think it is pretty hard to miss "Never do this" when reading the code section. That said, I don't have a strong objection to changing it. I've reduced the versions field to those branches this might get changed in, as is our standard practice with the versions field. Nor is this a security issue in our usage of that type, so I've changed the type to behavior. ---------- nosy: +r.david.murray type: security -> behavior versions: -Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 09:47:09 2016 From: report at bugs.python.org (R. David Murray) Date: Tue, 09 Aug 2016 13:47:09 +0000 Subject: [docs] [issue27718] help('signal') incomplete (e.g: signal.signal not visible) In-Reply-To: <1470746479.88.0.0919609545752.issue27718@psf.upfronthosting.co.za> Message-ID: <1470750429.78.0.212105492563.issue27718@psf.upfronthosting.co.za> R. David Murray added the comment: The conversion of the module from a pure python module to a mixed module apparently caused a number of changes to the pydoc output. This should be addressed to make the pydoc output complete, even if it still different in detail. ---------- nosy: +r.david.murray _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 12:08:47 2016 From: report at bugs.python.org (Ben Hoyt) Date: Tue, 09 Aug 2016 16:08:47 +0000 Subject: [docs] [issue27719] Misleading note about "args" attribute in "User-defined Exceptions" section of tutorial Message-ID: <1470758926.96.0.219997040874.issue27719@psf.upfronthosting.co.za> New submission from Ben Hoyt: In the official tutorial in the "User-defined Exceptions" section (https://docs.python.org/3.5/tutorial/errors.html#user-defined-exceptions) there's a note about a user-defined Exception subclass as follows: "In this example, the default __init__() of Exception has been overridden. The new behavior simply creates the value attribute. This replaces the default behavior of creating the args attribute." That last sentence is wrong: it used to be that way (it is in Python 2.x and I believe in Python pre 3.2), but now the implementation of BaseException.__new__ now sets args, so even when you override __init__ and don't call super() args is set. I think that's what you want, so I'm putting this down to a documentation bug. I think the sentence "This replaces the default behavior of creating the args attribute." should simply be removed (BaseException.__init__ basically does nothing now). This change happened for Python 3.3 and was backported to Python 3.2. See also: * The relevant part of BaseException.__new__ in the CPython codebase: https://github.com/python/cpython/blob/601ee5fab5df81a25611da0667030de531c1cda9/Objects/exceptions.c#L44-L48 * The issue where this behaviour was changed: http://bugs.python.org/issue1692335 * The commit where it was changed: https://hg.python.org/cpython/rev/68e2690a471d (on GitHub at https://github.com/python/cpython/commit/a71a87e695b05a67bd22c6ac74311b1f56f3932e) * You can repro this and confirm that "args" is definitely set with the attached script: $ python exception_args_test.py sys.version_info(major=3, minor=5, micro=2, releaselevel='final', serial=0) Error args: ('error!',) ---------- assignee: docs at python components: Documentation files: exception_args_test.py messages: 272256 nosy: benhoyt, docs at python, georg.brandl, sbt priority: normal severity: normal status: open title: Misleading note about "args" attribute in "User-defined Exceptions" section of tutorial versions: Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6 Added file: http://bugs.python.org/file44058/exception_args_test.py _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 12:10:56 2016 From: report at bugs.python.org (Ben Hoyt) Date: Tue, 09 Aug 2016 16:10:56 +0000 Subject: [docs] [issue27719] Misleading note about "args" attribute in "User-defined Exceptions" section of tutorial In-Reply-To: <1470758926.96.0.219997040874.issue27719@psf.upfronthosting.co.za> Message-ID: <1470759056.24.0.483605402133.issue27719@psf.upfronthosting.co.za> Ben Hoyt added the comment: Note that I added the committers from issue 1692335 to the Nosy List -- probably overzealous and probably not the folks who maintain the docs, but oh well. :-) ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 12:59:04 2016 From: report at bugs.python.org (Brett Cannon) Date: Tue, 09 Aug 2016 16:59:04 +0000 Subject: [docs] [issue27712] Tiny typos in import.rst Message-ID: <1470761944.9.0.637786458858.issue27712@psf.upfronthosting.co.za> Changes by Brett Cannon : ---------- assignee: docs at python -> brett.cannon nosy: +brett.cannon _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 13:25:19 2016 From: report at bugs.python.org (Antti Haapala) Date: Tue, 09 Aug 2016 17:25:19 +0000 Subject: [docs] [issue27720] decimal.Context.to_eng_string wrong docstring Message-ID: <1470763519.71.0.509753850108.issue27720@psf.upfronthosting.co.za> New submission from Antti Haapala: https://docs.python.org/3/library/decimal.html#decimal.Context.to_eng_string The docstring for `Context.to_eng_string` says "Converts a number to a string, using scientific notation.", which is, less extra comma, exactly the docstring for `Context.to_sci_string`. It should probably say "using engineering notation". Additionally, docstring for Decimal.to_eng_string uses the term "an engineering-type string", which no one uses outside the said docstring. It should probably also say "Convert to a string using engineering notation." ---------- assignee: docs at python components: Documentation messages: 272259 nosy: docs at python, ztane priority: normal severity: normal status: open title: decimal.Context.to_eng_string wrong docstring _______________________________________ Python tracker _______________________________________ From mtstorm2 at gmail.com Mon Aug 8 10:47:30 2016 From: mtstorm2 at gmail.com (Makoto T) Date: Mon, 8 Aug 2016 23:47:30 +0900 Subject: [docs] Japanese Documents Link Problem Message-ID: Hi, I'm looking for Japanese Documents which can be downloaded, but the following links seem to be dead. URL:https://docs.python.org/ftp/python/doc/3.5.1/python-3.5.1-docs-html.zip ( In the page... http://docs.python.jp/3/download.html) Thank you for your help. Sincerely, M. Tsutsumi -------------- next part -------------- An HTML attachment was scrubbed... URL: From o.a.gromyak at gmail.com Tue Aug 9 16:24:48 2016 From: o.a.gromyak at gmail.com (Oleg Gromyak) Date: Tue, 9 Aug 2016 23:24:48 +0300 Subject: [docs] [Low priority] [Not a bug] Small fix in logging module documentation Message-ID: Hello, I've found some difference about default *delay parameter in logging.handlers* (both 2 and 3 versions) https://docs.python.org/3/library/logging.handlers.html BaseRotatingHandler, TimedRotatingFileHandler use *delay=False,* while RotatingFileHandler uses *delay=0*. However, *delay is considered is bool* (RotatingFileHandler says: "If delay is true, then file opening is deferred until the first call to emit()."), so it might be better to *change delay=0 to delay=False* in *RotatingFileHandler*. So documentation style won't be different for that logging handlers. Thank you for attention and time, sorry for disturbing about such non-important issues. -- ? ???????, ???? ????'?? With best regards, Oleg Gromyak -------------- next part -------------- An HTML attachment was scrubbed... URL: From zachary.ware+pydocs at gmail.com Tue Aug 9 17:31:54 2016 From: zachary.ware+pydocs at gmail.com (Zachary Ware) Date: Tue, 9 Aug 2016 16:31:54 -0500 Subject: [docs] [Low priority] [Not a bug] Small fix in logging module documentation In-Reply-To: References: Message-ID: Hi Oleg, On Tue, Aug 9, 2016 at 3:24 PM, Oleg Gromyak wrote: > Hello, I've found some difference about default delay parameter in > logging.handlers > (both 2 and 3 versions) > https://docs.python.org/3/library/logging.handlers.html > > > BaseRotatingHandler, TimedRotatingFileHandler use delay=False, while > RotatingFileHandler uses delay=0. > > However, delay is considered is bool (RotatingFileHandler says: "If delay is > true, then file opening is deferred until the first call to emit()."), so it > might be better to change delay=0 to delay=False in RotatingFileHandler. > So documentation style won't be different for that logging handlers. > > Thank you for attention and time, sorry for disturbing about such > non-important issues. Thanks for the report! I've fixed this in the docs for 3.5 (along with the signature of WatchedFileHandler, which just used an older style for the optional arguments) since the actual default value in the code is False rather than 0. I didn't change the 2.7 docs, because the actual default in 2.7 is 0 rather than False. -- Zach From report at bugs.python.org Tue Aug 9 18:02:53 2016 From: report at bugs.python.org (Ankur Dedania) Date: Tue, 09 Aug 2016 22:02:53 +0000 Subject: [docs] [issue27722] Path.touch's keyword argument mode documented incorrectly Message-ID: <1470780173.7.0.896294950108.issue27722@psf.upfronthosting.co.za> New submission from Ankur Dedania: Path.touch's keyword argument mode documented incorrectly. In the documents, it shows keyword argument mode defaulted to 0o777, however within the code it is set to 0o666. ---------- assignee: docs at python components: Documentation messages: 272269 nosy: AnkurDedania, docs at python priority: normal severity: normal status: open title: Path.touch's keyword argument mode documented incorrectly type: behavior versions: Python 3.4, Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 18:11:11 2016 From: report at bugs.python.org (Roundup Robot) Date: Tue, 09 Aug 2016 22:11:11 +0000 Subject: [docs] [issue27722] Path.touch's keyword argument mode documented incorrectly In-Reply-To: <1470780173.7.0.896294950108.issue27722@psf.upfronthosting.co.za> Message-ID: <20160809221108.3475.21631.3C063256@psf.io> Roundup Robot added the comment: New changeset 773bc9a3172d by Zachary Ware in branch '3.5': Issue #27722: Fix default for touch method's 'mode' argument https://hg.python.org/cpython/rev/773bc9a3172d New changeset 763d98f0a105 by Zachary Ware in branch 'default': Closes #27722: Merge with 3.5 https://hg.python.org/cpython/rev/763d98f0a105 ---------- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 18:11:27 2016 From: report at bugs.python.org (Zachary Ware) Date: Tue, 09 Aug 2016 22:11:27 +0000 Subject: [docs] [issue27722] Path.touch's keyword argument mode documented incorrectly In-Reply-To: <1470780173.7.0.896294950108.issue27722@psf.upfronthosting.co.za> Message-ID: <1470780687.63.0.738703579219.issue27722@psf.upfronthosting.co.za> Zachary Ware added the comment: Thanks for the report! ---------- nosy: +zach.ware versions: -Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 18:40:13 2016 From: report at bugs.python.org (Roundup Robot) Date: Tue, 09 Aug 2016 22:40:13 +0000 Subject: [docs] [issue27205] Failing doctests in Library/collections.rst In-Reply-To: <1465000020.63.0.799580126218.issue27205@psf.upfronthosting.co.za> Message-ID: <20160809224010.3384.41752.72D92E93@psf.io> Roundup Robot added the comment: New changeset e399930d14f0 by Zachary Ware in branch '2.7': Issue #27205: Fix doctests in Doc/library/collections.rst https://hg.python.org/cpython/rev/e399930d14f0 New changeset 0d95e47cfe3e by Zachary Ware in branch '3.5': Issue #27205: Fix doctests in Doc/library/collections.rst. https://hg.python.org/cpython/rev/0d95e47cfe3e New changeset 6817b8112f6e by Zachary Ware in branch 'default': Closes #27205: Merge with 3.5 https://hg.python.org/cpython/rev/6817b8112f6e ---------- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 18:40:36 2016 From: report at bugs.python.org (Zachary Ware) Date: Tue, 09 Aug 2016 22:40:36 +0000 Subject: [docs] [issue27205] Failing doctests in Library/collections.rst In-Reply-To: <1465000020.63.0.799580126218.issue27205@psf.upfronthosting.co.za> Message-ID: <1470782436.06.0.456612627625.issue27205@psf.upfronthosting.co.za> Zachary Ware added the comment: Thanks for the patch! ---------- assignee: docs at python -> zach.ware nosy: +zach.ware type: -> behavior versions: +Python 2.7, Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 18:45:54 2016 From: report at bugs.python.org (Roundup Robot) Date: Tue, 09 Aug 2016 22:45:54 +0000 Subject: [docs] [issue27206] Failing doctests in Doc/tutorial/ In-Reply-To: <1465000511.18.0.692311972692.issue27206@psf.upfronthosting.co.za> Message-ID: <20160809224551.7956.4097.EE5CB9E1@psf.io> Roundup Robot added the comment: New changeset 8b7efeeefa50 by Zachary Ware in branch '3.5': Issue #27206: Fix doctests in Doc/tutorial. https://hg.python.org/cpython/rev/8b7efeeefa50 New changeset 61d7aeb6aa1b by Zachary Ware in branch 'default': Closes #27206: Merge with 3.5 https://hg.python.org/cpython/rev/61d7aeb6aa1b ---------- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 18:46:19 2016 From: report at bugs.python.org (Zachary Ware) Date: Tue, 09 Aug 2016 22:46:19 +0000 Subject: [docs] [issue27206] Failing doctests in Doc/tutorial/ In-Reply-To: <1465000511.18.0.692311972692.issue27206@psf.upfronthosting.co.za> Message-ID: <1470782779.49.0.634908652743.issue27206@psf.upfronthosting.co.za> Zachary Ware added the comment: Thanks for the patch! ---------- assignee: docs at python -> zach.ware nosy: +zach.ware type: -> behavior versions: +Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 19:34:31 2016 From: report at bugs.python.org (Berker Peksag) Date: Tue, 09 Aug 2016 23:34:31 +0000 Subject: [docs] [issue19489] move quick search box above TOC In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za> Message-ID: <1470785671.39.0.169387408193.issue19489@psf.upfronthosting.co.za> Berker Peksag added the comment: This looks pretty good to me, thanks! I have two minor suggestions: 1. It would be better to make "Quick search" a placeholder: 2.
  • will add an unnecessary border in search page. I'd change it to Also, +form.inline-search input { + display: inline; +} may cause weird compatibility problems in some (old?) browsers. We can change it to use display: inline-block instead. Is there a way to send this to upstream Sphinx? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 19:49:20 2016 From: report at bugs.python.org (Berker Peksag) Date: Tue, 09 Aug 2016 23:49:20 +0000 Subject: [docs] [issue21018] [patch] added missing documentation about escaping characters for configparser In-Reply-To: <1395464420.76.0.68706986346.issue21018@psf.upfronthosting.co.za> Message-ID: <1470786560.1.0.30177566002.issue21018@psf.upfronthosting.co.za> Berker Peksag added the comment: Thanks for the patch. Two things: * We want to keep docstrings short so could you please revert the changes in Lib/configparser.py? * It would be better to just add an example of escaping these characters in the "Interpolation of values" section (preferably with a short comment.) ---------- nosy: +berker.peksag stage: -> patch review versions: +Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 20:09:16 2016 From: report at bugs.python.org (Berker Peksag) Date: Wed, 10 Aug 2016 00:09:16 +0000 Subject: [docs] [issue27719] Misleading note about "args" attribute in "User-defined Exceptions" section of tutorial In-Reply-To: <1470758926.96.0.219997040874.issue27719@psf.upfronthosting.co.za> Message-ID: <1470787755.97.0.122718043796.issue27719@psf.upfronthosting.co.za> Berker Peksag added the comment: Thank you for your detailed report! Would you like to propose a patch? This behavior is already tested in testAttributes in Lib/test/test_exceptions.py so we just need a documentation patch. ---------- keywords: +easy nosy: +berker.peksag stage: -> needs patch type: -> behavior versions: -Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 20:12:39 2016 From: report at bugs.python.org (Berker Peksag) Date: Wed, 10 Aug 2016 00:12:39 +0000 Subject: [docs] [issue27720] decimal.Context.to_eng_string wrong docstring In-Reply-To: <1470763519.71.0.509753850108.issue27720@psf.upfronthosting.co.za> Message-ID: <1470787959.97.0.973821600719.issue27720@psf.upfronthosting.co.za> Changes by Berker Peksag : ---------- nosy: +skrah _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 21:40:43 2016 From: report at bugs.python.org (Michael Lee) Date: Wed, 10 Aug 2016 01:40:43 +0000 Subject: [docs] [issue27723] Document typing.Text and typing.AnyStr Message-ID: <1470793243.78.0.0997445491252.issue27723@psf.upfronthosting.co.za> New submission from Michael Lee: This patch documents typing.Text and typing.AnyStr. I decided against creating a new top-level section to document Text/AnyStr mainly because it seems like how exactly str/bytes/unicode is handled by mypy and described in PEP 484 might be changing sometime in the future and didn't want to add text that would need to be changed later on -- I'm not sure if that was the right call or not. ---------- assignee: docs at python components: Documentation files: document-text-and-anystr.patch keywords: patch messages: 272286 nosy: docs at python, gvanrossum, michael0x2a priority: normal severity: normal status: open title: Document typing.Text and typing.AnyStr versions: Python 3.5, Python 3.6 Added file: http://bugs.python.org/file44062/document-text-and-anystr.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 9 23:18:40 2016 From: report at bugs.python.org (Ammar Askar) Date: Wed, 10 Aug 2016 03:18:40 +0000 Subject: [docs] [issue19489] move quick search box above TOC In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za> Message-ID: <1470799120.29.0.476704039467.issue19489@psf.upfronthosting.co.za> Ammar Askar added the comment: > 1. It would be better to make "Quick search" a placeholder Do you mean in addition to the "Quick search" text that is already on the page or do you want to remove that? Because placeholder isn't fully compatible with some older browsers http://caniuse.com/#feat=input-placeholder > 2.
  • will add an unnecessary border in search page. I'd change it to Good idea, will fix this. > may cause weird compatibility problems in some (old?) browsers. What problems are you thinking of? I think `display: inline` is the right choice here since we want the inputs to inherit the height of the header. The page renders fine on all versions of IE from my testing. Also, newer versions of sphinx come with a newer jquery that breaks compatibility with IE8 which would cause the search box to not appear anyway. >Is there a way to send this to upstream Sphinx? I don't think so, it's one of those things that make sense as a theme, which is perfect since we have our own sphinx theme anyway. ---------- Added file: http://bugs.python.org/file44064/searchbar_in_header.diff3 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 00:03:47 2016 From: report at bugs.python.org (Martin Panter) Date: Wed, 10 Aug 2016 04:03:47 +0000 Subject: [docs] [issue27712] Tiny typos in import.rst Message-ID: <1470801827.64.0.914764893779.issue27712@psf.upfronthosting.co.za> New submission from Martin Panter: Looks good to me ---------- nosy: +martin.panter stage: -> commit review versions: +Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 00:48:30 2016 From: report at bugs.python.org (Ankur Dedania) Date: Wed, 10 Aug 2016 04:48:30 +0000 Subject: [docs] [issue27722] Path.touch's keyword argument mode documented incorrectly In-Reply-To: <1470780173.7.0.896294950108.issue27722@psf.upfronthosting.co.za> Message-ID: <1470804510.26.0.371323319136.issue27722@psf.upfronthosting.co.za> Ankur Dedania added the comment: Path.touch is also incorrect in python 3.4 documents ---------- status: closed -> open versions: +Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 01:00:07 2016 From: report at bugs.python.org (Zachary Ware) Date: Wed, 10 Aug 2016 05:00:07 +0000 Subject: [docs] [issue27722] Path.touch's keyword argument mode documented incorrectly In-Reply-To: <1470780173.7.0.896294950108.issue27722@psf.upfronthosting.co.za> Message-ID: <1470805207.81.0.97175443301.issue27722@psf.upfronthosting.co.za> Zachary Ware added the comment: Yes, but 3.4 is out of bugfix maintenance and thus its docs are no longer updated. ---------- status: open -> closed versions: -Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 01:31:46 2016 From: report at bugs.python.org (Roundup Robot) Date: Wed, 10 Aug 2016 05:31:46 +0000 Subject: [docs] [issue27207] Failing doctests in Doc/whatsnew/3.2.rst In-Reply-To: <1465000673.79.0.877090352163.issue27207@psf.upfronthosting.co.za> Message-ID: <20160810053142.11958.14098.685393C3@psf.io> Roundup Robot added the comment: New changeset cee3074233e6 by Zachary Ware in branch '3.5': Issue #27207: Fix doctests in Doc/whatsnew/3.2.rst https://hg.python.org/cpython/rev/cee3074233e6 New changeset ea43895ebfd9 by Zachary Ware in branch 'default': Closes #27207: Merge with 3.5 https://hg.python.org/cpython/rev/ea43895ebfd9 ---------- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 01:32:45 2016 From: report at bugs.python.org (Zachary Ware) Date: Wed, 10 Aug 2016 05:32:45 +0000 Subject: [docs] [issue27207] Failing doctests in Doc/whatsnew/3.2.rst In-Reply-To: <1465000673.79.0.877090352163.issue27207@psf.upfronthosting.co.za> Message-ID: <1470807165.54.0.349301319201.issue27207@psf.upfronthosting.co.za> Zachary Ware added the comment: Thanks for the patch! I added a couple more skips to get everything passing (the ones I skipped could not be properly tested). ---------- nosy: +zach.ware type: -> behavior versions: +Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 01:36:03 2016 From: report at bugs.python.org (Roundup Robot) Date: Wed, 10 Aug 2016 05:36:03 +0000 Subject: [docs] [issue27208] Failing doctests in Library/traceback.rst In-Reply-To: <1465000916.52.0.195426294226.issue27208@psf.upfronthosting.co.za> Message-ID: <20160810053559.3336.98706.EB8E08EB@psf.io> Roundup Robot added the comment: New changeset eadf2905f424 by Zachary Ware in branch '3.5': Issue #27208: Fix doctest in Doc/library/traceback.rst https://hg.python.org/cpython/rev/eadf2905f424 New changeset 76c04e780cd5 by Zachary Ware in branch 'default': Closes #27208: Merge with 3.5 https://hg.python.org/cpython/rev/76c04e780cd5 ---------- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 01:36:26 2016 From: report at bugs.python.org (Zachary Ware) Date: Wed, 10 Aug 2016 05:36:26 +0000 Subject: [docs] [issue27208] Failing doctests in Library/traceback.rst In-Reply-To: <1465000916.52.0.195426294226.issue27208@psf.upfronthosting.co.za> Message-ID: <1470807386.7.0.96638867671.issue27208@psf.upfronthosting.co.za> Zachary Ware added the comment: Thanks for the patch! ---------- nosy: +zach.ware type: -> behavior versions: +Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 01:40:34 2016 From: report at bugs.python.org (Roundup Robot) Date: Wed, 10 Aug 2016 05:40:34 +0000 Subject: [docs] [issue27209] Failing doctests in Library/email.*.rst Message-ID: <20160810054031.3238.77596.2C288291@psf.io> New submission from Roundup Robot: New changeset bb443518141e by Zachary Ware in branch '3.5': Issue #27209: Fix doctests in Doc/library/email*.rst https://hg.python.org/cpython/rev/bb443518141e New changeset 81dc2d250209 by Zachary Ware in branch 'default': Closes #27209: Merge with 3.5 https://hg.python.org/cpython/rev/81dc2d250209 ---------- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 01:40:52 2016 From: report at bugs.python.org (Zachary Ware) Date: Wed, 10 Aug 2016 05:40:52 +0000 Subject: [docs] [issue27209] Failing doctests in Library/email.*.rst In-Reply-To: <20160810054031.3238.77596.2C288291@psf.io> Message-ID: <1470807652.2.0.358391089581.issue27209@psf.upfronthosting.co.za> Zachary Ware added the comment: Thanks for the patch! ---------- nosy: +zach.ware type: -> behavior versions: +Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 02:01:36 2016 From: report at bugs.python.org (Roundup Robot) Date: Wed, 10 Aug 2016 06:01:36 +0000 Subject: [docs] [issue27210] Failing doctests due to environmental dependencies in Lib/*lib.rst In-Reply-To: <1465001215.61.0.0775726145069.issue27210@psf.upfronthosting.co.za> Message-ID: <20160810060132.3555.86071.8AF7671D@psf.io> Roundup Robot added the comment: New changeset 6b00ccf5e435 by Zachary Ware in branch '3.5': Issue #27210: Fix doctests for a few modules. https://hg.python.org/cpython/rev/6b00ccf5e435 New changeset 0a569e4b1d57 by Zachary Ware in branch 'default': Closes #27210: Merge with 3.5 https://hg.python.org/cpython/rev/0a569e4b1d57 ---------- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 02:03:03 2016 From: report at bugs.python.org (Zachary Ware) Date: Wed, 10 Aug 2016 06:03:03 +0000 Subject: [docs] [issue27210] Failing doctests due to environmental dependencies in Lib/{nntp, ftp, diff}lib.rst In-Reply-To: <1465001215.61.0.0775726145069.issue27210@psf.upfronthosting.co.za> Message-ID: <1470808983.3.0.285310012959.issue27210@psf.upfronthosting.co.za> Zachary Ware added the comment: Thanks for the patch! I made a couple changes in difflib.rst to avoid issues with sys.stdout.write() returning the number of characters written. ---------- nosy: +zach.ware title: Failing doctests due to environmental dependencies in Lib/*lib.rst -> Failing doctests due to environmental dependencies in Lib/{nntp,ftp,diff}lib.rst type: -> behavior versions: +Python 3.5 _______________________________________ Python tracker _______________________________________ From songofacandy at gmail.com Wed Aug 10 02:56:23 2016 From: songofacandy at gmail.com (INADA Naoki) Date: Wed, 10 Aug 2016 06:56:23 +0000 Subject: [docs] Japanese Documents Link Problem In-Reply-To: References: Message-ID: Hi, I'm maintainer of Japanese translations. I'm sorry about inconvenience, but we don't provide downloadable archive for now. The URL is generated from template, it's not intended. I filed an issue about it. Thank you for reporting. https://github.com/python-doc-ja/python-doc-ja/issues/738 On Wed, Aug 10, 2016 at 5:32 AM Makoto T wrote: > Hi, > > I'm looking for Japanese Documents which can be downloaded, but the > following links seem to be dead. > > URL: > https://docs.python.org/ftp/python/doc/3.5.1/python-3.5.1-docs-html.zip > ( In the page... http://docs.python.jp/3/download.html) > > Thank you for your help. > > Sincerely, > > M. Tsutsumi > _______________________________________________ > 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 Wed Aug 10 04:18:00 2016 From: report at bugs.python.org (Daisuke Miyakawa) Date: Wed, 10 Aug 2016 08:18:00 +0000 Subject: [docs] [issue27724] PEP3119 inconsintent with actual CPython impl Message-ID: <1470817080.1.0.906916235476.issue27724@psf.upfronthosting.co.za> New submission from Daisuke Miyakawa: Python 3.5.2 (and Python 2.7.12) uses Py_TPFLAGS_IS_ABSTRACT while PEP 3119 menttions "Py_TPFLAGS_ABSTRACT" for it. At some point had the name of the flag been changed without modifying PEP? ---------- assignee: docs at python components: Documentation messages: 272321 nosy: Daisuke Miyakawa, docs at python priority: normal severity: normal status: open title: PEP3119 inconsintent with actual CPython impl versions: Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 09:52:48 2016 From: report at bugs.python.org (R. David Murray) Date: Wed, 10 Aug 2016 13:52:48 +0000 Subject: [docs] [issue27724] PEP3119 inconsintent with actual CPython impl In-Reply-To: <1470817080.1.0.906916235476.issue27724@psf.upfronthosting.co.za> Message-ID: <1470837168.25.0.750961019279.issue27724@psf.upfronthosting.co.za> R. David Murray added the comment: Probably. PEPs, once completed (unless they are informational PEPs), are historical documents, and the real implementation may diverge from the PEP immediately, or after maintenance updates. The real documentation for the added feature should be in the main docs. We are not always good about making that true, and we do reference the PEPs, and so sometimes we do update them. I'll leave this open so someone knowledgeable about it can decide if this should be fixed, or if there are missing "real docs" (I don't get hits for either constant grepping the docs). ---------- nosy: +r.david.murray _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 13:32:01 2016 From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=) Date: Wed, 10 Aug 2016 17:32:01 +0000 Subject: [docs] [issue12290] __setstate__ is called for false values In-Reply-To: <1307586060.34.0.652262251036.issue12290@psf.upfronthosting.co.za> Message-ID: <1470850321.85.0.253480236564.issue12290@psf.upfronthosting.co.za> Changes by St?phane Wirtel : ---------- versions: +Python 3.5, Python 3.6 -Python 2.7, Python 3.3, Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 21:54:26 2016 From: report at bugs.python.org (Ben Hoyt) Date: Thu, 11 Aug 2016 01:54:26 +0000 Subject: [docs] [issue27719] Misleading note about "args" attribute in "User-defined Exceptions" section of tutorial In-Reply-To: <1470758926.96.0.219997040874.issue27719@psf.upfronthosting.co.za> Message-ID: <1470880465.94.0.0783287504685.issue27719@psf.upfronthosting.co.za> Ben Hoyt added the comment: Okay, patch attached -- I think it's best to simply remove that sentence. Side note: this is why GitHub is so good -- click edit, remove the sentence, click create pull request (approx time 30 seconds). I've got a new machine since I last did Python development, so to create an actual patch I needed to: download Mercurial, clone the repo, install Sphinx, edit the file, build the docs, create the patch (approx time 30 minutes). On the positive side, each of those steps was painless and trouble-free. :-) ---------- keywords: +patch Added file: http://bugs.python.org/file44071/issue27719-1.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 10 22:09:08 2016 From: report at bugs.python.org (Evelyn Mitchell) Date: Thu, 11 Aug 2016 02:09:08 +0000 Subject: [docs] [issue27720] decimal.Context.to_eng_string wrong docstring In-Reply-To: <1470763519.71.0.509753850108.issue27720@psf.upfronthosting.co.za> Message-ID: <1470881348.33.0.0832173351307.issue27720@psf.upfronthosting.co.za> Evelyn Mitchell added the comment: I had to look up what engineering notation meant, so I added detail to the docstring. ---------- nosy: +Evelyn Mitchell stage: -> patch review Added file: http://bugs.python.org/file44072/patch27720 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 11 00:48:08 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Thu, 11 Aug 2016 04:48:08 +0000 Subject: [docs] [issue27720] decimal.Context.to_eng_string wrong docstring In-Reply-To: <1470763519.71.0.509753850108.issue27720@psf.upfronthosting.co.za> Message-ID: <1470890888.42.0.994153742017.issue27720@psf.upfronthosting.co.za> Changes by Raymond Hettinger : ---------- assignee: docs at python -> rhettinger nosy: +rhettinger _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 11 02:14:26 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Thu, 11 Aug 2016 06:14:26 +0000 Subject: [docs] [issue27720] decimal.Context.to_eng_string wrong docstring In-Reply-To: <1470763519.71.0.509753850108.issue27720@psf.upfronthosting.co.za> Message-ID: <1470896066.92.0.365912324004.issue27720@psf.upfronthosting.co.za> Raymond Hettinger added the comment: Thanks Evelyn. I've refined this a bit to incorporate the more precise wording in the decimal arithmetic specification (see http://speleotrove.com/decimal/daconvs.html ). Also added the missing doctests and synced-up the wording between the docstrings and the main docs. ---------- keywords: +patch Added file: http://bugs.python.org/file44073/decimal_eng_doc.diff _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 11 03:22:48 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Thu, 11 Aug 2016 07:22:48 +0000 Subject: [docs] [issue27719] Misleading note about "args" attribute in "User-defined Exceptions" section of tutorial In-Reply-To: <1470758926.96.0.219997040874.issue27719@psf.upfronthosting.co.za> Message-ID: <1470900168.59.0.681874423145.issue27719@psf.upfronthosting.co.za> Raymond Hettinger added the comment: Thanks for noticing this. It looks like this particular example is now pointless and should be removed. The subsequent examples do a much better job of showing typical practices. ---------- nosy: +rhettinger Added file: http://bugs.python.org/file44075/exc_doc.diff _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 11 03:23:02 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Thu, 11 Aug 2016 07:23:02 +0000 Subject: [docs] [issue27719] Misleading note about "args" attribute in "User-defined Exceptions" section of tutorial In-Reply-To: <1470758926.96.0.219997040874.issue27719@psf.upfronthosting.co.za> Message-ID: <1470900182.81.0.898907738285.issue27719@psf.upfronthosting.co.za> Changes by Raymond Hettinger : ---------- assignee: docs at python -> rhettinger _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 11 03:51:07 2016 From: report at bugs.python.org (Antti Haapala) Date: Thu, 11 Aug 2016 07:51:07 +0000 Subject: [docs] [issue27720] decimal.Context.to_eng_string wrong docstring In-Reply-To: <1470763519.71.0.509753850108.issue27720@psf.upfronthosting.co.za> Message-ID: <1470901867.11.0.445153335405.issue27720@psf.upfronthosting.co.za> Antti Haapala added the comment: Raymond: your doc patch is not quite right. Decimal('123e1') is converted to Decimal('1.23e3') internally already; so that str(d) will print 1.23e3, scientific notation of that number is '1.23e3' and engineering notation is '1.23e3', thus not a good example. A better example would be Also, the engineering notation is a string, not a Decimal instance. Also, now that I test it, the whole `to_eng_string` seems to be utterly broken, same applies to "to_sci_string". They do not print in scientific notation if the exponent in the original number was 0: decimal.Decimal('123456789101214161820222426.0e0').to_eng_string() And all operations with decimal will now generate numbers with exponent of 0 if it is within their precision, so no engineering notation is ever printed, duh. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 11 03:57:28 2016 From: report at bugs.python.org (Stefan Krah) Date: Thu, 11 Aug 2016 07:57:28 +0000 Subject: [docs] [issue27720] decimal.Context.to_eng_string wrong docstring In-Reply-To: <1470763519.71.0.509753850108.issue27720@psf.upfronthosting.co.za> Message-ID: <1470902248.42.0.596244254822.issue27720@psf.upfronthosting.co.za> Stefan Krah added the comment: @Antti The behavior follows this standard: http://speleotrove.com/decimal/decarith.html Nothing we can do about it even if we wanted to. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 11 05:35:45 2016 From: report at bugs.python.org (Antti Haapala) Date: Thu, 11 Aug 2016 09:35:45 +0000 Subject: [docs] [issue27720] decimal.Context.to_eng_string wrong docstring In-Reply-To: <1470763519.71.0.509753850108.issue27720@psf.upfronthosting.co.za> Message-ID: <1470908145.17.0.995434016121.issue27720@psf.upfronthosting.co.za> Antti Haapala added the comment: @Stefan after reading the bad standard I agree that it follows the standard, as unfortunate as it is. However, that part is then also wrong in Raymond's documentation patch. It should be something like: the exponent is adjusted to a multiple of 3 if *any* exponent is to be shown, and exponent is shown only if the exponent is larger than there are significant figures in the number, or if it is less than or equal to -6, or something alike. Or perhaps it should say "This is not the notation you are looking for." ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 11 06:14:19 2016 From: report at bugs.python.org (Stefan Krah) Date: Thu, 11 Aug 2016 10:14:19 +0000 Subject: [docs] [issue27720] decimal.Context.to_eng_string wrong docstring In-Reply-To: <1470763519.71.0.509753850108.issue27720@psf.upfronthosting.co.za> Message-ID: <1470910459.93.0.518807760437.issue27720@psf.upfronthosting.co.za> Stefan Krah added the comment: > after reading the bad standard ... Make sure not to buy a Power 6 processor and not to use IEEE 754-2008, because that's essentially what you'll get. IEEE doesn't specify engineering notation though. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 11 11:15:50 2016 From: report at bugs.python.org (Mark Lawrence) Date: Thu, 11 Aug 2016 15:15:50 +0000 Subject: [docs] [issue21018] [patch] added missing documentation about escaping characters for configparser In-Reply-To: <1395464420.76.0.68706986346.issue21018@psf.upfronthosting.co.za> Message-ID: <1470928550.88.0.458094968411.issue21018@psf.upfronthosting.co.za> Changes by Mark Lawrence : ---------- nosy: -BreamoreBoy _______________________________________ Python tracker _______________________________________ From frank.wolbertus at tbikennislab.com Wed Aug 10 02:29:43 2016 From: frank.wolbertus at tbikennislab.com (Wolbertus, Frank (TBI-KennisLAB)) Date: Wed, 10 Aug 2016 06:29:43 +0000 Subject: [docs] Download Python 3.6.0a3 Documentation Message-ID: Like to receive PDF (A4 paper size) of the python 3.6.0a3 Documentation If I do it on the side it gives a error Met vriendelijke groet, Frank Wolbertus Developer [cid:30462935-B145-410D-AC04-8CF767C60D48] T +31 (0)6 53 22 13 56 | frank.wolbertus at tbi.nl | www.tbikennislab.nl | Hanzeweg 16, 2803 MC Gouda | routebeschrijving -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 11662 bytes Desc: image001.png URL: From guido at python.org Wed Aug 10 19:28:05 2016 From: guido at python.org (guido at python.org) Date: Wed, 10 Aug 2016 23:28:05 -0000 Subject: [docs] Document typing.Text and typing.AnyStr (issue 27723) Message-ID: <20160810232805.13033.53920@psf.upfronthosting.co.za> http://bugs.python.org/review/27723/diff/18103/Doc/library/typing.rst File Doc/library/typing.rst (right): http://bugs.python.org/review/27723/diff/18103/Doc/library/typing.rst#newcode657 Doc/library/typing.rst:657: ``AnyStr`` is a type alias meant to be used for functions that may accept It's not an alias, it's a type variable. http://bugs.python.org/review/27723/diff/18103/Doc/library/typing.rst#newcode668 Doc/library/typing.rst:668: in Python 3 and ``AnyStr = TypeVar('AnyStr', str, unicode)`` in Python 2. No need to document what it does for Python 2 (these docs are for Python 3 only). http://bugs.python.org/review/27723/diff/18103/Doc/library/typing.rst#newcode674 Doc/library/typing.rst:674: ``Text`` is aliased to ``unicode`` in Python 2 and ``str`` in Python 3. Here it's more defensible to mention Python 2, but I would still focus more on Python 3. E.g. "Text is an alias for str. It is provided to supply a forward commpatibility path for Python 2 code; in Python 2 it is an alias for unicode." http://bugs.python.org/review/27723/ From jrodolfolima at yahoo.com.br Thu Aug 11 10:51:51 2016 From: jrodolfolima at yahoo.com.br (J.Rodolfo) Date: Thu, 11 Aug 2016 14:51:51 +0000 (UTC) Subject: [docs] Broken download links References: <405725960.15337252.1470927111980.JavaMail.yahoo.ref@mail.yahoo.com> Message-ID: <405725960.15337252.1470927111980.JavaMail.yahoo@mail.yahoo.com> Hi there, I am trying to download the documents at: https://docs.python.org/3.4/download.html But all download links on the page seem to be broken and lead to pages with "404 Not Found" messages. Can you please refer me to ther links to these documents and/or let me know when this is fixed? Thank you for your attention, J.R. ???************************************************ ? J. Rodolfo Lima?? jrodolfolima at yahoo.com.br ??************************************************ -------------- next part -------------- An HTML attachment was scrubbed... URL: From report at bugs.python.org Thu Aug 11 11:30:43 2016 From: report at bugs.python.org (Evelyn Mitchell) Date: Thu, 11 Aug 2016 15:30:43 +0000 Subject: [docs] [issue27720] decimal.Context.to_eng_string wrong docstring In-Reply-To: <1470763519.71.0.509753850108.issue27720@psf.upfronthosting.co.za> Message-ID: <1470929443.34.0.0678044382277.issue27720@psf.upfronthosting.co.za> Evelyn Mitchell added the comment: Thank you Raymond for a detailed patch update. I will mention that matlab does not support this conversion [1]. R doesn't support engineering notation, either. It may be that this conversion isn't expected to be part of the standard library, and people are more likely to write their own. [2] The rationale for engineering notation is that it corresponds to SI units of measure. [1] https://www.mathworks.com/matlabcentral/newsreader/view_thread/22843 [2] http://stackoverflow.com/questions/8262302/python-fixed-exponent-in-scientific-notation ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 11 13:25:50 2016 From: report at bugs.python.org (Ben Hoyt) Date: Thu, 11 Aug 2016 17:25:50 +0000 Subject: [docs] [issue27719] Misleading note about "args" attribute in "User-defined Exceptions" section of tutorial In-Reply-To: <1470758926.96.0.219997040874.issue27719@psf.upfronthosting.co.za> Message-ID: <1470936349.97.0.267748163325.issue27719@psf.upfronthosting.co.za> Ben Hoyt added the comment: Removing that whole example sounds good to me, thanks. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 11 14:13:23 2016 From: report at bugs.python.org (Xiang Zhang) Date: Thu, 11 Aug 2016 18:13:23 +0000 Subject: [docs] [issue27740] Fix doc of Py_CompileStringExFlags Message-ID: <1470939203.79.0.619794104629.issue27740@psf.upfronthosting.co.za> New submission from Xiang Zhang: I think the doc of Py_CompileStringExFlags has two flaws: 1. Py_CompileStringExFlags should be replaced by Py_CompileStringObject from the context. Py_CompileStringExFlags in the context is meaningless. 2. *filename* is a byte string that should be decoded but not decoded from. It is ... = decode(filename) but not filename = decode(...). ---------- assignee: docs at python components: Documentation files: Py_CompileStringExFlags_doc.patch keywords: patch messages: 272468 nosy: docs at python, xiang.zhang priority: normal severity: normal status: open title: Fix doc of Py_CompileStringExFlags type: behavior versions: Python 3.6 Added file: http://bugs.python.org/file44078/Py_CompileStringExFlags_doc.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 11 14:48:31 2016 From: report at bugs.python.org (Nicholas Colclasure) Date: Thu, 11 Aug 2016 18:48:31 +0000 Subject: [docs] [issue27741] datetime.datetime.strptime functionality description incorrect Message-ID: <1470941311.19.0.0562450492824.issue27741@psf.upfronthosting.co.za> New submission from Nicholas Colclasure: The datetime.datetime.strptime documentation states that it is equivalent to datetime(*(time.strptime(date_string, format)[0:6])), but the time.struct_time returned by time.strptime does not include microseconds, implying that datetime's strptime would also not include microseconds, but testing of the functions shows that it does include them. Removing the false statement of equivalence would be enough to remove this bug from the documentation. ---------- assignee: docs at python components: Documentation messages: 272474 nosy: Valectar, docs at python priority: normal severity: normal status: open title: datetime.datetime.strptime functionality description incorrect type: behavior versions: Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 00:24:39 2016 From: report at bugs.python.org (Martin Panter) Date: Fri, 12 Aug 2016 04:24:39 +0000 Subject: [docs] [issue12887] Documenting all SO_* constants in socket module In-Reply-To: <1314987180.49.0.607596056761.issue12887@psf.upfronthosting.co.za> Message-ID: <1470975879.86.0.386635950303.issue12887@psf.upfronthosting.co.za> Martin Panter added the comment: See also Issue 27409, where I am proposing to list the SO_* and other constants by name (with associated Python version and whether they are missing on some platforms), but without descriptions. ---------- nosy: +martin.panter _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 06:47:38 2016 From: report at bugs.python.org (SilentGhost) Date: Fri, 12 Aug 2016 10:47:38 +0000 Subject: [docs] [issue27745] Fix typos in Argument Clinic howto In-Reply-To: <1470998649.34.0.55275760151.issue27745@psf.upfronthosting.co.za> Message-ID: <1470998858.18.0.0607821092056.issue27745@psf.upfronthosting.co.za> SilentGhost added the comment: Then I guess all the changes to Modules/_sqlite.c are there by mistake? Would you mid refreshing your patch to remove them? ---------- assignee: -> docs at python components: +Documentation nosy: +SilentGhost, docs at python versions: +Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 06:49:23 2016 From: report at bugs.python.org (Lele Gaifax) Date: Fri, 12 Aug 2016 10:49:23 +0000 Subject: [docs] [issue27745] Fix typos in Argument Clinic howto In-Reply-To: <1470998649.34.0.55275760151.issue27745@psf.upfronthosting.co.za> Message-ID: <1470998963.42.0.511770791088.issue27745@psf.upfronthosting.co.za> Lele Gaifax added the comment: Yes, sorry about that, picked the wrong file :-| I will renew the patch shortly! ---------- components: -Documentation versions: -Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 06:53:11 2016 From: report at bugs.python.org (Lele Gaifax) Date: Fri, 12 Aug 2016 10:53:11 +0000 Subject: [docs] [issue27745] Fix typos in Argument Clinic howto In-Reply-To: <1470998649.34.0.55275760151.issue27745@psf.upfronthosting.co.za> Message-ID: <1470999191.24.0.53261122193.issue27745@psf.upfronthosting.co.za> Lele Gaifax added the comment: Re-uploaded the patch file, without spurious stuff. ---------- Added file: http://bugs.python.org/file44084/ac-doc-typos.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 06:53:50 2016 From: report at bugs.python.org (Lele Gaifax) Date: Fri, 12 Aug 2016 10:53:50 +0000 Subject: [docs] [issue27745] Fix typos in Argument Clinic howto In-Reply-To: <1470998649.34.0.55275760151.issue27745@psf.upfronthosting.co.za> Message-ID: <1470999230.26.0.432654143896.issue27745@psf.upfronthosting.co.za> Changes by Lele Gaifax : Removed file: http://bugs.python.org/file44083/ac-doc-typos.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 06:55:00 2016 From: report at bugs.python.org (SilentGhost) Date: Fri, 12 Aug 2016 10:55:00 +0000 Subject: [docs] [issue27745] Fix typos in Argument Clinic howto In-Reply-To: <1470998649.34.0.55275760151.issue27745@psf.upfronthosting.co.za> Message-ID: <1470999299.99.0.753534850435.issue27745@psf.upfronthosting.co.za> SilentGhost added the comment: LGTM ---------- stage: -> commit review type: -> behavior _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 06:55:34 2016 From: report at bugs.python.org (SilentGhost) Date: Fri, 12 Aug 2016 10:55:34 +0000 Subject: [docs] [issue27745] Fix typos in Argument Clinic howto In-Reply-To: <1470998649.34.0.55275760151.issue27745@psf.upfronthosting.co.za> Message-ID: <1470999334.69.0.564792980823.issue27745@psf.upfronthosting.co.za> Changes by SilentGhost : ---------- components: +Documentation versions: +Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 07:17:50 2016 From: report at bugs.python.org (Xiang Zhang) Date: Fri, 12 Aug 2016 11:17:50 +0000 Subject: [docs] [issue27740] Fix doc of Py_CompileStringExFlags In-Reply-To: <1470939203.79.0.619794104629.issue27740@psf.upfronthosting.co.za> Message-ID: <1471000670.84.0.978689071458.issue27740@psf.upfronthosting.co.za> Changes by Xiang Zhang : Removed file: http://bugs.python.org/file44078/Py_CompileStringExFlags_doc.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 07:18:04 2016 From: report at bugs.python.org (Xiang Zhang) Date: Fri, 12 Aug 2016 11:18:04 +0000 Subject: [docs] [issue27740] Fix doc of Py_CompileStringExFlags In-Reply-To: <1470939203.79.0.619794104629.issue27740@psf.upfronthosting.co.za> Message-ID: <1471000684.58.0.832815577666.issue27740@psf.upfronthosting.co.za> Changes by Xiang Zhang : Added file: http://bugs.python.org/file44085/Py_CompileStringExFlags_doc.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 08:18:38 2016 From: report at bugs.python.org (Roundup Robot) Date: Fri, 12 Aug 2016 12:18:38 +0000 Subject: [docs] [issue27745] Fix typos in Argument Clinic howto In-Reply-To: <1470998649.34.0.55275760151.issue27745@psf.upfronthosting.co.za> Message-ID: <20160812121833.58133.65640.B57039B8@psf.io> Roundup Robot added the comment: New changeset 129c601e7bfa by Martin Panter in branch '3.5': Issue #27745: Fix some typos in Argument Clinic howto, by Lele Gaifax https://hg.python.org/cpython/rev/129c601e7bfa New changeset 8c33152fd75c by Martin Panter in branch 'default': Issue #27745: Merge typo fixes from 3.5 https://hg.python.org/cpython/rev/8c33152fd75c ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 08:33:46 2016 From: report at bugs.python.org (SilentGhost) Date: Fri, 12 Aug 2016 12:33:46 +0000 Subject: [docs] [issue27745] Fix typos in Argument Clinic howto In-Reply-To: <1470998649.34.0.55275760151.issue27745@psf.upfronthosting.co.za> Message-ID: <1471005226.68.0.984584265127.issue27745@psf.upfronthosting.co.za> SilentGhost added the comment: Thanks, Lele. ---------- resolution: -> fixed stage: commit review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 08:49:50 2016 From: report at bugs.python.org (Mark Lawrence) Date: Fri, 12 Aug 2016 12:49:50 +0000 Subject: [docs] [issue12887] Documenting all SO_* constants in socket module In-Reply-To: <1314987180.49.0.607596056761.issue12887@psf.upfronthosting.co.za> Message-ID: <1471006190.52.0.928079520233.issue12887@psf.upfronthosting.co.za> Changes by Mark Lawrence : ---------- nosy: -BreamoreBoy _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 10:01:01 2016 From: report at bugs.python.org (Paulo Gabriel Poiati) Date: Fri, 12 Aug 2016 14:01:01 +0000 Subject: [docs] [issue27747] Broken example in the queue module documentation Message-ID: <1471010461.03.0.586274907081.issue27747@psf.upfronthosting.co.za> New submission from Paulo Gabriel Poiati: I believe the code example at https://docs.python.org/3.6/library/queue.html is broken. The break condition in the worker loop (when the queued value is None) must call the `task_done` before breaking, otherwise the code blocks indefinitely in the `queue.join()` statement. ---------- assignee: docs at python components: Documentation messages: 272540 nosy: Paulo Gabriel Poiati, docs at python priority: normal severity: normal status: open title: Broken example in the queue module documentation type: enhancement versions: Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 10:42:52 2016 From: report at bugs.python.org (R. David Murray) Date: Fri, 12 Aug 2016 14:42:52 +0000 Subject: [docs] [issue27747] Broken example in the queue module documentation In-Reply-To: <1471010461.03.0.586274907081.issue27747@psf.upfronthosting.co.za> Message-ID: <1471012972.29.0.797435435443.issue27747@psf.upfronthosting.co.za> R. David Murray added the comment: The example looks correct to me. Have you tested it and seen it hang? The q.join() is done, and returns once all the puts have been processed. *Then* None is put for each worker, which terminates the worker thread. There's no q.join() to block at that point. ---------- nosy: +r.david.murray _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 12:44:28 2016 From: report at bugs.python.org (Roundup Robot) Date: Fri, 12 Aug 2016 16:44:28 +0000 Subject: [docs] [issue27719] Misleading note about "args" attribute in "User-defined Exceptions" section of tutorial In-Reply-To: <1470758926.96.0.219997040874.issue27719@psf.upfronthosting.co.za> Message-ID: <20160812164424.75786.28762.E7163EF7@psf.io> Roundup Robot added the comment: New changeset 6fdd29a9d5d4 by Raymond Hettinger in branch '3.5': Issue 27719: Remove a doc example that is not applicable in Python 3 https://hg.python.org/cpython/rev/6fdd29a9d5d4 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 12:44:40 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Fri, 12 Aug 2016 16:44:40 +0000 Subject: [docs] [issue27719] Misleading note about "args" attribute in "User-defined Exceptions" section of tutorial In-Reply-To: <1470758926.96.0.219997040874.issue27719@psf.upfronthosting.co.za> Message-ID: <1471020280.49.0.132485190674.issue27719@psf.upfronthosting.co.za> Changes by Raymond Hettinger : ---------- resolution: -> fixed status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 13:24:36 2016 From: report at bugs.python.org (Paulo Gabriel Poiati) Date: Fri, 12 Aug 2016 17:24:36 +0000 Subject: [docs] [issue27747] Broken example in the queue module documentation In-Reply-To: <1471010461.03.0.586274907081.issue27747@psf.upfronthosting.co.za> Message-ID: <1471022676.63.0.547687943742.issue27747@psf.upfronthosting.co.za> Paulo Gabriel Poiati added the comment: You are absolutely right David. I was calling join after putting `None` in the queue. Sorry, I'm closing this. ---------- resolution: -> not a bug status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 13:57:31 2016 From: report at bugs.python.org (Roundup Robot) Date: Fri, 12 Aug 2016 17:57:31 +0000 Subject: [docs] [issue27712] Tiny typos in import.rst In-Reply-To: <1470801827.64.0.914764893779.issue27712@psf.upfronthosting.co.za> Message-ID: <20160812175729.8293.92664.1CC9F5DD@psf.io> Roundup Robot added the comment: New changeset 927c29e1d646 by Brett Cannon in branch '3.5': Issue #27712: Fix some typos in the import docs. https://hg.python.org/cpython/rev/927c29e1d646 New changeset 42a461366d6c by Brett Cannon in branch 'default': Merge for issue #27712 https://hg.python.org/cpython/rev/42a461366d6c ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 13:57:56 2016 From: report at bugs.python.org (Brett Cannon) Date: Fri, 12 Aug 2016 17:57:56 +0000 Subject: [docs] [issue27712] Tiny typos in import.rst In-Reply-To: <1470801827.64.0.914764893779.issue27712@psf.upfronthosting.co.za> Message-ID: <1471024676.31.0.198674949144.issue27712@psf.upfronthosting.co.za> Brett Cannon added the comment: Thanks for the patch! ---------- resolution: -> fixed stage: commit review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 14:08:22 2016 From: report at bugs.python.org (Xiang Zhang) Date: Fri, 12 Aug 2016 18:08:22 +0000 Subject: [docs] [issue27712] Tiny typos in import.rst In-Reply-To: <1470801827.64.0.914764893779.issue27712@psf.upfronthosting.co.za> Message-ID: <1471025302.42.0.0798635604447.issue27712@psf.upfronthosting.co.za> Xiang Zhang added the comment: Thanks for your work too! :) ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 14:17:31 2016 From: report at bugs.python.org (R. David Murray) Date: Fri, 12 Aug 2016 18:17:31 +0000 Subject: [docs] [issue27747] Broken example in the queue module documentation In-Reply-To: <1471010461.03.0.586274907081.issue27747@psf.upfronthosting.co.za> Message-ID: <1471025851.69.0.493745315569.issue27747@psf.upfronthosting.co.za> Changes by R. David Murray : ---------- stage: -> resolved type: enhancement -> behavior _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 22:38:17 2016 From: report at bugs.python.org (Roundup Robot) Date: Sat, 13 Aug 2016 02:38:17 +0000 Subject: [docs] [issue24637] locals dictionary in PyRun_String In-Reply-To: <1436966586.07.0.0153968460371.issue24637@psf.upfronthosting.co.za> Message-ID: <20160813023814.19477.72394.D8EA0C06@psf.io> Roundup Robot added the comment: New changeset 0f2a09950ac8 by Berker Peksag in branch '3.5': Issue #24637: Document that locals can be any mapping object https://hg.python.org/cpython/rev/0f2a09950ac8 New changeset 61c4dbec2e2c by Berker Peksag in branch 'default': Issue #24637: Merge from 3.5 https://hg.python.org/cpython/rev/61c4dbec2e2c ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 12 22:39:20 2016 From: report at bugs.python.org (Berker Peksag) Date: Sat, 13 Aug 2016 02:39:20 +0000 Subject: [docs] [issue24637] locals dictionary in PyRun_String In-Reply-To: <1436966586.07.0.0153968460371.issue24637@psf.upfronthosting.co.za> Message-ID: <1471055960.14.0.0710916433447.issue24637@psf.upfronthosting.co.za> Berker Peksag added the comment: Thanks for the patch, Matthew! ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 13 11:17:50 2016 From: report at bugs.python.org (Decorater) Date: Sat, 13 Aug 2016 15:17:50 +0000 Subject: [docs] [issue27753] py_compile.compile() does not specify if it can accept a file like object or a bytes like object with the file's data. Message-ID: <1471101470.06.0.092616932845.issue27753@psf.upfronthosting.co.za> New submission from Decorater: py_compile.compile() does not specify if it can accept a file like object or a bytes like object with the file's data. Although I need something that can allow me to import byte like objects if the object contains valid python script data. (basically it would have to act as a import unless I have to exec the data in it which would be totally bad as it would not be able to retain all of the data. Long story short I need a way to import the data returned from the dec_script() function in this: https://bpaste.net/show/694c231c566c ---------- assignee: docs at python components: Documentation, Library (Lib) messages: 272590 nosy: Decorater, docs at python priority: normal severity: normal status: open title: py_compile.compile() does not specify if it can accept a file like object or a bytes like object with the file's data. versions: Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 13 11:41:42 2016 From: report at bugs.python.org (SilentGhost) Date: Sat, 13 Aug 2016 15:41:42 +0000 Subject: [docs] [issue27753] py_compile.compile() does not specify if it can accept a file like object or a bytes like object with the file's data. In-Reply-To: <1471101470.06.0.092616932845.issue27753@psf.upfronthosting.co.za> Message-ID: <1471102902.84.0.909872327263.issue27753@psf.upfronthosting.co.za> SilentGhost added the comment: It says "The source code is loaded from the file name *file*". That seems unambiguous enough to me. ---------- nosy: +SilentGhost type: -> behavior _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 13 12:43:16 2016 From: report at bugs.python.org (Xiang Zhang) Date: Sat, 13 Aug 2016 16:43:16 +0000 Subject: [docs] [issue27753] py_compile.compile() does not specify if it can accept a file like object or a bytes like object with the file's data. In-Reply-To: <1471101470.06.0.092616932845.issue27753@psf.upfronthosting.co.za> Message-ID: <1471106596.58.0.70093887244.issue27753@psf.upfronthosting.co.za> Xiang Zhang added the comment: Maybe in the sentence, name should be named? ---------- nosy: +xiang.zhang _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 13 12:52:26 2016 From: report at bugs.python.org (Decorater) Date: Sat, 13 Aug 2016 16:52:26 +0000 Subject: [docs] [issue27753] py_compile.compile() does not specify if it can accept a file like object or a bytes like object with the file's data. In-Reply-To: <1471101470.06.0.092616932845.issue27753@psf.upfronthosting.co.za> Message-ID: <1471107146.79.0.125315137121.issue27753@psf.upfronthosting.co.za> Decorater added the comment: yeah, true and to specify that it cannot be anything but a file. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 13 13:01:36 2016 From: report at bugs.python.org (SilentGhost) Date: Sat, 13 Aug 2016 17:01:36 +0000 Subject: [docs] [issue27753] py_compile.compile() does not specify if it can accept a file like object or a bytes like object with the file's data. In-Reply-To: <1471101470.06.0.092616932845.issue27753@psf.upfronthosting.co.za> Message-ID: <1471107695.95.0.716150926862.issue27753@psf.upfronthosting.co.za> SilentGhost added the comment: Do you care to propose an improved wording? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 13 13:47:26 2016 From: report at bugs.python.org (Decorater) Date: Sat, 13 Aug 2016 17:47:26 +0000 Subject: [docs] [issue27753] py_compile.compile() does not specify if it can accept a file like object or a bytes like object with the file's data. In-Reply-To: <1471101470.06.0.092616932845.issue27753@psf.upfronthosting.co.za> Message-ID: <1471110446.64.0.659801705949.issue27753@psf.upfronthosting.co.za> Changes by Decorater : Added file: http://bugs.python.org/file44095/py_compile.rst _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 13 13:47:52 2016 From: report at bugs.python.org (Decorater) Date: Sat, 13 Aug 2016 17:47:52 +0000 Subject: [docs] [issue27753] py_compile.compile() does not specify if it can accept a file like object or a bytes like object with the file's data. In-Reply-To: <1471101470.06.0.092616932845.issue27753@psf.upfronthosting.co.za> Message-ID: <1471110472.92.0.327252568188.issue27753@psf.upfronthosting.co.za> Decorater added the comment: Ok, file uploaded. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 13 13:51:13 2016 From: report at bugs.python.org (SilentGhost) Date: Sat, 13 Aug 2016 17:51:13 +0000 Subject: [docs] [issue27753] py_compile.compile() does not specify if it can accept a file like object or a bytes like object with the file's data. In-Reply-To: <1471101470.06.0.092616932845.issue27753@psf.upfronthosting.co.za> Message-ID: <1471110673.48.0.459113439753.issue27753@psf.upfronthosting.co.za> SilentGhost added the comment: I don't see how this is an improvement. Before it clearly said that the first argument must be file name, now it's an oddly confusing statement. Also, typically we don't list all the possibilities of what the arguments must not be. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 13 14:10:30 2016 From: report at bugs.python.org (Roundup Robot) Date: Sat, 13 Aug 2016 18:10:30 +0000 Subject: [docs] [issue27720] decimal.Context.to_eng_string wrong docstring In-Reply-To: <1470763519.71.0.509753850108.issue27720@psf.upfronthosting.co.za> Message-ID: <20160813181026.845.6057.C21ACF2E@psf.io> Roundup Robot added the comment: New changeset 825713d3786a by Raymond Hettinger in branch '2.7': Issue #27720: Fix error in eng_to_decimal docs and add examples from the specification. https://hg.python.org/cpython/rev/825713d3786a ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 13 14:16:08 2016 From: report at bugs.python.org (Roundup Robot) Date: Sat, 13 Aug 2016 18:16:08 +0000 Subject: [docs] [issue27720] decimal.Context.to_eng_string wrong docstring In-Reply-To: <1470763519.71.0.509753850108.issue27720@psf.upfronthosting.co.za> Message-ID: <20160813181605.23355.17070.873134CE@psf.io> Roundup Robot added the comment: New changeset de2a9c98948e by Raymond Hettinger in branch '3.5': Issue #27720: Fix error in eng_to_decimal docs and add examples from the specification. https://hg.python.org/cpython/rev/de2a9c98948e ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 13 14:18:23 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Sat, 13 Aug 2016 18:18:23 +0000 Subject: [docs] [issue27720] decimal.Context.to_eng_string wrong docstring In-Reply-To: <1470763519.71.0.509753850108.issue27720@psf.upfronthosting.co.za> Message-ID: <1471112303.1.0.340521048586.issue27720@psf.upfronthosting.co.za> Changes by Raymond Hettinger : ---------- resolution: -> fixed status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 13 14:48:43 2016 From: report at bugs.python.org (Roundup Robot) Date: Sat, 13 Aug 2016 18:48:43 +0000 Subject: [docs] [issue27753] py_compile.compile() does not specify if it can accept a file like object or a bytes like object with the file's data. In-Reply-To: <1471101470.06.0.092616932845.issue27753@psf.upfronthosting.co.za> Message-ID: <20160813184840.79138.61860.6AE611DB@psf.io> Roundup Robot added the comment: New changeset b1e4c8a3e786 by R David Murray in branch '2.7': #27753: fix typo (name->named). https://hg.python.org/cpython/rev/b1e4c8a3e786 New changeset c1cc1f616285 by R David Murray in branch '3.5': #27753: fix typo (name->named). https://hg.python.org/cpython/rev/c1cc1f616285 New changeset dda25c37d02b by R David Murray in branch 'default': Merge: #27753: fix typo (name->named). https://hg.python.org/cpython/rev/dda25c37d02b ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 13 14:49:33 2016 From: report at bugs.python.org (R. David Murray) Date: Sat, 13 Aug 2016 18:49:33 +0000 Subject: [docs] [issue27753] py_compile.compile() does not specify if it can accept a file like object or a bytes like object with the file's data. In-Reply-To: <1471101470.06.0.092616932845.issue27753@psf.upfronthosting.co.za> Message-ID: <1471114173.21.0.110716156423.issue27753@psf.upfronthosting.co.za> R. David Murray added the comment: Agreed, the current wording is correct and complete, except for the name vs named bit. I've fixed that. ---------- nosy: +r.david.murray resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 14 01:20:48 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Sun, 14 Aug 2016 05:20:48 +0000 Subject: [docs] [issue27205] Failing doctests in Library/collections.rst In-Reply-To: <1465000020.63.0.799580126218.issue27205@psf.upfronthosting.co.za> Message-ID: <1471152048.53.0.36204555638.issue27205@psf.upfronthosting.co.za> Raymond Hettinger added the comment: FYI, this should have been assigned to me (the author of the examples being modified). ---------- assignee: zach.ware -> rhettinger nosy: +rhettinger _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 14 17:12:05 2016 From: report at bugs.python.org (Ivan Levkivskyi) Date: Sun, 14 Aug 2016 21:12:05 +0000 Subject: [docs] [issue27723] Document typing.Text and typing.AnyStr In-Reply-To: <1470793243.78.0.0997445491252.issue27723@psf.upfronthosting.co.za> Message-ID: <1471209125.37.0.590997193488.issue27723@psf.upfronthosting.co.za> Ivan Levkivskyi added the comment: Thank you for the patch, Michael! I could add a comment that probably it is better to mention the definition of AnyStr = TypeVar('AnyStr', str, bytes) at beginning and only then go with examples. ---------- nosy: +levkivskyi _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 14 21:03:55 2016 From: report at bugs.python.org (Guido van Rossum) Date: Mon, 15 Aug 2016 01:03:55 +0000 Subject: [docs] [issue27723] Document typing.Text and typing.AnyStr In-Reply-To: <1471209125.37.0.590997193488.issue27723@psf.upfronthosting.co.za> Message-ID: Guido van Rossum added the comment: Also see my comments in rietveld. --Guido (mobile) ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 15 12:57:41 2016 From: report at bugs.python.org (Michael Lee) Date: Mon, 15 Aug 2016 16:57:41 +0000 Subject: [docs] [issue27723] Document typing.Text and typing.AnyStr In-Reply-To: <1470793243.78.0.0997445491252.issue27723@psf.upfronthosting.co.za> Message-ID: <1471280261.35.0.242256846072.issue27723@psf.upfronthosting.co.za> Michael Lee added the comment: Second revision attached below. ---------- Added file: http://bugs.python.org/file44121/document-text-and-anystr-2.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 15 13:15:34 2016 From: report at bugs.python.org (Ivan Levkivskyi) Date: Mon, 15 Aug 2016 17:15:34 +0000 Subject: [docs] [issue27723] Document typing.Text and typing.AnyStr In-Reply-To: <1471280261.35.0.242256846072.issue27723@psf.upfronthosting.co.za> Message-ID: Ivan Levkivskyi added the comment: Looks good to me. 15 ??? 2016 18:57 "Michael Lee" ????: > > Michael Lee added the comment: > > Second revision attached below. > > ---------- > Added file: http://bugs.python.org/file44121/document-text-and- > anystr-2.patch > > _______________________________________ > Python tracker > > _______________________________________ > ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 15 18:10:02 2016 From: report at bugs.python.org (Guido van Rossum) Date: Mon, 15 Aug 2016 22:10:02 +0000 Subject: [docs] [issue27723] Document typing.Text and typing.AnyStr In-Reply-To: <1470793243.78.0.0997445491252.issue27723@psf.upfronthosting.co.za> Message-ID: <1471299002.42.0.0176174732296.issue27723@psf.upfronthosting.co.za> Guido van Rossum added the comment: Committed and merged to 3.6. changeset: 102670:d5872d0863c8 branch: 3.5 parent: 102663:27a99a722828 user: Guido van Rossum date: Mon Aug 15 15:06:38 2016 -0700 summary: Add docs for typing.AnyStr and typing.Text. By Michael Lee. changeset: 102672:705416c5909e tag: tip parent: 102671:247ecbae325c parent: 102670:d5872d0863c8 user: Guido van Rossum date: Mon Aug 15 15:08:11 2016 -0700 summary: Add docs for typing.AnyStr and typing.Text. By Michael Lee. (Merge 3.5->3.6) ---------- resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 16 00:36:43 2016 From: report at bugs.python.org (Ben Finney) Date: Tue, 16 Aug 2016 04:36:43 +0000 Subject: [docs] [issue15660] Clarify 0 prefix for width specifier in str.format doc, In-Reply-To: <1345004440.11.0.680139192916.issue15660@psf.upfronthosting.co.za> Message-ID: <1471322203.25.0.162580999322.issue15660@psf.upfronthosting.co.za> Ben Finney added the comment: Terry Reedy wrote: > If the spec string is still available, it could be searched and the message adjusted if '=' is not present. That proposal should be a new issue if someone wants to push it. Done now, see Issue 27772. ---------- nosy: +bignose _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 16 15:28:55 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Tue, 16 Aug 2016 19:28:55 +0000 Subject: [docs] [issue27779] Sync-up docstrings in C version of the the decimal module Message-ID: <1471375735.77.0.977501297817.issue27779@psf.upfronthosting.co.za> New submission from Raymond Hettinger: The pure python version of decimal has extensive docstrings with text and explanatory examples drawn directly from the decimal arithmetic specification. Those should all be copied to the C version as well. This will improve usability for interactive use and improve help(). I would like to leave this work for one of the new aspiring core devs (perhaps Elizabeth, Lisa, or Nofar). ---------- assignee: docs at python components: Documentation keywords: easy messages: 272875 nosy: docs at python, rhettinger priority: normal severity: normal stage: needs patch status: open title: Sync-up docstrings in C version of the the decimal module versions: Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 16 15:55:23 2016 From: report at bugs.python.org (Stefan Krah) Date: Tue, 16 Aug 2016 19:55:23 +0000 Subject: [docs] [issue27779] Sync-up docstrings in C version of the the decimal module In-Reply-To: <1471375735.77.0.977501297817.issue27779@psf.upfronthosting.co.za> Message-ID: <1471377322.9.0.0210464326647.issue27779@psf.upfronthosting.co.za> Stefan Krah added the comment: I found the docstrings a bit too verbose (the power() docstring takes up more than a page), but I'm happy to add it and review a patch. The patch authors need to take the hand written function signatures into account. ---------- assignee: docs at python -> skrah nosy: +skrah _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 16 23:18:15 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Wed, 17 Aug 2016 03:18:15 +0000 Subject: [docs] [issue27779] Sync-up docstrings in C version of the the decimal module In-Reply-To: <1471375735.77.0.977501297817.issue27779@psf.upfronthosting.co.za> Message-ID: <1471403895.73.0.474233753237.issue27779@psf.upfronthosting.co.za> Raymond Hettinger added the comment: Historically, we've kept the docstrings 100% intact between the C and Python versions, even if they are big (see heapq.__doc__) for example. If there are differences in the "hand written" versions. I would like to have them compared on a case by case basis and resolved. Unless the C version implements something different, there should be no reason for a docstring difference. The originals are very close to the specification and to the documentation. We tried to stay true in part because there are so many niggling details that it would be hard to know without reading the spec. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 17 08:20:15 2016 From: report at bugs.python.org (STINNER Victor) Date: Wed, 17 Aug 2016 12:20:15 +0000 Subject: [docs] [issue10976] accept bytes in json.loads() In-Reply-To: <1295636509.41.0.0138366952356.issue10976@psf.upfronthosting.co.za> Message-ID: <1471436415.64.0.254996043288.issue10976@psf.upfronthosting.co.za> Changes by STINNER Victor : ---------- title: json.loads() raises TypeError on bytes object -> accept bytes in json.loads() _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 17 08:20:19 2016 From: report at bugs.python.org (STINNER Victor) Date: Wed, 17 Aug 2016 12:20:19 +0000 Subject: [docs] [issue10976] accept bytes in json.loads() In-Reply-To: <1295636509.41.0.0138366952356.issue10976@psf.upfronthosting.co.za> Message-ID: <1471436419.47.0.905731741033.issue10976@psf.upfronthosting.co.za> Changes by STINNER Victor : ---------- versions: +Python 3.6 -Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 17 08:28:10 2016 From: report at bugs.python.org (Antoine Pitrou) Date: Wed, 17 Aug 2016 12:28:10 +0000 Subject: [docs] [issue10976] accept bytes in json.loads() In-Reply-To: <1295636509.41.0.0138366952356.issue10976@psf.upfronthosting.co.za> Message-ID: <1471436890.72.0.356558769324.issue10976@psf.upfronthosting.co.za> Changes by Antoine Pitrou : ---------- nosy: -pitrou _______________________________________ Python tracker _______________________________________ From matthias.geier at gmail.com Fri Aug 12 13:51:37 2016 From: matthias.geier at gmail.com (Matthias Geier) Date: Fri, 12 Aug 2016 19:51:37 +0200 Subject: [docs] Superfluous dict() call in metaclass example? Message-ID: Dear list. Regarding this metaclass example: https://docs.python.org/3.6/reference/datamodel.html#metaclass-example It contains this line: result = type.__new__(cls, name, bases, dict(namespace)) I think the invocation of dict() here is superfluous and misleading. It's explained in the paragraph directly above this section: """ When a new class is created by type.__new__, the object provided as the namespace parameter is copied to a standard Python dictionary and the original object is discarded. The new copy becomes the __dict__ attribute of the class object. """ Since a copy is made anyway, what's the use of calling dict() on the OrderedDict instance? I tried running the code without dict() and it still seems to work fine. But maybe I'm wrong? cheers, Matthias From ashfaq at sustc.edu.cn Mon Aug 15 01:42:17 2016 From: ashfaq at sustc.edu.cn (=?utf-8?B?QXNoZmFxIEFobWFk?=) Date: Mon, 15 Aug 2016 13:42:17 +0800 Subject: [docs] Need Help Message-ID: Hello Dear, I am using Raccoon2 executed in MGLTools 1.5.7 rc1 and is using Python 2.7. I always face the following issue, i have searcher it too much but couldn't solve it. Can you help guide me. Exception in Tk callback Function: (type: ) Args: () Traceback (innermost last): File "/home/ash/mgltools_x86_64Linux2_1.5.7rc1/lib/python2.7/site-packages/Pmw/Pmw_1_3/lib/PmwBase.py", line 1747, in __call__ return apply(self.func, args) File "/home/ash/mgltools_x86_64Linux2_1.5.7rc1/MGLToolsPckgs/mglutil/util/callback.py", line 86, in __call__ return apply(self.function, args, kw) File "/home/ash/mgltools_x86_64Linux2_1.5.7rc1/MGLToolsPckgs/CADD/Raccoon2/gui/RaccoonProjManTree.py", line 1489, in _vs_download success = self.autoProcessResults(jobs = [ job ] ) File "/home/ash/mgltools_x86_64Linux2_1.5.7rc1/MGLToolsPckgs/CADD/Raccoon2/gui/RaccoonProjManTree.py", line 1606, in autoProcessResults processed = EF_resultprocessor.ProcessResultsGui(parent=self.parent, app=self.app, job=j, auto=True) File "/home/ash/mgltools_x86_64Linux2_1.5.7rc1/MGLToolsPckgs/CADD/Raccoon2/gui/EF_resultprocessor.py", line 105, in __init__ status = self.check() File "/home/ash/mgltools_x86_64Linux2_1.5.7rc1/MGLToolsPckgs/CADD/Raccoon2/gui/EF_resultprocessor.py", line 142, in check self.dprint("[%s|%s|%s] *CHECK FAIL* no ligands" % (self._current)) : not enough arguments for format string Regards, ------------------ Ashfaq Ahmad, PhD. Department of Biology, Faculty Research Building 1, South University of Science & Technology of China, Shenzhen. PR China. +86-1501-926-2786 -------------- next part -------------- An HTML attachment was scrubbed... URL: From donna.jean.peters at outlook.com Wed Aug 17 03:42:39 2016 From: donna.jean.peters at outlook.com (Donna Peters) Date: Wed, 17 Aug 2016 07:42:39 +0000 Subject: [docs] license Message-ID: Your licesne contradicts itself. In term 2 you grant derivative works and distribution rights with condition of copyright notice inclusion. In fact copyright notice inclusion in the derivative work is an option. You then in term 3 contradict the grant of term 2 by stating that the derivative work has to use the same license (which no one caring for consistency , accuracy and quite frankly the mental well being of others or in short anyone having any consideration or care for others would do.) 2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee ? prepare derivative works, distribute, .. provided, however, that PSF's License Agreement and PSF's notice of copyright, i.e., "Copyright ? 2001-2016 Python Software Foundation; All Rights Reserved" are retained in Python 2.7.12 alone or in any derivative version prepared by Licensee. 3. In the event Licensee prepares a derivative work that is based on or incorporates Python 2.7.12 or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python 2.7.12. I am looking for clarification simply because the gpl is a dirty license in every sense of the word that only the lowest and most despicable that agree with deceit and theft of others work promote and use and I am removing it from all my systems. I personally use BSD or MIT when I give things away. They are clear and honest. If I have expectations for return , I make that clear also and draw up licenses or agreements accordingly. Most good people I know and from whom I now obtain software do likewise. You can reply at spaesani at mail.com (I?m using a friend?s pc for this inquiry). PS : I authored the distributed (shared) cost license when I was 26 and hadn?t yet seen the (disgusting) gpl. No one can tell me honesty and fairness are not possible. With my license all this ?free? code would have been paid for and truly free a long long time ago without some group feigning moral superiority over others. Sent from Mail for Windows 10 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ArneMaximilian.Richter at baslerweb.com Wed Aug 17 05:41:18 2016 From: ArneMaximilian.Richter at baslerweb.com (Richter, Arne Maximilian) Date: Wed, 17 Aug 2016 09:41:18 +0000 Subject: [docs] Python Versions Message-ID: <6414cf3d154245a2b1d724b5d3e3969d@ahr206s.basler.corp> Hello, On the page https://docs.python.org/3/howto/pyporting.html for the version 3.5.2 and 3.6.0a4 is a mistake. The call "sys.version[0]" returns the version in form of a string and can therefore not be used in the way of "sys.version [0] == 3". This can be fixed by using "sys.version_info[0]" which returns the information's as number. Also are the information's not included in the 3.4 documentation, while older versions are correct. Yours sincerely, Arne M. Richter Arne Maximilian Richter Software Developer [BASLER-Logo_for_Signature] Basler AG An der Strusbek 60-62 22926 Ahrensburg Germany Tel. +49 4102 463 649 Fax +49 4102 463 46 649 ArneMaximilian.Richter at baslerweb.com www.baslerweb.com [http://baslerweb.com/baslermedia/socialmediaicons_email_signature/facebook_blue.gif] [http://baslerweb.com/baslermedia/socialmediaicons_email_signature/twitter_blue.gif] [http://baslerweb.com/baslermedia/socialmediaicons_email_signature/linkedin_blue.gif] [http://baslerweb.com/baslermedia/socialmediaicons_email_signature/kununu_blue.gif] [http://baslerweb.com/baslermedia/socialmediaicons_email_signature/youtube_blue.gif] [http://baslerweb.com/baslermedia/socialmediaicons_email_signature/xing_blue.gif] - Vorstand: Dr.-Ing. Dietmar Ley (Vorsitzender) * John P. Jennings * Arndt Bake * Hardy Mehl Aufsichtsratsvorsitzender: Norbert Basler Basler AG * Amtsgericht L?beck HRB 4090 * Ust-IdNr.: DE 135 098 121 * Steuer-Nr.: 30 292 04497 * WEEE-Reg.-Nr. DE 83888045 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jilin.Yang at arm.com Wed Aug 17 10:05:31 2016 From: Jilin.Yang at arm.com (Jilin Yang) Date: Wed, 17 Aug 2016 14:05:31 +0000 Subject: [docs] About unittest test case naming issue Message-ID: Hi, I checked that if I name a test case function as "case_one" within a unittest subclass, this test case won't be recognized when I try to run the script. (Using python 2.7) Is there anything mentioned in docs about it? Thanks! Br, Jilin IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zachary.ware+pydocs at gmail.com Wed Aug 17 10:53:36 2016 From: zachary.ware+pydocs at gmail.com (Zachary Ware) Date: Wed, 17 Aug 2016 09:53:36 -0500 Subject: [docs] Python Versions In-Reply-To: <6414cf3d154245a2b1d724b5d3e3969d@ahr206s.basler.corp> References: <6414cf3d154245a2b1d724b5d3e3969d@ahr206s.basler.corp> Message-ID: On Wed, Aug 17, 2016 at 4:41 AM, Richter, Arne Maximilian wrote: > Hello, > > On the page https://docs.python.org/3/howto/pyporting.html for the version > 3.5.2 and 3.6.0a4 is a mistake. The call ?sys.version[0]? returns the > version in form of a string and can therefore not be used in the way of > ?sys.version [0] == 3?. This can be fixed by using ?sys.version_info[0]? > which returns the information?s as number. Also are the information?s not > included in the 3.4 documentation, while older versions are correct. Thanks for the report! This has now been fixed. -- Zach From report at bugs.python.org Thu Aug 18 23:35:07 2016 From: report at bugs.python.org (bananaapple) Date: Fri, 19 Aug 2016 03:35:07 +0000 Subject: [docs] [issue22021] shutil.make_archive() root_dir do not work In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za> Message-ID: <1471577707.16.0.853967414033.issue22021@psf.upfronthosting.co.za> bananaapple added the comment: Sorry to bother. But This patch is still not accepted. I still suffer this issue. Is anyone willing to review this patch? Thanks ---------- nosy: +bananaapple _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 18 23:53:28 2016 From: report at bugs.python.org (bananaapple) Date: Fri, 19 Aug 2016 03:53:28 +0000 Subject: [docs] [issue22021] shutil.make_archive() root_dir do not work In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za> Message-ID: <1471578807.97.0.69022426187.issue22021@psf.upfronthosting.co.za> bananaapple added the comment: Or, Is there anything I could help? I am glad to help fixing this issue. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 00:47:52 2016 From: report at bugs.python.org (Berker Peksag) Date: Fri, 19 Aug 2016 04:47:52 +0000 Subject: [docs] [issue22021] shutil.make_archive() root_dir do not work In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za> Message-ID: <1471582072.45.0.170070294152.issue22021@psf.upfronthosting.co.za> Berker Peksag added the comment: Hi bananaapple, there are two things that need to be addressed: 1. We need to decide whether this is a bug in make_archive() implementation or not. See msg223572 and msg223668 for details. I personally agree with David's analysis in msg223668. We can rephrase make_archive() documentation to clarify what root_dir exactly does. 2. If this is a bug in make_archive() implementation, we need to add a test case. You can take a look at Lib/test/test_shutil.py. ---------- nosy: +berker.peksag _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 01:02:11 2016 From: report at bugs.python.org (Serhiy Storchaka) Date: Fri, 19 Aug 2016 05:02:11 +0000 Subject: [docs] [issue22021] shutil.make_archive() root_dir do not work In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za> Message-ID: <1471582931.82.0.198876011922.issue22021@psf.upfronthosting.co.za> Serhiy Storchaka added the comment: Agree with David, this is working as designed (and matching the behavior of say "tar -C"). But the documentation is not clear if not confusing. ---------- nosy: +serhiy.storchaka _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 01:17:29 2016 From: report at bugs.python.org (Berker Peksag) Date: Fri, 19 Aug 2016 05:17:29 +0000 Subject: [docs] [issue22021] shutil.make_archive() root_dir do not work In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za> Message-ID: <1471583849.08.0.65599418976.issue22021@psf.upfronthosting.co.za> Changes by Berker Peksag : ---------- versions: +Python 3.5, Python 3.6 -Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 01:21:08 2016 From: report at bugs.python.org (bananaapple) Date: Fri, 19 Aug 2016 05:21:08 +0000 Subject: [docs] [issue22021] shutil.make_archive() root_dir do not work In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za> Message-ID: <1471584068.52.0.0249135026473.issue22021@psf.upfronthosting.co.za> bananaapple added the comment: Hello Berker Peksag, 1. For now, I realize the comment of David. This is not a bug of make_archive() implementation. However, I think documentation is not clear to understand at the first time reading it. Maybe it should be rephrased. 2. Actually, what I am looking in this function is able to output the archive to another directory rather than current directory. But, this functionality is not provided. I think this functionality will be useful if implemented. What do you think about this? Thank you for your explaination. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 02:56:26 2016 From: report at bugs.python.org (Martin Panter) Date: Fri, 19 Aug 2016 06:56:26 +0000 Subject: [docs] [issue26050] Add new StreamReader.readuntil() method In-Reply-To: <1452285476.14.0.419432816204.issue26050@psf.upfronthosting.co.za> Message-ID: <1471589786.28.0.0426056892213.issue26050@psf.upfronthosting.co.za> Martin Panter added the comment: In revision 83450939b106, Yury added some documentation for readuntil(). I am not familiar with this StreamReader class, but maybe Mark or someone else can check if the remaining changes in his patch are still useful. I can suggest some spelling and wording fixes however. Bits in square brackets are my changes. ## read(n=-1): If *n* is zero, return [an] empty ``bytes`` object [immediately (single L)]. If *n* is positive, this function [tries] to read *n* bytes, [but may return less]. If EOF was received before any byte is read, this function returns [an] empty [bytes] object[, otherwise it returns at least one byte]. [The] returned value is not limited [by] [*limit* (add asterisks)], . . . If [the] stream was paused, . . . ## readline(): Read [] from the stream until [a] newline (``b'\n'``) is found. On success, return [the line, which] ends with [a] newline. If only [a] partial line can be read due to EOF, return [an] incomplete line without terminating newline. When EOF was reached [and] no bytes [were] read, [an] empty ``bytes`` object is returned. If [*limit* (add asterisks)] is reached, ValueError will be raised. In that case, if [a] newline was found, [the] complete line including newline will be removed from [the] internal buffer. [Otherwise, the] internal buffer will be cleared. [*Limit* (add asterisks)] is compared against [the length] of the line[, not counting the] newline. If [the] stream was paused, . . . ## readexactly(n): If *n* is zero, return [an] empty bytes object. [The] returned value is not limited by [*limit* (add asterisks)], . . . If [the] stream was paused, . . . ## readuntil(separator=b'\n'): Read [] from the stream until *separator* is found. On success, [the] chunk [of data] and its separator will be removed from [the] internal buffer (i.e. consumed). [The] returned chunk will include [the] separator at the end. [The] configured stream limit is used to [limit the] result. [*Limit* (add asterisks)] means [the maximum] length of [the] chunk . . . If EOF occurs and [a] complete separator [is] still not found, :exc:`IncompleteReadError`(, None) will be raised and [the] internal buffer becomes empty. . . . If [the] chunk cannot be read due to [the] limit, :exc:`LimitOverrunError` will be raised and data will be left in [the] internal buffer, . . . If [the] stream was paused, . . . ---------- assignee: -> docs at python components: +Documentation nosy: +docs at python, martin.panter stage: -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 03:33:57 2016 From: report at bugs.python.org (Martin Panter) Date: Fri, 19 Aug 2016 07:33:57 +0000 Subject: [docs] [issue26050] Add new StreamReader.readuntil() method In-Reply-To: <1452285476.14.0.419432816204.issue26050@psf.upfronthosting.co.za> Message-ID: <1471592037.09.0.658719339544.issue26050@psf.upfronthosting.co.za> Martin Panter added the comment: Also it looks like the b'\n' default confuses Sphinx. Maybe it needs extra escaping? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 04:51:51 2016 From: report at bugs.python.org (Roundup Robot) Date: Fri, 19 Aug 2016 08:51:51 +0000 Subject: [docs] [issue12946] PyModule_GetDict() claims it can never fail, but it can In-Reply-To: <1315585192.34.0.742122652176.issue12946@psf.upfronthosting.co.za> Message-ID: <20160819085141.24558.55486.C30460E6@psf.io> Roundup Robot added the comment: New changeset bd2a4c138b76 by Berker Peksag in branch '3.5': Issue #12946: Document that PyModule_GetDict can fail in some cases https://hg.python.org/cpython/rev/bd2a4c138b76 New changeset c2e74b88947d by Berker Peksag in branch 'default': Issue #12946: Merge from 3.5 https://hg.python.org/cpython/rev/c2e74b88947d ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 04:59:40 2016 From: report at bugs.python.org (Roundup Robot) Date: Fri, 19 Aug 2016 08:59:40 +0000 Subject: [docs] [issue12946] PyModule_GetDict() claims it can never fail, but it can In-Reply-To: <1315585192.34.0.742122652176.issue12946@psf.upfronthosting.co.za> Message-ID: <20160819085936.31581.57657.3F4F8BED@psf.io> Roundup Robot added the comment: New changeset 4b64a049f451 by Berker Peksag in branch 'default': Issue #12946: Remove dead code in PyModule_GetDict https://hg.python.org/cpython/rev/4b64a049f451 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 05:00:00 2016 From: report at bugs.python.org (Berker Peksag) Date: Fri, 19 Aug 2016 09:00:00 +0000 Subject: [docs] [issue12946] PyModule_GetDict() claims it can never fail, but it can In-Reply-To: <1315585192.34.0.742122652176.issue12946@psf.upfronthosting.co.za> Message-ID: <1471597200.88.0.334367264619.issue12946@psf.upfronthosting.co.za> Changes by Berker Peksag : ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 05:00:17 2016 From: report at bugs.python.org (Berker Peksag) Date: Fri, 19 Aug 2016 09:00:17 +0000 Subject: [docs] [issue12946] PyModule_GetDict() claims it can never fail, but it can In-Reply-To: <1315585192.34.0.742122652176.issue12946@psf.upfronthosting.co.za> Message-ID: <1471597217.92.0.3195506604.issue12946@psf.upfronthosting.co.za> Berker Peksag added the comment: Thanks for the report, Stefan! ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 10:50:34 2016 From: report at bugs.python.org (R. David Murray) Date: Fri, 19 Aug 2016 14:50:34 +0000 Subject: [docs] [issue22021] shutil.make_archive() root_dir do not work In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za> Message-ID: <1471618234.04.0.361277457914.issue22021@psf.upfronthosting.co.za> R. David Murray added the comment: "base_name is the name of the file to create, including the path". So you should be able to specify the path to where you want it created. If that doesn't work, that's a bug. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 10:53:30 2016 From: report at bugs.python.org (Xiang Zhang) Date: Fri, 19 Aug 2016 14:53:30 +0000 Subject: [docs] [issue27740] Fix doc of Py_CompileStringExFlags In-Reply-To: <1470939203.79.0.619794104629.issue27740@psf.upfronthosting.co.za> Message-ID: <1471618410.55.0.361023383489.issue27740@psf.upfronthosting.co.za> Xiang Zhang added the comment: Ping. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 11:45:35 2016 From: report at bugs.python.org (Berker Peksag) Date: Fri, 19 Aug 2016 15:45:35 +0000 Subject: [docs] [issue27740] Fix doc of Py_CompileStringExFlags In-Reply-To: <1470939203.79.0.619794104629.issue27740@psf.upfronthosting.co.za> Message-ID: <1471621535.71.0.546849159861.issue27740@psf.upfronthosting.co.za> Berker Peksag added the comment: I don't understand the second part of the patch. *filename* is a filesystem encoding (:func:`os.fsdecode`) encoded string [...] Do you want to document that filename should be encoded by using PyUnicode_EncodeFSDefault *before* passing it to Py_CompileStringExFlags (you will probably need to wrap it with something like PyBytes_AsString too)? If so, I think the os.fsdecode() part needs to be changed to os.fsencode(). I think the current wording is saying that filename is going to be decoded inside of Py_CompileStringExFlags (which is also correct.) ---------- nosy: +berker.peksag, haypo stage: -> patch review versions: +Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 11:55:38 2016 From: report at bugs.python.org (Xiang Zhang) Date: Fri, 19 Aug 2016 15:55:38 +0000 Subject: [docs] [issue27740] Fix doc of Py_CompileStringExFlags In-Reply-To: <1470939203.79.0.619794104629.issue27740@psf.upfronthosting.co.za> Message-ID: <1471622138.29.0.706692992163.issue27740@psf.upfronthosting.co.za> Xiang Zhang added the comment: > filename is going to be decoded inside of Py_CompileStringExFlags Actually all I want to express is this, *filename* will be decoded inside. But now the wording looks to me is that *filename* is already a decoded string when passed. I don't want to document anything about PyUnicode_EncodeFSDefault. I should remove (:func:`os.fsdecode`). How do you think? I'm Okay if you think the current wording is correct. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 19 21:35:27 2016 From: report at bugs.python.org (bananaapple) Date: Sat, 20 Aug 2016 01:35:27 +0000 Subject: [docs] [issue22021] shutil.make_archive() root_dir do not work In-Reply-To: <1405936213.68.0.143186152462.issue22021@psf.upfronthosting.co.za> Message-ID: <1471656927.69.0.780185568045.issue22021@psf.upfronthosting.co.za> bananaapple added the comment: I am sorry. I understand now. Thank you. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 20 01:49:05 2016 From: report at bugs.python.org (Caleb Hattingh) Date: Sat, 20 Aug 2016 05:49:05 +0000 Subject: [docs] [issue12982] Document that importing .pyo files needs python -O In-Reply-To: <1316032363.3.0.192750692303.issue12982@psf.upfronthosting.co.za> Message-ID: <1471672145.75.0.702544252073.issue12982@psf.upfronthosting.co.za> Caleb Hattingh added the comment: Presumably PEP488 (and the 4 years of inactivity) means that this issue could be closed? ---------- nosy: +cjrh _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 20 04:11:42 2016 From: report at bugs.python.org (Roundup Robot) Date: Sat, 20 Aug 2016 08:11:42 +0000 Subject: [docs] [issue12982] Document that importing .pyo files needs python -O In-Reply-To: <1316032363.3.0.192750692303.issue12982@psf.upfronthosting.co.za> Message-ID: <20160820081139.2362.63929.5E572D96@psf.io> Roundup Robot added the comment: New changeset 8e9dc3e4ea91 by Berker Peksag in branch '3.5': Issue #12982: Thanks to PEP 488, Python no longer creates .pyo files https://hg.python.org/cpython/rev/8e9dc3e4ea91 New changeset 1455851e7332 by Berker Peksag in branch 'default': Issue #12982: Merge from 3.5 https://hg.python.org/cpython/rev/1455851e7332 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 20 04:13:39 2016 From: report at bugs.python.org (Berker Peksag) Date: Sat, 20 Aug 2016 08:13:39 +0000 Subject: [docs] [issue12982] Document that importing .pyo files needs python -O In-Reply-To: <1316032363.3.0.192750692303.issue12982@psf.upfronthosting.co.za> Message-ID: <1471680819.23.0.0401690836388.issue12982@psf.upfronthosting.co.za> Berker Peksag added the comment: Yes, this can be closed as 'out of date'. I've just updated -O documentation to remove the mention of .pyo extension. Thanks! ---------- nosy: +berker.peksag resolution: -> out of date stage: needs patch -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 20 20:14:56 2016 From: report at bugs.python.org (Scott Macpherson) Date: Sun, 21 Aug 2016 00:14:56 +0000 Subject: [docs] [issue12594] Docs for "Using Python on a Macintosh" needs to be updated In-Reply-To: <1311174057.47.0.56455855185.issue12594@psf.upfronthosting.co.za> Message-ID: <1471738496.08.0.0558426192782.issue12594@psf.upfronthosting.co.za> Changes by Scott Macpherson : ---------- nosy: +macpherson.scott _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 20 20:24:43 2016 From: report at bugs.python.org (Scott Macpherson) Date: Sun, 21 Aug 2016 00:24:43 +0000 Subject: [docs] [issue12594] Docs for "Using Python on a Macintosh" needs to be updated In-Reply-To: <1311174057.47.0.56455855185.issue12594@psf.upfronthosting.co.za> Message-ID: <1471739081.91.0.552864460895.issue12594@psf.upfronthosting.co.za> Scott Macpherson added the comment: I'd like to help out with this issue if I can. This page in the documentation is really showing it's age now. * I think referring to "OS X" (soon to be "MacOS") instead of "Mac" or "Macintosh" would more accurate. * The opening paragraph of section 4.1 only refers to OS X 10.8, which was released over 4 years ago. * Is there any value in listing text editors in section 4.1.1? Editors frequently come-and-go. * I suspect a large number of Python 3 developers running OS X use http://brew.sh/ - would it be worth mentioning this somewhere? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 21 13:07:12 2016 From: report at bugs.python.org (Joshua Haas) Date: Sun, 21 Aug 2016 17:07:12 +0000 Subject: [docs] [issue27824] update ConfigParser docs regarding in-line comments Message-ID: <1471799232.17.0.640576355958.issue27824@psf.upfronthosting.co.za> New submission from Joshua Haas: Originally reported at http://bugs.python.org/issue27762 as a behavior bug but was determined to be won't fix. Thus I think this needs to be mentioned in the documentation at https://docs.python.org/2/library/configparser.html I propose that directly after the following: "(For backwards compatibility, only ; starts an inline comment, while # does not.)" be added: "Inline comments will not be recognised in lines that contain ; before the comment itself. To ensure that inline comments work as expected, do not use ; in config values." ---------- assignee: docs at python components: Documentation messages: 273306 nosy: docs at python, jahschwa priority: normal severity: normal status: open title: update ConfigParser docs regarding in-line comments type: enhancement versions: Python 2.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 21 16:56:47 2016 From: report at bugs.python.org (Ned Batchelder) Date: Sun, 21 Aug 2016 20:56:47 +0000 Subject: [docs] [issue27825] Make the documentation for statistics' data argument clearer. Message-ID: <1471813007.76.0.49945343113.issue27825@psf.upfronthosting.co.za> New submission from Ned Batchelder: The docs for statistics.mean say, "Return the sample arithmetic mean of data, a sequence or iterator of real-valued numbers." Most of the functions in statistics have a `data` argument, but this function is the only one that says, "a sequence or iterator." The examples all show lists. The page would be better if the introduction mentioned what `data` could be, instead of having to guess that median can take an iterator because mean says that it can. ---------- assignee: docs at python components: Documentation messages: 273318 nosy: docs at python, nedbat priority: normal severity: normal status: open title: Make the documentation for statistics' data argument clearer. _______________________________________ Python tracker _______________________________________ From alexandre at harano.net.br Sun Aug 21 00:23:56 2016 From: alexandre at harano.net.br (Alexandre Y. Harano) Date: Sun, 21 Aug 2016 01:23:56 -0300 Subject: [docs] Unable to download PDF (A4 paper size) for Python 3.4.5 Documentation Message-ID: Hello there. I opened the URL listing the offline versions for Python 3.4 https://docs.python.org/3.4/download.html However, both versions for PDF (A4 paper size) ("Packed as .zip" - https://docs.python.org/ftp/python/doc/3.4.5/python-3.4.5-docs-pdf-a4.zip - and - "Packed as .tar.bz2" - https://docs.python.org/ftp/python/doc/3.4.5/python-3.4.5-docs-pdf-a4.tar.bz2 ) gave me 404 errors. Thank you very much for your attention. Alexandre Harano. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pecharters at gmail.com Thu Aug 18 17:54:12 2016 From: pecharters at gmail.com (P E Charters) Date: Thu, 18 Aug 2016 17:54:12 -0400 Subject: [docs] Problems downloading documentation Message-ID: <5BEF3407-6C77-4D73-B3DD-7C066DC6AFBA@gmail.com> Any attempt to download documentation for Python 3.4.5 fails with a ?404 Not Found?. Is this a temporary glitch? Pete From sirarchitect1 at gmail.com Fri Aug 19 14:54:35 2016 From: sirarchitect1 at gmail.com (Lu Jeweler) Date: Fri, 19 Aug 2016 13:54:35 -0500 Subject: [docs] hey the links are broken 3.45 documentation download Message-ID: hey the links to the documentation download 3.4.5 is broken. I would love to have the documentation. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From report at bugs.python.org Mon Aug 22 09:48:09 2016 From: report at bugs.python.org (R. David Murray) Date: Mon, 22 Aug 2016 13:48:09 +0000 Subject: [docs] [issue27824] update ConfigParser docs regarding in-line comments In-Reply-To: <1471799232.17.0.640576355958.issue27824@psf.upfronthosting.co.za> Message-ID: <1471873689.19.0.24866293391.issue27824@psf.upfronthosting.co.za> R. David Murray added the comment: Alternate proposal. Replace that whole paragraph with: Configuration files may include comments, prefixed by specific characters (# and ;). Comments may appear on their own in an otherwise empty line. If a line has a value or section name that does not include a ';', an inline comment can be added by entering at least one space followed by a ';' and the comment. While supported, inline comments are fragile in the face of values that may contain ';'s, and thus are not recommended. Of course, I'm making a (new) value judgement in that last sentence so lukasz may override me :) ---------- nosy: +lukasz.langa, r.david.murray _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 22 09:50:12 2016 From: report at bugs.python.org (R. David Murray) Date: Mon, 22 Aug 2016 13:50:12 +0000 Subject: [docs] [issue27824] update ConfigParser docs regarding in-line comments In-Reply-To: <1471799232.17.0.640576355958.issue27824@psf.upfronthosting.co.za> Message-ID: <1471873812.79.0.687351495051.issue27824@psf.upfronthosting.co.za> R. David Murray added the comment: The python3 docs do not mention inline comments. Perhaps we even want a documented deprecation here? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 22 18:48:28 2016 From: report at bugs.python.org (Joshua Haas) Date: Mon, 22 Aug 2016 22:48:28 +0000 Subject: [docs] [issue27824] update ConfigParser docs regarding in-line comments In-Reply-To: <1471799232.17.0.640576355958.issue27824@psf.upfronthosting.co.za> Message-ID: <1471906107.99.0.0256021186337.issue27824@psf.upfronthosting.co.za> Joshua Haas added the comment: I'm not sure it's deprecated so much as moved. Python 3.5 includes an additional init parameter, so setting inline_comment_prefixes=';' allows inline comments even for values containing the ';' character, displaying the "expected behavior" described in my original bug report. They are, however, disabled by default, unlike in Python 2.7. I also have a different proposal I think might be more clear: Configuration files may include comments, prefixed by specific characters. Comments may appear on their own in an otherwise empty line using either '#' or ';'. In addition, inline comments can be added to the end of a line after a ';' as long as the ';' is preceded by a whitespace character. Only the first ';' in a line is checked, so an inline comment cannot be added to lines that already contain any ';'s. I'm also wondering if an example would be a good idea, as I don't think any of the examples on the doc page include comments: # this is a comment ; this is also a comment foo = bar ; inline comment password = jgfw;as1 ; this will be parsed as part of 'password' ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 23 08:22:13 2016 From: report at bugs.python.org (Niko Yasui) Date: Tue, 23 Aug 2016 12:22:13 +0000 Subject: [docs] [issue27837] Logging Cookbook Improvement Message-ID: <1471954933.3.0.792473866028.issue27837@psf.upfronthosting.co.za> New submission from Niko Yasui: Removed the unnecessary listener function and changed the worker loggers from root to children. Also replaced print statements with logging statements and a stdout handler to illustrate the usefulness of handler levels. This version also doesn't require a manual listener process or thread, since it's all handled by the interpreter in the background. As far as I know, it's just a one-line change from multiprocessing to threading, so it should be easy to adapt this example to improve the threading example as well. The previous example was hard for me to understand, and when I integrated it to my code, printed duplicates of every log item to all my handlers (including stdout) even though I hadn't added a stdout handler. Evidently this was my fault, since the original example code doesn't do that, but this updated code should be cleaner and easier to understand to avoid such integration problems in the first place. I hope it is a worthy contribution the docs. Feel free to provide any tips to improve it. ---------- assignee: docs at python components: Documentation files: multi_log_cookbook.py messages: 273437 nosy: Niko Yasui, docs at python priority: normal severity: normal status: open title: Logging Cookbook Improvement type: enhancement versions: Python 3.5 Added file: http://bugs.python.org/file44198/multi_log_cookbook.py _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 23 09:48:59 2016 From: report at bugs.python.org (Jakub Wilk) Date: Tue, 23 Aug 2016 13:48:59 +0000 Subject: [docs] [issue27839] "Python [...] calls sys.displayhook() on unhandled exceptions" Message-ID: <1471960139.35.0.924295727518.issue27839@psf.upfronthosting.co.za> New submission from Jakub Wilk: reads: "Python usually calls sys.displayhook() on unhandled exceptions. If Future.set_exception() is called, but the exception is never consumed, sys.displayhook() is not called." I believe this should be s/displayhook/excepthook/g. ---------- assignee: docs at python components: Documentation messages: 273446 nosy: docs at python, jwilk priority: normal severity: normal status: open title: "Python [...] calls sys.displayhook() on unhandled exceptions" _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 23 09:52:57 2016 From: report at bugs.python.org (R. David Murray) Date: Tue, 23 Aug 2016 13:52:57 +0000 Subject: [docs] [issue27837] Logging Cookbook Improvement In-Reply-To: <1471954933.3.0.792473866028.issue27837@psf.upfronthosting.co.za> Message-ID: <1471960377.02.0.716485913672.issue27837@psf.upfronthosting.co.za> R. David Murray added the comment: Can you provide this change as a diff, please? (See docs.python.org/devguide for information on generating reviewable patches). ---------- nosy: +r.david.murray, vinay.sajip _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 23 10:31:31 2016 From: report at bugs.python.org (Vinay Sajip) Date: Tue, 23 Aug 2016 14:31:31 +0000 Subject: [docs] [issue27837] Logging Cookbook Improvement In-Reply-To: <1471954933.3.0.792473866028.issue27837@psf.upfronthosting.co.za> Message-ID: <1471962691.79.0.560299597404.issue27837@psf.upfronthosting.co.za> Vinay Sajip added the comment: I specifically wanted to illustrate a separate listener process - the purpose here is not to show what might be the most efficient code, but to show communication via a queue between listener process and worker processes. You've removed this, which defeats the object of this example (for example, there's no QueueListener in your version). So I wouldn't want to implement your proposed change in its current form. Just to clarify, a diff of the cookbook ought to be a diff of the .rst file rather than just a changed code example within it - a direct comparison needs to be possible in order to see the changes easily in a side-by-side view. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 23 10:37:06 2016 From: report at bugs.python.org (Steven D'Aprano) Date: Tue, 23 Aug 2016 14:37:06 +0000 Subject: [docs] [issue27825] Make the documentation for statistics' data argument clearer. In-Reply-To: <1471813007.76.0.49945343113.issue27825@psf.upfronthosting.co.za> Message-ID: <1471963026.32.0.814999518142.issue27825@psf.upfronthosting.co.za> Changes by Steven D'Aprano : ---------- assignee: docs at python -> steven.daprano nosy: +steven.daprano _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 23 12:02:23 2016 From: report at bugs.python.org (Niko Yasui) Date: Tue, 23 Aug 2016 16:02:23 +0000 Subject: [docs] [issue27837] Logging Cookbook Improvement In-Reply-To: <1471954933.3.0.792473866028.issue27837@psf.upfronthosting.co.za> Message-ID: <1471968143.09.0.101283992279.issue27837@psf.upfronthosting.co.za> Niko Yasui added the comment: Thank you both for the helpful comments. Vinay, since you want to illustrate a listener process in the multiprocessing example, why not include a shorter, simpler example beforehand? This is my first time using logging, and it took me multiple hours to figure out what your example was doing and which parts were extra. Since a queue isn't necessary for logging with multiprocessing, I did my best to write a shorter example to introduce the concept before exploring your code with the listener. What do you think about this addition? ---------- keywords: +patch Added file: http://bugs.python.org/file44201/mp_log_cookbook.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 23 12:31:56 2016 From: report at bugs.python.org (Vinay Sajip) Date: Tue, 23 Aug 2016 16:31:56 +0000 Subject: [docs] [issue27837] Logging Cookbook Improvement In-Reply-To: <1471954933.3.0.792473866028.issue27837@psf.upfronthosting.co.za> Message-ID: <1471969916.7.0.528090310472.issue27837@psf.upfronthosting.co.za> Vinay Sajip added the comment: > Since a queue isn't necessary for logging with multiprocessing IMO a queue with QueueHandler/QueueListener is best practice when working with multiprocessing and logging. If you don't use them, things may seem to work some of the time but could fail in certain scenarios. For example, multiprocessing works differently on different platforms such as POSIX and Windows, which can lead to problems with simpler approaches. There are plenty of simpler examples in the logging tutorial and cookbook, which might be worth reviewing first if you are new to logging in Python. See this post for a discussion on using logging with multiprocessing: https://plumberjack.blogspot.co.uk/2010/09/using-logging-with-multiprocessing.html This was the original source of the example in the cookbook. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 23 20:44:53 2016 From: report at bugs.python.org (Roundup Robot) Date: Wed, 24 Aug 2016 00:44:53 +0000 Subject: [docs] [issue25916] wave module readframes now returns bytes not str In-Reply-To: <1450607471.45.0.396609211559.issue25916@psf.upfronthosting.co.za> Message-ID: <20160824004448.63928.23201.2667F340@psf.io> Roundup Robot added the comment: New changeset 7ac8e8568da2 by R David Murray in branch '3.5': #25916: fix a few 'string of bytes' references. https://hg.python.org/cpython/rev/7ac8e8568da2 New changeset 089f7d761a9c by R David Murray in branch 'default': Merge: #25916: fix a few 'string of bytes' references. https://hg.python.org/cpython/rev/089f7d761a9c ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 23 20:45:39 2016 From: report at bugs.python.org (R. David Murray) Date: Wed, 24 Aug 2016 00:45:39 +0000 Subject: [docs] [issue25916] wave module readframes now returns bytes not str In-Reply-To: <1450607471.45.0.396609211559.issue25916@psf.upfronthosting.co.za> Message-ID: <1471999539.35.0.473057162183.issue25916@psf.upfronthosting.co.za> R. David Murray added the comment: Thanks SilentGhost. ---------- resolution: -> fixed stage: commit review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 23 20:52:30 2016 From: report at bugs.python.org (R. David Murray) Date: Wed, 24 Aug 2016 00:52:30 +0000 Subject: [docs] [issue23183] timeit CLI best of 3: undocumented output format In-Reply-To: <1420620799.47.0.00516438922368.issue23183@psf.upfronthosting.co.za> Message-ID: <1471999950.18.0.247130941779.issue23183@psf.upfronthosting.co.za> R. David Murray added the comment: I think the use of "timing loop" is very confusing, since the word 'loop' refers to one execution of the statement body in the actual output text. What about calling it a 'timing run'? It looks like whatever we come up with should be applied to 3.5 and 3.6 as well. ---------- nosy: +r.david.murray stage: commit review -> needs patch versions: +Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 23 20:54:39 2016 From: report at bugs.python.org (Niko Yasui) Date: Wed, 24 Aug 2016 00:54:39 +0000 Subject: [docs] [issue27837] Logging Cookbook Improvement In-Reply-To: <1471954933.3.0.792473866028.issue27837@psf.upfronthosting.co.za> Message-ID: <1472000079.19.0.130910783388.issue27837@psf.upfronthosting.co.za> Changes by Niko Yasui : Removed file: http://bugs.python.org/file44198/multi_log_cookbook.py _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 23 20:56:16 2016 From: report at bugs.python.org (Niko Yasui) Date: Wed, 24 Aug 2016 00:56:16 +0000 Subject: [docs] [issue27837] Logging Cookbook Improvement In-Reply-To: <1471954933.3.0.792473866028.issue27837@psf.upfronthosting.co.za> Message-ID: <1472000176.09.0.936157002072.issue27837@psf.upfronthosting.co.za> Niko Yasui added the comment: I see, I didn't realize that the simpler code would break under certain conditions. While there are definitely simpler examples in other documents, I haven't been able to find any indication that there is a simpler way to do multiprocessing and logging together, either on StackOverflow or the Python docs, other than by stumbling into it accidentally while writing code for this thread. Since multiprocessing in Python usually requires some extra work-arounds compared to single processing solutions, I searched specifically for multiprocessing logging options. I was also not surprised that I needed a queue, since multiprocessing is complicated. IMO the docs would be more clear if there was either a simpler example with a caveat that it wouldn't work in windows, or with a small paragraph saying that after 3.2, using logging as if it were on a single process would not cause problems. Just to clarify, my understanding is that the child loggers on separate processes pass records to the main logger, which runs on the original process, which then handles the records and writes to a file. In this way there is no problem of simultaneously writing to the same file. Is the above correct for the code I wrote? Thanks for your patience with my inexperience. It's been a long time since I've spent so much time on learning a new module, and I think improving the docs will help other people avoid spending so much time. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 24 05:25:37 2016 From: report at bugs.python.org (=?utf-8?q?Jens_J=C3=B8rgen_Mortensen?=) Date: Wed, 24 Aug 2016 09:25:37 +0000 Subject: [docs] [issue27846] Base64 expansion factor is 4 to 3, not 6 to 4 Message-ID: <1472030737.8.0.133776759316.issue27846@psf.upfronthosting.co.za> New submission from Jens J?rgen Mortensen: The documentation has a note saying: "Base64 has an expansion factor of 6 to 4". I believe it should be 4 to 3. https://docs.python.org/dev/library/base64.html ---------- assignee: docs at python components: Documentation messages: 273543 nosy: Jens.J?rgen.Mortensen, docs at python priority: normal severity: normal status: open title: Base64 expansion factor is 4 to 3, not 6 to 4 type: enhancement versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 24 08:46:48 2016 From: report at bugs.python.org (R. David Murray) Date: Wed, 24 Aug 2016 12:46:48 +0000 Subject: [docs] [issue27846] Base64 expansion factor is 4 to 3, not 6 to 4 In-Reply-To: <1472030737.8.0.133776759316.issue27846@psf.upfronthosting.co.za> Message-ID: <1472042808.18.0.182576402573.issue27846@psf.upfronthosting.co.za> R. David Murray added the comment: Maybe we should just drop that note. To achieve any sort of clarity we'd have to say that base85 is 15 for 12 and base64 is 16 for 12. And putting it that way it doesn't seem like all that much of an advantage :) ---------- nosy: +r.david.murray versions: +Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 24 08:53:46 2016 From: report at bugs.python.org (Vinay Sajip) Date: Wed, 24 Aug 2016 12:53:46 +0000 Subject: [docs] [issue27837] Logging Cookbook Improvement In-Reply-To: <1471954933.3.0.792473866028.issue27837@psf.upfronthosting.co.za> Message-ID: <1472043226.68.0.0959952563335.issue27837@psf.upfronthosting.co.za> Vinay Sajip added the comment: The thing about queues does not relate just to logging - it relates to all communication between different multiprocessing processes, of which logging is just an example. The logging cookbook is not the place to provide tutorial information on e.g. multi-threading or multiprocessing and the various gotchas that can cause problems (e.g. the state of threading locks after fork). Whole books could be written about this stuff, and no doubt have been. > Just to clarify, my understanding is that the child loggers on separate processes pass records to the main logger No, you're mixing up loggers and handlers. Look at the basic and advanced tutorial in the stdlib docs, and e.g. https://plumberjack.blogspot.co.uk/2009/09/python-logging-101.html to get an idea of the difference between them. The other posts on that site are also worth looking at, though many of those posts have been incorporated into the logging cookbook over time. > Thanks for your patience with my inexperience. You're welcome. If further discussion is needed, it's best to continue it on e.g. Stack Overflow or the python-list mailing list. ---------- resolution: -> wont fix stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 24 11:55:30 2016 From: report at bugs.python.org (R. David Murray) Date: Wed, 24 Aug 2016 15:55:30 +0000 Subject: [docs] [issue19489] move quick search box above TOC In-Reply-To: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za> Message-ID: <1472054130.34.0.258342941346.issue19489@psf.upfronthosting.co.za> R. David Murray added the comment: Moving back to patch review for someone to sign off on the changes. ---------- nosy: +r.david.murray stage: commit review -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 24 12:50:47 2016 From: report at bugs.python.org (Roundup Robot) Date: Wed, 24 Aug 2016 16:50:47 +0000 Subject: [docs] [issue20124] The documentation for the atTime parameter of TimedRotatimeFileHandler is confusing In-Reply-To: <1388879336.03.0.25076651665.issue20124@psf.upfronthosting.co.za> Message-ID: <20160824164923.24131.55148.7EC0D657@psf.io> Roundup Robot added the comment: New changeset 8d13c1f33d21 by Vinay Sajip in branch 'default': Closes #20124: clarified usage of the atTime parameter in TimedRotatingFileHandler documentation. https://hg.python.org/cpython/rev/8d13c1f33d21 ---------- nosy: +python-dev resolution: -> fixed stage: needs patch -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 24 13:09:20 2016 From: report at bugs.python.org (Vinay Sajip) Date: Wed, 24 Aug 2016 17:09:20 +0000 Subject: [docs] [issue19504] Change "customise" to "customize". In-Reply-To: <1383659200.62.0.979344465483.issue19504@psf.upfronthosting.co.za> Message-ID: <1472058560.95.0.0415455416816.issue19504@psf.upfronthosting.co.za> Changes by Vinay Sajip : ---------- nosy: -vinay.sajip _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 24 16:18:53 2016 From: report at bugs.python.org (Terry J. Reedy) Date: Wed, 24 Aug 2016 20:18:53 +0000 Subject: [docs] [issue26638] Avoid warnings about missing CLI options when building documentation In-Reply-To: <1458881380.09.0.599104229044.issue26638@psf.upfronthosting.co.za> Message-ID: <1472069933.83.0.453472828517.issue26638@psf.upfronthosting.co.za> Terry J. Reedy added the comment: I built the 3.5 docs on Win10 with Sphinx 1.3.3 and corresponding dependencies and got a new warning as a result of 8ba0000c90be for #26462: F:\Python\dev\36\Doc\whatsnew\3.2.rst:2063: WARNING: Pygments lexer name 'doscon' is not known Thinking the problem was an out-of-date pygments module, I updated sphinx and dependencies (to 1.4.6, etc). I was right that updating pygments fixed the warning above, but now I get 140 warnings!!! 4 are from the reading phase for configparser.rst. The first: F:\Python\dev\35\Doc\library\configparser.rst:240: WARNING: Could not lex literal_block as "ini". Highlighting skipped. I presume this could be fixed, but I don't know how. 136 are about " _______________________________________ From report at bugs.python.org Wed Aug 24 16:33:25 2016 From: report at bugs.python.org (Zachary Ware) Date: Wed, 24 Aug 2016 20:33:25 +0000 Subject: [docs] [issue26638] Avoid warnings about missing CLI options when building documentation In-Reply-To: <1458881380.09.0.599104229044.issue26638@psf.upfronthosting.co.za> Message-ID: <1472070804.95.0.799079642636.issue26638@psf.upfronthosting.co.za> Zachary Ware added the comment: Terry: for now, you can downgrade Sphinx to 1.3.6 as it is known to build with no warnings (that's the version the Docs buildbot currently uses). ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 24 17:39:51 2016 From: report at bugs.python.org (Terry J. Reedy) Date: Wed, 24 Aug 2016 21:39:51 +0000 Subject: [docs] [issue26638] Avoid warnings about missing CLI options when building documentation In-Reply-To: <1458881380.09.0.599104229044.issue26638@psf.upfronthosting.co.za> Message-ID: <1472074791.36.0.876057419364.issue26638@psf.upfronthosting.co.za> Terry J. Reedy added the comment: Only 138 warnings with 2.7. Zack, how do I downgrade. I examined the result of pip install -h but cannot see how. I presume that 'sphinx' and '1.3.6' should be combined into a '' but this latter is not defined and the things I tried, including the output format of 'pip list' did not work. Does anything else need to be downgraded? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 24 18:07:15 2016 From: report at bugs.python.org (Berker Peksag) Date: Wed, 24 Aug 2016 22:07:15 +0000 Subject: [docs] [issue27717] sqlite documentation bug In-Reply-To: <1470745775.08.0.0704550754852.issue27717@psf.upfronthosting.co.za> Message-ID: <1472076435.86.0.249522216386.issue27717@psf.upfronthosting.co.za> Berker Peksag added the comment: > I think it is pretty hard to miss "Never do this" when reading the code section. I agree with David. However, I may be biased since I spend a lot of time reading docs.python.org :) Here is a patch that moves the insecure example to a separate code block. ---------- keywords: +patch nosy: +berker.peksag stage: -> patch review Added file: https://bugs.python.org/file44214/issue27717.diff _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 25 07:37:57 2016 From: report at bugs.python.org (=?utf-8?q?Jens_J=C3=B8rgen_Mortensen?=) Date: Thu, 25 Aug 2016 11:37:57 +0000 Subject: [docs] [issue27846] Base64 expansion factor is 4 to 3, not 6 to 4 In-Reply-To: <1472030737.8.0.133776759316.issue27846@psf.upfronthosting.co.za> Message-ID: <1472125077.44.0.903577544222.issue27846@psf.upfronthosting.co.za> Jens J?rgen Mortensen added the comment: That would also be a solution. Also, the sentence is not quite grammatically correct: "when space [is] expensive". ---------- versions: -Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 25 07:38:43 2016 From: report at bugs.python.org (=?utf-8?q?Jens_J=C3=B8rgen_Mortensen?=) Date: Thu, 25 Aug 2016 11:38:43 +0000 Subject: [docs] [issue27846] Base64 expansion factor is 4 to 3, not 6 to 4 In-Reply-To: <1472030737.8.0.133776759316.issue27846@psf.upfronthosting.co.za> Message-ID: <1472125123.27.0.398964194333.issue27846@psf.upfronthosting.co.za> Changes by Jens J?rgen Mortensen : ---------- versions: +Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 25 09:12:50 2016 From: report at bugs.python.org (Vinay Sajip) Date: Thu, 25 Aug 2016 13:12:50 +0000 Subject: [docs] [issue23746] sysconfg.is_python_build() is buggy In-Reply-To: <1427101982.73.0.589713060591.issue23746@psf.upfronthosting.co.za> Message-ID: <1472130770.54.0.765151974505.issue23746@psf.upfronthosting.co.za> Vinay Sajip added the comment: It's not *only* used in test - it's also used in third party libraries. For example, it's used in distlib (which is vendored by pip) to determine whether it's being run from a source build. ---------- nosy: +vinay.sajip _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 25 09:56:15 2016 From: report at bugs.python.org (Vinay Sajip) Date: Thu, 25 Aug 2016 13:56:15 +0000 Subject: [docs] [issue23105] os.O_SHLOCK and os.O_EXLOCK are not available on Linux In-Reply-To: <1419345535.42.0.312768269587.issue23105@psf.upfronthosting.co.za> Message-ID: <1472133375.06.0.336748891507.issue23105@psf.upfronthosting.co.za> Vinay Sajip added the comment: The existing docs have a section "These constants are GNU extensions and not present if they are not defined by the C library." There could be a corresponding section for BSD extensions to which O_EXLOCK and O_SHLOCK are moved, or the word "GNU" can removed from the existing section and these two flags moved to it. How does that sound? My preference would be for the latter. ---------- nosy: +vinay.sajip _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 25 10:14:27 2016 From: report at bugs.python.org (Roundup Robot) Date: Thu, 25 Aug 2016 14:14:27 +0000 Subject: [docs] [issue23746] sysconfg.is_python_build() is buggy In-Reply-To: <1427101982.73.0.589713060591.issue23746@psf.upfronthosting.co.za> Message-ID: <20160825141416.113158.46698.0B8E6837@psf.io> Roundup Robot added the comment: New changeset bf51f1f3569a by Vinay Sajip in branch '3.5': Issue #23746: Clarified is_python_build() documentation. https://hg.python.org/cpython/rev/bf51f1f3569a New changeset a0a7c5b1af97 by Vinay Sajip in branch 'default': Closes #23746: merged update from 3.5. https://hg.python.org/cpython/rev/a0a7c5b1af97 ---------- nosy: +python-dev resolution: -> fixed stage: needs patch -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 25 11:20:23 2016 From: report at bugs.python.org (Zachary Ware) Date: Thu, 25 Aug 2016 15:20:23 +0000 Subject: [docs] [issue26638] Avoid warnings about missing CLI options when building documentation In-Reply-To: <1458881380.09.0.599104229044.issue26638@psf.upfronthosting.co.za> Message-ID: <1472138423.68.0.843661697906.issue26638@psf.upfronthosting.co.za> Zachary Ware added the comment: The syntax is ` install ""`, so in this case 'pip install "Sphinx==1.3.6"` (or `pip install "Sphinx<1.4"`) should do it for you. That ought to also take care of downgrading any other packages that need it (though I don't think there are any), or at least tell you which ones should be downgraded and to what. I'm not sure why there are both `pip list` and `pip freeze`, but `pip freeze` is the one that outputs usable syntax for a requirement specifier. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 25 12:51:22 2016 From: report at bugs.python.org (Serhiy Storchaka) Date: Thu, 25 Aug 2016 16:51:22 +0000 Subject: [docs] [issue27846] Base64 expansion factor is 4 to 3, not 6 to 4 In-Reply-To: <1472030737.8.0.133776759316.issue27846@psf.upfronthosting.co.za> Message-ID: <1472143882.64.0.72993399751.issue27846@psf.upfronthosting.co.za> Changes by Serhiy Storchaka : ---------- nosy: +pitrou _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 25 12:53:52 2016 From: report at bugs.python.org (Antoine Pitrou) Date: Thu, 25 Aug 2016 16:53:52 +0000 Subject: [docs] [issue27846] Base64 expansion factor is 4 to 3, not 6 to 4 In-Reply-To: <1472030737.8.0.133776759316.issue27846@psf.upfronthosting.co.za> Message-ID: <1472144032.18.0.472060370537.issue27846@psf.upfronthosting.co.za> Antoine Pitrou added the comment: Agreed with David. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 25 15:34:25 2016 From: report at bugs.python.org (Terry J. Reedy) Date: Thu, 25 Aug 2016 19:34:25 +0000 Subject: [docs] [issue26638] Avoid warnings about missing CLI options when building documentation In-Reply-To: <1458881380.09.0.599104229044.issue26638@psf.upfronthosting.co.za> Message-ID: <1472153665.66.0.656564900238.issue26638@psf.upfronthosting.co.za> Terry J. Reedy added the comment: Thank you, that worked -- and should have been documented in the help output. All the sphinx dependencies were inequalities, and rebuilding worked. The devguide only says "You are expected to have installed a recent version of Sphinx on your system or in a virtualenv,". Could we add "We currently recommend 'python -m pip install sphinx==1.3.6' as the easiest way to install and the best version for most people to install. See https://bugs.python.org/issue26638 for why." (I am assuming that pip works on all systems, not just Windows.) The sentence finishes with "so that the Makefile can find the sphinx-build command." On Windows. this is most easily done by installing Sphinx with a Python version that was added to PATH when installed. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 25 17:29:42 2016 From: report at bugs.python.org (Gregory P. Smith) Date: Thu, 25 Aug 2016 21:29:42 +0000 Subject: [docs] [issue23702] docs.python.org/3/howto/descriptor.html still refers to "unbound methods" In-Reply-To: <1426708114.47.0.635748134131.issue23702@psf.upfronthosting.co.za> Message-ID: <1472160582.44.0.582236734264.issue23702@psf.upfronthosting.co.za> Changes by Gregory P. Smith : ---------- nosy: +gregory.p.smith priority: normal -> high _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 25 23:30:14 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Fri, 26 Aug 2016 03:30:14 +0000 Subject: [docs] [issue19504] Change "customise" to "customize". In-Reply-To: <1383659200.62.0.979344465483.issue19504@psf.upfronthosting.co.za> Message-ID: <1472182214.12.0.67225121507.issue19504@psf.upfronthosting.co.za> Changes by Raymond Hettinger : ---------- assignee: docs at python -> rhettinger nosy: +rhettinger _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 26 00:12:31 2016 From: report at bugs.python.org (Roundup Robot) Date: Fri, 26 Aug 2016 04:12:31 +0000 Subject: [docs] [issue19504] Change "customise" to "customize". In-Reply-To: <1383659200.62.0.979344465483.issue19504@psf.upfronthosting.co.za> Message-ID: <20160826041221.27150.45670.1D70DC7D@psf.io> Roundup Robot added the comment: New changeset 579360b1c8fe by Raymond Hettinger in branch '3.5': Issue 19504: Change "customise" to "customize" American spelling. https://hg.python.org/cpython/rev/579360b1c8fe ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 26 00:13:00 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Fri, 26 Aug 2016 04:13:00 +0000 Subject: [docs] [issue19504] Change "customise" to "customize". In-Reply-To: <1383659200.62.0.979344465483.issue19504@psf.upfronthosting.co.za> Message-ID: <1472184780.57.0.257326011115.issue19504@psf.upfronthosting.co.za> Raymond Hettinger added the comment: Thanks for the patch. ---------- resolution: -> fixed status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 26 15:35:37 2016 From: report at bugs.python.org (Berker Peksag) Date: Fri, 26 Aug 2016 19:35:37 +0000 Subject: [docs] [issue8145] Documentation about sqlite3 isolation_level In-Reply-To: <1268643705.49.0.319902511171.issue8145@psf.upfronthosting.co.za> Message-ID: <1472240137.83.0.0781743165683.issue8145@psf.upfronthosting.co.za> Berker Peksag added the comment: sqlite_transaction_doc.patch looks good to me and applies cleanly to current default branch. One minor note: It would be nice to document that the default mode is "BEGIN DEFERRED" in Connection.isolation_level documentation. ---------- nosy: +berker.peksag stage: patch review -> commit review versions: +Python 3.5, Python 3.6 -Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 26 22:21:57 2016 From: report at bugs.python.org (Martin Panter) Date: Sat, 27 Aug 2016 02:21:57 +0000 Subject: [docs] [issue26638] Avoid warnings about missing CLI options when building documentation In-Reply-To: <1458881380.09.0.599104229044.issue26638@psf.upfronthosting.co.za> Message-ID: <1472264517.3.0.915567488662.issue26638@psf.upfronthosting.co.za> Martin Panter added the comment: Terry: the four "ini" syntax highlighting warnings were also mentioned in . In that bug, we fixed many other similar warnings, but I think we left those as being less easy to fix. One thing (other than suppress_warnings = ['ref.option']) that might help you see warnings relevant to your change is if you first build the docs without your change, ignore all those warnings, and then rebuild with your change. The second build may produce less irrelevant warnings. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 26 22:36:01 2016 From: report at bugs.python.org (Eryk Sun) Date: Sat, 27 Aug 2016 02:36:01 +0000 Subject: [docs] [issue27871] ctypes docs must be more explicit about the type a func returns In-Reply-To: <1472247803.52.0.0680824647216.issue27871@psf.upfronthosting.co.za> Message-ID: <1472265361.08.0.22116651592.issue27871@psf.upfronthosting.co.za> Eryk Sun added the comment: See section 2.7 in the ctypes docs: Fundamental data types, when returned as foreign function call results, or, for example, by retrieving structure field members or array items, are transparently converted to native Python types. In other words, if a foreign function has a restype of c_char_p, you will always receive a Python bytes object, not a c_char_p instance. Subclasses of fundamental data types do not inherit this behavior. So, if a foreign functions restype is a subclass of c_void_p, you will receive an instance of this subclass from the function call. Of course, you can get the value of the pointer by accessing the value attribute. For example: class my_char_p(ctypes.c_char_p): pass >>> locale = ctypes.create_string_buffer(b'en_US.UTF-8') >>> setlocale.restype = ctypes.c_char_p >>> result = setlocale(0, locale) >>> result b'en_US.UTF-8' >>> setlocale.restype = my_char_p >>> result = setlocale(0, locale) >>> result my_char_p(31391216) >>> result.value b'en_US.UTF-8' > when he/she passes that value into the next library function A function that takes pointer arguments really should have argtypes defined so that there's no chance of accidentally getting the default integer conversion to a C int. ---------- assignee: -> docs at python components: +Documentation nosy: +docs at python, eryksun resolution: -> not a bug stage: -> resolved status: open -> closed versions: -Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 27 09:42:09 2016 From: report at bugs.python.org (John Hagen) Date: Sat, 27 Aug 2016 13:42:09 +0000 Subject: [docs] [issue27877] Add recipe for "valueless" Enums to docs Message-ID: <1472305329.28.0.714722611618.issue27877@psf.upfronthosting.co.za> New submission from John Hagen: Many programming languages allow the developer to define a enum without specifying values when there would be no significance to those values. Adding some kind of support in the stdlib itself was rejected due to the high degree of magic that would be needed: https://bugs.python.org/issue26988 I propose that a simple example be added to the enum docs that show a developer how to use a normal Python Enum to create this most common and basic enum (without values). import enum class Color(enum.Enum): red = object() green = object() blue = object() object() returns a new unique value while conveying that that value should not be expected to be used in any meaningful way (unlike an integer value, which could be used to encode the Enum in some way). There is no extra magic going on here, no new code that needs to be added to the stdlib, and no bare identifiers that could confuse linters. For example, PyCharm already fully understands the above example and statically types it. This example also allows the developer to omit the extra @enum.unique() boilerplate that is normally needed, since he or she cannot accidentally use the same integer value twice. ---------- assignee: docs at python components: Documentation messages: 273780 nosy: John Hagen, barry, docs at python, eli.bendersky, ethan.furman priority: normal severity: normal status: open title: Add recipe for "valueless" Enums to docs type: enhancement versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 27 15:41:35 2016 From: report at bugs.python.org (Xiang Zhang) Date: Sat, 27 Aug 2016 19:41:35 +0000 Subject: [docs] [issue27740] Fix doc of Py_CompileStringExFlags In-Reply-To: <1470939203.79.0.619794104629.issue27740@psf.upfronthosting.co.za> Message-ID: <1472326895.66.0.97349260593.issue27740@psf.upfronthosting.co.za> Xiang Zhang added the comment: I am not a native speaker so I decide not to trap in the minor part. Could you just fix the first point if there is no doubt? I'm okay with the second part staying as now. ---------- Added file: https://bugs.python.org/file44242/issue27740.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 27 23:38:06 2016 From: report at bugs.python.org (Richard) Date: Sun, 28 Aug 2016 03:38:06 +0000 Subject: [docs] [issue27882] Python docs on 3.52 Math module lists math.log2 as function but it does not exist Message-ID: <1472355486.46.0.630327302232.issue27882@psf.upfronthosting.co.za> Changes by Richard : ---------- assignee: docs at python components: Documentation nosy: PyRW, docs at python priority: normal severity: normal status: open title: Python docs on 3.52 Math module lists math.log2 as function but it does not exist versions: Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 27 23:43:24 2016 From: report at bugs.python.org (Richard) Date: Sun, 28 Aug 2016 03:43:24 +0000 Subject: [docs] [issue27882] Python docs on 9.52 Math module lists math.log2 as function but it does not exist Message-ID: <1472355804.23.0.122848128735.issue27882@psf.upfronthosting.co.za> Changes by Richard : ---------- title: Python docs on 3.52 Math module lists math.log2 as function but it does not exist -> Python docs on 9.52 Math module lists math.log2 as function but it does not exist _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 27 23:43:45 2016 From: report at bugs.python.org (Richard) Date: Sun, 28 Aug 2016 03:43:45 +0000 Subject: [docs] [issue27882] Python docs on 9.2 Math module lists math.log2 as function but it does not exist Message-ID: <1472355825.91.0.677269784318.issue27882@psf.upfronthosting.co.za> Changes by Richard : ---------- title: Python docs on 9.52 Math module lists math.log2 as function but it does not exist -> Python docs on 9.2 Math module lists math.log2 as function but it does not exist _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 27 23:45:54 2016 From: report at bugs.python.org (Richard) Date: Sun, 28 Aug 2016 03:45:54 +0000 Subject: [docs] [issue27882] Python docs on 9.2 Math module lists math.log2 as function but it does not exist Message-ID: <1472355954.71.0.708927326629.issue27882@psf.upfronthosting.co.za> Changes by Richard : Added file: https://bugs.python.org/file44244/docbugmathlog2.jpg _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 00:24:55 2016 From: report at bugs.python.org (Emanuel Barry) Date: Sun, 28 Aug 2016 04:24:55 +0000 Subject: [docs] [issue27882] Python docs on 9.2 Math module lists math.log2 as function but it does not exist Message-ID: <1472358295.58.0.523948529034.issue27882@psf.upfronthosting.co.za> New submission from Emanuel Barry: The function does definitely exist for me. Please make sure your Python version is up-to-date. Also, please post a short summary of the issue, and avoid screenshots whenever possible; it's more work for you, makes it harder for us to reproduce/follow (need to manually type everything back), and makes it impossible for the blind and visually impaired to participate. Thanks! ---------- assignee: docs at python -> components: -Documentation nosy: +ebarry status: open -> pending _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 03:31:35 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Sun, 28 Aug 2016 07:31:35 +0000 Subject: [docs] [issue27882] Python docs on 9.2 Math module lists math.log2 as function but it does not exist In-Reply-To: <1472358295.58.0.523948529034.issue27882@psf.upfronthosting.co.za> Message-ID: <1472369495.44.0.266945693977.issue27882@psf.upfronthosting.co.za> Raymond Hettinger added the comment: Also, check your Python version to make sure that you're running Python 3.3 or later. ---------- nosy: +rhettinger status: pending -> open _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 04:14:05 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Sun, 28 Aug 2016 08:14:05 +0000 Subject: [docs] [issue27877] Add recipe for "valueless" Enums to docs In-Reply-To: <1472305329.28.0.714722611618.issue27877@psf.upfronthosting.co.za> Message-ID: <1472372045.68.0.867130284401.issue27877@psf.upfronthosting.co.za> Raymond Hettinger added the comment: -0 I concur with OP's observation that "object() returns a new unique value while conveying that that value should not be expected to be used in any meaningful way" and that this recipe could help reinforce that notion. That said, the idiomatic way to communicate this in Python is to use None rather than to create distinct meaningless objects. Also, the motivation seems questionable. Instead of showing a real world case where some confusion exists, there seems to be a general irritation that Enum implementation details differ in some respects from various compiled languages. ISTM, the recipe is aimed at an imagined problem rather than an actual problem -- in a real use case (not a toy Color example), I would expect that if the value field is meaningless, then the use case itself will tend to make it self-evident that there is no reason to access the value field (and if it didn't, I don't see how returning some arbitrary instance of object() would be more informative than returning None.) ---------- nosy: +rhettinger _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 04:46:18 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Sun, 28 Aug 2016 08:46:18 +0000 Subject: [docs] [issue27877] Add recipe for "valueless" Enums to docs In-Reply-To: <1472305329.28.0.714722611618.issue27877@psf.upfronthosting.co.za> Message-ID: <1472373978.87.0.792959851406.issue27877@psf.upfronthosting.co.za> Changes by Raymond Hettinger : ---------- Removed message: https://bugs.python.org/msg273815 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 04:47:30 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Sun, 28 Aug 2016 08:47:30 +0000 Subject: [docs] [issue27877] Add recipe for "valueless" Enums to docs In-Reply-To: <1472305329.28.0.714722611618.issue27877@psf.upfronthosting.co.za> Message-ID: <1472374050.75.0.111114721718.issue27877@psf.upfronthosting.co.za> Raymond Hettinger added the comment: After a little more thought, I think this would be a worthwhile recipe and would help communicate the notion that the value has no particular meaning. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 05:37:33 2016 From: report at bugs.python.org (Serhiy Storchaka) Date: Sun, 28 Aug 2016 09:37:33 +0000 Subject: [docs] [issue27882] Python docs on 9.2 Math module lists math.log2 as function but it does not exist In-Reply-To: <1472358295.58.0.523948529034.issue27882@psf.upfronthosting.co.za> Message-ID: <1472377053.24.0.996444373226.issue27882@psf.upfronthosting.co.za> Changes by Serhiy Storchaka : ---------- status: open -> pending _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 14:38:23 2016 From: report at bugs.python.org (John Hagen) Date: Sun, 28 Aug 2016 18:38:23 +0000 Subject: [docs] [issue27877] Add recipe for "valueless" Enums to docs In-Reply-To: <1472305329.28.0.714722611618.issue27877@psf.upfronthosting.co.za> Message-ID: <1472409503.93.0.858184069004.issue27877@psf.upfronthosting.co.za> John Hagen added the comment: Raymond, thanks for your consideration and input. I'll work on a small patch unless I hear from Ethan that he'd rather do it. I'm happy to defer to his expertise. I did try out None as a value just to be sure that that didn't work as it would not be a bad alternative. But since the values are "equal", Enum tries to alias them. import enum @enum.unique class Color(enum.Enum): red = None green = None blue = None >>> ValueError: duplicate values found in : green -> red, blue -> red ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 15:07:12 2016 From: report at bugs.python.org (Andrew Svetlov) Date: Sun, 28 Aug 2016 19:07:12 +0000 Subject: [docs] [issue27886] Docs: the difference between rename and replace is not obvious Message-ID: <1472411232.42.0.47360960084.issue27886@psf.upfronthosting.co.za> New submission from Andrew Svetlov: Hi. On reading the doc for pathlib I've stuck with `.rename()` and `.replace()` (https://docs.python.org/3/library/pathlib.html#pathlib.Path.rename). What's the difference? Going to pathlib's source code I've figured out that methods are use different functions from `os` module: `os.rename()` and `os.replace()`. But the documentation for `os` module is not obvious too: the docs for both functions are almost equal from my perspective, the only significant difference is that `os.rename()` suggests to use `os.replace()` for cross-compatibility. Could anybody explain the difference? Also, at least the doc for `pathlib.Path.rename` worth to have a sentence like borrowed from `os.rename`: "If you want cross-platform overwriting of the destination, use replace()." ---------- assignee: docs at python components: Documentation keywords: easy messages: 273836 nosy: asvetlov, docs at python, pitrou priority: low severity: normal status: open title: Docs: the difference between rename and replace is not obvious type: behavior versions: Python 3.4, Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 15:38:35 2016 From: report at bugs.python.org (R. David Murray) Date: Sun, 28 Aug 2016 19:38:35 +0000 Subject: [docs] [issue27886] Docs: the difference between rename and replace is not obvious In-Reply-To: <1472411232.42.0.47360960084.issue27886@psf.upfronthosting.co.za> Message-ID: <1472413115.19.0.52282610743.issue27886@psf.upfronthosting.co.za> R. David Murray added the comment: The existing docs are pretty clear on the difference: rename is only guaranteed to replace an existing file on unix (which I think means posix in this context), whereas replace always replaces the file, regardless of platform. I'm actually surprised that rename is even part of the pathlib API, since its cross platform behavior is not consistent. It also seems as though the replace docs are incorrect, since they imply directories are replaced, but the os docs say they are not. The "this is a posix requirement" note in os.replace also seems imprecise. Windows is not posix, so that note leaves me wondering if replace is atomic on Windows or not. That should be clarified one way or another. I think adding the cross platform note in the pathlib docs is reasonable, since it addresses the question of why there are two similar functions. ---------- nosy: +r.david.murray _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 15:38:47 2016 From: report at bugs.python.org (R. David Murray) Date: Sun, 28 Aug 2016 19:38:47 +0000 Subject: [docs] [issue27886] Docs: the difference between rename and replace is not obvious In-Reply-To: <1472411232.42.0.47360960084.issue27886@psf.upfronthosting.co.za> Message-ID: <1472413127.56.0.858075255684.issue27886@psf.upfronthosting.co.za> Changes by R. David Murray : ---------- versions: -Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 16:03:34 2016 From: report at bugs.python.org (Andrew Svetlov) Date: Sun, 28 Aug 2016 20:03:34 +0000 Subject: [docs] [issue27886] Docs: the difference between rename and replace is not obvious In-Reply-To: <1472411232.42.0.47360960084.issue27886@psf.upfronthosting.co.za> Message-ID: <1472414614.15.0.405849285123.issue27886@psf.upfronthosting.co.za> Andrew Svetlov added the comment: Just keeping the reference to `os.rename()`: https://docs.python.org/3/library/os.html#os.rename Aha, `os.rename` says: "On Unix, if dst exists and is a file, it will be replaced silently if the user has permission." and "On Windows, if dst already exists, OSError will be raised even if it is a file." Sorry, I've missed this. Maybe it worth to add `.. warning:` section for both `os.rename` and `pathlib.Path.rename`? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 16:05:48 2016 From: report at bugs.python.org (R. David Murray) Date: Sun, 28 Aug 2016 20:05:48 +0000 Subject: [docs] [issue27886] Docs: the difference between rename and replace is not obvious In-Reply-To: <1472411232.42.0.47360960084.issue27886@psf.upfronthosting.co.za> Message-ID: <1472414748.59.0.0517273162174.issue27886@psf.upfronthosting.co.za> R. David Murray added the comment: No, we don't like to overuse warnings. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 17:03:40 2016 From: report at bugs.python.org (John Hagen) Date: Sun, 28 Aug 2016 21:03:40 +0000 Subject: [docs] [issue27877] Add recipe for "valueless" Enums to docs In-Reply-To: <1472305329.28.0.714722611618.issue27877@psf.upfronthosting.co.za> Message-ID: <1472418220.91.0.254626028182.issue27877@psf.upfronthosting.co.za> John Hagen added the comment: Patch attached. ---------- keywords: +patch Added file: https://bugs.python.org/file44249/issue27877.johnthagen.01.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 18:56:53 2016 From: report at bugs.python.org (Eryk Sun) Date: Sun, 28 Aug 2016 22:56:53 +0000 Subject: [docs] [issue27886] Docs: the difference between rename and replace is not obvious In-Reply-To: <1472411232.42.0.47360960084.issue27886@psf.upfronthosting.co.za> Message-ID: <1472425013.11.0.713050633245.issue27886@psf.upfronthosting.co.za> Eryk Sun added the comment: Having rename() in pathlib is fine as long as it links to the os docs. This probably needs a new issue, but I do see room for improvement in the latter. For Unix, the os.rename and os.replace docs should clarify that an empty destination directory can be replaced by another directory. For example: >>> os.mkdir('foo1') >>> os.mkdir('foo2') >>> os.rename('foo1', 'foo2') The specification of rename [1] states that "[i]f the *old* argument points to the pathname of a directory, the *new* argument shall not point to the pathname of a file that is not a directory". It further specifies that "[i]f *new* names an existing directory, it shall be required to be an empty directory". Windows, on the other hand, doesn't allow replacing a directory, even an empty one. The wording for os.rename and os.replace could be changed to something like: "[i]f dst is a directory, OSError will be raised, except not on Unix if src is a directory and dst is empty". Windows MoveFileEx calls NtSetInformationFile to set the FileRenameInformation [2]. The MSDN docs do not explicitly require that the operation is atomic, unlike POSIX rename. I think it's a reasonable expectation that a Windows filesystem should rename atomically, and that's probably the case. However, it should be clear that only Unix guarantees this, e.g. "[i]f successful, on Unix the renaming will be an atomic operation, as required by POSIX". MSDN claims that a rename will fail in the following cases: A file or directory can only be renamed within a volume. Even if ReplaceIfExists is set to TRUE, the rename operation will still fail if a file with the same name already exists and is a directory, a read-only file, or a currently executing file. A file cannot be renamed if it has any open handles, unless it is only open because of a batch opportunistic lock (oplock) and the batch oplock can be broken immediately. A file cannot be renamed if a file with the same name exists and has open handles (except in the batch-oplock case described earlier). A directory cannot be renamed if it or any of its subdirectories contains a file that has open handles (except in the batch-oplock case described earlier). For the third case, actually an open file can be renamed if delete/rename access is shared. For example: >>> with open('foo1', 'w') as f: f.write('foo1') ... 4 Open the file with shared delete access: >>> SHARE_ALL = 7 >>> _winapi.CreateFile('foo1', 0x80000000, SHARE_ALL, 0, 3, 0, 0) 224 and rename/replace succeeds: >>> os.replace('foo1', 'foo2') >>> open('foo2').read() 'foo1' Anyway, the os.replace docs could state in general that: "[o]n Windows, a PermissionError will be raised if dst is a read-only file, or if either src or dst is currently open, or if src is a directory with an open file". [1]: http://pubs.opengroup.org/onlinepubs/9699919799/functions/rename.html [2]: https://msdn.microsoft.com/en-us/library/ff540344 ---------- nosy: +eryksun _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 19:23:04 2016 From: report at bugs.python.org (Martin Panter) Date: Sun, 28 Aug 2016 23:23:04 +0000 Subject: [docs] [issue24045] Behavior of large returncodes (sys.exit(nn)) In-Reply-To: <1429836429.07.0.888331603842.issue24045@psf.upfronthosting.co.za> Message-ID: <1472426584.92.0.439619211664.issue24045@psf.upfronthosting.co.za> Martin Panter added the comment: Is this a duplicate of Issue 24052? ---------- nosy: +martin.panter _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 28 19:41:50 2016 From: report at bugs.python.org (Emanuel Barry) Date: Sun, 28 Aug 2016 23:41:50 +0000 Subject: [docs] [issue27877] Add recipe for "valueless" Enums to docs In-Reply-To: <1472305329.28.0.714722611618.issue27877@psf.upfronthosting.co.za> Message-ID: <1472427710.55.0.381819486362.issue27877@psf.upfronthosting.co.za> Emanuel Barry added the comment: The patch doesn't apply. I manually copy-pasted the lines in the source and generated a new one. I would probably rephrase "these values hold no meaning and should not be used" into "the values are not important" or something along those lines. ---------- nosy: +ebarry Added file: https://bugs.python.org/file44250/enum_valueless_1.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 29 06:07:36 2016 From: report at bugs.python.org (Eryk Sun) Date: Mon, 29 Aug 2016 10:07:36 +0000 Subject: [docs] [issue24045] Behavior of large returncodes (sys.exit(nn)) In-Reply-To: <1429836429.07.0.888331603842.issue24045@psf.upfronthosting.co.za> Message-ID: <1472465256.32.0.4663975044.issue24045@psf.upfronthosting.co.za> Eryk Sun added the comment: Unix waitpid() packs the process exit status and terminating signal number into a single status value. As specified by POSIX [1], the WEXITSTATUS function returns only the lower 8 bits of the process exit status. In theory, waitid() and wait6() can return the full 32-bit status value in the siginfo_t si_status. Apparently NetBSD does this [2], but evidently Linux does not: >>> p = subprocess.Popen(['python3', '-c','import os; os._exit(257)']) >>> os.waitid(os.P_PID, p.pid, os.WEXITED).si_status 1 For Windows, programs sometimes return 16-bit WinAPI error codes or 32-bit HRESULT error codes. A critical error or unhandled exception may even result in returning a 32-bit NTSTATUS code (e.g. if you cancel the Windows error reporting dialog). Currently the Python 3 implementation of sys.exit and os._exit converts to a signed long, but the Windows exit code is an unsigned long. To use integer return codes in the range 0x80000000-0xFFFFFFFF requires manually converting to the corresponding negative signed value. Technically the two error types that require 32-bit values are signed (i.e. HRESULT and NTSTATUS), so this shouldn't be a problem. However, in practice sometimes a function -- and definitely subprocess.Popen -- returns an HRESULT error code as an unsigned value. It would be convenient, at least on Windows, if handle_system_exit in Python/pythonrun.c converted the value using PyLong_AsUnsignedLongMask instead of PyLong_AsLong. Similarly os._exit could use Argument Clinic's "unsigned int" format, which also calls PyLong_AsUnsignedLongMask. The problem with using PyLong_AsLong on Windows (32-bit or 64-bit) is that it overflows with an error value of -1 for values greater than 0x7FFFFFFF. In this case, os._exit raises OverflowError. handle_system_exit, on the other hand, ignores the exception. It just uses the -1 error value as the exit code, i.e. 0xFFFFFFFF. [1]: http://pubs.opengroup.org/onlinepubs/9699919799/functions/wait.html [2]: https://www.daemon-systems.org/man/wait.2.html ---------- nosy: +eryksun _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 29 07:25:56 2016 From: report at bugs.python.org (John Hagen) Date: Mon, 29 Aug 2016 11:25:56 +0000 Subject: [docs] [issue27877] Add recipe for "valueless" Enums to docs In-Reply-To: <1472305329.28.0.714722611618.issue27877@psf.upfronthosting.co.za> Message-ID: <1472469956.58.0.648655112238.issue27877@psf.upfronthosting.co.za> Changes by John Hagen : Removed file: https://bugs.python.org/file44249/issue27877.johnthagen.01.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 29 07:28:10 2016 From: report at bugs.python.org (John Hagen) Date: Mon, 29 Aug 2016 11:28:10 +0000 Subject: [docs] [issue27877] Add recipe for "valueless" Enums to docs In-Reply-To: <1472305329.28.0.714722611618.issue27877@psf.upfronthosting.co.za> Message-ID: <1472470090.08.0.197549251127.issue27877@psf.upfronthosting.co.za> John Hagen added the comment: Emanuel, I like your rewording. Uploaded a new patch incorporating it. ---------- Added file: https://bugs.python.org/file44252/issue27877.johnthagen.02.patch _______________________________________ Python tracker _______________________________________ From g_cleary at u.pacific.edu Sat Aug 27 09:43:22 2016 From: g_cleary at u.pacific.edu (Geoff Cleary) Date: Sat, 27 Aug 2016 06:43:22 -0700 Subject: [docs] broken links to downloadable Python 3.4 docs Message-ID: Hi, Just a quick note to let you know that the links for downloading the Python 3.4 HTML docs are broken. On this page: https://docs.python.org/3.4/download.html These two links end up as 404?s: https://www.python.org/ftp/python/doc/3.4.5/python-3.4.5-docs-html.zip https://www.python.org/ftp/python/doc/3.4.5/python-3.4.5-docs-html.tar.bz2 Geoff Cleary g_cleary at u.pacific.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From report at bugs.python.org Mon Aug 29 11:27:30 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Mon, 29 Aug 2016 15:27:30 +0000 Subject: [docs] [issue27877] Add recipe for "valueless" Enums to docs In-Reply-To: <1472305329.28.0.714722611618.issue27877@psf.upfronthosting.co.za> Message-ID: <1472484450.43.0.811301173306.issue27877@psf.upfronthosting.co.za> Changes by Raymond Hettinger : ---------- assignee: docs at python -> ethan.furman _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 29 12:42:08 2016 From: report at bugs.python.org (Mark Dickinson) Date: Mon, 29 Aug 2016 16:42:08 +0000 Subject: [docs] [issue27882] Python docs on 9.2 Math module lists math.log2 as function but it does not exist In-Reply-To: <1472358295.58.0.523948529034.issue27882@psf.upfronthosting.co.za> Message-ID: <1472488928.71.0.27467571657.issue27882@psf.upfronthosting.co.za> Mark Dickinson added the comment: Closing. The docs are correct for the corresponding version of Python: math.log2 is new in Python 3.3, and the entry for math.log2 is there in Python 3.3 but not Python 3.2 or Python 2.7. @PyRW: It looks as though this is simply a version mismatch (looking at the wrong docs for the Python version you're using). If you double check `sys.version` and find that math.log2 still appears to be missing even on Python >= 3.3, feel free to reopen this issue with more information. ---------- nosy: +mark.dickinson resolution: -> not a bug stage: -> resolved status: pending -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 10:55:26 2016 From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=) Date: Tue, 30 Aug 2016 14:55:26 +0000 Subject: [docs] [issue27893] BytesParser.parsebytes docstring fix Message-ID: <1472568926.5.0.442423552273.issue27893@psf.upfronthosting.co.za> Changes by Ville Skytt? : ---------- assignee: docs at python components: Documentation files: parser.patch keywords: patch nosy: docs at python, scop priority: normal severity: normal status: open title: BytesParser.parsebytes docstring fix type: enhancement Added file: http://bugs.python.org/file44270/parser.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 11:28:58 2016 From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=) Date: Tue, 30 Aug 2016 15:28:58 +0000 Subject: [docs] [issue27894] Fix to_addrs refs in smtplib docs Message-ID: <1472570938.49.0.131080504212.issue27894@psf.upfronthosting.co.za> Changes by Ville Skytt? : ---------- assignee: docs at python components: Documentation files: smtplib-doc.patch keywords: patch nosy: docs at python, scop priority: normal severity: normal status: open title: Fix to_addrs refs in smtplib docs type: enhancement Added file: http://bugs.python.org/file44271/smtplib-doc.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 11:44:37 2016 From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=) Date: Tue, 30 Aug 2016 15:44:37 +0000 Subject: [docs] [issue27895] Spelling fixes Message-ID: <1472571877.66.0.847810688637.issue27895@psf.upfronthosting.co.za> Changes by Ville Skytt? : ---------- assignee: docs at python components: Documentation files: spelling.patch keywords: patch nosy: docs at python, scop priority: normal severity: normal status: open title: Spelling fixes type: enhancement Added file: http://bugs.python.org/file44272/spelling.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 11:49:19 2016 From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=) Date: Tue, 30 Aug 2016 15:49:19 +0000 Subject: [docs] [issue27895] Spelling fixes Message-ID: <1472572159.07.0.229782675857.issue27895@psf.upfronthosting.co.za> Changes by Ville Skytt? : Removed file: http://bugs.python.org/file44272/spelling.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 11:50:06 2016 From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=) Date: Tue, 30 Aug 2016 15:50:06 +0000 Subject: [docs] [issue27895] Spelling fixes Message-ID: <1472572206.32.0.0198378317251.issue27895@psf.upfronthosting.co.za> Changes by Ville Skytt? : Added file: http://bugs.python.org/file44273/spelling2.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 11:52:08 2016 From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=) Date: Tue, 30 Aug 2016 15:52:08 +0000 Subject: [docs] [issue27895] Spelling fixes Message-ID: <1472572328.89.0.340323592517.issue27895@psf.upfronthosting.co.za> Changes by Ville Skytt? : Added file: http://bugs.python.org/file44274/spelling3.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 11:52:16 2016 From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=) Date: Tue, 30 Aug 2016 15:52:16 +0000 Subject: [docs] [issue27895] Spelling fixes Message-ID: <1472572336.15.0.105570193814.issue27895@psf.upfronthosting.co.za> Changes by Ville Skytt? : Removed file: http://bugs.python.org/file44273/spelling2.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 12:03:39 2016 From: report at bugs.python.org (Julien) Date: Tue, 30 Aug 2016 16:03:39 +0000 Subject: [docs] [issue27896] Allow passing sphinx options to Doc/Makefile Message-ID: <1472573019.01.0.777773652271.issue27896@psf.upfronthosting.co.za> New submission from Julien: Context: - Providing french translation to docs.python.rg/fr/: http://bugs.python.org/issue26546 - Simplifying my first proposition of docsbuild-scripts: https://github.com/python/docsbuild-scripts/pull/1 Goals: - Simplify my modifications of docsbuild-scripts to make it more robust - Avoid executing external (~untrusted) Makefile on docs.python.org servers To achieve this, I need the ``Doc/Makefile`` to be sufficient to build internationalized versions by passing sphinx options to it, I'd like to call, typically: make autobuild-stable SPHINXOPTS='-D language=fr -D locale_dirs=./locale/' Which work if `Doc/Makefile` don't erase but append to the `SPHINXOPTS` variable. Which is done by `allow_sphinxopts.diff`. We may simplify it further by adding `locale_dirs` to `Doc/conf.py` which does not break the english build, but I'm not sure if it's of any interest. We may abstract it further by accepting a new parameter like SPHINXLANG='fr', with a default of 'en', but in every case I think it's a good thing to allow passing arbitrary SPHINXOPTS so let's start with this? ---------- assignee: docs at python components: Documentation files: allow_sphinxopts.diff keywords: patch messages: 273921 nosy: docs at python, sizeof priority: normal severity: normal status: open title: Allow passing sphinx options to Doc/Makefile versions: Python 3.6 Added file: http://bugs.python.org/file44275/allow_sphinxopts.diff _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 12:27:12 2016 From: report at bugs.python.org (Tomas Orsava) Date: Tue, 30 Aug 2016 16:27:12 +0000 Subject: [docs] [issue25573] FrameSummary repr() does not support previously working uses of repr in traceback module In-Reply-To: <1446845666.11.0.0803768990935.issue25573@psf.upfronthosting.co.za> Message-ID: <1472574431.87.0.223646160885.issue25573@psf.upfronthosting.co.za> Tomas Orsava added the comment: This problem has already been addressed in issue 27208, and it was fixed by updating the documentation to reflect the new repr(). Therefore, I believe this issue can be closed. ---------- nosy: +torsava _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 12:42:36 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Tue, 30 Aug 2016 16:42:36 +0000 Subject: [docs] [issue27895] Spelling fixes Message-ID: <1472575356.72.0.601730705439.issue27895@psf.upfronthosting.co.za> Changes by Raymond Hettinger : ---------- assignee: docs at python -> rhettinger nosy: +rhettinger _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 13:46:00 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Tue, 30 Aug 2016 17:46:00 +0000 Subject: [docs] [issue27895] Spelling fixes Message-ID: <1472579160.51.0.388214887835.issue27895@psf.upfronthosting.co.za> New submission from Raymond Hettinger: Thanks for the patch. Some of these were a bit embarrassing. Removed the Lib/test/decimaltestdata because this is from an external source (not our code) that is periodically refreshed. I had to hand edit some of the changes to test_asyncio because the patch was breaking those tests for some reason. I had some hesitancy about changing function or variable names in real code and had to spend time looking at each in detail but they all seem legitimate. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 13:48:06 2016 From: report at bugs.python.org (Roundup Robot) Date: Tue, 30 Aug 2016 17:48:06 +0000 Subject: [docs] [issue27895] Spelling fixes In-Reply-To: <1472579160.51.0.388214887835.issue27895@psf.upfronthosting.co.za> Message-ID: <20160830174758.13094.401.C257102F@psf.io> Roundup Robot added the comment: New changeset 75d6d5d9b674 by Raymond Hettinger in branch 'default': Issue #27895: Spelling fixes (Contributed by Ville Skytt?). https://hg.python.org/cpython/rev/75d6d5d9b674 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 13:50:54 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Tue, 30 Aug 2016 17:50:54 +0000 Subject: [docs] [issue27895] Spelling fixes In-Reply-To: <1472579160.51.0.388214887835.issue27895@psf.upfronthosting.co.za> Message-ID: <1472579454.47.0.620579748872.issue27895@psf.upfronthosting.co.za> Raymond Hettinger added the comment: FYI, the patch did not apply cleanly to Python 3.5 so this was applied to 3.6 only. If someone feels this is important to them, they are welcome to backport the applicable parts of the patch. ---------- resolution: -> fixed status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 15:57:34 2016 From: report at bugs.python.org (Roundup Robot) Date: Tue, 30 Aug 2016 19:57:34 +0000 Subject: [docs] [issue27895] Spelling fixes In-Reply-To: <1472579160.51.0.388214887835.issue27895@psf.upfronthosting.co.za> Message-ID: <20160830195731.31657.93098.E2DE5622@psf.io> Roundup Robot added the comment: New changeset 89ce78ce1bfa by Raymond Hettinger in branch 'default': Issue #27895: Strengthen the dict reader tests. https://hg.python.org/cpython/rev/89ce78ce1bfa ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 16:47:12 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Tue, 30 Aug 2016 20:47:12 +0000 Subject: [docs] [issue27894] Fix to_addrs refs in smtplib docs Message-ID: <1472590032.04.0.495055043865.issue27894@psf.upfronthosting.co.za> Changes by Raymond Hettinger : ---------- resolution: -> fixed status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 17:08:00 2016 From: report at bugs.python.org (Anthony Flury) Date: Tue, 30 Aug 2016 21:08:00 +0000 Subject: [docs] [issue27901] inspect.ismethod returns different results on the same basic code between Python2.7 Python3.5 In-Reply-To: <1472585181.25.0.672560198795.issue27901@psf.upfronthosting.co.za> Message-ID: <1472591280.18.0.88755748748.issue27901@psf.upfronthosting.co.za> Anthony Flury added the comment: Not sure I agree with closing this. I am not convinced (as a reasonably seasoned developer) that the documentation is clear. It may not be a bug in the code, resulting as it does from a change in the way methods are implemented in Python 3.5, but I do think that the documentation could be a lot clearer. It does read as if it is written for someone who already knows what the library does, rather than as a guide for someone trying to work through it for the first time. I have changed this to a documentation issue - I hope that this is ok. ---------- assignee: -> docs at python components: +Documentation -Library (Lib) nosy: +docs at python resolution: not a bug -> status: closed -> open _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 17:42:47 2016 From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=) Date: Tue, 30 Aug 2016 21:42:47 +0000 Subject: [docs] [issue27895] Spelling fixes In-Reply-To: <1472579160.51.0.388214887835.issue27895@psf.upfronthosting.co.za> Message-ID: <1472593367.83.0.698362357067.issue27895@psf.upfronthosting.co.za> Ville Skytt? added the comment: Right, I noticed the asyncio test breakage as well, that was one of the reasons I attached a couple of versions of the patch. spelling3 was not supposed to contain the breaking changes any more, maybe you worked on an earlier one? Anyway, thanks. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 17:47:35 2016 From: report at bugs.python.org (R. David Murray) Date: Tue, 30 Aug 2016 21:47:35 +0000 Subject: [docs] [issue27902] pstats.Stats: strip_dirs() method cannot handle file paths from different OS In-Reply-To: <1472590175.77.0.992836532809.issue27902@psf.upfronthosting.co.za> Message-ID: <1472593655.56.0.848457641993.issue27902@psf.upfronthosting.co.za> R. David Murray added the comment: We could add to the compatibility paragraph that compatibility with files produced by the same program on a different platform is not guaranteed. For the option, that would be an enhancement, and you should open a new issue for that. ---------- assignee: -> docs at python components: +Documentation -Windows nosy: +docs at python, r.david.murray stage: -> needs patch type: behavior -> enhancement versions: +Python 2.7, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 17:51:20 2016 From: report at bugs.python.org (Michael Lee) Date: Tue, 30 Aug 2016 21:51:20 +0000 Subject: [docs] [issue27905] Add documentation for typing.Type Message-ID: <1472593880.19.0.114422348142.issue27905@psf.upfronthosting.co.za> New submission from Michael Lee: This patch adds some documentation for typing.Type[C]. The content itself is mostly an abbreviated version of the description from PEP 484 -- let me know if the patch is too terse or needs more examples. ---------- assignee: docs at python components: Documentation files: document-type.patch keywords: patch messages: 273974 nosy: docs at python, gvanrossum, michael0x2a priority: normal severity: normal status: open title: Add documentation for typing.Type versions: Python 3.5, Python 3.6 Added file: http://bugs.python.org/file44285/document-type.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 18:17:23 2016 From: report at bugs.python.org (Martin Panter) Date: Tue, 30 Aug 2016 22:17:23 +0000 Subject: [docs] [issue27893] email.parser.BytesParser.parsebytes docs fix Message-ID: <1472595443.04.0.800364435102.issue27893@psf.upfronthosting.co.za> New submission from Martin Panter: Actually it seems the parameter is called *text*: >>> BytesParser().parsebytes(bytes=b"") TypeError: parsebytes() got an unexpected keyword argument 'bytes' >>> BytesParser().parsebytes(text=b"") ---------- components: +email nosy: +barry, martin.panter, r.david.murray title: BytesParser.parsebytes docstring fix -> email.parser.BytesParser.parsebytes docs fix versions: +Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 20:30:41 2016 From: report at bugs.python.org (Steven D'Aprano) Date: Wed, 31 Aug 2016 00:30:41 +0000 Subject: [docs] [issue27901] inspect.ismethod returns different results on the same basic code between Python2.7 Python3.5 In-Reply-To: <1472585181.25.0.672560198795.issue27901@psf.upfronthosting.co.za> Message-ID: <1472603441.03.0.537327687325.issue27901@psf.upfronthosting.co.za> Steven D'Aprano added the comment: > I do think that the documentation could be a lot clearer. Which specific documentation are you referring to? The "What's New" document from 3.0? That's a historical document, a snapshot of the past. If you have a concern about the current documentation, can you tell us specifically where and what? ---------- nosy: +steven.daprano _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 20:31:14 2016 From: report at bugs.python.org (R. David Murray) Date: Wed, 31 Aug 2016 00:31:14 +0000 Subject: [docs] [issue27893] email.parser.BytesParser.parsebytes docs fix In-Reply-To: <1472595443.04.0.800364435102.issue27893@psf.upfronthosting.co.za> Message-ID: <1472603474.43.0.169355263406.issue27893@psf.upfronthosting.co.za> R. David Murray added the comment: Yeah, and it should probably remain so at this point. It's not even completely wrong; from an email perspective it is text. It should also say "equivalent", not "precisely equivalent", since BytesIO is not in fact involved in the implementation. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 20:39:32 2016 From: report at bugs.python.org (R. David Murray) Date: Wed, 31 Aug 2016 00:39:32 +0000 Subject: [docs] [issue27901] inspect.ismethod returns different results on the same basic code between Python2.7 Python3.5 In-Reply-To: <1472585181.25.0.672560198795.issue27901@psf.upfronthosting.co.za> Message-ID: <1472603972.1.0.749177056808.issue27901@psf.upfronthosting.co.za> R. David Murray added the comment: The docs do not so much assume you know what the library does, as they assume you know how python3 works. Which is to say, that bound methods are obtained from instances and that functions defined on a class are functions. That's documented in the data model docs, and the inspect docs in general assume you understand the python data model and are using inspect to probe it. As Steven said, if you can point specifically to something you think can be improved we will consider it, but know that the python3 docs are in general written without respect to how python2 worked. There are very few references to python2 in the python3 docs, and this is by design. The story is different in the python2 docs, so conceivably there could be something inserted there about the python3 difference. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 20:42:41 2016 From: report at bugs.python.org (R. David Murray) Date: Wed, 31 Aug 2016 00:42:41 +0000 Subject: [docs] [issue27901] inspect.ismethod returns different results on the same basic code between Python2.7 Python3.5 In-Reply-To: <1472585181.25.0.672560198795.issue27901@psf.upfronthosting.co.za> Message-ID: <1472604161.5.0.757882122619.issue27901@psf.upfronthosting.co.za> R. David Murray added the comment: Perhaps we could add a cross link from 'bound method' to the 'instance methods' section of the data model docs. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 21:17:52 2016 From: report at bugs.python.org (Roundup Robot) Date: Wed, 31 Aug 2016 01:17:52 +0000 Subject: [docs] [issue27893] email.parser.BytesParser.parsebytes docs fix In-Reply-To: <1472595443.04.0.800364435102.issue27893@psf.upfronthosting.co.za> Message-ID: <20160831011749.52817.47258.80D8A04C@psf.io> Roundup Robot added the comment: New changeset b8dd9ae08a91 by R David Murray in branch '3.5': #27893: arg name and bytes references in email.parser docs. https://hg.python.org/cpython/rev/b8dd9ae08a91 New changeset 059f9f518834 by R David Murray in branch 'default': Merge #27893: arg name and bytes references in email.parser docs. https://hg.python.org/cpython/rev/059f9f518834 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 21:19:30 2016 From: report at bugs.python.org (R. David Murray) Date: Wed, 31 Aug 2016 01:19:30 +0000 Subject: [docs] [issue27893] email.parser.BytesParser.parsebytes docs fix In-Reply-To: <1472595443.04.0.800364435102.issue27893@psf.upfronthosting.co.za> Message-ID: <1472606370.57.0.147411625109.issue27893@psf.upfronthosting.co.za> Changes by R. David Murray : ---------- resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 30 21:29:31 2016 From: report at bugs.python.org (Anthony Flury) Date: Wed, 31 Aug 2016 01:29:31 +0000 Subject: [docs] [issue27901] inspect.ismethod returns different results on the same basic code between Python2.7 Python3.5 In-Reply-To: <1472585181.25.0.672560198795.issue27901@psf.upfronthosting.co.za> Message-ID: <1472606971.12.0.900612809118.issue27901@psf.upfronthosting.co.za> Anthony Flury added the comment: Assuming the reader knows the details of how Python works is not a great assumption when those documents are being used (by the most part) by people like me who are reasonable developers but who don't know, and for most cases don't care about the internals of Python. The inspect library is a bit different I conceed, as the user is starting to poke under the belly of the beast as it were, but i do think it would be useful to link from Inspect to the data model docs, were the terminology is discussed in more detail. If I had tried to port my existing code to Python3.5, and it would have failed it's test set at this point - I don't think that the inspect library docs as they are would have helped. I know inspect is deliving into the internals - but for most people a block of code within a def block within a class definition is a method - that is what everyone refers to them - even though internally they aren't bound, and aren't 'methods' strictly speaking - I think the docs should try to bridge the gap between common (non expert) language and the correct language terminology where neccessary ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 31 00:15:30 2016 From: report at bugs.python.org (Martin Panter) Date: Wed, 31 Aug 2016 04:15:30 +0000 Subject: [docs] [issue27895] Spelling fixes In-Reply-To: <1472579160.51.0.388214887835.issue27895@psf.upfronthosting.co.za> Message-ID: <1472616930.41.0.319518032138.issue27895@psf.upfronthosting.co.za> Martin Panter added the comment: Be careful with user-visible changes to the code, like the _encoded_EMTPY attribute (Issue 27630). I wouldn?t backport that. ---------- nosy: +martin.panter versions: +Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 31 02:13:05 2016 From: report at bugs.python.org (SilentGhost) Date: Wed, 31 Aug 2016 06:13:05 +0000 Subject: [docs] [issue27895] Spelling fixes In-Reply-To: <1472579160.51.0.388214887835.issue27895@psf.upfronthosting.co.za> Message-ID: <1472623985.54.0.880921897922.issue27895@psf.upfronthosting.co.za> Changes by SilentGhost : ---------- stage: -> resolved _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 31 02:43:04 2016 From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=) Date: Wed, 31 Aug 2016 06:43:04 +0000 Subject: [docs] [issue27895] Spelling fixes In-Reply-To: <1472579160.51.0.388214887835.issue27895@psf.upfronthosting.co.za> Message-ID: <1472625784.09.0.985840895103.issue27895@psf.upfronthosting.co.za> Ville Skytt? added the comment: @rhettinger, the test_asyncio thing I mentioned is now taken care of in #27907. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 31 06:04:49 2016 From: report at bugs.python.org (Tomas Orsava) Date: Wed, 31 Aug 2016 10:04:49 +0000 Subject: [docs] =?utf-8?q?=5Bissue27910=5D_Doc/library/traceback=2Erst_?= =?utf-8?q?=E2=80=94_references_to_tuples_should_be_replaced_with_new_Fram?= =?utf-8?q?eSummary_object?= Message-ID: <1472637889.08.0.384463773035.issue27910@psf.upfronthosting.co.za> New submission from Tomas Orsava: In the documentation for the `traceback` module, the definitions of functions `extract_tb` [0], `format_list` [1] and classmethod `from_list` [2] mention the old style (4-)tuples that these functions used to return or accept. Since Python 3.5, however, they return or accept a FrameSummary object instead of the 4-tuple, or a StackSummary object instead of a list of 4-tuples. I'm including a patch that fixes these definitions to make them reflect the new reality. [0] https://docs.python.org/3.6/library/traceback.html#traceback.extract_tb [1] https://docs.python.org/3.6/library/traceback.html#traceback.format_list [2] https://docs.python.org/3.6/library/traceback.html#traceback.StackSummary.from_list ---------- assignee: docs at python components: Documentation files: traceback-doc.patch keywords: patch messages: 274010 nosy: docs at python, torsava priority: normal severity: normal status: open title: Doc/library/traceback.rst ? references to tuples should be replaced with new FrameSummary object versions: Python 3.5, Python 3.6 Added file: http://bugs.python.org/file44293/traceback-doc.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 31 06:08:25 2016 From: report at bugs.python.org (SilentGhost) Date: Wed, 31 Aug 2016 10:08:25 +0000 Subject: [docs] =?utf-8?q?=5Bissue27910=5D_Doc/library/traceback=2Erst_?= =?utf-8?q?=E2=80=94_references_to_tuples_should_be_replaced_with_new_Fram?= =?utf-8?q?eSummary_object?= In-Reply-To: <1472637889.08.0.384463773035.issue27910@psf.upfronthosting.co.za> Message-ID: <1472638105.14.0.498592355453.issue27910@psf.upfronthosting.co.za> Changes by SilentGhost : ---------- stage: -> patch review type: -> behavior _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 31 06:09:00 2016 From: report at bugs.python.org (SilentGhost) Date: Wed, 31 Aug 2016 10:09:00 +0000 Subject: [docs] =?utf-8?q?=5Bissue27910=5D_Doc/library/traceback=2Erst_?= =?utf-8?q?=E2=80=94_references_to_tuples_should_be_replaced_with_new_Fram?= =?utf-8?q?eSummary_object?= In-Reply-To: <1472637889.08.0.384463773035.issue27910@psf.upfronthosting.co.za> Message-ID: <1472638140.66.0.588532242627.issue27910@psf.upfronthosting.co.za> SilentGhost added the comment: LGTM. ---------- nosy: +SilentGhost stage: patch review -> commit review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 31 06:23:13 2016 From: report at bugs.python.org (Berker Peksag) Date: Wed, 31 Aug 2016 10:23:13 +0000 Subject: [docs] =?utf-8?q?=5Bissue27910=5D_Doc/library/traceback=2Erst_?= =?utf-8?q?=E2=80=94_references_to_tuples_should_be_replaced_with_new_Fram?= =?utf-8?q?eSummary_object?= In-Reply-To: <1472637889.08.0.384463773035.issue27910@psf.upfronthosting.co.za> Message-ID: <1472638993.51.0.617675885388.issue27910@psf.upfronthosting.co.za> Berker Peksag added the comment: I think we need to decide whether this is a documentation bug or a regression in traceback module. See also issue 25573 for a similar report. ---------- nosy: +berker.peksag, r.david.murray, rbcollins stage: commit review -> patch review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 31 06:41:57 2016 From: report at bugs.python.org (R. David Murray) Date: Wed, 31 Aug 2016 10:41:57 +0000 Subject: [docs] [issue27895] Spelling fixes In-Reply-To: <1472579160.51.0.388214887835.issue27895@psf.upfronthosting.co.za> Message-ID: <1472640117.12.0.0899721264592.issue27895@psf.upfronthosting.co.za> R. David Murray added the comment: Good point, Martin, but I'd actually be OK with backporting that particular one. It is relatively new, and I doubt anyone is using it. Sorry for dropping the ball on the other issue. ---------- nosy: +r.david.murray _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 31 07:23:30 2016 From: report at bugs.python.org (Tomas Orsava) Date: Wed, 31 Aug 2016 11:23:30 +0000 Subject: [docs] =?utf-8?q?=5Bissue27910=5D_Doc/library/traceback=2Erst_?= =?utf-8?q?=E2=80=94_references_to_tuples_should_be_replaced_with_new_Fram?= =?utf-8?q?eSummary_object?= In-Reply-To: <1472637889.08.0.384463773035.issue27910@psf.upfronthosting.co.za> Message-ID: <1472642610.26.0.875041103433.issue27910@psf.upfronthosting.co.za> Tomas Orsava added the comment: Hi Berker: It's a bit complicated?this specific issue I opened isn't a regression, because it's exactly the change that was intended: Use FrameSummary instead of a 4-tuple to pass the frame data. If you see the last comment for the issue 25573 you linked to, that issue has already been resolved by the docs being updated to reflect the new way of passing data. However, that is not to say there can't be regressions connected to this, but they have to do with the fact that FrameSummary implements only a subset of methods available of tuples. E.g. that FrameSummary does not implement __len__ like tuple does, see issue 26502. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 31 17:29:22 2016 From: report at bugs.python.org (Ethan Furman) Date: Wed, 31 Aug 2016 21:29:22 +0000 Subject: [docs] [issue26051] Non-data descriptors in pydoc In-Reply-To: <1452295309.05.0.476253695659.issue26051@psf.upfronthosting.co.za> Message-ID: <1472678962.63.0.100250373689.issue26051@psf.upfronthosting.co.za> Changes by Ethan Furman : ---------- nosy: +ethan.furman _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 31 20:24:18 2016 From: report at bugs.python.org (Raymond Hettinger) Date: Thu, 01 Sep 2016 00:24:18 +0000 Subject: [docs] [issue26051] Non-data descriptors in pydoc In-Reply-To: <1452295309.05.0.476253695659.issue26051@psf.upfronthosting.co.za> Message-ID: <1472689458.42.0.0152703943974.issue26051@psf.upfronthosting.co.za> Changes by Raymond Hettinger : ---------- nosy: +rhettinger priority: normal -> low type: -> enhancement versions: -Python 3.5 _______________________________________ Python tracker _______________________________________