From kreut at hotmail.com  Mon Feb  1 07:54:08 2016
From: kreut at hotmail.com (Eric Kean)
Date: Mon, 1 Feb 2016 04:54:08 -0800
Subject: [docs] Small typo
Message-ID: <BLU437-SMTP823B7ADCB6D335F9E561A7B2DE0@phx.gbl>

Hi,

First off, I'm just learning Python (coming from PHP) and these docs are *super* clear.  I did, however, notice one typo:

In the description of list.pop() in https://docs.python.org/3/tutorial/datastructures.html,  "the method signature denote that" should be "the method signature denotes that".  

Kind regards,

Eric

From founder at ten3.org  Mon Feb  1 08:45:23 2016
From: founder at ten3.org (Anthony Petrillo)
Date: Mon, 1 Feb 2016 08:45:23 -0500
Subject: [docs] making a python doc build available in Africa where
 there is no internet
In-Reply-To: <CAPOVWOQGo8D1dgN4mLn1gGQFXRmz_yATs0SMGKQd+xK34taNTQ@mail.gmail.com>
References: <CA+v5LHEHZ8SZh9vQoCaZdjNX69Uki9Ux_OMMKSh3ZW+Fb5ko6A@mail.gmail.com>
 <CAPOVWOQGo8D1dgN4mLn1gGQFXRmz_yATs0SMGKQd+xK34taNTQ@mail.gmail.com>
Message-ID: <CA+v5LHEAJHc3mAgzwgKuERCEqpcACvmUbu5iQG-jwBVpbkfocQ@mail.gmail.com>

Thank you very much.

I guess my brain went to sleep. I saw the html download but for some reason
wasn't thinking it would be the one I could to the intersphinx with. I
appreciate you pointing me there.

Anthony

On Sun, Jan 31, 2016 at 10:05 AM, Senthil Kumaran <senthil at uthcode.com>
wrote:

>
> On Fri, Jan 29, 2016 at 8:03 PM, Anthony Petrillo <founder at ten3.org>
> wrote:
>
>> Would it be possible to get a copy of one of your build directories (or
>> whatever you call them) for Python 3.3, 3.4 or 3.5. We do not need them
>> all. Just one.
>
>
> Here you can download these:
>
> https://docs.python.org/3/download.html
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160201/62a95f98/attachment.html>

From report at bugs.python.org  Mon Feb  1 09:18:10 2016
From: report at bugs.python.org (Ben Hoyt)
Date: Mon, 01 Feb 2016 14:18:10 +0000
Subject: [docs] [issue26248] Improve scandir DirEntry docs,
 especially re symlinks and caching
In-Reply-To: <1454258622.6.0.285150622743.issue26248@psf.upfronthosting.co.za>
Message-ID: <1454336290.61.0.509337381136.issue26248@psf.upfronthosting.co.za>


Ben Hoyt added the comment:

Thanks, Victor!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26248>
_______________________________________

From report at bugs.python.org  Mon Feb  1 12:21:22 2016
From: report at bugs.python.org (Antti Haapala)
Date: Mon, 01 Feb 2016 17:21:22 +0000
Subject: [docs] [issue26261] NamedTemporaryFile documentation is vague about
 the `name` attribute
Message-ID: <1454347282.51.0.892341568817.issue26261@psf.upfronthosting.co.za>


New submission from Antti Haapala:

The documentation for NamedTemporaryFile is a bit vague. It says

[--] That name can be retrieved from the name attribute of the file object. [--] The returned object is always a file-like object whose file
attribute is the underlying true file object. This file-like object can be used in a with statement, just like a normal file.

That `file-like object` vs `true file object` made me assume that I need to do

    f = NamedTemporaryFile()
    f.file.name

to get the filename, which sort of worked, but only later realized that `f.file.name` is actually the file descriptor number on Linux, a.k.a an integer. Thus I suggest that the one sentence be changed to "That name can be retrieved from the name attribute of the returned file-like object."

----------
assignee: docs at python
components: Documentation
messages: 259334
nosy: docs at python, ztane
priority: normal
severity: normal
status: open
title: NamedTemporaryFile documentation is vague about the `name` attribute

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26261>
_______________________________________

From report at bugs.python.org  Mon Feb  1 12:21:37 2016
From: report at bugs.python.org (Antti Haapala)
Date: Mon, 01 Feb 2016 17:21:37 +0000
Subject: [docs] [issue26261] NamedTemporaryFile documentation is vague about
 the `name` attribute
In-Reply-To: <1454347282.51.0.892341568817.issue26261@psf.upfronthosting.co.za>
Message-ID: <1454347297.07.0.0137642162956.issue26261@psf.upfronthosting.co.za>


Changes by Antti Haapala <antti at haapala.name>:


----------
type:  -> enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26261>
_______________________________________

From zachary.ware+pydocs at gmail.com  Mon Feb  1 12:28:21 2016
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Mon, 1 Feb 2016 11:28:21 -0600
Subject: [docs] Small typo
In-Reply-To: <BLU437-SMTP823B7ADCB6D335F9E561A7B2DE0@phx.gbl>
References: <BLU437-SMTP823B7ADCB6D335F9E561A7B2DE0@phx.gbl>
Message-ID: <CAKJDb-MgFwhF+P-D8V-iejrEPm8gk+hzgWmmSwVdQ_JH3En+0g@mail.gmail.com>

On Mon, Feb 1, 2016 at 6:54 AM, Eric Kean <kreut at hotmail.com> wrote:
> Hi,
>
> First off, I'm just learning Python (coming from PHP) and these docs are *super* clear.

Thank you!  We try to keep our documentation high quality, and reports
like yours are a big help in that regard.

> I did, however, notice one typo:
>
> In the description of list.pop() in https://docs.python.org/3/tutorial/datastructures.html,  "the method signature denote that" should be "the method signature denotes that".

In this case, it is correct as written.  Looking earlier in the
sentence, the subject is 'the square brackets' and you wouldn't say
"the square brackets denotes" since brackets is plural.

Thank you for the report, though!  Please do report any other typos or
inaccuracies that you come across.

Regards,
-- 
Zach

From kreut at hotmail.com  Mon Feb  1 13:00:28 2016
From: kreut at hotmail.com (Eric Kean)
Date: Mon, 1 Feb 2016 10:00:28 -0800
Subject: [docs] Small typo
In-Reply-To: <CAKJDb-MgFwhF+P-D8V-iejrEPm8gk+hzgWmmSwVdQ_JH3En+0g@mail.gmail.com>
References: <BLU437-SMTP823B7ADCB6D335F9E561A7B2DE0@phx.gbl>,
 <CAKJDb-MgFwhF+P-D8V-iejrEPm8gk+hzgWmmSwVdQ_JH3En+0g@mail.gmail.com>
Message-ID: <BAY180-W1D6FD07E83B7C8F1FCFC4B2DE0@phx.gbl>

You bet!  And the documentation quality is definitely super high as compared to say, PHP.

Regards,

Eric

> From: zachary.ware+pydocs at gmail.com
> Date: Mon, 1 Feb 2016 11:28:21 -0600
> Subject: Re: [docs] Small typo
> To: docs at python.org
> CC: kreut at hotmail.com
> 
> On Mon, Feb 1, 2016 at 6:54 AM, Eric Kean <kreut at hotmail.com> wrote:
> > Hi,
> >
> > First off, I'm just learning Python (coming from PHP) and these docs are *super* clear.
> 
> Thank you!  We try to keep our documentation high quality, and reports
> like yours are a big help in that regard.
> 
> > I did, however, notice one typo:
> >
> > In the description of list.pop() in https://docs.python.org/3/tutorial/datastructures.html,  "the method signature denote that" should be "the method signature denotes that".
> 
> In this case, it is correct as written.  Looking earlier in the
> sentence, the subject is 'the square brackets' and you wouldn't say
> "the square brackets denotes" since brackets is plural.
> 
> Thank you for the report, though!  Please do report any other typos or
> inaccuracies that you come across.
> 
> Regards,
> -- 
> Zach
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160201/fa8eea85/attachment.html>

From report at bugs.python.org  Mon Feb  1 21:37:35 2016
From: report at bugs.python.org (Martin Panter)
Date: Tue, 02 Feb 2016 02:37:35 +0000
Subject: [docs] [issue26261] NamedTemporaryFile documentation is vague about
 the `name` attribute
In-Reply-To: <1454347282.51.0.892341568817.issue26261@psf.upfronthosting.co.za>
Message-ID: <1454380654.96.0.788823975521.issue26261@psf.upfronthosting.co.za>


Martin Panter added the comment:

Also the doc string could be updated. I guess suggesting ?file.name? is even more confusing :)

----------
nosy: +martin.panter
stage:  -> needs patch
versions: +Python 2.7, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26261>
_______________________________________

From report at bugs.python.org  Tue Feb  2 02:52:41 2016
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 02 Feb 2016 07:52:41 +0000
Subject: [docs] [issue26244] zlib.compressobj level default value
 documentation
In-Reply-To: <1454179728.88.0.137425597988.issue26244@psf.upfronthosting.co.za>
Message-ID: <20160202075238.20013.2800@psf.io>


Roundup Robot added the comment:

New changeset 650cf38fba28 by Martin Panter in branch '2.7':
Issue #26244: Clarify default zlib compression level in documentation
https://hg.python.org/cpython/rev/650cf38fba28

New changeset 950e0bfe94ae by Martin Panter in branch '3.5':
Issue #26244: Clarify default zlib compression level in documentation
https://hg.python.org/cpython/rev/950e0bfe94ae

New changeset 03708c680eca by Martin Panter in branch 'default':
Issue #26244: Merge zlib documentation from 3.5
https://hg.python.org/cpython/rev/03708c680eca

----------
nosy: +python-dev

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26244>
_______________________________________

From report at bugs.python.org  Tue Feb  2 04:57:19 2016
From: report at bugs.python.org (Martin Panter)
Date: Tue, 02 Feb 2016 09:57:19 +0000
Subject: [docs] [issue26244] zlib.compressobj level default value
 documentation
In-Reply-To: <1454179728.88.0.137425597988.issue26244@psf.upfronthosting.co.za>
Message-ID: <1454407039.13.0.273700788165.issue26244@psf.upfronthosting.co.za>


Martin Panter added the comment:

I also made a small change to the compressobj() doc string.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26244>
_______________________________________

From report at bugs.python.org  Tue Feb  2 06:33:17 2016
From: report at bugs.python.org (Martin Panter)
Date: Tue, 02 Feb 2016 11:33:17 +0000
Subject: [docs] =?utf-8?q?=5Bissue23200=5D_Deprecate_the_zlib_decompressor?=
 =?utf-8?b?4oCZcyBmbHVzaCgpIG1ldGhvZA==?=
In-Reply-To: <1420766781.53.0.179588350228.issue23200@psf.upfronthosting.co.za>
Message-ID: <1454412797.64.0.518266909584.issue23200@psf.upfronthosting.co.za>


Martin Panter added the comment:

New version of the patch merged with current code and cleaning up the zipfile EOF detection.

----------
Added file: http://bugs.python.org/file41780/deprecate-flush.v2.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23200>
_______________________________________

From cdragan at micron.com  Tue Feb  2 12:32:30 2016
From: cdragan at micron.com (Cristian Dragan (cdragan))
Date: Tue, 2 Feb 2016 17:32:30 +0000
Subject: [docs] Python tutorial - example on "range" function (chapter
 Built-in Functions)
Message-ID: <1aefa9c10ce24096bf1089d57967792c@bowex17c.micron.com>

Hi,

According to the definition of the range function (within the Python tutorial 2.7.11) I assume that

>>> range(1, 0)

Should have 1 element: [1], while the tutorial specify: [].

Please let me know if I misunderstood the definition of the "range" function.

Thank you very much,
Cristian Dragan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160202/2b0220db/attachment.html>

From georg at python.org  Tue Feb  2 12:57:31 2016
From: georg at python.org (Georg Brandl)
Date: Tue, 2 Feb 2016 18:57:31 +0100
Subject: [docs] Python tutorial - example on "range" function (chapter
 Built-in Functions)
In-Reply-To: <1aefa9c10ce24096bf1089d57967792c@bowex17c.micron.com>
References: <1aefa9c10ce24096bf1089d57967792c@bowex17c.micron.com>
Message-ID: <56B0EE0B.4020504@python.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/02/2016 06:32 PM, Cristian Dragan (cdragan) wrote:
> Hi,
> 
> 
> 
> According to the definition of the range function (within the Python
> tutorial 2.7.11) I assume that
> 
> 
> 
> />>> range(1, 0)/
> 
> 
> 
> Should have 1 element: [1], while the tutorial specify: [].
> 
> 
> 
> Please let me know if I misunderstood the definition of the ?range?
> function.

Hi Cristian,

as far as I can see, the tutorial only contains an informal description of
range(), which covers the basic use.  Corner cases like this should be
covered by the library docs, which you get to when you click the range()
link.

Unfortunately, that text doesn't fully specify this case either, although
the example code shows both range(0) and range(1, 0) being empty.

So I think that the range() docs should be amended.  In Python 3, the text
is much clearer: https://docs.python.org/3/library/stdtypes.html#range

If you'd like the tutorial text to change as well, can you tell us more
specifically where?

cheers,
Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlaw7gsACgkQN9GcIYhpnLAHIgCfUZdKHjsLHhGpEv0HvBeyUnPO
loMAoK3JDjJQVxejGUfOBzFjF/PAtV/h
=fW3L
-----END PGP SIGNATURE-----

From report at bugs.python.org  Tue Feb  2 13:43:09 2016
From: report at bugs.python.org (Andrew Barnert)
Date: Tue, 02 Feb 2016 18:43:09 +0000
Subject: [docs] [issue26267] UUID docs should say how to get "standard form"
Message-ID: <1454438589.41.0.991764109365.issue26267@psf.upfronthosting.co.za>


New submission from Andrew Barnert:

Most real-world code that uses the UUID module wants either the standard format '{12345678-1234-5678-1234-567812345678}', or the same thing without the braces.

There are a number of different documented accessors, but none of them give you either of these. The simplest way I can think of to guarantee the standard format from what's documented is '{%08x-%04x-%04x-%02x%02x-%12x}' % u.fields.

It might be nice to add accessors for standard form and braceless standard form, but that probably isn't necessary--as long as there's documentation saying that __str__ returns the braceless standard form.

The example code does say that, but I don't think people can trust that a comment in an example is binding documentation--plus, plenty of people don't read the examples looking for more information about things that aren't documented. And I've seen people come up with buggy versions of the format string that miss leading zeros, or horrible things like repr(u)[6:42].

----------
assignee: docs at python
components: Documentation
messages: 259414
nosy: abarnert, docs at python
priority: normal
severity: normal
status: open
title: UUID docs should say how to get "standard form"
type: enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26267>
_______________________________________

From report at bugs.python.org  Tue Feb  2 14:08:09 2016
From: report at bugs.python.org (SilentGhost)
Date: Tue, 02 Feb 2016 19:08:09 +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: <1454440089.91.0.264320028732.issue26267@psf.upfronthosting.co.za>


SilentGhost added the comment:

The docs seem to clearly show a str(x) as the way to produce the desired form (without braces). https://docs.python.org/3/library/uuid.html#example

----------
nosy: +SilentGhost

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26267>
_______________________________________

From report at bugs.python.org  Tue Feb  2 14:09:30 2016
From: report at bugs.python.org (Andrew Barnert)
Date: Tue, 02 Feb 2016 19:09:30 +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: <1454440170.58.0.593072045407.issue26267@psf.upfronthosting.co.za>


Andrew Barnert added the comment:

> The docs seem to clearly show a str(x) as the way to produce the desired form (without braces). https://docs.python.org/3/library/uuid.html#example

Please read the last paragraph of the original message.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26267>
_______________________________________

From report at bugs.python.org  Tue Feb  2 14:23:30 2016
From: report at bugs.python.org (Timo Furrer)
Date: Tue, 02 Feb 2016 19:23:30 +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: <1454441010.84.0.0295368556411.issue26267@psf.upfronthosting.co.za>


Changes by Timo Furrer <tuxtimo at gmail.com>:


----------
nosy: +tuxtimo

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26267>
_______________________________________

From report at bugs.python.org  Tue Feb  2 14:38:53 2016
From: report at bugs.python.org (SilentGhost)
Date: Tue, 02 Feb 2016 19:38:53 +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: <1454441933.56.0.97907579776.issue26267@psf.upfronthosting.co.za>


SilentGhost added the comment:

Well, you seem to suggest we add something to documentation to accommodate people who don't read it in the first place.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26267>
_______________________________________

From report at bugs.python.org  Tue Feb  2 16:02:01 2016
From: report at bugs.python.org (Andrew Barnert)
Date: Tue, 02 Feb 2016 21:02:01 +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: <1454446921.95.0.161558650141.issue26267@psf.upfronthosting.co.za>


Andrew Barnert added the comment:

No, I suggest we add something for users who don't think that a comment in an example is the place to look for documentation, but do think that actual documentation of a class or method is.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26267>
_______________________________________

From report at bugs.python.org  Tue Feb  2 16:13:38 2016
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 02 Feb 2016 21:13:38 +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: <1454447618.74.0.735957321513.issue26267@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Andrew is right, this should be documented "properly".

----------
nosy: +georg.brandl

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26267>
_______________________________________

From report at bugs.python.org  Tue Feb  2 16:17:50 2016
From: report at bugs.python.org (=?utf-8?q?Gedai_Tam=C3=A1s_Bence?=)
Date: Tue, 02 Feb 2016 21:17:50 +0000
Subject: [docs] [issue26261] NamedTemporaryFile documentation is vague about
 the `name` attribute
In-Reply-To: <1454347282.51.0.892341568817.issue26261@psf.upfronthosting.co.za>
Message-ID: <1454447870.4.0.21286067996.issue26261@psf.upfronthosting.co.za>


Gedai Tam?s Bence added the comment:

Antti, would you like to provide a patch? If you don't want to work on it, I can give it a try.

----------
nosy: +beng94

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26261>
_______________________________________

From jontetlak at gmail.com  Tue Feb  2 17:53:06 2016
From: jontetlak at gmail.com (Jon Tetlak)
Date: Tue, 2 Feb 2016 16:53:06 -0600
Subject: [docs] Type on the 26.1 typing page
Message-ID: <CANvaVHVdxPd6t0FKmzJ9n80vYxqGNafh=vyoEn9Nr8RCngCsug@mail.gmail.com>

26.1. typing ? Support for type hints ? Python 3.5.1 documentation

https://docs.python.org/3/library/typing.html

At the top section, in the last sentence, ..."expected to by of type
str"... should say *be *instead of *by *correct? Really minor typo, but
found it and figured I would pass it along.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160202/c8b1fbfe/attachment.html>

From zachary.ware+pydocs at gmail.com  Tue Feb  2 18:07:35 2016
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Tue, 2 Feb 2016 17:07:35 -0600
Subject: [docs] Type on the 26.1 typing page
In-Reply-To: <CANvaVHVdxPd6t0FKmzJ9n80vYxqGNafh=vyoEn9Nr8RCngCsug@mail.gmail.com>
References: <CANvaVHVdxPd6t0FKmzJ9n80vYxqGNafh=vyoEn9Nr8RCngCsug@mail.gmail.com>
Message-ID: <CAKJDb-PC0ZT+gEQdULkqUzwS_=yCFb5FYWbevHbwX3ymWGUfQg@mail.gmail.com>

On Tue, Feb 2, 2016 at 4:53 PM, Jon Tetlak <jontetlak at gmail.com> wrote:
> 26.1. typing ? Support for type hints ? Python 3.5.1 documentation
>
> https://docs.python.org/3/library/typing.html
>
> At the top section, in the last sentence, ..."expected to by of type str"...
> should say be instead of by correct? Really minor typo, but found it and
> figured I would pass it along.

Thanks for the report!  Fixed in
https://hg.python.org/cpython/rev/e4eb2a8fdb7c/ and will be live on
the web soon.

Regards,
-- 
Zach

From report at bugs.python.org  Tue Feb  2 22:52:29 2016
From: report at bugs.python.org (Lorenzo Ancora)
Date: Wed, 03 Feb 2016 03:52:29 +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: <1454471548.91.0.6110567569.issue26209@psf.upfronthosting.co.za>


Lorenzo Ancora added the comment:

(msg259229) Terry J. Reedy i Suggest that a standard and globally accepted scheme to manage IPv4 addresses is:

  "Host:PortNumber" --> (host, PortNumber)
  "Host"            --> (host, DefaultPortNumber)
  "IP:PortNumber" --> (host, PortNumber)
  "IP"            --> (host, DefaultPortNumber)

...where DefaultPortNumber is protocol and system dependent (IANA standard, see the SMTP line in: http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml).

A simple research reveals that all versions of the module are (sadly) poorly documented, but the module is an interface to a very important protocol that indeed must be offered by the standard library.
The only little suggestion in the documentation of the module is: https://docs.python.org/3.6/library/socket.html#socket.socket.accept
...from a one-word link in: https://docs.python.org/3.6/library/smtpd.html#smtpd.SMTPChannel.addr
Which has only an indirect relation with the object itself.

Many users may not recognize the cause of the error if the documentation doesn't explicitate the information to correctly initialize the core objects of the module.
I also Suggest that at least the object should return an helpful error in newer versions of Python.

Thank you for your efforts guys. :-)

----------
components: +Library (Lib)
versions: +Python 3.2, Python 3.3, Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26209>
_______________________________________

From salony.permanand at gmail.com  Wed Feb  3 01:56:12 2016
From: salony.permanand at gmail.com (Salony Permanand)
Date: Wed, 3 Feb 2016 12:26:12 +0530
Subject: [docs] problem in installing python
Message-ID: <CAKbdRk3GObigxWQ4RHyXGRJZO=PN0-xwZUBbj-LAFCPrABBWfg@mail.gmail.com>

sir,
I downloaded different version of python but no one is installed on my pc
because of same installation error each time having error code 2203.
Please solve it...
Thanking you


Salony Permanand
IIT Allahabad
7275838206
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160203/ea3a0c0f/attachment-0001.html>

From report at bugs.python.org  Wed Feb  3 04:42:27 2016
From: report at bugs.python.org (Jurjen N.E. Bos)
Date: Wed, 03 Feb 2016 09:42:27 +0000
Subject: [docs] [issue26256] Fast decimalisation and conversion to other
 bases
In-Reply-To: <1454322513.41.0.794136944555.issue26256@psf.upfronthosting.co.za>
Message-ID: <1454492547.73.0.915660717034.issue26256@psf.upfronthosting.co.za>


Jurjen N.E. Bos added the comment:

OMG is decimal that fast?
Maybe I should change the issue then to "documentation missing": it nowhere says in the documentation that decimal has optimized multiprecision computations. It only says that precision "can be as large as needed for a given problem", but I never realized that that included millions of digits.
It computed to my complete surprise 2**2**29 to full precision (161 million decimal digits) in about a minute. That smells suspiciously like FFT style multiplication, which implies that it is way more sophisticated than integer multiplication!
I suggest that the documentation of the decimal module recommends using decimal for multiprecision computations, as long as you use the builtin version.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python
versions: +Python 3.4 -Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26256>
_______________________________________

From report at bugs.python.org  Wed Feb  3 04:51:53 2016
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 03 Feb 2016 09:51:53 +0000
Subject: [docs] [issue26256] Fast decimalisation and conversion to other
 bases
In-Reply-To: <1454322513.41.0.794136944555.issue26256@psf.upfronthosting.co.za>
Message-ID: <1454493113.31.0.355157643012.issue26256@psf.upfronthosting.co.za>


STINNER Victor added the comment:

"It's great to have this stuff, but I don't think it belongs in core Python: I'd much rather that the core Python integer implementation remain simple, portable and low-maintenance, and work well for the domain it's intended for: small-to-medium size integers."

Yeah I agree. Maybe we need to explain that somewhere? In the devguide? Even in Python doc?

I know that they are super crazy^W fast algorithm to handle very large numbers (hum, what is large? more than 4096 bits?), but they are usually very complex.

Projects like GMP have ultra fast code with optimizations in assemblers. Having assembler implementation is clearly out of the scope of Python.


"Maybe I should change the issue then to "documentation missing": it nowhere says in the documentation that decimal has optimized multiprecision computations."

Well, nowhere means:
https://docs.python.org/dev/whatsnew/3.3.html#decimal

Usually, we don't document performances of a function, maybe only its complexity.

--

You may move to the numpy community which is problably more keen on such optimization than the Python *core*.

----------
nosy: +haypo

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26256>
_______________________________________

From report at bugs.python.org  Wed Feb  3 05:00:18 2016
From: report at bugs.python.org (Jurjen N.E. Bos)
Date: Wed, 03 Feb 2016 10:00:18 +0000
Subject: [docs] [issue26256] Fast decimalisation and conversion to other
 bases
In-Reply-To: <1454322513.41.0.794136944555.issue26256@psf.upfronthosting.co.za>
Message-ID: <1454493618.73.0.590664111844.issue26256@psf.upfronthosting.co.za>


Jurjen N.E. Bos added the comment:

That reference you gave says that the binary version is faster than the Python version, but here the _complexity_ actually changed by a lot.
Only people who know the library by name will notice that it is this fast.
But you are right, for 99% of the people it doesn't make much of a difference.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26256>
_______________________________________

From report at bugs.python.org  Wed Feb  3 05:41:36 2016
From: report at bugs.python.org (Stefan Krah)
Date: Wed, 03 Feb 2016 10:41:36 +0000
Subject: [docs] [issue26256] Fast decimalisation and conversion to other
 bases
In-Reply-To: <1454493113.31.0.355157643012.issue26256@psf.upfronthosting.co.za>
Message-ID: <20160203104125.GA17635@bytereef.org>


Stefan Krah added the comment:

On Wed, Feb 03, 2016 at 09:51:53AM +0000, STINNER Victor wrote:
> Well, nowhere means:
> https://docs.python.org/dev/whatsnew/3.3.html#decimal

Okay, but hardly anyone reads that, and I can't blame them. :)

For example, if I use something like Lua, I won't read a release announcement
from 2012.

> Usually, we don't document performances of a function, maybe only its complexity.

As Jurjen said, the presence of the FFT (actually fast number theoretic
transform here) in Decimal is something completely unexpected, so if there's
a place for a line or two in the docs that makes some users happy I'd be
in favor of it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26256>
_______________________________________

From report at bugs.python.org  Wed Feb  3 07:02:44 2016
From: report at bugs.python.org (Terry J. Reedy)
Date: Wed, 03 Feb 2016 12:02:44 +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: <1454500964.02.0.0526607043025.issue26209@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Doc fixes unrelated to security fixes are not applied to security-fix-only versions.

----------
versions:  -Python 3.2, Python 3.3, Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26209>
_______________________________________

From shaharyi88 at gmail.com  Wed Feb  3 15:37:13 2016
From: shaharyi88 at gmail.com (=?UTF-8?B?16nXl9eoINeZ?=)
Date: Wed, 3 Feb 2016 22:37:13 +0200
Subject: [docs] doc bug report
Message-ID: <CACDb2ATMj-v23qG6YnVh_sv8EjeakNS9muT53vFY9AFQcUqAVA@mail.gmail.com>

Hello,

In the client-side code here:
https://docs.python.org/2/library/socketserver.html#socketserver-tcpserver-example

the line:

received = sock.recv(1024)

is a bad programming example.
This is not the proper way to receive data using a socket.
You must receive in a loop until a whole message is received or the socket
is closed (getting empty data).

The least you can do is say that this is only for the demo to work in most
cases. I.e., when the machine network card is not too busy.

To clarify, say the network card was busy and only managed to read 5 bytes
in the single recv() call you have. The client-output in this case would be
"PYTHON" and not "PYTHON IS NICE".

Regards,
Shahar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160203/59b6565f/attachment.html>

From Denis.Akhiyarov at woodgroupkenny.com  Wed Feb  3 22:29:27 2016
From: Denis.Akhiyarov at woodgroupkenny.com (AKHIYAROV, Denis (WGK))
Date: Thu, 4 Feb 2016 03:29:27 +0000
Subject: [docs] update link - alternative implementation Python for .Net
Message-ID: <3325F0E4B832144293520141988AFFA845C8A78D@WP-EX-MBX-01.WOODGROUP.com>

Python for .Net is now hosted at http://pythonnet.github.io/

Update the links on these pages:

https://docs.python.org/3/reference/introduction.html
https://docs.python.org/2/reference/introduction.html


Thanks,
Denis

Please consider the environment before printing this email.

This email and its attachments may contain information which is confidential and/or legally privileged. If you are not the intended recipient of this e-mail please notify the sender immediately by e-mail and delete this e-mail and its attachments from your computer and IT systems. You must not copy, re-transmit, use or disclose (other than to the sender) the existence or contents of this e-mail or its attachments or permit anyone else to do so.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160204/9a6f0159/attachment.html>

From zachary.ware+pydocs at gmail.com  Wed Feb  3 23:16:56 2016
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Wed, 3 Feb 2016 22:16:56 -0600
Subject: [docs] update link - alternative implementation Python for .Net
In-Reply-To: <3325F0E4B832144293520141988AFFA845C8A78D@WP-EX-MBX-01.WOODGROUP.com>
References: <3325F0E4B832144293520141988AFFA845C8A78D@WP-EX-MBX-01.WOODGROUP.com>
Message-ID: <CAKJDb-Pd_3iA7Nw-DC=WD5M3zYQxS9A-rhVQpViLZ9J=k7werQ@mail.gmail.com>

On Wed, Feb 3, 2016 at 9:29 PM, AKHIYAROV, Denis (WGK)
<Denis.Akhiyarov at woodgroupkenny.com> wrote:
> Python for .Net is now hosted at http://pythonnet.github.io/
>
> Update the links on these pages:
>
> https://docs.python.org/3/reference/introduction.html
> https://docs.python.org/2/reference/introduction.html

Fixed, thanks for the report!

-- 
Zach

From airsoftnut at gmail.com  Thu Feb  4 16:32:50 2016
From: airsoftnut at gmail.com (Simon Smith)
Date: Thu, 4 Feb 2016 23:32:50 +0200
Subject: [docs] Documentation error
Message-ID: <CANeSQamnPBkeM1qmWzSbfcydF6wsrPgHLL9ERrEdnhtXaPEH8A@mail.gmail.com>

Very minor error but I believe:

 The authority, if present, must NOT contain the ?userinfo? component - for
example ?joe at password:example.com? is not correct.

Should read:

 The authority, if present, must NOT contain the ?userinfo? component - for
example ?*joe:password@*example.com? is not correct.

Located on page: https://docs.python.org/3.5/howto/urllib2.html

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160204/5e75d107/attachment.html>

From ashraf.gardizy.it at outlook.com  Thu Feb  4 17:27:45 2016
From: ashraf.gardizy.it at outlook.com (Ashraf gardizy)
Date: Fri, 5 Feb 2016 02:57:45 +0430
Subject: [docs] Need your instruction for choosing GUI framework
Message-ID: <SNT149-W61EB2915A86291CFDDC5C3B4D10@phx.gbl>

To whom may concern,
Hi Dear;
I have recently started development of applications using Python and its awesome and interesting  but I don't know which framework should I use for developing GUI application using Python.kindly instruct me.
Thanks
Ashraf Gardizy Kabul Afghanistan 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160205/7fcf8cd1/attachment.html>

From report at bugs.python.org  Fri Feb  5 04:00:58 2016
From: report at bugs.python.org (Frank Millman)
Date: Fri, 05 Feb 2016 09:00:58 +0000
Subject: [docs] [issue26294] Queue().unfinished_tasks not in docs -
 deliberate?
Message-ID: <1454662858.22.0.0628824582163.issue26294@psf.upfronthosting.co.za>


New submission from Frank Millman:

dir(queue.Queue()) shows an attribute 'unfinished_tasks'.

It appears to be the counter referred to in the docs to 'join()', but it is not documented itself.

I would like to make use of it, but I don't know if it is part of the official API for this module.

Please advise.

----------
assignee: docs at python
components: Documentation
messages: 259645
nosy: docs at python, frankmillman
priority: normal
severity: normal
status: open
title: Queue().unfinished_tasks not in docs - deliberate?
versions: Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26294>
_______________________________________

From report at bugs.python.org  Fri Feb  5 08:03:36 2016
From: report at bugs.python.org (Ben Hoyt)
Date: Fri, 05 Feb 2016 13:03:36 +0000
Subject: [docs] [issue26248] Improve scandir DirEntry docs,
 especially re symlinks and caching
In-Reply-To: <1454258622.6.0.285150622743.issue26248@psf.upfronthosting.co.za>
Message-ID: <1454677416.13.0.560020541232.issue26248@psf.upfronthosting.co.za>


Ben Hoyt added the comment:

Seeing this has been merged (thanks Victor), can this issue be closed? Guido, are you happy with the changes given your comments at http://bugs.python.org/issue26032#msg257665?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26248>
_______________________________________

From report at bugs.python.org  Fri Feb  5 09:04:45 2016
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 05 Feb 2016 14:04:45 +0000
Subject: [docs] [issue26248] Improve scandir DirEntry docs,
 especially re symlinks and caching
In-Reply-To: <1454677416.13.0.560020541232.issue26248@psf.upfronthosting.co.za>
Message-ID: <CAMpsgwY6M1_rsJFt0W8GgwSJX0KiJ2SjdOU-7nCFipeU1Np=gw@mail.gmail.com>


STINNER Victor added the comment:

Ben Hoyt added the comment:
> Seeing this has been merged (thanks Victor), can this issue be closed?

As I wrote, I left the issue open for wait for feedback. I know that
some people to read the doc online:
https://docs.python.org/dev/library/os.html#os.DirEntry

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26248>
_______________________________________

From report at bugs.python.org  Fri Feb  5 16:25:03 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 05 Feb 2016 21:25:03 +0000
Subject: [docs] [issue26248] Improve scandir DirEntry docs,
 especially re symlinks and caching
In-Reply-To: <1454258622.6.0.285150622743.issue26248@psf.upfronthosting.co.za>
Message-ID: <1454707503.76.0.618066385065.issue26248@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Thanks very much for all that added information!

----------
resolution:  -> fixed
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26248>
_______________________________________

From report at bugs.python.org  Fri Feb  5 22:13:56 2016
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 06 Feb 2016 03:13:56 +0000
Subject: [docs] [issue26240] Docstring of the subprocess module should be
 cleaned up
In-Reply-To: <1454131083.41.0.870668221205.issue26240@psf.upfronthosting.co.za>
Message-ID: <1454728436.23.0.489366758604.issue26240@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

I agree. The module docstring should briefly describe the module and maybe list the contents, a line for each.  The itertools docstring does the latter; the math docstring does not, though I would not mind if it did.

----------
nosy: +terry.reedy

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26240>
_______________________________________

From senthil at uthcode.com  Fri Feb  5 22:41:56 2016
From: senthil at uthcode.com (Senthil Kumaran)
Date: Fri, 5 Feb 2016 19:41:56 -0800
Subject: [docs] Documentation error
In-Reply-To: <CANeSQamnPBkeM1qmWzSbfcydF6wsrPgHLL9ERrEdnhtXaPEH8A@mail.gmail.com>
References: <CANeSQamnPBkeM1qmWzSbfcydF6wsrPgHLL9ERrEdnhtXaPEH8A@mail.gmail.com>
Message-ID: <CAPOVWOR2_DpuQgUt6iL9xsxfuy9XbucfMepNA+KOmHyhvs-KLA@mail.gmail.com>

Thanks for the report.

It's fixed in.

3.6:
https://hg.python.org/cpython/rev/0c0a531fd269

3.5
https://hg.python.org/cpython/rev/aca6b47a260c

2.7
https://hg.python.org/cpython/rev/a2a9ff290cb2

-- 
Senthil


On Thu, Feb 4, 2016 at 1:32 PM, Simon Smith <airsoftnut at gmail.com> wrote:

> Very minor error but I believe:
>
>  The authority, if present, must NOT contain the ?userinfo? component -
> for example ?joe at password:example.com? is not correct.
>
> Should read:
>
>  The authority, if present, must NOT contain the ?userinfo? component -
> for example ?*joe:password@*example.com? is not correct.
>
> Located on page: https://docs.python.org/3.5/howto/urllib2.html
>
> Regards
>
> _______________________________________________
> docs mailing list
> docs at python.org
> https://mail.python.org/mailman/listinfo/docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160205/9170886d/attachment.html>

From report at bugs.python.org  Sat Feb  6 07:51:30 2016
From: report at bugs.python.org (Lorenzo Ancora)
Date: Sat, 06 Feb 2016 12:51:30 +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: <1454763090.17.0.868466804463.issue26209@psf.upfronthosting.co.za>


Lorenzo Ancora added the comment:

(msg259475) Terry J. Reedy thank you for the correction, I've confused the versions affected with the versions actually supported.
Since this doesn't only affect the documentation, is it correct to assign the issue to docs at python?
The expert index indicates giampaolo.rodola as the module maintainer, so he should be moved from the nosy list to the field "Assigned To" and docs at python should be in the nosy list.

Also, there is a documentation on how to send a patch for a specific module in Python 3.5?
I'd like to help by creating a new source code patch. :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26209>
_______________________________________

From ardavidbecker at gmail.com  Sat Feb  6 00:41:47 2016
From: ardavidbecker at gmail.com (david becker)
Date: Sat, 6 Feb 2016 11:11:47 +0530
Subject: [docs] Issue with python function names
Message-ID: <CAJ3vjLw+dZSXw3x4kEXraRM97=YoFLH7i6wzs6EDGsjCktm2og@mail.gmail.com>

Hi,

I have a query in using function names. Python allows users to write their
own functions with built-in function names.

Example:
def print():
      return "strange"

print() -- Returns strange
++++++++++++++++++++++++++++

But the built in "print" function doesn't work any more till i restart the
shell.
I personally feel users should not be allowed to use built in function
names. Is there any special reason why python allows them?

Thanks,
David Becker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160206/3d825e0e/attachment-0001.html>

From ardavidbecker at gmail.com  Sat Feb  6 00:49:10 2016
From: ardavidbecker at gmail.com (david becker)
Date: Sat, 6 Feb 2016 11:19:10 +0530
Subject: [docs] Issue with python function names
In-Reply-To: <CAJ3vjLw+dZSXw3x4kEXraRM97=YoFLH7i6wzs6EDGsjCktm2og@mail.gmail.com>
References: <CAJ3vjLw+dZSXw3x4kEXraRM97=YoFLH7i6wzs6EDGsjCktm2og@mail.gmail.com>
Message-ID: <CAJ3vjLy_VBAcWQVhmK+F+MSiOW_CpbLgWqyOp0HH0==cGQAVUw@mail.gmail.com>

And of course the same thing happens if we use them for variable names as
well.

>>> type = 2
>>> type(4)
Traceback (most recent call last):
  File "<pyshell#74>", line 1, in <module>
    type(4)
TypeError: 'int' object is not callable


I feel there is no point in allowing them as they cannot be used. Users are
restricted to use the 32 keywords but we can't force them to remember all
built in function names and not to use them as variable or function names.
:)

Thanks,
David Becker

On Sat, Feb 6, 2016 at 11:11 AM, david becker <ardavidbecker at gmail.com>
wrote:

> Hi,
>
> I have a query in using function names. Python allows users to write their
> own functions with built-in function names.
>
> Example:
> def print():
>       return "strange"
>
> print() -- Returns strange
> ++++++++++++++++++++++++++++
>
> But the built in "print" function doesn't work any more till i restart the
> shell.
> I personally feel users should not be allowed to use built in function
> names. Is there any special reason why python allows them?
>
> Thanks,
> David Becker
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160206/68803518/attachment-0001.html>

From report at bugs.python.org  Sat Feb  6 09:21:38 2016
From: report at bugs.python.org (=?utf-8?q?Tam=C3=A1s_Bence_Gedai?=)
Date: Sat, 06 Feb 2016 14:21:38 +0000
Subject: [docs] [issue20109] TestProgram is mentioned in the unittest docs
 but is not documented
In-Reply-To: <1388685707.72.0.688331916968.issue20109@psf.upfronthosting.co.za>
Message-ID: <1454768498.62.0.596272045299.issue20109@psf.upfronthosting.co.za>


Tam?s Bence Gedai added the comment:

I think TestProgram should be anonymous, all the work is done in its constructor. I don't see why would anyone would call its functions. I can update the docs if it's needed.

----------
nosy: +beng94

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20109>
_______________________________________

From report at bugs.python.org  Sat Feb  6 10:54:22 2016
From: report at bugs.python.org (kernc)
Date: Sat, 06 Feb 2016 15:54:22 +0000
Subject: [docs] [issue26303] Shared execution context between doctests in a
 module
Message-ID: <1454774062.04.0.526927951264.issue26303@psf.upfronthosting.co.za>


New submission from kernc:

The doctest execution context documentation [0] says the tests get shallow *copies* of module's globals, so one test can't mingle with results of another. This makes it impossible to make literate modules such as:


    """
    This module is about reusable doctests context.

    Examples
    --------
    Let's prepare something the later examples can work with:

    >>> import foo
    >>> result = foo.Something()
    2
    
    """
    class Bar:
        """
        Class about something.

        >>> bar = Bar(foo)
        >>> bar.uses(foo)
        True
        
        """
        def baz(self):
            """
            Returns 3.

            >>> result + bar.baz()
            5
            
            """
            return 3


I.e. one has to instantiate everything in every single test. The documentation says one can pass their own globals as `glob=your_dict`, but it doesn't mention the dict is *cleared* after the test run.

Please acknowledge the use case of doctests in a module sharing their environment and results sometimes legitimately exists, and to make it future-compatible, please amend the final paragraph of the relevant part of documentation [0] like so:


    You can force use of your own dict as the execution context by 
    passing `globs=your_dict` to `testmod()` or `testfile()` instead, 
    e.g., to have all doctests in a module use the _same_ execution
    context (sharing variables), define a context like so:
    
        class Context(dict):
            def copy(self):
                return self
            def clear(self):
                pass
    
    and use it, optionally prepopulated with `M`'s globals:
    
        doctest.testmod(module,
                        glob=Context(module.__dict__.copy()))


Thank you!


[0]: https://docs.python.org/3/library/doctest.html#what-s-the-execution-context

----------
assignee: docs at python
components: Documentation
messages: 259731
nosy: docs at python, kernc
priority: normal
severity: normal
status: open
title: Shared execution context between doctests in a module
type: enhancement
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26303>
_______________________________________

From report at bugs.python.org  Sat Feb  6 11:16:50 2016
From: report at bugs.python.org (kernc)
Date: Sat, 06 Feb 2016 16:16:50 +0000
Subject: [docs] [issue26303] Shared execution context between doctests in a
 module
In-Reply-To: <1454774062.04.0.526927951264.issue26303@psf.upfronthosting.co.za>
Message-ID: <1454775410.48.0.717673977371.issue26303@psf.upfronthosting.co.za>


kernc added the comment:

The use case is not unpopular [1] and with unambiguous examples like

    >>> arr = np.arange(5)
    >>> my_sum(arr)
    10

(i.e., without importing numpy as np everywhere), it also makes a lot of sense.


[1]: http://stackoverflow.com/questions/13106118/object-reuse-in-python-doctest/35242443

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26303>
_______________________________________

From report at bugs.python.org  Sat Feb  6 13:41:49 2016
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 06 Feb 2016 18:41:49 +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: <1454784109.83.0.101627766824.issue26209@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Code patches should not be assigned to 'docs'.  But Berker, for the reason stated, thinks this should be doc only.  Giampaolo is not currently active, so should not be assigned the issue by anyone else.

After making a patch -- see the devguide -- use the File: Browse button to upload a file.  You can suggest a specific doc change in a message, without a .patch or .diff file.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26209>
_______________________________________

From report at bugs.python.org  Sat Feb  6 13:45:22 2016
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 06 Feb 2016 18:45:22 +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: <1454784322.06.0.587624850573.issue26209@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Note that the proposed code change would be a 3.6 only enhancement.  Adding the other versions was part of changing to a doc-only issue.  Note also that if the module is not deprecated, then a 3.6 code change could be considered.  But only a doc change for now.

----------
dependencies: +Deprecate smtpd (based on deprecated asyncore/asynchat): write a new smtp server with asyncio

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26209>
_______________________________________

From report at bugs.python.org  Sat Feb  6 15:32:35 2016
From: report at bugs.python.org (Aviv Palivoda)
Date: Sat, 06 Feb 2016 20:32:35 +0000
Subject: [docs] [issue26250] no document for sqlite3.Cursor.connection
In-Reply-To: <1454262712.53.0.251399487214.issue26250@psf.upfronthosting.co.za>
Message-ID: <1454790755.47.0.346627252556.issue26250@psf.upfronthosting.co.za>


Aviv Palivoda added the comment:

Added patch with my suggestion for sqlite3.Cursor.connection attribute documentation

----------
assignee:  -> docs at python
components: +Documentation, Extension Modules -Library (Lib)
keywords: +patch
nosy: +docs at python, ghaering, palaviv
versions: +Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41838/sqlite3-cursor-connection-doc.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26250>
_______________________________________

From report at bugs.python.org  Sat Feb  6 19:03:44 2016
From: report at bugs.python.org (Lorenzo Ancora)
Date: Sun, 07 Feb 2016 00:03:44 +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: <1454803424.76.0.210909666577.issue26209@psf.upfronthosting.co.za>


Lorenzo Ancora added the comment:

(msg259748) ok, then I propose to correct https://docs.python.org/dev/library/smtpd.html?highlight=q#smtpd.SMTPServer from:

.. class:: SMTPServer(localaddr, remoteaddr, data_size_limit=33554432,\
                      map=None, enable_SMTPUTF8=False, decode_data=True)

   Create a new :class:`SMTPServer` object, which binds to local address
   *localaddr*.  It will treat *remoteaddr* as an upstream SMTP relayer.  It
   inherits from :class:`asyncore.dispatcher`, and so will insert itself into
   :mod:`asyncore`'s event loop on instantiation.


To:


.. class:: SMTPServer(localaddr, remoteaddr, data_size_limit=33554432,\
                      map=None, enable_SMTPUTF8=False, decode_data=True)

   Creates a new :class:`SMTPServer` object, which binds to local address
   *localaddr* and uses *remoteaddr* as an upstream SMTP relayer.
   Both parameters should be a tuple in the form ``("host", portnumber)``, where *host* is a valid IP/FQDN.
   The object will insert itself into :mod:`asyncore`'s event loop on instantiation (inherits from :class:`asyncore.dispatcher`) and can be started with a call to :class:`asyncore.loop`.

---

These clarifications should be also inserted in the source code as heredocs (without the Sphynx syntax).
I really think that those changes will make the use of smtpd easier.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26209>
_______________________________________

From report at bugs.python.org  Sat Feb  6 21:40:41 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 07 Feb 2016 02:40:41 +0000
Subject: [docs] [issue25179] PEP 498 f-strings need to be documented
In-Reply-To: <1442688918.61.0.173837832796.issue25179@psf.upfronthosting.co.za>
Message-ID: <20160207024038.11217.34998@psf.io>


Roundup Robot added the comment:

New changeset f25d8cbd074a by Martin Panter in branch '3.5':
Issue #25179: Preparatory cleanup of existing docs on string formatting
https://hg.python.org/cpython/rev/f25d8cbd074a

New changeset fe692ee6d19a by Martin Panter in branch '2.7':
Issue #25179: Preparatory cleanup of existing docs on string formatting
https://hg.python.org/cpython/rev/fe692ee6d19a

----------
nosy: +python-dev

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25179>
_______________________________________

From report at bugs.python.org  Sat Feb  6 22:06:43 2016
From: report at bugs.python.org (Martin Panter)
Date: Sun, 07 Feb 2016 03:06:43 +0000
Subject: [docs] [issue25179] PEP 498 f-strings need to be documented
In-Reply-To: <1442688918.61.0.173837832796.issue25179@psf.upfronthosting.co.za>
Message-ID: <1454814401.67.0.000471406931441.issue25179@psf.upfronthosting.co.za>


Martin Panter added the comment:

Regarding doc strings, it seems that a constant f-string without any interpolations does become a doc string. But I would treat this as an implementation detail, not something to advertise.

Attached is my attempt at a patch. Please have a look and let me know if there are things I missed, if I added too much detail, wrong terminology, or whatever. I haven?t really written documentation like this before.

The combinations and permutations of all the Fr". . ." prefixes are getting borderline out of hand in the lexical_analysis.rst grammar. Any suggestions?

I put the bulk of the documentation in a new section ?Formatted string literals? of the Lexical Analysis chapter, the same place that describes escape sequences and raw strings. Let me know if there is a more appropriate place for it. It doesn?t feel quite right where it is because this chapter comes before Expressions, and f-strings use expressions inside them.

I also made minimal changes to existing parts of the documentation and tutorial, to point to the new documentation. Perhaps some code examples could be changed from str.format() to f". . .", but I think that would be the subject of a separate patch. There are even places that still use the outdated "{0}".format() numbering.

----------
keywords: +patch
nosy: +martin.panter
stage: needs patch -> patch review
Added file: http://bugs.python.org/file41839/f-strings.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25179>
_______________________________________

From report at bugs.python.org  Sun Feb  7 00:59:29 2016
From: report at bugs.python.org (Ned Deily)
Date: Sun, 07 Feb 2016 05:59:29 +0000
Subject: [docs] [issue25226] "suffix" attribute not documented in
 logging.TimedRotatingFileHandler
In-Reply-To: <1443087278.13.0.950277021973.issue25226@psf.upfronthosting.co.za>
Message-ID: <1454824769.69.0.369805619728.issue25226@psf.upfronthosting.co.za>


Changes by Ned Deily <nad at python.org>:


----------
nosy: +vinay.sajip

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25226>
_______________________________________

From report at bugs.python.org  Sun Feb  7 03:57:41 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 07 Feb 2016 08:57:41 +0000
Subject: [docs] [issue26294] Queue().unfinished_tasks not in docs -
 deliberate?
In-Reply-To: <1454662858.22.0.0628824582163.issue26294@psf.upfronthosting.co.za>
Message-ID: <1454835461.15.0.442967375738.issue26294@psf.upfronthosting.co.za>


Changes by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
assignee: docs at python -> rhettinger
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26294>
_______________________________________

From report at bugs.python.org  Sun Feb  7 04:04:21 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 07 Feb 2016 09:04:21 +0000
Subject: [docs] [issue26294] Queue().unfinished_tasks not in docs -
 deliberate?
In-Reply-To: <1454662858.22.0.0628824582163.issue26294@psf.upfronthosting.co.za>
Message-ID: <1454835860.98.0.601758094813.issue26294@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Just as you thought, the 'unfinished_tasks' attribute not intended to be part of the public API for queues.

----------
resolution:  -> not a bug
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26294>
_______________________________________

From georg at python.org  Sun Feb  7 05:43:06 2016
From: georg at python.org (Georg Brandl)
Date: Sun, 7 Feb 2016 11:43:06 +0100
Subject: [docs] Issue with python function names
In-Reply-To: <CAJ3vjLy_VBAcWQVhmK+F+MSiOW_CpbLgWqyOp0HH0==cGQAVUw@mail.gmail.com>
References: <CAJ3vjLw+dZSXw3x4kEXraRM97=YoFLH7i6wzs6EDGsjCktm2og@mail.gmail.com>
 <CAJ3vjLy_VBAcWQVhmK+F+MSiOW_CpbLgWqyOp0HH0==cGQAVUw@mail.gmail.com>
Message-ID: <56B71FBA.9050904@python.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi David,

there are few reasons why this is the way it is:

- - The builtins are not the only names that can be accidentally overridden.
  The same goes for imported modules, or any classes/functions imported
  from modules.  It's hard to see where to draw the line.

- - At the same time, being able to override existing name bindings is part
  of the Pythonic "consenting adults" policy.  It makes it possible, for
  example, to quickly change how output using "print" works in a script.

- - The interactive shell is a special case anyway.  Normally the shadowing
  is limited to the module or local scope where it happens.

Note that as with many other questions of freedom vs enforcement, linters
like pyflakes/pylint do a good job of recoginizing this shadowing and
warning about it if so desired.

cheers,
Georg


On 02/06/2016 06:49 AM, david becker wrote:
> And of course the same thing happens if we use them for variable names as
> well.
> 
>>>> type = 2 type(4)
> Traceback (most recent call last): File "<pyshell#74>", line 1, in
> <module> type(4) TypeError: 'int' object is not callable
> 
> 
> I feel there is no point in allowing them as they cannot be used. Users
> are restricted to use the 32 keywords but we can't force them to remember
> all built in function names and not to use them as variable or function
> names. :)
> 
> Thanks, David Becker
> 
> On Sat, Feb 6, 2016 at 11:11 AM, david becker <ardavidbecker at gmail.com 
> <mailto:ardavidbecker at gmail.com>> wrote:
> 
> Hi,
> 
> I have a query in using function names. Python allows users to write their 
> own functions with built-in function names.
> 
> Example: def print(): return "strange"
> 
> print() -- Returns strange ++++++++++++++++++++++++++++
> 
> But the built in "print" function doesn't work any more till i restart the 
> shell. I personally feel users should not be allowed to use built in
> function names. Is there any special reason why python allows them?
> 
> Thanks, David Becker
> 
> 
> 
> 
> _______________________________________________ docs mailing list 
> docs at python.org https://mail.python.org/mailman/listinfo/docs
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAla3H7oACgkQN9GcIYhpnLABqACfaPpaYIBEkVBxFL71PXhHJlKO
WKMAn0WJ3BrTSe3ogv4uaevp6HkHarjj
=KV53
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sun Feb  7 06:33:30 2016
From: report at bugs.python.org (SilentGhost)
Date: Sun, 07 Feb 2016 11:33:30 +0000
Subject: [docs] [issue25226] "suffix" attribute not documented in
 logging.TimedRotatingFileHandler
In-Reply-To: <1443087278.13.0.950277021973.issue25226@psf.upfronthosting.co.za>
Message-ID: <1454844810.56.0.995387006374.issue25226@psf.upfronthosting.co.za>


SilentGhost added the comment:

It isn't documented because it's an internal attribute. If it did work for someone, it's by accident. Naturally, Vinay would have to make a final judgement regarding this, but I'd be inclined to close as not a bug.

----------
nosy: +SilentGhost

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25226>
_______________________________________

From eric at trueblade.com  Sun Feb  7 10:32:18 2016
From: eric at trueblade.com (eric at trueblade.com)
Date: Sun, 07 Feb 2016 15:32:18 -0000
Subject: [docs] PEP 498 f-strings need to be documented (issue 25179)
Message-ID: <20160207153218.4067.40787@psf.upfronthosting.co.za>

Reviewers: ,

Message:
Thanks for taking this on!

I have just a few nits, as noted.


http://bugs.python.org/review/25179/diff/16513/Doc/reference/lexical_analysis.rst
File Doc/reference/lexical_analysis.rst (right):

http://bugs.python.org/review/25179/diff/16513/Doc/reference/lexical_analysis.rst#newcode661
Doc/reference/lexical_analysis.rst:661: cannot be split between
literals.
between -> across

http://bugs.python.org/review/25179/diff/16513/Doc/whatsnew/3.6.rst
File Doc/whatsnew/3.6.rst (right):

http://bugs.python.org/review/25179/diff/16513/Doc/whatsnew/3.6.rst#newcode95
Doc/whatsnew/3.6.rst:95: >>> f"He said his name is {name!r}."
Many people will see this as their first example. As such, I'd delete
the !r and just have it be f"He said his name is {name}."

I think !r would tend to scare people off.



Please review this at http://bugs.python.org/review/25179/

Affected files:
  Doc/faq/programming.rst
  Doc/library/datetime.rst
  Doc/library/enum.rst
  Doc/library/stdtypes.rst
  Doc/library/string.rst
  Doc/reference/datamodel.rst
  Doc/reference/lexical_analysis.rst
  Doc/tutorial/inputoutput.rst
  Doc/tutorial/introduction.rst
  Doc/whatsnew/3.6.rst



From report at bugs.python.org  Sun Feb  7 13:49:50 2016
From: report at bugs.python.org (Vinay Sajip)
Date: Sun, 07 Feb 2016 18:49:50 +0000
Subject: [docs] [issue25226] "suffix" attribute not documented in
 logging.TimedRotatingFileHandler
In-Reply-To: <1443087278.13.0.950277021973.issue25226@psf.upfronthosting.co.za>
Message-ID: <1454870990.36.0.417415208168.issue25226@psf.upfronthosting.co.za>


Vinay Sajip added the comment:

It's not documented, and not intended to be changeable by the user, because it is not set to a fixed value - the value depends on the "when" (to rollover) and "interval" arguments to the handler initializer. If you really need to have functionality other than the default, the way to do this is by creating a subclass and changing its behaviour appropriately.

IMO the accepted SO answer you linked to doesn't give correct advice.

----------
resolution:  -> not a bug
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25226>
_______________________________________

From report at bugs.python.org  Sun Feb  7 14:13:37 2016
From: report at bugs.python.org (SilentGhost)
Date: Sun, 07 Feb 2016 19:13:37 +0000
Subject: [docs] [issue25226] "suffix" attribute not documented in
 logging.TimedRotatingFileHandler
In-Reply-To: <1443087278.13.0.950277021973.issue25226@psf.upfronthosting.co.za>
Message-ID: <1454872417.78.0.481688612862.issue25226@psf.upfronthosting.co.za>


Changes by SilentGhost <ghost.adh at gmail.com>:


----------
stage:  -> resolved

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25226>
_______________________________________

From report at bugs.python.org  Sun Feb  7 18:23:16 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 07 Feb 2016 23:23:16 +0000
Subject: [docs] [issue26198] PyArg_ParseTuple with format "et#" and "es#"
 detects overflow by raising TypeError instead of ValueError
In-Reply-To: <1453738388.34.0.790534194643.issue26198@psf.upfronthosting.co.za>
Message-ID: <20160207232313.2639.41186@psf.io>


Roundup Robot added the comment:

New changeset ab25ce400abd by Serhiy Storchaka in branch '2.7':
Issue #26198: Fixed error messages for some argument parsing errors.
https://hg.python.org/cpython/rev/ab25ce400abd

New changeset 9f998e24d8d8 by Serhiy Storchaka in branch '3.5':
Issue #26198: Fixed error messages for some argument parsing errors.
https://hg.python.org/cpython/rev/9f998e24d8d8

New changeset f8bdc0ea3bcf by Serhiy Storchaka in branch 'default':
Issue #26198: Fixed error messages for some argument parsing errors.
https://hg.python.org/cpython/rev/f8bdc0ea3bcf

New changeset 53d66a554beb by Serhiy Storchaka in branch 'default':
Issue #26198: ValueError is now raised instead of TypeError on buffer
https://hg.python.org/cpython/rev/53d66a554beb

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26198>
_______________________________________

From report at bugs.python.org  Sun Feb  7 23:36:40 2016
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 08 Feb 2016 04:36:40 +0000
Subject: [docs] [issue8810] TZ offset description is unclear in docs
In-Reply-To: <1274718021.16.0.883294684947.issue8810@psf.upfronthosting.co.za>
Message-ID: <1454906200.09.0.0262296206037.issue8810@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

I agree it makes sense to merge this and #9305, and since the latter has seen more recent activity, I'll do the merge in that direction.

----------
resolution:  -> duplicate
stage: patch review -> 
status: open -> closed
superseder:  -> Don't use east/west of UTC in date/time documentation

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8810>
_______________________________________

From report at bugs.python.org  Mon Feb  8 00:55:56 2016
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 08 Feb 2016 05:55:56 +0000
Subject: [docs] [issue26198] PyArg_ParseTuple with format "et#" and "es#"
 detects overflow by raising TypeError instead of ValueError
In-Reply-To: <1453738388.34.0.790534194643.issue26198@psf.upfronthosting.co.za>
Message-ID: <1454910956.33.0.108788674114.issue26198@psf.upfronthosting.co.za>


Berker Peksag added the comment:

test_datetime is broken on 3.5 and default:

======================================================================
FAIL: test_format (test.datetimetester.TestSubclassDateTime)
----------------------------------------------------------------------
TypeError: __format__() argument 1 must be str, not int

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/var/lib/buildbot/slaves/profile-opt-bot/3.5.gps-debian-profile-opt/build/Lib/test/datetimetester.py", line 1578, in test_format
    dt.__format__(123)
AssertionError: "^must be str, not int$" does not match "__format__() argument 1 must be str, not int"

http://buildbot.python.org/all/builders/AMD64%20Debian%20PGO%203.5/builds/632/steps/test/logs/stdio

http://buildbot.python.org/all/builders/x86%20Tiger%203.x/builds/10486/steps/test/logs/stdio

----------
nosy: +berker.peksag

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26198>
_______________________________________

From report at bugs.python.org  Mon Feb  8 02:27:50 2016
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 08 Feb 2016 07:27:50 +0000
Subject: [docs] [issue26198] PyArg_ParseTuple with format "et#" and "es#"
 detects overflow by raising TypeError instead of ValueError
In-Reply-To: <1453738388.34.0.790534194643.issue26198@psf.upfronthosting.co.za>
Message-ID: <20160208072746.1566.29238@psf.io>


Roundup Robot added the comment:

New changeset 22b0a63808f8 by Serhiy Storchaka in branch '3.5':
Issue #26198: Make datetime error tests more lenient.
https://hg.python.org/cpython/rev/22b0a63808f8

New changeset a9c9e4054f3f by Serhiy Storchaka in branch 'default':
Issue #26198: Make datetime error tests more lenient.
https://hg.python.org/cpython/rev/a9c9e4054f3f

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26198>
_______________________________________

From report at bugs.python.org  Mon Feb  8 02:30:47 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 08 Feb 2016 07:30:47 +0000
Subject: [docs] [issue26198] PyArg_ParseTuple with format "et#" and "es#"
 detects overflow by raising TypeError instead of ValueError
In-Reply-To: <1453738388.34.0.790534194643.issue26198@psf.upfronthosting.co.za>
Message-ID: <1454916647.68.0.430149077867.issue26198@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thanks Berker.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26198>
_______________________________________

From report at bugs.python.org  Mon Feb  8 02:55:33 2016
From: report at bugs.python.org (Martin Panter)
Date: Mon, 08 Feb 2016 07:55:33 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzMDRdIEZpeCDigJxhbGxvd3MgdG8gPHZlcmI+?=
 =?utf-8?q?=E2=80=9D_in_documentation?=
Message-ID: <1454918132.41.0.149238322531.issue26304@psf.upfronthosting.co.za>


New submission from Martin Panter:

This patch changes instances of ?. . . allows to <verb>? to ?. . . allows <verb>ing? or similar. I understand the original form is not correct English grammar, although the equivalent is apparently valid in some other languages. As a native English speaker it feels awkward to me, although the meaning is clear. This question & answer <https://english.stackexchange.com/questions/60271/grammatical-complements-for-allow> seem to back me up, but I thought I should get a quick review or second opinion before changing everything.

----------
assignee: docs at python
components: Documentation
files: allows-to.patch
keywords: patch
messages: 259827
nosy: docs at python, martin.panter
priority: normal
severity: normal
stage: patch review
status: open
title: Fix ?allows to <verb>? in documentation
versions: Python 2.7, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41845/allows-to.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26304>
_______________________________________

From report at bugs.python.org  Mon Feb  8 03:25:01 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 08 Feb 2016 08:25:01 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzMDRdIEZpeCDigJxhbGxvd3MgdG8gPHZlcmI+?=
 =?utf-8?q?=E2=80=9D_in_documentation?=
In-Reply-To: <1454918132.41.0.149238322531.issue26304@psf.upfronthosting.co.za>
Message-ID: <1454919901.68.0.360407350523.issue26304@psf.upfronthosting.co.za>


Changes by Serhiy Storchaka <storchaka at gmail.com>:


----------
nosy: +r.david.murray

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26304>
_______________________________________

From report at bugs.python.org  Mon Feb  8 03:59:48 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 08 Feb 2016 08:59:48 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzMDRdIEZpeCDigJxhbGxvd3MgdG8gPHZlcmI+?=
 =?utf-8?q?=E2=80=9D_in_documentation?=
In-Reply-To: <1454918132.41.0.149238322531.issue26304@psf.upfronthosting.co.za>
Message-ID: <1454921987.99.0.81649436217.issue26304@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

I have read the patch, and it LGTM. At least it does exactly what is declared (and fixes some other minor errors). Thank you Martin.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26304>
_______________________________________

From report at bugs.python.org  Mon Feb  8 04:37:54 2016
From: report at bugs.python.org (Michael Foord)
Date: Mon, 08 Feb 2016 09:37:54 +0000
Subject: [docs] [issue20109] TestProgram is mentioned in the unittest docs
 but is not documented
In-Reply-To: <1388685707.72.0.688331916968.issue20109@psf.upfronthosting.co.za>
Message-ID: <1454924274.19.0.869072870326.issue20109@psf.upfronthosting.co.za>


Michael Foord added the comment:

TestProgram is an abomination, but it has been publicly exposed in unittest since forever.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20109>
_______________________________________

From report at bugs.python.org  Mon Feb  8 11:15:15 2016
From: report at bugs.python.org (Eric V. Smith)
Date: Mon, 08 Feb 2016 16:15:15 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzMDRdIEZpeCDigJxhbGxvd3MgdG8gPHZlcmI+?=
 =?utf-8?q?=E2=80=9D_in_documentation?=
In-Reply-To: <1454918132.41.0.149238322531.issue26304@psf.upfronthosting.co.za>
Message-ID: <1454948115.7.0.270886720588.issue26304@psf.upfronthosting.co.za>


Eric V. Smith added the comment:

I agree that the "to xxx" changes look good. And the handful of other corrections look good, too.

I left a review comment with one typo I found.

----------
nosy: +eric.smith

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26304>
_______________________________________

From eric at trueblade.com  Mon Feb  8 11:14:29 2016
From: eric at trueblade.com (eric at trueblade.com)
Date: Mon, 08 Feb 2016 16:14:29 -0000
Subject: [docs] =?utf-8?b?Rml4IOKAnGFsbG93cyB0byA8dmVyYj7igJ0gaW4gZG9jdW1l?=
 =?utf-8?q?ntation_=28issue_26304=29?=
Message-ID: <20160208161429.4067.85653@psf.upfronthosting.co.za>

Looks good, other than the one typo I found.


http://bugs.python.org/review/26304/diff/16519/Misc/HISTORY
File Misc/HISTORY (right):

http://bugs.python.org/review/26304/diff/16519/Misc/HISTORY#newcode2237
Misc/HISTORY:2237: attribute which allows seting custom per-pickler
reduction functions.
Should be "setting".

http://bugs.python.org/review/26304/

From report at bugs.python.org  Mon Feb  8 13:06:44 2016
From: report at bugs.python.org (Marien)
Date: Mon, 08 Feb 2016 18:06:44 +0000
Subject: [docs] =?utf-8?q?=5Bissue26310=5D_Fix_typo_=E2=80=9Cvariariables?=
 =?utf-8?q?=E2=80=9D_in_socketserver=2Epy?=
Message-ID: <1454954804.39.0.970337231827.issue26310@psf.upfronthosting.co.za>


New submission from Marien:

This patch fixes a typo in socketserver.py

----------
assignee: docs at python
components: Documentation
files: fix-typo-variariables.patch
keywords: patch
messages: 259869
nosy: docs at python, marienfr
priority: normal
severity: normal
status: open
title: Fix typo ?variariables? in socketserver.py
Added file: http://bugs.python.org/file41858/fix-typo-variariables.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26310>
_______________________________________

From report at bugs.python.org  Mon Feb  8 13:53:30 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 08 Feb 2016 18:53:30 +0000
Subject: [docs] [issue26198] PyArg_ParseTuple with format "et#" and "es#"
 detects overflow by raising TypeError instead of ValueError
In-Reply-To: <1453738388.34.0.790534194643.issue26198@psf.upfronthosting.co.za>
Message-ID: <1454957610.93.0.29350634016.issue26198@psf.upfronthosting.co.za>


Changes by Serhiy Storchaka <storchaka at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26198>
_______________________________________

From francismb at email.de  Mon Feb  8 15:03:47 2016
From: francismb at email.de (francismb at email.de)
Date: Mon, 08 Feb 2016 20:03:47 -0000
Subject: [docs] =?utf-8?q?Fix_typo_=E2=80=9Cvariariables=E2=80=9D_in_socke?=
 =?utf-8?q?tserver=2Epy_=28issue_26310=29?=
Message-ID: <20160208200347.23644.79073@psf.upfronthosting.co.za>


https://bugs.python.org/review/26310/diff/16529/Lib/socketserver.py
File Lib/socketserver.py (right):

https://bugs.python.org/review/26310/diff/16529/Lib/socketserver.py#newcode674
Lib/socketserver.py:674: can define arbitrary other instance variables.
LGTM

https://bugs.python.org/review/26310/

From report at bugs.python.org  Mon Feb  8 20:38:43 2016
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 09 Feb 2016 01:38:43 +0000
Subject: [docs] =?utf-8?q?=5Bissue26310=5D_Fix_typo_=E2=80=9Cvariariables?=
 =?utf-8?q?=E2=80=9D_in_socketserver=2Epy?=
In-Reply-To: <1454954804.39.0.970337231827.issue26310@psf.upfronthosting.co.za>
Message-ID: <20160209013838.1543.80149@psf.io>


Roundup Robot added the comment:

New changeset 1383a260b66d by Martin Panter in branch '3.5':
Issues #26310, #26311: Fix typos in the documentation and code comments
https://hg.python.org/cpython/rev/1383a260b66d

New changeset e2d3c93d8763 by Martin Panter in branch 'default':
Issues #26310, 26311: Merge typo fixes from 3.5
https://hg.python.org/cpython/rev/e2d3c93d8763

New changeset 8c7a8c7a02b9 by Martin Panter in branch '2.7':
Issues #26310, #26311: Fix typos in the documentation
https://hg.python.org/cpython/rev/8c7a8c7a02b9

----------
nosy: +python-dev

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26310>
_______________________________________

From report at bugs.python.org  Mon Feb  8 20:58:39 2016
From: report at bugs.python.org (Martin Panter)
Date: Tue, 09 Feb 2016 01:58:39 +0000
Subject: [docs] =?utf-8?q?=5Bissue26310=5D_Fix_typo_=E2=80=9Cvariariables?=
 =?utf-8?q?=E2=80=9D_in_socketserver=2Epy?=
In-Reply-To: <1454954804.39.0.970337231827.issue26310@psf.upfronthosting.co.za>
Message-ID: <1454983119.13.0.710962003239.issue26310@psf.upfronthosting.co.za>


Martin Panter added the comment:

Thankyou for the report. I also took the opportunity to switch the words ?arbitrary other . . .? around to ?other arbitrary . . .?.

----------
nosy: +martin.panter

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26310>
_______________________________________

From report at bugs.python.org  Mon Feb  8 20:58:51 2016
From: report at bugs.python.org (Martin Panter)
Date: Tue, 09 Feb 2016 01:58:51 +0000
Subject: [docs] =?utf-8?q?=5Bissue26310=5D_Fix_typo_=E2=80=9Cvariariables?=
 =?utf-8?q?=E2=80=9D_in_socketserver=2Epy?=
In-Reply-To: <1454954804.39.0.970337231827.issue26310@psf.upfronthosting.co.za>
Message-ID: <1454983131.94.0.270150810556.issue26310@psf.upfronthosting.co.za>


Changes by Martin Panter <vadmium+py at gmail.com>:


----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
versions: +Python 2.7, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26310>
_______________________________________

From report at bugs.python.org  Mon Feb  8 21:17:19 2016
From: report at bugs.python.org (Martin Panter)
Date: Tue, 09 Feb 2016 02:17:19 +0000
Subject: [docs] [issue25179] PEP 498 f-strings need to be documented
In-Reply-To: <1442688918.61.0.173837832796.issue25179@psf.upfronthosting.co.za>
Message-ID: <1454984238.52.0.692566844915.issue25179@psf.upfronthosting.co.za>


Martin Panter added the comment:

Updated with Eric?s suggestions

----------
Added file: http://bugs.python.org/file41864/f-strings.v2.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25179>
_______________________________________

From vadmium+py at gmail.com  Mon Feb  8 20:57:22 2016
From: vadmium+py at gmail.com (vadmium+py at gmail.com)
Date: Tue, 09 Feb 2016 01:57:22 -0000
Subject: [docs] PEP 498 f-strings need to be documented (issue 25179)
Message-ID: <20160209015722.4067.28562@psf.upfronthosting.co.za>


https://bugs.python.org/review/25179/diff/16513/Doc/reference/lexical_analysis.rst
File Doc/reference/lexical_analysis.rst (right):

https://bugs.python.org/review/25179/diff/16513/Doc/reference/lexical_analysis.rst#newcode661
Doc/reference/lexical_analysis.rst:661: cannot be split between
literals.
On 2016/02/07 16:32:18, eric.smith wrote:
> between -> across

Done.

https://bugs.python.org/review/25179/diff/16513/Doc/whatsnew/3.6.rst
File Doc/whatsnew/3.6.rst (right):

https://bugs.python.org/review/25179/diff/16513/Doc/whatsnew/3.6.rst#newcode95
Doc/whatsnew/3.6.rst:95: >>> f"He said his name is {name!r}."
On 2016/02/07 16:32:18, eric.smith wrote:
> Many people will see this as their first example. As such, I'd delete
the !r and
> just have it be f"He said his name is {name}."
> 
> I think !r would tend to scare people off.

Done.

https://bugs.python.org/review/25179/

From report at bugs.python.org  Tue Feb  9 08:16:36 2016
From: report at bugs.python.org (Rory McCann)
Date: Tue, 09 Feb 2016 13:16:36 +0000
Subject: [docs] [issue26320] Web documentation for 2.7 has unreadable
 highlights in Table of Contents
Message-ID: <1455023796.48.0.712407093962.issue26320@psf.upfronthosting.co.za>


New submission from Rory McCann:

Using Firefox 41.0.2 on Ubuntu 14.04, most table of contents in the online docs have unreadable highlighted sections, where modules/methods are named.

See https://docs.python.org/2/library/datetime.html for a good example, or the attached screenshot.

I think this highlighting has appeared recently.
The 3.x versions are fine, as is 2.6.

----------
assignee: docs at python
components: Documentation
files: Screenshot from 2016-02-09 13:15:43.png
messages: 259930
nosy: Rory McCann, docs at python
priority: normal
severity: normal
status: open
title: Web documentation for 2.7 has unreadable highlights in Table of Contents
type: enhancement
versions: Python 2.7
Added file: http://bugs.python.org/file41867/Screenshot from 2016-02-09 13:15:43.png

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26320>
_______________________________________

From report at bugs.python.org  Tue Feb  9 08:30:20 2016
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 09 Feb 2016 13:30:20 +0000
Subject: [docs] [issue26320] Web documentation for 2.7 has unreadable
 highlights in Table of Contents
In-Reply-To: <1455023796.48.0.712407093962.issue26320@psf.upfronthosting.co.za>
Message-ID: <1455024620.51.0.767702660323.issue26320@psf.upfronthosting.co.za>


Georg Brandl added the comment:

In addition, the object description headers (function names...) are not styled as they should be.

Has the doc style been changed recently?

----------
nosy: +benjamin.peterson, ezio.melotti, georg.brandl

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26320>
_______________________________________

From report at bugs.python.org  Tue Feb  9 15:48:20 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Tue, 09 Feb 2016 20:48:20 +0000
Subject: [docs] [issue26322] Missing docs for typing.Set
Message-ID: <1455050900.92.0.506743123977.issue26322@psf.upfronthosting.co.za>


New submission from Guido van Rossum:

The typing docs don't seem to mention Set (which is a bit of an anomaly, since it corresponds to builtins.set, not to collections.abc.Set -- the latter is typing.AbstractSet). Also, AbstractSet is mentioned twice. (And the second occurrence somehow doesn't have a "paragraph" link.)

All this should be easy to fix.

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 259954
nosy: docs at python, gvanrossum
priority: normal
severity: normal
status: open
title: Missing docs for typing.Set
versions: Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26322>
_______________________________________

From report at bugs.python.org  Tue Feb  9 16:12:15 2016
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 09 Feb 2016 21:12:15 +0000
Subject: [docs] [issue26322] Missing docs for typing.Set
In-Reply-To: <1455050900.92.0.506743123977.issue26322@psf.upfronthosting.co.za>
Message-ID: <1455052335.8.0.770214051167.issue26322@psf.upfronthosting.co.za>


Changes by Ezio Melotti <ezio.melotti at gmail.com>:


----------
nosy: +ezio.melotti
stage:  -> needs patch
type:  -> enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26322>
_______________________________________

From report at bugs.python.org  Tue Feb  9 18:04:35 2016
From: report at bugs.python.org (Martin Panter)
Date: Tue, 09 Feb 2016 23:04:35 +0000
Subject: [docs] [issue21996] gettarinfo method does not handle files without
 text string names
In-Reply-To: <1405583528.37.0.553699872308.issue21996@psf.upfronthosting.co.za>
Message-ID: <1455059075.92.0.6770251028.issue21996@psf.upfronthosting.co.za>


Changes by Martin Panter <vadmium+py at gmail.com>:


----------
dependencies: +Tarfile using fstat on GZip file object

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21996>
_______________________________________

From report at bugs.python.org  Tue Feb  9 18:07:22 2016
From: report at bugs.python.org (Martin Panter)
Date: Tue, 09 Feb 2016 23:07:22 +0000
Subject: [docs] [issue23453] Opening a stream with tarfile.open() triggers a
 TypeError: can't concat bytes to str error
In-Reply-To: <1423739998.49.0.706967373594.issue23453@psf.upfronthosting.co.za>
Message-ID: <1455059242.64.0.0312984406616.issue23453@psf.upfronthosting.co.za>


Changes by Martin Panter <vadmium+py at gmail.com>:


----------
stage:  -> needs patch
type: crash -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23453>
_______________________________________

From report at bugs.python.org  Tue Feb  9 21:53:51 2016
From: report at bugs.python.org (Martin Panter)
Date: Wed, 10 Feb 2016 02:53:51 +0000
Subject: [docs] [issue5824] SocketServer.DatagramRequestHandler Broken under
 Linux
In-Reply-To: <1240525238.53.0.858571250541.issue5824@psf.upfronthosting.co.za>
Message-ID: <1455072831.02.0.964279741191.issue5824@psf.upfronthosting.co.za>


Martin Panter added the comment:

It is not that wfile.getvalue() returns None, it is that self.client_address is None. If the client explicitly binds to a name, then the server gets that name in the client_address, and then everything seems to work properly for me on Linux.

On Linux, using strace and an unbound anonymous client, I see that recvfrom() outputs a zero-length sending address structure, which Python?s makesockaddr() function converts to None with the comment /* No address -- may be recvfrom() from known socket */. The man page <http://man7.org/linux/man-pages/man7/unix.7.html> actually says the address length should be sizeof(sa_family_t) in this case, so maybe that is a minor bug for Linux or the man page.

How does this work on non-Linux platforms? I?m not really familiar with Unix domain sockets, especially datagram ones, but it seems to me that the main confusion is whether DatagramRequestHandler supports anonymous Unix domain clients or not.

As in Issue 1767511, I think DatagramRequestHandler is designed to always send a response back to the sender of the request. If you don?t want to send a response, why are you using this class?

----------
nosy: +martin.panter

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5824>
_______________________________________

From report at bugs.python.org  Wed Feb 10 00:09:32 2016
From: report at bugs.python.org (Benjamin Peterson)
Date: Wed, 10 Feb 2016 05:09:32 +0000
Subject: [docs] [issue26320] Web documentation for 2.7 has unreadable
 highlights in Table of Contents
In-Reply-To: <1455024620.51.0.767702660323.issue26320@psf.upfronthosting.co.za>
Message-ID: <1455080968.4094924.516963610.631D87EB@webmail.messagingengine.com>


Benjamin Peterson added the comment:

I upgraded Sphinx a month or so ago. Could that do it?

On Tue, Feb 9, 2016, at 05:30, Georg Brandl wrote:
> 
> Georg Brandl added the comment:
> 
> In addition, the object description headers (function names...) are not
> styled as they should be.
> 
> Has the doc style been changed recently?
> 
> ----------
> nosy: +benjamin.peterson, ezio.melotti, georg.brandl
> 
> _______________________________________
> Python tracker <report at bugs.python.org>
> <http://bugs.python.org/issue26320>
> _______________________________________

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26320>
_______________________________________

From report at bugs.python.org  Wed Feb 10 00:47:07 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 10 Feb 2016 05:47:07 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzMDRdIEZpeCDigJxhbGxvd3MgdG8gPHZlcmI+?=
 =?utf-8?q?=E2=80=9D_in_documentation?=
In-Reply-To: <1454918132.41.0.149238322531.issue26304@psf.upfronthosting.co.za>
Message-ID: <20160210054700.40084.89736@psf.io>


Roundup Robot added the comment:

New changeset 818e91105418 by Martin Panter in branch '3.5':
Issue #26304: Change "allows to <verb>" to "allows <verb>ing" or similar
https://hg.python.org/cpython/rev/818e91105418

New changeset d01abc2d5197 by Martin Panter in branch 'default':
Issue #26304: Merge doc wording from 3.5
https://hg.python.org/cpython/rev/d01abc2d5197

New changeset 37f6f965023d by Martin Panter in branch 'default':
Issue #26304: Additional ?allows to? fix specific to 3.6
https://hg.python.org/cpython/rev/37f6f965023d

----------
nosy: +python-dev

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26304>
_______________________________________

From report at bugs.python.org  Wed Feb 10 01:31:30 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 10 Feb 2016 06:31:30 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzMDRdIEZpeCDigJxhbGxvd3MgdG8gPHZlcmI+?=
 =?utf-8?q?=E2=80=9D_in_documentation?=
In-Reply-To: <1454918132.41.0.149238322531.issue26304@psf.upfronthosting.co.za>
Message-ID: <20160210063122.61960.78424@psf.io>


Roundup Robot added the comment:

New changeset 4cfc19f667aa by Martin Panter in branch '2.7':
Issue #26304: Change "allows to <verb>" to "allows <verb>ing" or similar
https://hg.python.org/cpython/rev/4cfc19f667aa

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26304>
_______________________________________

From report at bugs.python.org  Wed Feb 10 01:37:30 2016
From: report at bugs.python.org (Martin Panter)
Date: Wed, 10 Feb 2016 06:37:30 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzMDRdIEZpeCDigJxhbGxvd3MgdG8gPHZlcmI+?=
 =?utf-8?q?=E2=80=9D_in_documentation?=
In-Reply-To: <1454918132.41.0.149238322531.issue26304@psf.upfronthosting.co.za>
Message-ID: <1455086250.42.0.718086359733.issue26304@psf.upfronthosting.co.za>


Martin Panter added the comment:

Thanks for the reviews, and spotting my typo. I also sneaked in eight more changes (?allowing to?), to asyncio-eventloop.rst, ctypes.rst, whatsnew/3.3.rst, howto/pyporting.rst, Misc/NEWS, and Misc/HISTORY.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26304>
_______________________________________

From report at bugs.python.org  Wed Feb 10 01:56:03 2016
From: report at bugs.python.org (Martin Panter)
Date: Wed, 10 Feb 2016 06:56:03 +0000
Subject: [docs] [issue25496] tarfile: Default value for compresslevel is not
 documented
In-Reply-To: <1446021567.06.0.820338275323.issue25496@psf.upfronthosting.co.za>
Message-ID: <1455087363.89.0.0794284278902.issue25496@psf.upfronthosting.co.za>


Martin Panter added the comment:

For gzip compression, there is also a proposal to change the default: Issue 26253.

Anyway, the patch looks good for now.

----------
nosy: +martin.panter
stage: needs patch -> patch review
versions: +Python 2.7 -Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25496>
_______________________________________

From report at bugs.python.org  Wed Feb 10 04:06:52 2016
From: report at bugs.python.org (Georg Brandl)
Date: Wed, 10 Feb 2016 09:06:52 +0000
Subject: [docs] [issue26320] Web documentation for 2.7 has unreadable
 highlights in Table of Contents
In-Reply-To: <1455023796.48.0.712407093962.issue26320@psf.upfronthosting.co.za>
Message-ID: <1455095212.95.0.988742244946.issue26320@psf.upfronthosting.co.za>


Georg Brandl added the comment:

That's possible. I'll have a look.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26320>
_______________________________________

From report at bugs.python.org  Wed Feb 10 07:45:07 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 10 Feb 2016 12:45:07 +0000
Subject: [docs] [issue26320] Web documentation for 2.7 has unreadable
 highlights in Table of Contents
In-Reply-To: <1455023796.48.0.712407093962.issue26320@psf.upfronthosting.co.za>
Message-ID: <20160210124502.6675.86535@psf.io>


Roundup Robot added the comment:

New changeset 5715a6d9ff12 by Georg Brandl in branch '2.7':
Closes #26320: fix stylesheet after Sphinx update.
https://hg.python.org/cpython/rev/5715a6d9ff12

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26320>
_______________________________________

From report at bugs.python.org  Wed Feb 10 07:45:38 2016
From: report at bugs.python.org (Georg Brandl)
Date: Wed, 10 Feb 2016 12:45:38 +0000
Subject: [docs] [issue26320] Web documentation for 2.7 has unreadable
 highlights in Table of Contents
In-Reply-To: <1455023796.48.0.712407093962.issue26320@psf.upfronthosting.co.za>
Message-ID: <1455108338.93.0.791702244051.issue26320@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Should be fixed now (a rebuild of the online docs will be done within a few hours). Thanks for the report!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26320>
_______________________________________

From report at bugs.python.org  Wed Feb 10 10:16:03 2016
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 10 Feb 2016 15:16:03 +0000
Subject: [docs] [issue26330] shutil.disk_usage() on Windows can't properly
 handle unicode
In-Reply-To: <1455117077.45.0.531847730839.issue26330@psf.upfronthosting.co.za>
Message-ID: <1455117363.55.0.298067642301.issue26330@psf.upfronthosting.co.za>


Changes by STINNER Victor <victor.stinner at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation, Windows
nosy: +docs at python, paul.moore, steve.dower, tim.golden, zach.ware

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26330>
_______________________________________

From report at bugs.python.org  Wed Feb 10 10:35:42 2016
From: report at bugs.python.org (Giampaolo Rodola')
Date: Wed, 10 Feb 2016 15:35:42 +0000
Subject: [docs] [issue26330] shutil.disk_usage() on Windows can't properly
 handle unicode
In-Reply-To: <1455117077.45.0.531847730839.issue26330@psf.upfronthosting.co.za>
Message-ID: <1455118542.05.0.804595216056.issue26330@psf.upfronthosting.co.za>


Giampaolo Rodola' added the comment:

You are right, my bad. I'll fix doc mentioning that on Windows "path" can only be a directory (on UNIX it can also be a file).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26330>
_______________________________________

From report at bugs.python.org  Wed Feb 10 10:36:47 2016
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 10 Feb 2016 15:36:47 +0000
Subject: [docs] [issue26330] shutil.disk_usage() on Windows can't properly
 handle unicode
In-Reply-To: <1455117077.45.0.531847730839.issue26330@psf.upfronthosting.co.za>
Message-ID: <1455118607.23.0.689989668057.issue26330@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> You are right, my bad.

No problem. I read the doc before replying, and it is not said that the path must exist or must be a directory:
https://docs.python.org/dev/library/shutil.html#shutil.disk_usage

> I'll fix doc mentioning that on Windows "path" can only be a directory (on UNIX it can also be a file).

Great!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26330>
_______________________________________

From report at bugs.python.org  Wed Feb 10 10:41:49 2016
From: report at bugs.python.org (Giampaolo Rodola')
Date: Wed, 10 Feb 2016 15:41:49 +0000
Subject: [docs] [issue26330] shutil.disk_usage() on Windows can't properly
 handle unicode
In-Reply-To: <1455117077.45.0.531847730839.issue26330@psf.upfronthosting.co.za>
Message-ID: <1455118908.82.0.872288424412.issue26330@psf.upfronthosting.co.za>


Giampaolo Rodola' added the comment:

Different but kind of related, disk_usage() is not able to accept bytes:

>>> shutil.disk_usage(b'.')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\python34\lib\shutil.py", line 989, in disk
    total, free = nt._getdiskusage(path)
TypeError: must be str, not bytes
>>>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26330>
_______________________________________

From report at bugs.python.org  Wed Feb 10 10:44:32 2016
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 10 Feb 2016 15:44:32 +0000
Subject: [docs] [issue26330] shutil.disk_usage() on Windows can't properly
 handle unicode
In-Reply-To: <1455118908.82.0.872288424412.issue26330@psf.upfronthosting.co.za>
Message-ID: <CAMpsgwaZOxEUMY0kBAtpTsgyW=cZroBjJN4PveneB=UKhRg8vw@mail.gmail.com>


STINNER Victor added the comment:

> Different but kind of related, disk_usage() is not able to accept bytes:

On Python 3, I don't think that it's a big issue: bytes filenames are
deprecated.

See the current thread on python-dev:
https://mail.python.org/pipermail/python-dev/2016-February/143150.html

It's really much better to use Unicode on Windows, and I also suggest
you to use Unicode on UNIX/BSD.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26330>
_______________________________________

From report at bugs.python.org  Wed Feb 10 14:52:44 2016
From: report at bugs.python.org (Nicholas Chammas)
Date: Wed, 10 Feb 2016 19:52:44 +0000
Subject: [docs] [issue26334] bytes.translate() doesn't take keyword
 arguments; docs suggests it does
Message-ID: <1455133964.48.0.745384045329.issue26334@psf.upfronthosting.co.za>


New submission from Nicholas Chammas:

The docs for `bytes.translate()` [0] show the following signature:

```
bytes.translate(table[, delete])
```

However, calling this method with keyword arguments yields:

```
>>> b''.translate(table='la table', delete=b'delete')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: translate() takes no keyword arguments
```

I'm guessing other methods have this same issue. (e.g. `str.translate()`)

Do the docs need to be updated, or should these methods be updated to accept keyword arguments, or something else?

[0] https://docs.python.org/3/library/stdtypes.html#bytes.translate

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 260034
nosy: Nicholas Chammas, docs at python
priority: normal
severity: normal
status: open
title: bytes.translate() doesn't take keyword arguments; docs suggests it does
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26334>
_______________________________________

From report at bugs.python.org  Wed Feb 10 15:21:17 2016
From: report at bugs.python.org (SilentGhost)
Date: Wed, 10 Feb 2016 20:21:17 +0000
Subject: [docs] [issue26334] bytes.translate() doesn't take keyword
 arguments; docs suggests it does
In-Reply-To: <1455133964.48.0.745384045329.issue26334@psf.upfronthosting.co.za>
Message-ID: <1455135677.39.0.427720448349.issue26334@psf.upfronthosting.co.za>


SilentGhost added the comment:

I don't think docs suggest that in any way. The keyword arguments are typically described like this: https://docs.python.org/3/library/stdtypes.html#str.split

bytes.translate has a typical signature of a function with optional positional arguments.

----------
nosy: +SilentGhost

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26334>
_______________________________________

From report at bugs.python.org  Wed Feb 10 16:31:38 2016
From: report at bugs.python.org (Nicholas Chammas)
Date: Wed, 10 Feb 2016 21:31:38 +0000
Subject: [docs] [issue26334] bytes.translate() doesn't take keyword
 arguments; docs suggests it does
In-Reply-To: <1455133964.48.0.745384045329.issue26334@psf.upfronthosting.co.za>
Message-ID: <1455139898.86.0.532771835419.issue26334@psf.upfronthosting.co.za>


Nicholas Chammas added the comment:

So you're saying if `bytes.translate()` accepted keyword arguments, its signature would look something like this?

```
bytes.translate(table, delete=None)
```

I guess I was under the mistaken assumption that argument names in the docs always matched keyword arguments in the signature.

But you're right, a strictly positional argument (I guess specified via something like `args*`?) doesn't have a name.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26334>
_______________________________________

From c01udayakumar at gmail.com  Thu Feb 11 06:16:21 2016
From: c01udayakumar at gmail.com (Udayakumar Chakrapani)
Date: Thu, 11 Feb 2016 16:46:21 +0530
Subject: [docs] python.exe not working
Message-ID: <CAPCX0-XFBp6KTeKNPyqJjRznCETC7dU1jkXmde_4c4r20+JeLg@mail.gmail.com>

I have installed Python 2.7 on my windows 7, 32 bit. But whenever I tried
to open the search engine it says that, " python.exe has stopped
working'.Kindly give me required feedback to address the issue

*Problem details are given below*

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    python.exe
  Application Version:    0.0.0.0
  Application Timestamp:    4a4511fa
  Fault Module Name:    python31.dll
  Fault Module Version:    3.1.150.1013
  Fault Module Timestamp:    4a4511e0
  Exception Code:    40000015
  Exception Offset:    0008ae32
  OS Version:    6.1.7601.2.1.0.256.1
  Locale ID:    1033
  Additional Information 1:    797a
  Additional Information 2:    797a05e23c16fa32242738fd5f81bc0e
  Additional Information 3:    e185
  Additional Information 4:    e1857253e6ff59a55bde3fa6ff43a305


                                                       Eagerly waiting for
your reply
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160211/58fd5193/attachment.html>

From report at bugs.python.org  Thu Feb 11 09:33:13 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 11 Feb 2016 14:33:13 +0000
Subject: [docs] [issue15068] fileinput requires two EOF when reading stdin
In-Reply-To: <1339687174.96.0.0386214807139.issue15068@psf.upfronthosting.co.za>
Message-ID: <1455201193.51.0.762969977724.issue15068@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Ping.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15068>
_______________________________________

From report at bugs.python.org  Thu Feb 11 12:25:39 2016
From: report at bugs.python.org (Georg Brandl)
Date: Thu, 11 Feb 2016 17:25:39 +0000
Subject: [docs] [issue15693] expose glossary link on hover
In-Reply-To: <1345132108.78.0.567099034623.issue15693@psf.upfronthosting.co.za>
Message-ID: <1455211539.35.0.451448880378.issue15693@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


----------
assignee: georg.brandl -> 

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15693>
_______________________________________

From report at bugs.python.org  Thu Feb 11 14:15:07 2016
From: report at bugs.python.org (Mike Taylor)
Date: Thu, 11 Feb 2016 19:15:07 +0000
Subject: [docs] [issue24712] Docs page's sidebar vibrates on mouse wheel
 scroll on Chrome.
In-Reply-To: <1437780127.19.0.0270083299372.issue24712@psf.upfronthosting.co.za>
Message-ID: <1455218107.71.0.46277786004.issue24712@psf.upfronthosting.co.za>


Mike Taylor added the comment:

Great, thanks Ezio! Will take a stab now.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue24712>
_______________________________________

From report at bugs.python.org  Thu Feb 11 21:12:33 2016
From: report at bugs.python.org (Anthony Tuininga)
Date: Fri, 12 Feb 2016 02:12:33 +0000
Subject: [docs] [issue26346] PySequenceMethods documentation missing
 sq_slice and sq_ass_slice
Message-ID: <1455243153.76.0.688486976715.issue26346@psf.upfronthosting.co.za>


New submission from Anthony Tuininga:

These methods are completely missing from the documentation found here:

https://docs.python.org/3/c-api/typeobj.html

----------
assignee: docs at python
components: Documentation
messages: 260154
nosy: atuining, docs at python
priority: normal
severity: normal
status: open
title: PySequenceMethods documentation missing sq_slice and sq_ass_slice
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26346>
_______________________________________

From report at bugs.python.org  Thu Feb 11 23:16:25 2016
From: report at bugs.python.org (Martin Panter)
Date: Fri, 12 Feb 2016 04:16:25 +0000
Subject: [docs] [issue26346] PySequenceMethods documentation missing
 sq_slice and sq_ass_slice
In-Reply-To: <1455243153.76.0.688486976715.issue26346@psf.upfronthosting.co.za>
Message-ID: <1455250585.17.0.228348149206.issue26346@psf.upfronthosting.co.za>


Martin Panter added the comment:

Maybe they are missing because they don?t exist in Python 3 :) <https://hg.python.org/cpython/file/v3.5.1/Include/object.h#l291>

Perhaps what is needed instead is a list of the actual fields in order, since I assume Python supports compilers that can?t use the designated initializer (PySequenceMethods){.sq_contains=...} syntax.

----------
nosy: +martin.panter

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26346>
_______________________________________

From report at bugs.python.org  Thu Feb 11 23:31:13 2016
From: report at bugs.python.org (Anthony Tuininga)
Date: Fri, 12 Feb 2016 04:31:13 +0000
Subject: [docs] [issue26346] PySequenceMethods documentation missing
 sq_slice and sq_ass_slice
In-Reply-To: <1455243153.76.0.688486976715.issue26346@psf.upfronthosting.co.za>
Message-ID: <1455251473.2.0.574290948164.issue26346@psf.upfronthosting.co.za>


Anthony Tuininga added the comment:

Ah yes. The fields are still there, though, just marked as not used. Interestingly enough they aren't documented in the Python 2 documentation either....and they are in the Python 2.7 headers I have (not marked as unused either).

Your suggestion makes sense. The reason I ran into it is I followed an example found in the core code for Python 3.5.1....which referenced sq_slice and sq_ass_slice in the order they are defined in the structure...

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26346>
_______________________________________

From report at bugs.python.org  Fri Feb 12 14:01:49 2016
From: report at bugs.python.org (Anish Shah)
Date: Fri, 12 Feb 2016 19:01:49 +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: <1455303709.88.0.688974315201.issue26209@psf.upfronthosting.co.za>


Changes by Anish Shah <shah.anish07 at gmail.com>:


----------
nosy: +anish.shah

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26209>
_______________________________________

From report at bugs.python.org  Fri Feb 12 18:22:20 2016
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 12 Feb 2016 23:22:20 +0000
Subject: [docs] [issue26334] bytes.translate() doesn't take keyword
 arguments; docs suggests it does
In-Reply-To: <1455133964.48.0.745384045329.issue26334@psf.upfronthosting.co.za>
Message-ID: <1455319340.11.0.882713491479.issue26334@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

This is a known, generic issue with c-coded functions.  Some C functions have been converted, especially those with boolean parameters, and especially those with multiple boolean parameters.

I think, but an not sure, that / is sometimes used to signal that the preceding are position only, and that this may have something to do with ArgumentClinic.  I also would like a consistent indication.  But this may be a duplicate issue.

----------
nosy: +terry.reedy

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26334>
_______________________________________

From report at bugs.python.org  Fri Feb 12 18:41:53 2016
From: report at bugs.python.org (Nicholas Chammas)
Date: Fri, 12 Feb 2016 23:41:53 +0000
Subject: [docs] [issue26334] bytes.translate() doesn't take keyword
 arguments; docs suggests it does
In-Reply-To: <1455133964.48.0.745384045329.issue26334@psf.upfronthosting.co.za>
Message-ID: <1455320513.54.0.812402746254.issue26334@psf.upfronthosting.co.za>


Nicholas Chammas added the comment:

Yep, you're right. I'm just understanding now that we have lots of methods defined in C which have signatures like this.

Is there an umbrella issue, perhaps, that covers adding support for keyword-based arguments to functions defined in C, like `translate()`?

----------
resolution:  -> duplicate
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26334>
_______________________________________

From report at bugs.python.org  Fri Feb 12 19:47:02 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 13 Feb 2016 00:47:02 +0000
Subject: [docs] [issue25179] PEP 498 f-strings need to be documented
In-Reply-To: <1442688918.61.0.173837832796.issue25179@psf.upfronthosting.co.za>
Message-ID: <20160213004659.18364.9231@psf.io>


Roundup Robot added the comment:

New changeset f4d7de7d18c0 by Martin Panter in branch 'default':
Issue #25179: Documentation for formatted string literals aka f-strings
https://hg.python.org/cpython/rev/f4d7de7d18c0

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25179>
_______________________________________

From report at bugs.python.org  Fri Feb 12 22:14:43 2016
From: report at bugs.python.org (Martin Panter)
Date: Sat, 13 Feb 2016 03:14:43 +0000
Subject: [docs] [issue25179] PEP 498 f-strings need to be documented
In-Reply-To: <1442688918.61.0.173837832796.issue25179@psf.upfronthosting.co.za>
Message-ID: <1455333282.89.0.373486170298.issue25179@psf.upfronthosting.co.za>


Martin Panter added the comment:

Hopefully that did it. Let me know if I missed anything.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25179>
_______________________________________

From report at bugs.python.org  Sat Feb 13 03:52:33 2016
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 13 Feb 2016 08:52:33 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1455353553.05.0.362002737641.issue26355@psf.upfronthosting.co.za>


Changes by Nick Coghlan <ncoghlan at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26355>
_______________________________________

From report at bugs.python.org  Sat Feb 13 05:24:40 2016
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 13 Feb 2016 10:24:40 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1455359080.94.0.389152594413.issue26355@psf.upfronthosting.co.za>


Changes by Ezio Melotti <ezio.melotti at gmail.com>:


----------
nosy: +ezio.melotti

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26355>
_______________________________________

From report at bugs.python.org  Sat Feb 13 06:58:36 2016
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 13 Feb 2016 11:58:36 +0000
Subject: [docs] [issue25726] sys.setprofile / sys.getprofile asymetry
In-Reply-To: <1448406267.14.0.484592445826.issue25726@psf.upfronthosting.co.za>
Message-ID: <1455364716.81.0.100558622619.issue25726@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Ok, this is because internally, sys.setprofile (or to be exact, PyEval_SetProfile) sets two things: a C function, and a "profileobj", which is the argument to setprofile().

sys.setprofile sets the C function to the "profile_trampoline", which supports calling Python profile functions.  The profileobj is the Python profile function.

The C profiler sets the C function to a different callback, and uses the profileobj for storing the reference to the Profiler object.

sys.getprofile just returns the profileobj, which means that you can't save/restore the profiler state with the two functions when using cProfile.

There is not much we can do here except for explicitly documenting this.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25726>
_______________________________________

From report at bugs.python.org  Sat Feb 13 07:13:49 2016
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 13 Feb 2016 12:13:49 +0000
Subject: [docs] [issue26355] Emit major version based canonical URLs for docs
In-Reply-To: <1455353539.4.0.541474968967.issue26355@psf.upfronthosting.co.za>
Message-ID: <1455365629.25.0.900814702943.issue26355@psf.upfronthosting.co.za>


Georg Brandl added the comment:

So we'd have to add a <link> tag? Should be easy.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26355>
_______________________________________

From report at bugs.python.org  Sat Feb 13 13:01:55 2016
From: report at bugs.python.org (Anish Shah)
Date: Sat, 13 Feb 2016 18:01:55 +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: <1455386515.39.0.787510011657.issue26209@psf.upfronthosting.co.za>


Changes by Anish Shah <shah.anish07 at gmail.com>:


----------
nosy:  -anish.shah

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26209>
_______________________________________

From report at bugs.python.org  Sun Feb 14 00:16:03 2016
From: report at bugs.python.org (Martin Panter)
Date: Sun, 14 Feb 2016 05:16:03 +0000
Subject: [docs] [issue5824] SocketServer.DatagramRequestHandler Broken under
 Linux
In-Reply-To: <1240525238.53.0.858571250541.issue5824@psf.upfronthosting.co.za>
Message-ID: <1455426963.67.0.160416130485.issue5824@psf.upfronthosting.co.za>


Martin Panter added the comment:

Also see the three commented-out tests in test_socketserver. I presume the code needs to ensure the client binds to a name, and then the tests will be able to receive something back from the server.

----------
stage:  -> needs patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5824>
_______________________________________

From report at bugs.python.org  Sun Feb 14 02:33:11 2016
From: report at bugs.python.org (Martin Panter)
Date: Sun, 14 Feb 2016 07:33:11 +0000
Subject: [docs] [issue20598] argparse docs: '7'.split() is confusing magic
In-Reply-To: <1392132505.16.0.864715722344.issue20598@psf.upfronthosting.co.za>
Message-ID: <1455435191.62.0.787518778585.issue20598@psf.upfronthosting.co.za>


Martin Panter added the comment:

Here is a more conservative patch. What do you think Paul?

* Keep all the changes to single-item and empty lists
* Revert many of the other changes, except where there are only a few arguments and I feel it would make the section or piece of code too inconsistent

----------
stage: commit review -> patch review
Added file: http://bugs.python.org/file41915/single-arg-list.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20598>
_______________________________________

From report at bugs.python.org  Sun Feb 14 05:51:23 2016
From: report at bugs.python.org (Martin Panter)
Date: Sun, 14 Feb 2016 10:51:23 +0000
Subject: [docs] [issue26334] bytes.translate() doesn't take keyword
 arguments; docs suggests it does
In-Reply-To: <1455133964.48.0.745384045329.issue26334@psf.upfronthosting.co.za>
Message-ID: <1455447083.46.0.702857413433.issue26334@psf.upfronthosting.co.za>


Martin Panter added the comment:

Nicholas, there is Issue 8706 about converting functions and methods to accept keywords in general.

There is also the slash ?/? indicator proposed by PEP 457, which is used for some functions in pydoc; bytes.replace() for instance. In Issue 23738 I was trying to get some consensus on using this slash notation in the main documentation, in which case bytes.translate() could look like

bytes.translate(table, delete=b"", /)

And there is Issue 21314 about where to document the slash notation that is already used in pydoc.

----------
nosy: +martin.panter
superseder:  -> accept keyword arguments on most base type methods and builtins

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26334>
_______________________________________

From report at bugs.python.org  Mon Feb 15 05:35:57 2016
From: report at bugs.python.org (Xavier Combelle)
Date: Mon, 15 Feb 2016 10:35:57 +0000
Subject: [docs] [issue26363] builtins propagation is misleading described in
 exec and eval documentation
Message-ID: <1455532557.92.0.652570511332.issue26363@psf.upfronthosting.co.za>


Changes by Xavier Combelle <xavier.combelle at gmail.com>:


----------
assignee: docs at python
components: Documentation
nosy: docs at python, xcombelle
priority: normal
severity: normal
status: open
title: builtins propagation is misleading described in exec and eval documentation

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26363>
_______________________________________

From report at bugs.python.org  Mon Feb 15 05:42:15 2016
From: report at bugs.python.org (Xavier Combelle)
Date: Mon, 15 Feb 2016 10:42:15 +0000
Subject: [docs] [issue26363] __builtins__ propagation is misleading
 described in exec and eval documentation
Message-ID: <1455532935.35.0.388834921119.issue26363@psf.upfronthosting.co.za>


New submission from Xavier Combelle:

According to my experiment in code, the current behavior of python3.5 is different that the document says. If I understand well the purpose of this behavior is to propagate the __builtins__ global constant if globals has not one.

In
https://docs.python.org/3.6/library/functions.html#eval

it is written  "If the globals dictionary is present and lacks ?__builtins__?, the current globals are copied into globals before expression is parsed." only the __builtins__ looks copied not all the globals


In
https://docs.python.org/3.6/library/functions.html#exec
It is written:
"If the globals dictionary does not contain a value for the key __builtins__, a reference to the dictionary of the built-in module builtins is inserted under that key." it looks like it is not a reference to the built-in module builtin, but a reference to __builtin__ global

----------
title: builtins propagation is misleading described in exec and eval documentation -> __builtins__ propagation is misleading described in exec and eval documentation
versions: +Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26363>
_______________________________________

From report at bugs.python.org  Mon Feb 15 05:46:55 2016
From: report at bugs.python.org (Julien)
Date: Mon, 15 Feb 2016 10:46:55 +0000
Subject: [docs] [issue26363] __builtins__ propagation is misleading
 described in exec and eval documentation
In-Reply-To: <1455532935.35.0.388834921119.issue26363@psf.upfronthosting.co.za>
Message-ID: <1455533215.65.0.515325601342.issue26363@psf.upfronthosting.co.za>


Changes by Julien <python at mandark.fr>:


----------
nosy: +sizeof

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26363>
_______________________________________

From report at bugs.python.org  Mon Feb 15 10:49:23 2016
From: report at bugs.python.org (Tony R.)
Date: Mon, 15 Feb 2016 15:49:23 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdwqBvdmVyIOKAnC4uIHZlcnNpb25jaGFuZ2Vk4oCdIHdoZXJlIGFwcHJv?=
 =?utf-8?q?priate?=
Message-ID: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>


New submission from Tony R.:

In the documentation, I noticed several uses of ``.. versionchanged::`` that described things which had been added.  

I love Python, and its documentation, and I wanted to contribute.  So, I figured a low-risk contribution would be to change ``.. versionchanged::`` to ?.. versionadded? where appropriate.  (I also tweaked the descriptions accordingly.  E.g., ?Added the *x* argument? became ?The *x* argument?, because it?s unnecessary to say ?added? in a description under ?.. versionadded?.)

I did also make a few unrelated tweaks along the way--all very minor, and related to phrasing or formatting. 

Please let me know if I can do anything else to get this merged!

----------
assignee: docs at python
components: Documentation
files: _docs-version-markup.patch
keywords: patch
messages: 260313
nosy: Tony R., docs at python
priority: normal
severity: normal
status: open
title: Use ?.. versionadded??over ?.. versionchanged? where appropriate
type: enhancement
Added file: http://bugs.python.org/file41929/_docs-version-markup.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From report at bugs.python.org  Mon Feb 15 11:14:32 2016
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 15 Feb 2016 16:14:32 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdwqBvdmVyIOKAnC4uIHZlcnNpb25jaGFuZ2Vk4oCdIHdoZXJlIGFwcHJv?=
 =?utf-8?q?priate?=
In-Reply-To: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
Message-ID: <1455552872.93.0.519646126274.issue26366@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Hi Tony,

thanks for the patch, and for the will to contribute.  I'm not sure this patch should be merged though; the original intention was to use "versionadded" where the API item is completely new.  So "The parameter x was added" in a function is using "versionchanged" because only an aspect of the function's signature was changed.

There may be a bit of confusion because many people wrote changes, and not every change is reviewed by the same developers, but this is the original intent that I think we should not change wholesale.

----------
nosy: +georg.brandl

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From report at bugs.python.org  Mon Feb 15 11:23:14 2016
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 15 Feb 2016 16:23:14 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdwqBvdmVyIOKAnC4uIHZlcnNpb25jaGFuZ2Vk4oCdIHdoZXJlIGFwcHJv?=
 =?utf-8?q?priate?=
In-Reply-To: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
Message-ID: <1455553394.44.0.646121361214.issue26366@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I agree with Georg.
I also went to double-check what the devguide says, and at https://docs.python.org/devguide/documenting.html#paragraph-level-markup it shows an example of versionadded for a parameter.
If a versionchanged should be used instead, maybe the devguide should be fixed.

Having versionadded/changed used consistently would also be nice though, especially if we can start exploiting them (together with deprecated/deprecated-removed) to auto-generate sections of the whatsnew page.

----------
nosy: +ezio.melotti

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From report at bugs.python.org  Mon Feb 15 11:47:28 2016
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 15 Feb 2016 16:47:28 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdwqBvdmVyIOKAnC4uIHZlcnNpb25jaGFuZ2Vk4oCdIHdoZXJlIGFwcHJv?=
 =?utf-8?q?priate?=
In-Reply-To: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
Message-ID: <1455554848.32.0.405973473065.issue26366@psf.upfronthosting.co.za>


Georg Brandl added the comment:

The devguide should be updated, yes.

And probably someone should look at the remaining versionadded's...

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From report at bugs.python.org  Mon Feb 15 16:03:37 2016
From: report at bugs.python.org (Martin Panter)
Date: Mon, 15 Feb 2016 21:03:37 +0000
Subject: [docs] [issue26224] Add "version added" for documentation of
 asyncio.timeout for documentation of python 3.4, 3.5, 3.6
In-Reply-To: <1453935768.98.0.383268297204.issue26224@psf.upfronthosting.co.za>
Message-ID: <1455570217.78.0.920291535878.issue26224@psf.upfronthosting.co.za>


Changes by Martin Panter <vadmium+py at gmail.com>:


----------
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26224>
_______________________________________

From report at bugs.python.org  Mon Feb 15 16:12:10 2016
From: report at bugs.python.org (Martin Panter)
Date: Mon, 15 Feb 2016 21:12:10 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdwqBvdmVyIOKAnC4uIHZlcnNpb25jaGFuZ2Vk4oCdIHdoZXJlIGFwcHJv?=
 =?utf-8?q?priate?=
In-Reply-To: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
Message-ID: <1455570730.26.0.780620935746.issue26366@psf.upfronthosting.co.za>


Martin Panter added the comment:

If you changed existing versionadded notices to versionchanged in similar cases, how would the size of the patch compare? This problem was also recently brought up at <https://bugs.python.org/review/19475/diff/16235/Doc/library/datetime.rst#newcode1180>.

My weak opinion is that a new parameter is a new API item, not just a change in behaviour, so should probably have ?versionadded?. But I hardly think it is a big problem whichever markup is used.

----------
nosy: +martin.panter

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From report at bugs.python.org  Mon Feb 15 17:22:18 2016
From: report at bugs.python.org (Ori Avtalion)
Date: Mon, 15 Feb 2016 22:22:18 +0000
Subject: [docs] [issue20169] random module doc page has broken links
In-Reply-To: <1389135190.46.0.595431802912.issue20169@psf.upfronthosting.co.za>
Message-ID: <1455574938.96.0.25550186823.issue20169@psf.upfronthosting.co.za>


Changes by Ori Avtalion <ori at avtalion.name>:


----------
nosy: +salty-horse

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20169>
_______________________________________

From report at bugs.python.org  Mon Feb 15 20:44:16 2016
From: report at bugs.python.org (Ryan Stuart)
Date: Tue, 16 Feb 2016 01:44:16 +0000
Subject: [docs] [issue26368] grammatical error in documentation
Message-ID: <1455587055.9.0.191263906998.issue26368@psf.upfronthosting.co.za>


New submission from Ryan Stuart:

The note for 18.5.5.1. Stream functions is missing a word. It should read "Note The top-level functions in this module are meant **as** convenience wrappers only; there?s really nothing special there, and if they don?t do exactly what you want, feel free to copy their code."

----------
assignee: docs at python
components: Documentation
files: asyncio-stream_docs.patch
keywords: patch
messages: 260339
nosy: Ryan Stuart, docs at python
priority: normal
severity: normal
status: open
title: grammatical error in documentation
versions: Python 3.4, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41931/asyncio-stream_docs.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26368>
_______________________________________

From report at bugs.python.org  Mon Feb 15 21:28:45 2016
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 16 Feb 2016 02:28:45 +0000
Subject: [docs] [issue26368] grammatical error in documentation
In-Reply-To: <1455587055.9.0.191263906998.issue26368@psf.upfronthosting.co.za>
Message-ID: <20160216022841.18358.35548@psf.io>


Roundup Robot added the comment:

New changeset 8ee91cb2e2a4 by Ned Deily in branch '3.5':
Issue #26368: fix typo in asynchio stream doc, reported by Ryan Stuart.
https://hg.python.org/cpython/rev/8ee91cb2e2a4

New changeset 12502327d2c0 by Ned Deily in branch 'default':
Issue #26368: fix typo in asynchio stream doc, reported by Ryan Stuart.
https://hg.python.org/cpython/rev/12502327d2c0

----------
nosy: +python-dev

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26368>
_______________________________________

From report at bugs.python.org  Mon Feb 15 21:30:14 2016
From: report at bugs.python.org (Ned Deily)
Date: Tue, 16 Feb 2016 02:30:14 +0000
Subject: [docs] [issue26368] grammatical error in asyncio stream
 documentation
In-Reply-To: <1455587055.9.0.191263906998.issue26368@psf.upfronthosting.co.za>
Message-ID: <1455589814.56.0.0187522270843.issue26368@psf.upfronthosting.co.za>


Ned Deily added the comment:

Thanks for the report, Ryan!

----------
nosy: +ned.deily
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
title: grammatical error in documentation -> grammatical error in asyncio stream documentation
versions:  -Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26368>
_______________________________________

From report at bugs.python.org  Mon Feb 15 21:52:55 2016
From: report at bugs.python.org (Mike Short)
Date: Tue, 16 Feb 2016 02:52:55 +0000
Subject: [docs] [issue22062] Fix pathlib.Path.(r)glob doc glitches.
In-Reply-To: <1406239862.0.0.293742999811.issue22062@psf.upfronthosting.co.za>
Message-ID: <1455591175.51.0.637415061293.issue22062@psf.upfronthosting.co.za>


Changes by Mike Short <bmshort at gmail.com>:


----------
keywords: +patch
Added file: http://bugs.python.org/file41932/pathlib.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22062>
_______________________________________

From report at bugs.python.org  Mon Feb 15 22:03:06 2016
From: report at bugs.python.org (Mike Short)
Date: Tue, 16 Feb 2016 03:03:06 +0000
Subject: [docs] [issue22062] Fix pathlib.Path.(r)glob doc glitches.
In-Reply-To: <1406239862.0.0.293742999811.issue22062@psf.upfronthosting.co.za>
Message-ID: <1455591786.72.0.45745523973.issue22062@psf.upfronthosting.co.za>


Changes by Mike Short <bmshort at gmail.com>:


Added file: http://bugs.python.org/file41933/pathlib.py.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22062>
_______________________________________

From report at bugs.python.org  Mon Feb 15 23:23:15 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 16 Feb 2016 04:23:15 +0000
Subject: [docs] [issue20169] random module doc page has broken links
In-Reply-To: <1389135190.46.0.595431802912.issue20169@psf.upfronthosting.co.za>
Message-ID: <1455596595.29.0.68244499075.issue20169@psf.upfronthosting.co.za>


Changes by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
assignee: rhettinger -> 

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20169>
_______________________________________

From report at bugs.python.org  Tue Feb 16 02:38:00 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 16 Feb 2016 07:38:00 +0000
Subject: [docs] [issue20169] random module doc page has broken links
In-Reply-To: <1389135190.46.0.595431802912.issue20169@psf.upfronthosting.co.za>
Message-ID: <1455608280.65.0.751600691553.issue20169@psf.upfronthosting.co.za>


Changes by Serhiy Storchaka <storchaka at gmail.com>:


----------
nosy: +georg.brandl
priority: low -> normal
versions: +Python 3.6 -Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20169>
_______________________________________

From report at bugs.python.org  Tue Feb 16 04:05:55 2016
From: report at bugs.python.org (Eryk Sun)
Date: Tue, 16 Feb 2016 09:05:55 +0000
Subject: [docs] [issue14597] Cannot unload dll in ctypes until script exits
In-Reply-To: <1334581773.77.0.209505875468.issue14597@psf.upfronthosting.co.za>
Message-ID: <1455613554.92.0.791058918113.issue14597@psf.upfronthosting.co.za>


Eryk Sun added the comment:

The _ctypes extension module provides dlclose on POSIX and FreeLibrary on Windows. For the reasons already stated in this issue, ctypes should not automatically call these functions, but maybe they should be documented and imported to the ctypes module instead of being buried in the private _ctypes extension module. You could also implement them with ctypes itself, but the existing functions in the _ctypes module already set a proper exception if the call fails and properly use pointers (an HMODULE is a pointer).

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
versions: +Python 2.7, Python 3.5, Python 3.6 -Python 3.3

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14597>
_______________________________________

From report at bugs.python.org  Tue Feb 16 04:07:29 2016
From: report at bugs.python.org (Eryk Sun)
Date: Tue, 16 Feb 2016 09:07:29 +0000
Subject: [docs] [issue14597] Cannot unload dll in ctypes until script exits
In-Reply-To: <1334581773.77.0.209505875468.issue14597@psf.upfronthosting.co.za>
Message-ID: <1455613649.71.0.611182853258.issue14597@psf.upfronthosting.co.za>


Eryk Sun added the comment:

As to not being able to delete a loaded DLL on Windows, a workaround that may help in some instances is to rename it to a temporary name on the same volume. This is useful for upgrading in place. If you have admin privileges you can even flag the renamed DLL to be deleted when the system reboots:

    MoveFileExW(renamed_dll_path, NULL, MOVEFILE_DELAY_UNTIL_REBOOT)

Renaming a loaded DLL succeeds because the system opens the file with delete sharing, which allows renaming (i.e. relinking) an open file. 

To verify this, let's check the associated file object that's used by the mapping for python35.dll. We can see this in a local kernel debugging session. The following is in 64-bit Windows 7.

Attach to the Python process address space:

    lkd> .tlist python.exe
     0n2296 python.exe
    lkd> !process 0n2296 0
    Searching for Process with Cid == 8f8
    Cid handle table at fffff8a003506000 with 951 entries in use

    PROCESS fffffa800712fb10
        SessionId: 0  Cid: 08f8    Peb: 7fffffdf000  ParentCid: 02b8
        DirBase: 20780d000  ObjectTable: fffff8a0189fe1a0  HandleCount:  67.
        Image: python.exe

    lkd> .process /p /r 0xfffffa800712fb10 
    Implicit process is now fffffa80`0712fb10
    Loading User Symbols
    ...................................

Get the base address for python35.dll.

    lkd> lm m python35
    start             end                 module name
    00000000`66fb0000 00000000`67393000   python35   (deferred)

Get the associated Virtual Address Descriptor (VAD).

    lkd> !vad 66fb0000
    VAD             level  start  end    commit
    fffffa800855f230 (-1)  66fb0  67392  151 Mapped  Exe
                                         EXECUTE_WRITECOPY
                                         \Program Files\Python35\python35.dll

Get the File object reference from the associated control area.

    lkd> ?? ((nt!_MMVAD *)0xfffffa800855f230)->Subsection->ControlArea->FilePointer
    struct _EX_FAST_REF
       +0x000 Object           : 0xfffffa80`093f1503 Void
       +0x000 RefCnt           : 0y0011
       +0x000 Value            : 0xfffffa80`093f1503

The low nibble in the above address is information that needs to be masked out, so the address is actually 0xfffffa80`093f1500. Verify we have the correct file object by checking the filename.
       
    lkd> ?? ((nt!_FILE_OBJECT *)0xfffffa80`093f1500)->FileName
    struct _UNICODE_STRING
     "\Program Files\Python35\python35.dll"
       +0x000 Length           : 0x48
       +0x002 MaximumLength    : 0x78
       +0x008 Buffer           : 0xfffff8a0`04b23690
                                 "\Program Files\Python35\python35.dll"

Finally, check the sharing mode. We see below that the file for a DLL mapping is loaded with read and delete sharing, but not write sharing.

    lkd> ?? ((nt!_FILE_OBJECT *)0xfffffa80`093f1500)->SharedRead
    unsigned char 0x01 ''
    lkd> ?? ((nt!_FILE_OBJECT *)0xfffffa80`093f1500)->SharedDelete
    unsigned char 0x01 ''
    lkd> ?? ((nt!_FILE_OBJECT *)0xfffffa80`093f1500)->SharedWrite
    unsigned char 0x00 ''

Thus when deleting a DLL fails, it's not due to ERROR_SHARING_VIOLATION (32). The sharing mode would actually permit deleting the file. Instead the error is ERROR_ACCESS_DENIED (5), which results from the system call NtSetInformationFile returning STATUS_CANNOT_DELETE (0xC0000121), because the file currently has a mapped image or data section. But that doesn't stop us from renaming it to get it out of the way of an in-place upgrade.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14597>
_______________________________________

From report at bugs.python.org  Tue Feb 16 06:48:52 2016
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 16 Feb 2016 11:48:52 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdwqBvdmVyIOKAnC4uIHZlcnNpb25jaGFuZ2Vk4oCdIHdoZXJlIGFwcHJv?=
 =?utf-8?q?priate?=
In-Reply-To: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
Message-ID: <1455623332.14.0.638159999326.issue26366@psf.upfronthosting.co.za>


Berker Peksag added the comment:

I agree with Georg and Ezio. We should update the devguide.

Tony, would you like to propose a patch? The repo is at https://hg.python.org/devguide

----------
nosy: +berker.peksag

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From report at bugs.python.org  Tue Feb 16 06:53:11 2016
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 16 Feb 2016 11:53:11 +0000
Subject: [docs] [issue24911] Context manager of socket.socket is not
 documented
In-Reply-To: <1440189246.69.0.0632097129757.issue24911@psf.upfronthosting.co.za>
Message-ID: <1455623591.92.0.928219306242.issue24911@psf.upfronthosting.co.za>


Berker Peksag added the comment:

socket-context.patch looks good to me. There is no need to add a NEWS entry for this.

----------
nosy: +berker.peksag
stage: patch review -> commit review
versions:  -Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue24911>
_______________________________________

From report at bugs.python.org  Tue Feb 16 06:58:58 2016
From: report at bugs.python.org (Ben Spiller)
Date: Tue, 16 Feb 2016 11:58:58 +0000
Subject: [docs] [issue26369] doc for unicode.decode and str.encode is
 unnecessarily confusing
Message-ID: <1455623938.04.0.928922751587.issue26369@psf.upfronthosting.co.za>


New submission from Ben Spiller:

It's well known that lots of people struggle writing correct programs using non-ascii strings in python 2.x, but I think one of the main reasons for this could be very easily fixed with a small addition to the documentation for str.encode and unicode.decode, which is currently quite vague. 

The decode/encode methods really make most sense when called on a unicode string i.e. unicode.encode() to produce a byte string, or on a byte string e.g. str.decode() to produce a unicode object from a byte string. 

However, the additional presence of the opposite methods str.encode() and unicode.decode() is quite confusing, and a frequent source of errors - e.g. calling str.encode('utf-8') first DECODES the str object (which might already be in utf8) to a unicode string **using the default encoding of "ascii"** (!) before ENCODING to a utf-8 byte str as requested, which of course will fail at the first stage with the classic error "UnicodeDecodeError: 'ascii' codec can't decode byte" if there are any non-ascii chars present. It's unfortunate that this initial decode/encode stage ignores both the "encoding" argument (used only for the subsequent encode/decode) and the "errors" argument (commonly used when the programmer is happy with a best-effort conversion e.g. for logging purposes).

Anyway, given this behaviour, a lot of time would be saved by a simple sentence on the doc for str.encode()/unicode.decode() essentially warning people that those methods aren't that useful and they probably really intended to use str.decode()/unicode.encode() - the current doc gives absolutely no clue about this extra stage which ignores the input arguments and sues 'ascii' and 'strict'. It might also be worth stating in the documentation that the pattern (u.encode(encoding) if isinstance(u, unicode) else u) can be helpful for cases where you unavoidably have to deal with both kinds of input, string calling str.encode is such a bad idea. 

In an ideal world I'd love to see the implementation of str.encode/unicode.decode changed to be more useful (i.e. instead of using ascii, it would be more logical and useful to use the passed-in encoding to perform the initial decode/encode, and the apss-in 'errors' value). I wasn't sure if that change would be accepted so for now I'm proposing better documentation of the existing behaviour as a second-best.

----------
assignee: docs at python
components: Documentation
messages: 260359
nosy: benspiller, docs at python
priority: normal
severity: normal
status: open
title: doc for unicode.decode and str.encode is unnecessarily confusing
type: behavior
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26369>
_______________________________________

From report at bugs.python.org  Tue Feb 16 08:01:38 2016
From: report at bugs.python.org (Steven D'Aprano)
Date: Tue, 16 Feb 2016 13:01:38 +0000
Subject: [docs] [issue26369] doc for unicode.decode and str.encode is
 unnecessarily confusing
In-Reply-To: <1455623938.04.0.928922751587.issue26369@psf.upfronthosting.co.za>
Message-ID: <1455627698.41.0.52547652524.issue26369@psf.upfronthosting.co.za>


Steven D'Aprano added the comment:

Perhaps you could suggest a specific change to the docstrings for str.encode and unicode.decode?

(BTW, I presume you are aware that the equivalent of (bytes)str.encode and unicode.decode are gone in Python 3?)

----------
nosy: +steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26369>
_______________________________________

From report at bugs.python.org  Tue Feb 16 08:32:03 2016
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 16 Feb 2016 13:32:03 +0000
Subject: [docs] [issue26369] doc for unicode.decode and str.encode is
 unnecessarily confusing
In-Reply-To: <1455623938.04.0.928922751587.issue26369@psf.upfronthosting.co.za>
Message-ID: <1455629523.26.0.298980077289.issue26369@psf.upfronthosting.co.za>


Changes by Ezio Melotti <ezio.melotti at gmail.com>:


----------
nosy: +ezio.melotti

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26369>
_______________________________________

From report at bugs.python.org  Tue Feb 16 09:35:44 2016
From: report at bugs.python.org (Brian Curtin)
Date: Tue, 16 Feb 2016 14:35:44 +0000
Subject: [docs] [issue14597] Cannot unload dll in ctypes until script exits
In-Reply-To: <1334581773.77.0.209505875468.issue14597@psf.upfronthosting.co.za>
Message-ID: <1455633344.93.0.564280981192.issue14597@psf.upfronthosting.co.za>


Changes by Brian Curtin <brian at python.org>:


----------
nosy:  -brian.curtin

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14597>
_______________________________________

From report at bugs.python.org  Tue Feb 16 11:03:12 2016
From: report at bugs.python.org (Yury Selivanov)
Date: Tue, 16 Feb 2016 16:03:12 +0000
Subject: [docs] [issue24911] Context manager of socket.socket is not
 documented
In-Reply-To: <1440189246.69.0.0632097129757.issue24911@psf.upfronthosting.co.za>
Message-ID: <1455638592.78.0.80397652742.issue24911@psf.upfronthosting.co.za>


Yury Selivanov added the comment:

The patch looks good.  It would also be cool if you can add a short code snippet somewhere:

   sock = socket.socket()
   with sock:
      sock.bind(('127.0.0.1', 8080))
      sock.listen()
      ...

----------
nosy: +yselivanov

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue24911>
_______________________________________

From report at bugs.python.org  Tue Feb 16 13:14:03 2016
From: report at bugs.python.org (Mark Mikofski)
Date: Tue, 16 Feb 2016 18:14:03 +0000
Subject: [docs] [issue14597] Cannot unload dll in ctypes until script exits
In-Reply-To: <1334581773.77.0.209505875468.issue14597@psf.upfronthosting.co.za>
Message-ID: <1455646442.94.0.571133870345.issue14597@psf.upfronthosting.co.za>


Mark Mikofski added the comment:

Snippets of "proprietary" code

`setup.py`
----------
# run clean or build libraries if they don't exist
if 'clean' in sys.argv:
    try:
        os.remove(os.path.join(LIB_DIR, SOLPOSAM_LIB_FILE))
        os.remove(os.path.join(LIB_DIR, SPECTRL2_LIB_FILE))
    except OSError as err:
        sys.stderr.write('%s\n' % err)

`core.py`
---------
    # load the DLL
    solposAM_dll = ctypes.cdll.LoadLibrary(SOLPOSAMDLL)
    _solposAM = solposAM_dll.solposAM

After deleting files, setup.py tries to build, then runs test_cdlls.py a unittest that contains test_solposAM() that calls solposAM() and imports core.py that contains solposAM.

Case 1:
-------
I put the load library calls inside the function solposAM().
Function calls works as expected.
I am able to delete dlls after interpreter exits and restarts using os.remove()

Case 2:
-------
I put the load library calls at the module level.
Function calls works as expected.
If I try to delete dlls after interpreter exits and restarts using os.remove() I get access denied, but I can delete them from windows explorer.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14597>
_______________________________________

From victor.stinner at gmail.com  Wed Feb 17 06:19:27 2016
From: victor.stinner at gmail.com (victor.stinner at gmail.com)
Date: Wed, 17 Feb 2016 11:19:27 -0000
Subject: [docs] Context manager of socket.socket is not documented (issue
 24911)
Message-ID: <20160217111927.14613.317@psf.upfronthosting.co.za>


http://bugs.python.org/review/24911/diff/15445/Doc/library/socket.rst
File Doc/library/socket.rst (right):

http://bugs.python.org/review/24911/diff/15445/Doc/library/socket.rst#newcode771
Doc/library/socket.rst:771: Support for the :keyword:`with` statement
was added.  Exiting the
I suggest to use ":term:`context manager` protocol" instead, as:

https://docs.python.org/dev/library/os.html#os.scandir

"The scandir() iterator supports the context manager protocol and has
the following method:"

http://bugs.python.org/review/24911/

From report at bugs.python.org  Wed Feb 17 06:25:01 2016
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 17 Feb 2016 11:25:01 +0000
Subject: [docs] [issue24911] Context manager of socket.socket is not
 documented
In-Reply-To: <1440189246.69.0.0632097129757.issue24911@psf.upfronthosting.co.za>
Message-ID: <1455708301.04.0.952164054205.issue24911@psf.upfronthosting.co.za>


STINNER Victor added the comment:

I reviewed the patch.

> It would also be cool if you can add a short code snippet somewhere:

The socket module has examples.

Why not modifying these examples to promote the context manager protocol?

Example:
--------
s = socket.socket(socket.AF_INET, socket.SOCK_STREAM) as s
# use with to ensure that the socket is closed, especially on error
with s:
  s.bind((HOST, PORT))
  s.listen(1)
  conn, addr = s.accept()
  with conn:
    print('Connected by', addr)
    while True:
        data = conn.recv(1024)
        if not data: break
        conn.sendall(data)
    conn.close()
--------

The second "with conn:" is maybe overkill. What do you think?

For a client connection, usually I prefer to explicitly close the socket (even if I use "with conn:") to get exception on my ".close()" line, instead of getting an exception from the context manager, which is harder to understand.

----------
nosy: +haypo

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue24911>
_______________________________________

From report at bugs.python.org  Wed Feb 17 16:43:04 2016
From: report at bugs.python.org (David Rager)
Date: Wed, 17 Feb 2016 21:43:04 +0000
Subject: [docs] [issue26378] Typo in regex documentation
Message-ID: <1455745384.28.0.629898893574.issue26378@psf.upfronthosting.co.za>


New submission from David Rager:

In the following sentence, "few" should probably be "fewer."

"Repetitions such as * are greedy; when repeating a RE, the matching engine will try to repeat it as many times as possible. If later portions of the pattern don?t match, the matching engine will then back up and try again with few repetitions."

https://docs.python.org/2/howto/regex.html

Thanks for such a great language and documentation!  My apologies if this isn't actually a typo.

----------
assignee: docs at python
components: Documentation
messages: 260411
nosy: David Rager, docs at python
priority: normal
severity: normal
status: open
title: Typo in regex documentation
type: enhancement
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26378>
_______________________________________

From vadmium+py at gmail.com  Wed Feb 17 17:07:08 2016
From: vadmium+py at gmail.com (vadmium+py at gmail.com)
Date: Wed, 17 Feb 2016 22:07:08 -0000
Subject: [docs] Context manager of socket.socket is not documented
 (issue 24911)
Message-ID: <20160217220708.14613.31648@psf.upfronthosting.co.za>


https://bugs.python.org/review/24911/diff/15445/Doc/library/socket.rst
File Doc/library/socket.rst (right):

https://bugs.python.org/review/24911/diff/15445/Doc/library/socket.rst#newcode771
Doc/library/socket.rst:771: Support for the :keyword:`with` statement
was added.  Exiting the
On 2016/02/17 12:19:27, haypo wrote:
> I suggest to use ":term:`context manager` protocol" instead

Agreed; I like this over the original text.

https://bugs.python.org/review/24911/

From report at bugs.python.org  Wed Feb 17 19:37:23 2016
From: report at bugs.python.org (Martin Panter)
Date: Thu, 18 Feb 2016 00:37:23 +0000
Subject: [docs] [issue24911] Context manager of socket.socket is not
 documented
In-Reply-To: <1440189246.69.0.0632097129757.issue24911@psf.upfronthosting.co.za>
Message-ID: <1455755843.01.0.500157994158.issue24911@psf.upfronthosting.co.za>


Martin Panter added the comment:

Thanks for the reviews.

In this new patch, I modified two existing examples, but did not add any new example. Does that work for you Yury?

Also modified example code for the socketserver module.

Victor: IMO the ?with conn? in the example is not overkill. It ensures the client connection socket is cleaned up, which is completely independent of the server listening socket s.

What exceptions can you get out of conn.close()? I can only think of unusual programming errors like EBADF. I would prefer to remove close() as being redundant with the context manager.

----------
Added file: http://bugs.python.org/file41943/socket-context.v2.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue24911>
_______________________________________

From report at bugs.python.org  Wed Feb 17 21:03:09 2016
From: report at bugs.python.org (karl)
Date: Thu, 18 Feb 2016 02:03:09 +0000
Subject: [docs] [issue24772] Smaller viewport shifts the "expand left menu"
 character into the text
In-Reply-To: <1438422511.74.0.548589592521.issue24772@psf.upfronthosting.co.za>
Message-ID: <1455760989.79.0.462323146044.issue24772@psf.upfronthosting.co.za>


karl added the comment:

Where should I propose a patch to help resolve this issue?
A pointer to the code in the repo and I will do it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue24772>
_______________________________________

From davidpietz51 at gmail.com  Wed Feb 17 20:10:13 2016
From: davidpietz51 at gmail.com (G51)
Date: Wed, 17 Feb 2016 19:10:13 -0600
Subject: [docs] Want to help; need direction.
Message-ID: <27D1EE4F-2F89-45B8-95D4-AF1D57188110@gmail.com>

	Summary:  I wish to help with documenting Python documentation.  Starting at the ?complaining? level.


	What?s up Docs

Details:
	I am pretty much a beginner with programming who really wants to learn Python.   I?ve done just two outdated courses, and few small programs/scripts for myself. 

	I have taught school and ESL, speak a second language and have experience as a lay reader.

	When I read some of the Python documentation, it is clear that beginners could easily be slowed down due to ambiguities and omissions that a more experienced programmer could easily overlook, be he or she either the reader or the writer.

	What is unclear to me, when I click on volunteer, is whether I am volunteering for documenting code or documenting documentation, the latter of which is my preference.

	I believe my lack of experience will be a great asset in this case.

Appreciate any direction you can give me,

									David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160217/36d268da/attachment-0001.html>

From davidpietz51 at gmail.com  Wed Feb 17 20:17:50 2016
From: davidpietz51 at gmail.com (G51)
Date: Wed, 17 Feb 2016 19:17:50 -0600
Subject: [docs] Want to help; need direction.
Message-ID: <AD6A8214-3682-4E34-A33F-B8BC5C4006E3@gmail.com>

	What?s up - ,

Summary:  I wish to help with documenting Python documentation.  Starting at the ?complaining? level.


Details:
	I am pretty much a beginner with programming who really wants to learn Python, with just two outdated courses, and few small programs/scripts for myself. 

	I have taught school and ESL, speak a second language and have experience as a lay reader.

	When I read some of the Python documentation, it is clear that beginners could easily be slowed down due to ambiguities and omissions that a more experienced programmer could easily overlook, be he or she either the reader or the writer.  

	What is unclear to me when I click on links is whether I am volunteering for documenting code or documenting documentation, the latter of which is my preference.

	I believe my lack of experience will be a great asset in this.

Appreciate any direction you can give me,

									David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160217/3f55f47d/attachment-0001.html>

From report at bugs.python.org  Thu Feb 18 02:08:14 2016
From: report at bugs.python.org (Eryk Sun)
Date: Thu, 18 Feb 2016 07:08:14 +0000
Subject: [docs] [issue20010] time.strftime('%z') didn't make +HHMM return in
 windows xp
In-Reply-To: <1387319931.23.0.412917689607.issue20010@psf.upfronthosting.co.za>
Message-ID: <1455779294.1.0.0171926295883.issue20010@psf.upfronthosting.co.za>


Eryk Sun added the comment:

%z works correctly in the new CRT that's used by 3.5:

    Python 3.5.1 (v3.5.1:37a07cee5969, Dec  6 2015, 01:54:25)
    [MSC v.1900 64 bit (AMD64)] on win32
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import time
    >>> time.strftime('%z', time.localtime(time.time()))
    '-0000'
    >>> time.strftime('%Z', time.localtime(time.time()))
    'Coordinated Universal Time'

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
versions: +Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20010>
_______________________________________

From report at bugs.python.org  Thu Feb 18 02:43:20 2016
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 18 Feb 2016 07:43:20 +0000
Subject: [docs] [issue26378] Typo in regex documentation
In-Reply-To: <1455745384.28.0.629898893574.issue26378@psf.upfronthosting.co.za>
Message-ID: <20160218074317.1962.8605@psf.io>


Roundup Robot added the comment:

New changeset c272a1e53f5b by Benjamin Peterson in branch '2.7':
fix typo (closes #26378)
https://hg.python.org/cpython/rev/c272a1e53f5b

New changeset 69717fdd9d5a by Benjamin Peterson in branch '3.5':
fix typo (closes #26378)
https://hg.python.org/cpython/rev/69717fdd9d5a

New changeset 6f0d3ae9f1f3 by Benjamin Peterson in branch 'default':
merge 3.5 (#26378)
https://hg.python.org/cpython/rev/6f0d3ae9f1f3

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26378>
_______________________________________

From report at bugs.python.org  Thu Feb 18 03:13:42 2016
From: report at bugs.python.org (Georg Brandl)
Date: Thu, 18 Feb 2016 08:13:42 +0000
Subject: [docs] [issue26378] Typo in regex documentation
In-Reply-To: <1455745384.28.0.629898893574.issue26378@psf.upfronthosting.co.za>
Message-ID: <1455783222.88.0.129875532034.issue26378@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Thanks for the report!

----------
nosy: +georg.brandl

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26378>
_______________________________________

From report at bugs.python.org  Thu Feb 18 10:40:39 2016
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 18 Feb 2016 15:40:39 +0000
Subject: [docs] [issue16915] mode of socket.makefile is more limited than
 documentation suggests
In-Reply-To: <1357825217.2.0.655032840521.issue16915@psf.upfronthosting.co.za>
Message-ID: <1455810039.22.0.051055873811.issue16915@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the report and for the patch. I would prefer to keep the code simple so I just applied documentation changes with a minor tweak.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +berker.peksag, docs at python
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
versions: +Python 3.5, Python 3.6 -Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16915>
_______________________________________

From report at bugs.python.org  Thu Feb 18 11:27:57 2016
From: report at bugs.python.org (Tony R.)
Date: Thu, 18 Feb 2016 16:27:57 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdwqBvdmVyIOKAnC4uIHZlcnNpb25jaGFuZ2Vk4oCdIHdoZXJlIGFwcHJv?=
 =?utf-8?q?priate?=
In-Reply-To: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
Message-ID: <1455812877.69.0.541684407424.issue26366@psf.upfronthosting.co.za>


Tony R. added the comment:

> My weak opinion is that a new parameter is a new API item, not just a change in behaviour, so should probably have ?versionadded?. 

This was my reasoning as well.  

Also, when I noticed so many instances of ``.. versionchanged`` that all say ?Added the *x* parameter? (or whatever), it strikes me that these are a *large class of changes*, which all have some kind of addition in common.  If you think about it, deprecations and removals are also changes, but they are a large-enough class of changes to merit a distinct markup directive.  

So, just as this is true for ?deprecated? or ?deprecated-removed?, I believe it is just as true for ?added?.  Once all additions, deprecations, and removals have been marked up as such, I think find that there?s still PLENTY of annotations that remain under ``.. versionchanged``.  

Put another way: 

Since these are all different types of changes, it is most useful to the reader if the most specific *type* of change is reflected in the markup.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From report at bugs.python.org  Thu Feb 18 13:43:06 2016
From: report at bugs.python.org (Anish Shah)
Date: Thu, 18 Feb 2016 18:43:06 +0000
Subject: [docs] [issue26149] Suggest PyCharm Community as an editor for Unix
 platforms
In-Reply-To: <1453153728.95.0.733172914649.issue26149@psf.upfronthosting.co.za>
Message-ID: <1455820986.92.0.665852905057.issue26149@psf.upfronthosting.co.za>


Changes by Anish Shah <shah.anish07 at gmail.com>:


----------
nosy: +anish.shah

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26149>
_______________________________________

From report at bugs.python.org  Thu Feb 18 19:00:57 2016
From: report at bugs.python.org (Daan Bakker)
Date: Fri, 19 Feb 2016 00:00:57 +0000
Subject: [docs] [issue26390] hashlib's pbkdf2_hmac documentation "rounds"
 does not match source
Message-ID: <1455840057.88.0.0946194046166.issue26390@psf.upfronthosting.co.za>


New submission from Daan Bakker:

The documentation for pbkdf2_hmac at https://docs.python.org/3/library/hashlib.html uses the "rounds" keyword:

hashlib.pbkdf2_hmac(name, password, salt, rounds, dklen=None)

However, the actual source code uses "iterations". No-one has probably noticed it before because no error is raised if the number of iterations is given as a positional argument.

----------
assignee: docs at python
components: Documentation
files: pbkdf2_4.patch
keywords: patch
messages: 260490
nosy: dbakker, docs at python
priority: normal
severity: normal
status: open
title: hashlib's pbkdf2_hmac documentation "rounds" does not match source
type: enhancement
versions: Python 3.4, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41963/pbkdf2_4.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26390>
_______________________________________

From report at bugs.python.org  Thu Feb 18 20:24:28 2016
From: report at bugs.python.org (Martin Panter)
Date: Fri, 19 Feb 2016 01:24:28 +0000
Subject: [docs] [issue26390] hashlib's pbkdf2_hmac documentation "rounds"
 does not match source
In-Reply-To: <1455840057.88.0.0946194046166.issue26390@psf.upfronthosting.co.za>
Message-ID: <1455845067.85.0.864322565257.issue26390@psf.upfronthosting.co.za>


Martin Panter added the comment:

Thanks for the patch. The documentation still mentions *rounds* in one place, which I presume was meant to be a direct reference to the parameter.

----------
nosy: +martin.panter
stage:  -> patch review
versions:  -Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26390>
_______________________________________

From report at bugs.python.org  Thu Feb 18 21:50:25 2016
From: report at bugs.python.org (Martin Panter)
Date: Fri, 19 Feb 2016 02:50:25 +0000
Subject: [docs] [issue5824] SocketServer.DatagramRequestHandler Broken under
 Linux
In-Reply-To: <1240525238.53.0.858571250541.issue5824@psf.upfronthosting.co.za>
Message-ID: <1455850225.02.0.0369470970284.issue5824@psf.upfronthosting.co.za>


Martin Panter added the comment:

Here is a patch to enable the Unix domain DatagramRequestHandler tests, and bind the client to a socket name. Tests pass for me on Linux :)

The Python 2 version will need to have lowercase socketserver changed case to camel-case SocketServer.

----------
components: +Tests -Documentation
keywords: +patch
stage: needs patch -> patch review
versions: +Python 3.5, Python 3.6 -Python 3.1, Python 3.2
Added file: http://bugs.python.org/file41964/bind-unix.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5824>
_______________________________________

From report at bugs.python.org  Thu Feb 18 21:54:44 2016
From: report at bugs.python.org (Martin Panter)
Date: Fri, 19 Feb 2016 02:54:44 +0000
Subject: [docs] [issue5824] SocketServer.DatagramRequestHandler Broken under
 Linux
In-Reply-To: <1240525238.53.0.858571250541.issue5824@psf.upfronthosting.co.za>
Message-ID: <1455850484.97.0.683561954556.issue5824@psf.upfronthosting.co.za>


Changes by Martin Panter <vadmium+py at gmail.com>:


Removed file: http://bugs.python.org/file41964/bind-unix.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5824>
_______________________________________

From report at bugs.python.org  Thu Feb 18 21:55:03 2016
From: report at bugs.python.org (Martin Panter)
Date: Fri, 19 Feb 2016 02:55:03 +0000
Subject: [docs] [issue5824] SocketServer.DatagramRequestHandler Broken under
 Linux
In-Reply-To: <1240525238.53.0.858571250541.issue5824@psf.upfronthosting.co.za>
Message-ID: <1455850503.75.0.532722899913.issue5824@psf.upfronthosting.co.za>


Changes by Martin Panter <vadmium+py at gmail.com>:


Added file: http://bugs.python.org/file41965/bind-unix.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5824>
_______________________________________

From report at bugs.python.org  Thu Feb 18 22:35:13 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 19 Feb 2016 03:35:13 +0000
Subject: [docs] [issue15608] Improve socketserver doc
In-Reply-To: <1344541466.79.0.410789330017.issue15608@psf.upfronthosting.co.za>
Message-ID: <20160219033446.1705.29346@psf.io>


Roundup Robot added the comment:

New changeset 8b71cd67f548 by Martin Panter in branch '3.5':
Issue #15608: Improve socketserver module documentation
https://hg.python.org/cpython/rev/8b71cd67f548

New changeset fbb8b634fe59 by Martin Panter in branch 'default':
Issue #15608: Merge socketserver doc from 3.5
https://hg.python.org/cpython/rev/fbb8b634fe59

----------
nosy: +python-dev

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15608>
_______________________________________

From report at bugs.python.org  Thu Feb 18 23:01:38 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 19 Feb 2016 04:01:38 +0000
Subject: [docs] [issue15608] Improve socketserver doc
In-Reply-To: <1344541466.79.0.410789330017.issue15608@psf.upfronthosting.co.za>
Message-ID: <20160219040125.1715.65141@psf.io>


Roundup Robot added the comment:

New changeset 9211b7e60c92 by Martin Panter in branch '2.7':
Issue #15608: Improve socketserver module documentation
https://hg.python.org/cpython/rev/9211b7e60c92

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15608>
_______________________________________

From report at bugs.python.org  Thu Feb 18 23:04:09 2016
From: report at bugs.python.org (Martin Panter)
Date: Fri, 19 Feb 2016 04:04:09 +0000
Subject: [docs] [issue15608] Improve socketserver doc
In-Reply-To: <1344541466.79.0.410789330017.issue15608@psf.upfronthosting.co.za>
Message-ID: <1455854649.85.0.828635911027.issue15608@psf.upfronthosting.co.za>


Changes by Martin Panter <vadmium+py at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 2.7, Python 3.6 -Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15608>
_______________________________________

From report at bugs.python.org  Thu Feb 18 23:14:16 2016
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 19 Feb 2016 04:14:16 +0000
Subject: [docs] [issue16823] Python quits on running tkinter code with
 threads
In-Reply-To: <1356924189.65.0.303016065786.issue16823@psf.upfronthosting.co.za>
Message-ID: <1455855256.46.0.501705176516.issue16823@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

If I understand the test code, it creates the tk window in thread 0 (the main thread), generates data in thread 1, sends data via a queue to thread 2, which then inserts it into the Text widget.  I ran a 3.x version up to 34000 iterations.  When I comment out 'tk.mainloop()' or stop the mainloop with ^C, thread 2 stops (reproducibly) with

Exception in thread Thread-2:
Traceback (most recent call last):
  File "C:\Programs\Python35\lib\threading.py", line 914, in _bootstrap_inner
    self.run()
  File "C:\Programs\Python35\lib\threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "F:\Python\mypy\tem.py", line 23, in QueueHandler
    widinst.configure(state="normal")
  File "C:\Programs\Python35\lib\tkinter\__init__.py", line 1330, in configure
    return self._configure('configure', cnf, kw)
  File "C:\Programs\Python35\lib\tkinter\__init__.py", line 1321, in _configure
    self.tk.call(_flatten((self._w, cmd)) + self._options(cnf))
RuntimeError: main thread is not in main loop

I removed the spamming of Shell with 'running' and sped up the test code by reducing the queued and inserted text to the iteration number and reran to completion at 999999.  I retract my statement about all widget access in threads being unsupported.  At least some seems to be at least in 3.x.

Running the original test code above in 2.7.11 from IDLE and console both fail before 2000 iterations in my tries.

Sarbjit: I do not understand 'tkinter wizard'.

Serhiy: I am coming back to this after reading #11077.  Do you have any idea why this code runs in 3.x but eventually fails in 2.x?  If there anything to do, or just close?

----------
nosy: +serhiy.storchaka -gpolo, roger.serwy
Added file: http://bugs.python.org/file41966/tem.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16823>
_______________________________________

From report at bugs.python.org  Thu Feb 18 23:14:39 2016
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 19 Feb 2016 04:14:39 +0000
Subject: [docs] [issue16823] Python quits on running tkinter code with
 threads
In-Reply-To: <1356924189.65.0.303016065786.issue16823@psf.upfronthosting.co.za>
Message-ID: <1455855279.38.0.801238531726.issue16823@psf.upfronthosting.co.za>


Changes by Terry J. Reedy <tjreedy at udel.edu>:


----------
versions: +Python 3.5 -Python 3.2, Python 3.3, Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16823>
_______________________________________

From report at bugs.python.org  Fri Feb 19 02:52:10 2016
From: report at bugs.python.org (Mark Dickinson)
Date: Fri, 19 Feb 2016 07:52:10 +0000
Subject: [docs] [issue26374] concurrent_futures Executor.map semantics
 better specified in docs
In-Reply-To: <1455711990.13.0.290959896018.issue26374@psf.upfronthosting.co.za>
Message-ID: <1455868330.0.0.827624264535.issue26374@psf.upfronthosting.co.za>


Changes by Mark Dickinson <dickinsm at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26374>
_______________________________________

From report at bugs.python.org  Fri Feb 19 02:58:01 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 19 Feb 2016 07:58:01 +0000
Subject: [docs] [issue20169] random module doc page has broken links
In-Reply-To: <1389135190.46.0.595431802912.issue20169@psf.upfronthosting.co.za>
Message-ID: <20160219075755.1669.19114@psf.io>


Roundup Robot added the comment:

New changeset 2d8e8d0e7162 by Georg Brandl in branch '2.7':
Closes #20169: fix inner links random doc.
https://hg.python.org/cpython/rev/2d8e8d0e7162

New changeset 426ac89548b3 by Georg Brandl in branch '3.5':
Closes #20169: fix inner links random doc.
https://hg.python.org/cpython/rev/426ac89548b3

----------
nosy: +python-dev
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20169>
_______________________________________

From report at bugs.python.org  Fri Feb 19 02:59:55 2016
From: report at bugs.python.org (Mark Dickinson)
Date: Fri, 19 Feb 2016 07:59:55 +0000
Subject: [docs] [issue26374] concurrent_futures Executor.map semantics
 better specified in docs
In-Reply-To: <1455711990.13.0.290959896018.issue26374@psf.upfronthosting.co.za>
Message-ID: <1455868795.29.0.648783738168.issue26374@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

I just noticed this point, which may be confusing things:

> Rebut: order is undefined, concurrent_futures specifies map() returns an iterator, where builtin map returns a list.

In Python 3, the built-in map function returns an iterator, not a list.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26374>
_______________________________________

From report at bugs.python.org  Fri Feb 19 03:01:18 2016
From: report at bugs.python.org (Georg Brandl)
Date: Fri, 19 Feb 2016 08:01:18 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdwqBvdmVyIOKAnC4uIHZlcnNpb25jaGFuZ2Vk4oCdIHdoZXJlIGFwcHJv?=
 =?utf-8?q?priate?=
In-Reply-To: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
Message-ID: <1455868878.85.0.545312504177.issue26366@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Here are the original descriptions of the old LaTeX version.

    \begin{macrodesc}{versionadded}{\op{explanation}\p{version}}
      The version of Python which added the described feature to the
      library or C API.  \var{explanation} should be a \emph{brief}
      explanation of the change consisting of a capitalized sentence
      fragment; a period will be appended by the formatting process.
      When this applies to an entire module, it should be placed at
      the top of the module section before any prose.
    \end{macrodesc}

    \begin{macrodesc}{versionchanged}{\op{explanation}\p{version}}
      The version of Python in which the named feature was changed in
      some way (new parameters, changed side effects, etc.).
      \var{explanation} should be a \emph{brief} explanation of the
      change consisting of a capitalized sentence fragment; a
      period will be appended by the formatting process.  This should
      not generally be applied to modules.
    \end{macrodesc}

Adding a parameter is explicitly a "versionchanged" kind of change.

Since the Sphinx items are supposed to be equivalent, this has always been the intention, even if the current devguide deviates.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From report at bugs.python.org  Fri Feb 19 05:34:08 2016
From: report at bugs.python.org (Daan Bakker)
Date: Fri, 19 Feb 2016 10:34:08 +0000
Subject: [docs] [issue26390] hashlib's pbkdf2_hmac documentation "rounds"
 does not match source
In-Reply-To: <1455840057.88.0.0946194046166.issue26390@psf.upfronthosting.co.za>
Message-ID: <1455878048.78.0.645893093503.issue26390@psf.upfronthosting.co.za>


Daan Bakker added the comment:

Good catch. I updated that reference now from rounds to iterations as well.

----------
Added file: http://bugs.python.org/file41969/pbkdf2_5.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26390>
_______________________________________

From pedro.curtis.rangel at gmail.com  Fri Feb 19 08:40:44 2016
From: pedro.curtis.rangel at gmail.com (Pedro Pereira)
Date: Fri, 19 Feb 2016 10:40:44 -0300
Subject: [docs] =?utf-8?q?Ajuda_em_manual_no_idioma_ingl=C3=AAs?=
Message-ID: <CANo7oSD==A80T4ojxNBPSe0j17vjZbUcujZn+ds22UygAgw5Qw@mail.gmail.com>

Bom dia

Sou iniciante no mundo da programa??o comecei estudando C/C++ e agora
fiquei fascinado pelo Pyhon gostaria de saber se a PYTHON BRASIL tem o "The
Python Library Reference" traduzido para o Portugu?s, se tiver gostaria se
fosse poss?vel me enviar o arquivo em pdf pode ser qual quer vers?o, pois
pretendo ser um especialista em python.

desde j? agrade?o sua compreens?o.

Pedro Pereira Rangel Junior
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160219/1028a846/attachment.html>

From report at bugs.python.org  Fri Feb 19 10:02:25 2016
From: report at bugs.python.org (Tony R.)
Date: Fri, 19 Feb 2016 15:02:25 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdwqBvdmVyIOKAnC4uIHZlcnNpb25jaGFuZ2Vk4oCdIHdoZXJlIGFwcHJv?=
 =?utf-8?q?priate?=
In-Reply-To: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
Message-ID: <1455894145.28.0.961044404724.issue26366@psf.upfronthosting.co.za>


Tony R. added the comment:

> Here are the original descriptions of the old LaTeX version.

Holy crap!  You all used to use LaTeX?!  :D  

(I know--LaTeX is still going strong in academia.  I just had no idea it was ever part of Python?s documentation, except as an output format.)

> Adding a parameter is explicitly a "versionchanged" kind of change.
> 
> Since the Sphinx items are supposed to be equivalent, this has always been the intention, even if the current devguide deviates.

Ah, okay.  

Well then, if this is the sort of place where the status quo is sacred, then there is nothing more to discuss.  

But if anyone reading this is open to the idea, please re-read my previous comment in this thread.  The quoted LaTeX docs are clear, but I still believe my ?all changes = (deprecated-removed changes) + (added changes) + (other changes)? interpretation makes more sense than the LaTeX definition.  

I also think it is more helpful to the *reader*--which, I respectfully suggest, should be the basis for any documentation?s guidelines--by marking up changes according to this grouping.

It?s not my desire to be troublesome by making one more appeal.  I simply want to point out that just because somebody wrote the LaTeX definitions a long time ago doesn?t mean that we cannot rewrite them.  They were written by somebody just like us, after all.  

If it?s not obvious by now, I feel strongly about good semantic markup.  The purpose of semantic markup is to describe what something *is*. I just think that changes form a hierarchy, with a generic ?change??as something of the base class, and ?deprecated?, ?removed?, and ?added??as specializations.

If you?re reading this, and you feel similarly--speak up!  

What do you think?


Respectfully,

?Tony

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From fred at fdrake.net  Fri Feb 19 10:38:10 2016
From: fred at fdrake.net (Fred Drake)
Date: Fri, 19 Feb 2016 10:38:10 -0500
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRk?=
	=?utf-8?b?ZWTigJ0gb3ZlciDigJwuLiB2ZXJzaW9uY2hhbmdlZOKAnSB3aGVyZSBh?=
	=?utf-8?q?ppropriate?=
In-Reply-To: <1455894145.28.0.961044404724.issue26366@psf.upfronthosting.co.za>
References: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
 <1455894145.28.0.961044404724.issue26366@psf.upfronthosting.co.za>
Message-ID: <CAFT4OTHXOCC2+yGP3jwqMXka3HS1Mq79NB4bHZR6Ukh91qHfDA@mail.gmail.com>

On Fri, Feb 19, 2016 at 10:02 AM, Tony R. <report at bugs.python.org> wrote:
> Holy crap!  You all used to use LaTeX?!  :D

Python's documentation has a long & colorful history.  :-)

> Well then, if this is the sort of place where the status quo is sacred, then
> there is nothing more to discuss.

Status quo is not sacred, but does have some value.  Changing how busy
people do things is non-trivial.

> But if anyone reading this is open to the idea, please re-read my previous
> comment in this thread.  The quoted LaTeX docs are clear, but I still
> believe my ?all changes = (deprecated-removed changes) + (added
> changes) + (other changes)? interpretation makes more sense than the
> LaTeX definition.
>
> I also think it is more helpful to the *reader*--which, I respectfully suggest,
> should be the basis for any documentation?s guidelines--by marking up
> changes according to this grouping.

I think we all agree that the documentation is for the reader.

> It?s not my desire to be troublesome by making one more appeal.
> I simply want to point out that just because somebody wrote the
> LaTeX definitions a long time ago doesn?t mean that we cannot
> rewrite them.  They were written by somebody just like us, after all.

As the person who wrote them, I don't consider them sacred or
unchangeable.

Having some rational basis for whatever we use is good, and it should
be clearly documented clearly.

> If it?s not obvious by now, I feel strongly about good semantic markup.

We're on the same page here.

> The purpose of semantic markup is to describe what something *is*.
> I just think that changes form a hierarchy, with a generic ?change? as
> something of the base class, and ?deprecated?, ?removed?, and ?added?
> as specializations.

Again, agreed.  That doesn't imply that the specializations encompass
all changes, though.  For some, 'versionchanged' is reasonable.

Part of the problem is getting the granularity right.  The initial intent was
that 'version*' were annotations for the enclosing object (function, class,
method, etc.).  If we want to have something more granular (parameter
added / deprecated / whatever), we should have distinct markup for that.

That could look something like:

    .. parameteradded:: alternate 3.6
       Further explanation goes here.

It's helpful to think of these annotations as pronouns; the antecedent
needs to be clear before they can be interpreted correctly.  It sounds
like that needs to be clarified in the documentation, and possibly
provision added for a more fine-grained form of annotation.


  -Fred

-- 
Fred L. Drake, Jr.    <fred at fdrake.net>
"A storm broke loose in my mind."  --Albert Einstein

From report at bugs.python.org  Fri Feb 19 11:21:01 2016
From: report at bugs.python.org (Georg Brandl)
Date: Fri, 19 Feb 2016 16:21:01 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdIG92ZXIg4oCcLi4gdmVyc2lvbmNoYW5nZWTigJ0gd2hlcmUgYXBwcm9w?=
 =?utf-8?q?riate?=
In-Reply-To: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
Message-ID: <1455898861.89.0.0788731685797.issue26366@psf.upfronthosting.co.za>


Georg Brandl added the comment:

> Well then, if this is the sort of place where the status quo is sacred,
> then there is nothing more to discuss.  

That wasn't my intention when quoting the old documenting guide, it was just
to show what the intent was (and still is), and that I didn't just invent it.
As Fred says, the status quo is not sacred, but we are usually pragmatic and
a nontrivial amount of weight is needed to change it.

> But if anyone reading this is open to the idea, please re-read my previous
> comment in this thread.  The quoted LaTeX docs are clear, but I still
> believe my ?all changes = (deprecated-removed changes) + (added changes) +
> (other changes)? interpretation makes more sense than the LaTeX definition.

It's one interpretation, yes.  My interpretation (which coincides with the one
written back then by Fred) is that the versionchanged applies to the API item
in whose block it occurs.  And a function is not *added* by the addition of
a parameter, it is *changed* by that.  The parameter itself is not a marked-
up API item.  If the structure was like

.. function:: foo(a, b)
   .. parameter:: a
   .. parameter:: b

then adding a parameter c would definitely be marked up as

   .. parameter:: c
      .. versionadded: 3.x

Anyway.  You think your interpretation is better, others including myself
prefer the current one.  This is exactly the kind of argument where the 
status quo wins because the churn necessary to change is not justified.

> It?s not my desire to be troublesome by making one more appeal.  I simply
> want to point out that just because somebody wrote the LaTeX definitions a
> long time ago doesn?t mean that we cannot rewrite them.  They were written
> by somebody just like us, after all.  

Again, you're mistaking the reason I quoted them.

> If it?s not obvious by now, I feel strongly about good semantic markup.
> The purpose of semantic markup is to describe what something *is*. I just
> think that changes form a hierarchy, with a generic ?change? as something
> of the base class, and ?deprecated?, ?removed?, and ?added? as specializations.

That's a nice strawman -- we all feel semantic markup is important, and we
are talking about nothing but semantic markup here.  We're just discussing
the interpretation of one aspect of the semantics.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From report at bugs.python.org  Fri Feb 19 11:37:42 2016
From: report at bugs.python.org (Pas)
Date: Fri, 19 Feb 2016 16:37:42 +0000
Subject: [docs] [issue23061] Update pep8 to specify explicitly 'module
 level' imports at top of file
In-Reply-To: <1418703864.09.0.281927050653.issue23061@psf.upfronthosting.co.za>
Message-ID: <1455899862.02.0.0767602469784.issue23061@psf.upfronthosting.co.za>


Changes by Pas <pasthelod at gmail.com>:


----------
nosy: +pas

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23061>
_______________________________________

From report at bugs.python.org  Fri Feb 19 12:21:05 2016
From: report at bugs.python.org (Tony R.)
Date: Fri, 19 Feb 2016 17:21:05 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdIG92ZXIg4oCcLi4gdmVyc2lvbmNoYW5nZWTigJ0gd2hlcmUgYXBwcm9w?=
 =?utf-8?q?riate?=
In-Reply-To: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
Message-ID: <1455902465.65.0.490056045558.issue26366@psf.upfronthosting.co.za>


Tony R. added the comment:

> Part of the problem is getting the granularity right.  The initial intent was
> that 'version*' were annotations for the enclosing object (function, class,
> method, etc.).  If we want to have something more granular (parameter
> added / deprecated / whatever), we should have distinct markup for that.
> 
> That could look something like:
> 
>     .. parameteradded:: alternate 3.6
>        Further explanation goes here.
> 
> It's helpful to think of these annotations as pronouns; the antecedent
> needs to be clear before they can be interpreted correctly.

Isn?t language fun?!?!  *insane smile* 8)

> It sounds
> like that needs to be clarified in the documentation, and possibly
> provision added for a more fine-grained form of annotation.

Okay.  I can participate in the discussion of that, if it would help...but adding a completely new annotation type is outside my current ability to contribute.  


----

> > Well then, if this is the sort of place where the status quo is sacred,
> > then there is nothing more to discuss.  
> 
> That wasn't my intention when quoting the old documenting guide, it was just
> to show what the intent was (and still is), and that I didn't just invent it.

Your intent was clear to me!  I did not mean to say that you -- or anyone -- just invented it.  

I only know that mature projects (like Python) tend to hold more strongly to the status quo, and that I was advocating a change that was probably going to be an uphill battle to convince others as worthwhile.

> That's a nice strawman -- we all feel semantic markup is important, and we
> are talking about nothing but semantic markup here.  We're just discussing
> the interpretation of one aspect of the semantics.

It was not my wish to set up a strawman.  (I have no formal training in logic, anyways; I?d probably screw it up if I deliberately tried!)  

The reason I was stressing semantic markup is because I anticipated resistance from the mindset of ?Ugh, I don?t want to deal with this tedious crap!?  I  wanted to emphasize semantic markup as something valuable -- worth making an effort for, even if it might appear tedious or trivial at first glance.  

----

That said, I think it?s time for me to bow out of this conversation.  I?ve never made a successful contribution to any part of Python, including the documentation.  There was some talk of updating the devguide or adding new annotations, so I hope that something good comes out of that!  But the issue patch is where my comfort level is right now, and it appears that it?s a no-go.

Thank you for your time, your consideration, and the discussion!

?Tony

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From report at bugs.python.org  Fri Feb 19 12:37:14 2016
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Fri, 19 Feb 2016 17:37:14 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdIG92ZXIg4oCcLi4gdmVyc2lvbmNoYW5nZWTigJ0gd2hlcmUgYXBwcm9w?=
 =?utf-8?q?riate?=
In-Reply-To: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
Message-ID: <1455903434.77.0.47072571677.issue26366@psf.upfronthosting.co.za>


Fred L. Drake, Jr. added the comment:

Another reason to value the status-quo in this case is that this isn't just
a matter for the Python documentation; it's about the recommended usage for
the markup, which is used by many other packages.

Questions that should be discussed include:

1. Should we clarify the documentation for the current annotations to
   the intended use is more consistently understood, or should we leave
   it as-is?

2. Are other distinct kinds of annotations (such as per-parameter notes)
   needed?

   If so, we'll need to consider specific reader / information-content
   needs and determine how they should be marked using new constructs.

   This is independent of implementation, which is likely straightforward.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From report at bugs.python.org  Fri Feb 19 17:53:46 2016
From: report at bugs.python.org (Martin Panter)
Date: Fri, 19 Feb 2016 22:53:46 +0000
Subject: [docs] [issue13354] tcpserver should document non-threaded
 long-living connections
In-Reply-To: <1320570611.72.0.286817751979.issue13354@psf.upfronthosting.co.za>
Message-ID: <1455922426.52.0.129437482285.issue13354@psf.upfronthosting.co.za>


Martin Panter added the comment:

Bas: I think you need to provide more information. Are you talking about protocols like HTTP, where multiple high-level (HTTP-level) requests are made over a single low-level (socket-level) connection? Some example code might help.

Overriding shutdown_request() sounds like a bad idea. I think you eventually would want to truly shutdown the connection. Perhaps it is better to override process_request() and avoid it calling shutdown() until it is ready.

----------
status: open -> pending

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13354>
_______________________________________

From report at bugs.python.org  Fri Feb 19 19:18:58 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 20 Feb 2016 00:18:58 +0000
Subject: [docs] [issue21996] gettarinfo method does not handle files without
 text string names
In-Reply-To: <1405583528.37.0.553699872308.issue21996@psf.upfronthosting.co.za>
Message-ID: <20160220001853.1695.88984@psf.io>


Roundup Robot added the comment:

New changeset 94a94deaf06a by Martin Panter in branch '3.5':
Issues #22468, #21996, #22208: Clarify gettarinfo() and TarInfo usage
https://hg.python.org/cpython/rev/94a94deaf06a

New changeset 9d5217aaea13 by Martin Panter in branch '2.7':
Issues #22468, #21996, #22208: Clarify gettarinfo() and TarInfo usage
https://hg.python.org/cpython/rev/9d5217aaea13

----------
nosy: +python-dev

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21996>
_______________________________________

From report at bugs.python.org  Fri Feb 19 19:18:58 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 20 Feb 2016 00:18:58 +0000
Subject: [docs] [issue22468] Tarfile using fstat on GZip file object
In-Reply-To: <1411462192.65.0.458428981621.issue22468@psf.upfronthosting.co.za>
Message-ID: <20160220001853.1695.39846@psf.io>


Roundup Robot added the comment:

New changeset 94a94deaf06a by Martin Panter in branch '3.5':
Issues #22468, #21996, #22208: Clarify gettarinfo() and TarInfo usage
https://hg.python.org/cpython/rev/94a94deaf06a

New changeset e66c476b25ec by Martin Panter in branch 'default':
Issue #22468: Merge gettarinfo() doc from 3.5
https://hg.python.org/cpython/rev/e66c476b25ec

New changeset 9d5217aaea13 by Martin Panter in branch '2.7':
Issues #22468, #21996, #22208: Clarify gettarinfo() and TarInfo usage
https://hg.python.org/cpython/rev/9d5217aaea13

----------
nosy: +python-dev

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22468>
_______________________________________

From report at bugs.python.org  Fri Feb 19 19:26:53 2016
From: report at bugs.python.org (Martin Panter)
Date: Sat, 20 Feb 2016 00:26:53 +0000
Subject: [docs] [issue22468] Tarfile using fstat on GZip file object
In-Reply-To: <1411462192.65.0.458428981621.issue22468@psf.upfronthosting.co.za>
Message-ID: <1455928013.33.0.946103577346.issue22468@psf.upfronthosting.co.za>


Martin Panter added the comment:

Hoping my clarification in the documentation is enough to call this fixed

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 2.7, Python 3.6 -Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22468>
_______________________________________

From report at bugs.python.org  Fri Feb 19 19:27:16 2016
From: report at bugs.python.org (Martin Panter)
Date: Sat, 20 Feb 2016 00:27:16 +0000
Subject: [docs] [issue21996] gettarinfo method does not handle files without
 text string names
In-Reply-To: <1405583528.37.0.553699872308.issue21996@psf.upfronthosting.co.za>
Message-ID: <1455928036.5.0.879278661198.issue21996@psf.upfronthosting.co.za>


Changes by Martin Panter <vadmium+py at gmail.com>:


----------
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed
versions: +Python 3.6 -Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21996>
_______________________________________

From report at bugs.python.org  Fri Feb 19 19:29:23 2016
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 20 Feb 2016 00:29:23 +0000
Subject: [docs] [issue26369] doc for unicode.decode and str.encode is
 unnecessarily confusing
In-Reply-To: <1455623938.04.0.928922751587.issue26369@psf.upfronthosting.co.za>
Message-ID: <1455928163.86.0.214801783855.issue26369@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

The intended use for str.encode is for same-type transcoding, like this:

I was unaware of the seemingly useless behavior you quote.

>>> 'abc'.encode('base64')
'YWJj\n'
>>> 'YWJj\n'.decode('base64')
'abc'

Here is a similar use for unicode.decode.

>>> u'abc'.encode('base64')
'YWJj\n'
>>> u'YWJj\n'.decode('base64')
'abc'

Any doc change should make the intended use clear if not already.

(Note that the above give lookup errors in 3.x
>>> 'abc'.encode('base64')
...
LookupError: 'base64' is not a text encoding; use codecs.encode() to handle arbitrary codecs)

----------
nosy: +terry.reedy

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26369>
_______________________________________

From report at bugs.python.org  Fri Feb 19 20:49:31 2016
From: report at bugs.python.org (Bas Wijnen)
Date: Sat, 20 Feb 2016 01:49:31 +0000
Subject: [docs] [issue13354] tcpserver should document non-threaded
 long-living connections
In-Reply-To: <1320570611.72.0.286817751979.issue13354@psf.upfronthosting.co.za>
Message-ID: <1455932971.07.0.292034759334.issue13354@psf.upfronthosting.co.za>


Bas Wijnen added the comment:

For example, I have some programs which are HTTP servers that implement WebSockets.  For regular web page requests, it is acceptable if the connection is closed after the page is sent.  But for a WebSocket it isn't: the whole point of that protocol is to allow the server to send unsolicited messages to the browser.  If the connection is closed, it cannot do that.  The documentation currently suggests that the only way to avoid handle() closing the connection is to not return.  That means that the only way to do other things is by using multi-processing or (shiver) multi-threading.

My suggestion is to add a short explanation about how connections can be kept open after handle() returns, so that a single threaded event loop can be used.  Of course the socket must then be manually closed when the program is done with it.

If I understand you correctly, overriding process_request would allow handle() to return without closing the socket.  That does sound better than overriding shutdown_request.

In the current documentation (same link as before, now for version 3.5.1), there is no mention at all about close() or shutdown() of the accepted sockets.  The only information on the subject is that if you want asynchronous handling of data, you must start a new thread or process.  This is not true, and in many cases it is not what I would recommend.  I think event loops are much easier to maintain and debug than multi-process applications, and infinitely easier than multi-threading applications.  I don't mind that other people disagree, and I'm not suggesting that those ways of handling should be removed (multi-process has its place, and I can't convince everyone that multi-threading is evil).  What I'm saying is that the ability to use an event loop to handle asynchronous data with this class deserves to be mentioned as well.

Obviously, it does then need to have the explanation about what to override to make it work.  My suggestion is simply what I ended up with after seeing it fail and reading the code.  If what you describe is the recommended way, please say that instead.  My point is that the scenario should presented as an option, I don't have an opinion on what it should say.

----------
status: pending -> open

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13354>
_______________________________________

From report at bugs.python.org  Fri Feb 19 23:49:16 2016
From: report at bugs.python.org (Martin Panter)
Date: Sat, 20 Feb 2016 04:49:16 +0000
Subject: [docs] [issue13354] tcpserver should document non-threaded
 long-living connections
In-Reply-To: <1320570611.72.0.286817751979.issue13354@psf.upfronthosting.co.za>
Message-ID: <1455943756.15.0.683571618612.issue13354@psf.upfronthosting.co.za>


Martin Panter added the comment:

Thanks for the fast response!

There is a paragraph right at the end of <https://docs.python.org/3/library/socketserver.html#server-creation-notes> that mentions this technique: ?. . . maintain an explicit table of partially finished requests . . .?. Perhaps that is the suggestion that you couldn?t find before.

I once wrote an RTSP proxy that uses a related technique. It still handles each high-level RSTP request or RTP packet synchronously, but uses the ?selectors? module to switch between the various connections and listening sockets after each high-level request had been handled. Code at <https://repo.or.cz/python-iview.git/blob/refs/heads/rtsp:/iview/utils.py#l318>.

Do you want to propose some specific additions or a patch to the documentation?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13354>
_______________________________________

From report at bugs.python.org  Sat Feb 20 01:24:20 2016
From: report at bugs.python.org (Mark Lawrence)
Date: Sat, 20 Feb 2016 06:24:20 +0000
Subject: [docs] [issue13354] tcpserver should document non-threaded
 long-living connections
In-Reply-To: <1320570611.72.0.286817751979.issue13354@psf.upfronthosting.co.za>
Message-ID: <1455949460.99.0.130282486224.issue13354@psf.upfronthosting.co.za>


Changes by Mark Lawrence <breamoreboy at yahoo.co.uk>:


----------
nosy:  -BreamoreBoy

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13354>
_______________________________________

From report at bugs.python.org  Sat Feb 20 02:45:21 2016
From: report at bugs.python.org (Martin Panter)
Date: Sat, 20 Feb 2016 07:45:21 +0000
Subject: [docs] [issue26261] NamedTemporaryFile documentation is vague about
 the `name` attribute
In-Reply-To: <1454347282.51.0.892341568817.issue26261@psf.upfronthosting.co.za>
Message-ID: <1455954321.87.0.238022530474.issue26261@psf.upfronthosting.co.za>


Martin Panter added the comment:

Here is my proposed patch.

----------
keywords: +patch
stage: needs patch -> patch review
Added file: http://bugs.python.org/file41977/tempfile-name.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26261>
_______________________________________

From report at bugs.python.org  Sat Feb 20 03:48:52 2016
From: report at bugs.python.org (Bas Wijnen)
Date: Sat, 20 Feb 2016 08:48:52 +0000
Subject: [docs] [issue13354] tcpserver should document non-threaded
 long-living connections
In-Reply-To: <1320570611.72.0.286817751979.issue13354@psf.upfronthosting.co.za>
Message-ID: <1455958132.05.0.649668055813.issue13354@psf.upfronthosting.co.za>


Bas Wijnen added the comment:

Thank you for your fast response as well.

I overlooked that paragraph indeed.  It doesn't mention anything about avoiding a socket shutdown however.  Keeping a list of requests isn't very useful if all the sockets in the list are closed. ;-)

So I would indeed suggest an addition: I would change this paragraph:

These four classes process requests synchronously; each request must be completed before the next request can be started. This isn?t suitable if each request takes a long time to complete, because it requires a lot of computation, or because it returns a lot of data which the client is slow to process. The solution is to create a separate process or thread to handle each request; the ForkingMixIn and ThreadingMixIn mix-in classes can be used to support asynchronous behaviour.

into:

By default, these four classes process requests synchronously; each request must be completed before the next request can be started. This isn?t suitable if each request takes a long time to complete, because it requires a lot of computation, or because it returns a lot of data which the client is slow to process, or because the information that should be sent to the client isn't available yet when the request is made. One possible solution is to create a separate process or thread to handle each request; the ForkingMixIn and ThreadingMixIn mix-in classes can be used to support asynchronous behaviour. Another option is to store the socket for later use, and disable the shutting down of the socket by overriding process_request with an function that only calls finish_request, and not shutdown_request. In that case, the socket must be shut down by the program when it is done with it.

At the end of the last paragraph you refer to, it should also be mentioned that the program must do something to prevent the socket from being shut down.  In the description of process_request, it would probably also be useful to add that the default implementation (as opposed to *MixIn) calls shutdown_request() after finish_request().

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13354>
_______________________________________

From report at bugs.python.org  Sat Feb 20 10:53:56 2016
From: report at bugs.python.org (Eryk Sun)
Date: Sat, 20 Feb 2016 15:53:56 +0000
Subject: [docs] [issue4928] Problem with tempfile.NamedTemporaryFile
In-Reply-To: <1231838566.25.0.143957228078.issue4928@psf.upfronthosting.co.za>
Message-ID: <1455983636.59.0.716145432887.issue4928@psf.upfronthosting.co.za>


Eryk Sun added the comment:

Maybe a note could be added to suggest using a SIGTERM signal handler (e.g. the handler could raise a SIGTERM exception):

POSIX: The file will not be deleted if the process is terminated abruptly by a signal. A process may register a SIGTERM handler to ensure that the file is deleted, but SIGKILL cannot be handled. Windows: the file will be deleted when it is closed, even if the process is terminated.

Note that for Windows it is possible to make the file permanent, but it's probably not common enough to bother with documenting this. Currently the documentation states that "[w]hether the name can be used to open the file a second time, while the named temporary file is still open, varies across platforms (it can be so used on Unix; it cannot on Windows NT or later)". Actually on Windows the file can be opened again while the named temporary file is still open. You can use an opener that calls os.open with the O_TEMPORARY flag. But the opener can also call _winapi.CreateFile with read, write, and delete sharing. If DELETE access is requested this handle can be used to make the file permanent via SetFileInformationByHandle.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, eryksun
versions: +Python 3.5, Python 3.6 -Python 3.1, Python 3.2

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue4928>
_______________________________________

From mike.clare.bellamy at gmail.com  Sun Feb 21 00:34:13 2016
From: mike.clare.bellamy at gmail.com (Mike Bellamy)
Date: Sun, 21 Feb 2016 16:34:13 +1100
Subject: [docs] LIST PROBLEM IN PYTHON 3.3
Message-ID: <CAJPm+Dd1GRh7YSriV1A8m5WXtkfem+6Ph+N2Yk07kXhZKj13gQ@mail.gmail.com>

I do not know whether to call this a BUG because it seems obviously
intended.. but totally undocumented and unexpected..

I am new to Python and this was a major problem, waste of time and gave
logic errors which were difficult to trace..

mylist = [[1,2],[3,4],[5,6],[7,8]]    # matrix or list of lists
temp = mylist[0]
mylist[3] = temp
print(mylist)

[1,2], [3,4], [5,6], [1,2]

# Now modify mylist[3]

mylist[3][1] = 0
print(mylist)

[1,0],[3,4],[5,6],[1,0]

Note mylist[0] and mylist[3] are pointers to the same data so when I
thought I was copying a list item Python did not make a true copy..
Nothing in the docs I read said anything about this..

regards
*Mike Bellamy*
*Keep Calm and Carry On*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160221/d08a45e2/attachment.html>

From report at bugs.python.org  Sun Feb 21 04:45:59 2016
From: report at bugs.python.org (Dhiraj)
Date: Sun, 21 Feb 2016 09:45:59 +0000
Subject: [docs] [issue26398] cgi.escape() Can Lead To XSS and HTMLi
 Vulnerabilities
Message-ID: <1456047959.51.0.622191858918.issue26398@psf.upfronthosting.co.za>


New submission from Dhiraj:

The Pre-defined Module cgi.escape() can lead to XSS or HTMLi
in every Version of Python.

Example :

import cgi
test = "<h1>Vulnerable</h1>"
cgi.escape(test)

Works Properly all the Charters are escape properly but ,

Example 2:

import cgi 
test2 = ' " '
cgi.escape(test2) 

Do not works Fine and the ' " ' Character is not escape properly and this may cause and XSS or HTMLi
Please find the Attachments Below (PFA)

The Python Security Expert says :

" - The behavior of the cgi.escape() function is not a bug. It works
exactly as documented in the Python documentation,
https://docs.python.org/2/library/cgi.html#cgi.escape

- By default the cgi.escape() function only escapes the three chars '<',
'>' and '&'. The double quote char '"' is not quoted unless you cann
cgi.escape() with quote=True. The default mode is suitable for
escaping blocks of text that may contain HTML."

He says that if the quote = True then its not Vulnerable.
Example :

cgi.escape('<h1>"&auml;"</h1>', quote=True)

But Many Websites Developers and many popular Companies forget to implement the
quote = True function and this may cause XSS and HTMLi
According to me there should be a Predefine value in cgi.escape() which makes 
quote = True ,  then it will not be Vulnerable.

I hope this will be patched soon and will be Updated.
Thank You (PFA)
Dhiraj Mishra
Bug

----------
assignee: docs at python
components: Documentation
files: CGI.ESCAPE_2.png
messages: 260600
nosy: DhirajMishra, docs at python
priority: normal
severity: normal
status: open
title: cgi.escape() Can Lead To XSS and HTMLi Vulnerabilities
versions: Python 3.6
Added file: http://bugs.python.org/file41982/CGI.ESCAPE_2.png

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26398>
_______________________________________

From report at bugs.python.org  Sun Feb 21 05:09:30 2016
From: report at bugs.python.org (Martin Panter)
Date: Sun, 21 Feb 2016 10:09:30 +0000
Subject: [docs] [issue26398] cgi.escape() Can Lead To XSS and HTML
 Vulnerabilities
In-Reply-To: <1456047959.51.0.622191858918.issue26398@psf.upfronthosting.co.za>
Message-ID: <1456049370.23.0.726389892083.issue26398@psf.upfronthosting.co.za>


Martin Panter added the comment:

The Python 3 documentation <https://docs.python.org/3/library/cgi.html#cgi.escape> says this is deprecated in favour of html.escape(), which by default has quote=True. AFAIK there is no equivalent in Python 2. See Issue 2830 for the addition of html.escape(), and also Issue 9061 about cgi.escape() introducing vulnerabilities.

----------
nosy: +martin.panter
title: cgi.escape() Can Lead To XSS and HTMLi Vulnerabilities -> cgi.escape() Can Lead To XSS and HTML Vulnerabilities

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26398>
_______________________________________

From report at bugs.python.org  Sun Feb 21 05:58:12 2016
From: report at bugs.python.org (Manvi B)
Date: Sun, 21 Feb 2016 10:58:12 +0000
Subject: [docs] [issue26247] Document Chrome/Chromium for python2.7
In-Reply-To: <1454250201.34.0.379638558981.issue26247@psf.upfronthosting.co.za>
Message-ID: <1456052292.28.0.400462908406.issue26247@psf.upfronthosting.co.za>


Manvi B added the comment:

We (Elena Oat and I) tried to open web browser Chrome/Chromium in versions 2.7, 3.3, 3.5 and 3.6. It seems working and so updated in the table for version 2.7. The patch issue26247.diff is submitted.

----------
keywords: +patch
nosy: +Manvi B
Added file: http://bugs.python.org/file41983/issue26247.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26247>
_______________________________________

From report at bugs.python.org  Sun Feb 21 06:05:30 2016
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 21 Feb 2016 11:05:30 +0000
Subject: [docs] [issue26247] Document Chrome/Chromium for python2.7
In-Reply-To: <1454250201.34.0.379638558981.issue26247@psf.upfronthosting.co.za>
Message-ID: <1456052730.78.0.946678522968.issue26247@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Thanks for the patch, however since this is for the 2.7 branch, it should only say in which 2.7.x version this has been added.  The note should also use the .. versionadded:: directive.
All minor releases are tagged in the repo, so you can try to update the repo to each 2.7.x version and check in which one chrome support has been introduced.

----------
nosy: +ezio.melotti
stage:  -> needs patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26247>
_______________________________________

From report at bugs.python.org  Sun Feb 21 07:31:25 2016
From: report at bugs.python.org (Dhiraj)
Date: Sun, 21 Feb 2016 12:31:25 +0000
Subject: [docs] [issue26398] cgi.escape() Can Lead To XSS and HTML
 Vulnerabilities
In-Reply-To: <1456047959.51.0.622191858918.issue26398@psf.upfronthosting.co.za>
Message-ID: <1456057885.46.0.350942149443.issue26398@psf.upfronthosting.co.za>


Dhiraj added the comment:

Hello @martin.panter okay But still the module cgi.escape() Vulnerable  if the Python Docs have created a new html.escape so you might remove the cgi.escape() or Implement the quote = True in cgi.escape()  Predefine as its in html.escape because Developer mostly use CGI. 
Its an Humble request , I hope I did well.

Thank You martin.panter

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26398>
_______________________________________

From report at bugs.python.org  Sun Feb 21 10:35:43 2016
From: report at bugs.python.org (=?utf-8?b?UmHDumwgTsO6w7FleiBkZSBBcmVuYXM=?=)
Date: Sun, 21 Feb 2016 15:35:43 +0000
Subject: [docs] [issue26401] Error in documentation for "compile" built-in
 function
Message-ID: <1456068943.64.0.547733660691.issue26401@psf.upfronthosting.co.za>


New submission from Ra?l N??ez de Arenas:

According to the documentation, if the 'compile' built-in function encounters NUL bytes in the compiled source, it raises TypeError, but this is not true:

>>> source = '\u0000'
>>> compile(source, '', 'single')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: source code string cannot contain null bytes

It raises ValueError, not TypeError. And IMHO, it's the proper exception to raise...

----------
assignee: docs at python
components: Documentation
messages: 260613
nosy: Ra?l N??ez de Arenas, docs at python
priority: normal
severity: normal
status: open
title: Error in documentation for "compile" built-in function
type: enhancement
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26401>
_______________________________________

From report at bugs.python.org  Sun Feb 21 10:47:32 2016
From: report at bugs.python.org (SilentGhost)
Date: Sun, 21 Feb 2016 15:47:32 +0000
Subject: [docs] [issue26401] Error in documentation for "compile" built-in
 function
In-Reply-To: <1456068943.64.0.547733660691.issue26401@psf.upfronthosting.co.za>
Message-ID: <1456069652.57.0.283503157531.issue26401@psf.upfronthosting.co.za>


SilentGhost added the comment:

Here is the patch.

----------
keywords: +patch
nosy: +SilentGhost
versions: +Python 3.6
Added file: http://bugs.python.org/file41985/issue26401.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26401>
_______________________________________

From report at bugs.python.org  Sun Feb 21 12:29:42 2016
From: report at bugs.python.org (Christian Heimes)
Date: Sun, 21 Feb 2016 17:29:42 +0000
Subject: [docs] [issue26398] cgi.escape() Can Lead To XSS and HTML
 Vulnerabilities
In-Reply-To: <1456047959.51.0.622191858918.issue26398@psf.upfronthosting.co.za>
Message-ID: <1456075782.16.0.441029049588.issue26398@psf.upfronthosting.co.za>


Changes by Christian Heimes <lists at cheimes.de>:


----------
nosy: +christian.heimes

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26398>
_______________________________________

From report at bugs.python.org  Sun Feb 21 12:58:19 2016
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 21 Feb 2016 17:58:19 +0000
Subject: [docs] [issue26401] Error in documentation for "compile" built-in
 function
In-Reply-To: <1456068943.64.0.547733660691.issue26401@psf.upfronthosting.co.za>
Message-ID: <1456077499.0.0.0751303399988.issue26401@psf.upfronthosting.co.za>


Berker Peksag added the comment:

It would be good to add a versionchanged note. Something like:

   .. versionchanged:: 3.5
      Previously, a :exc:`TypeError` was raised [...]

----------
nosy: +berker.peksag
stage:  -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26401>
_______________________________________

From report at bugs.python.org  Sun Feb 21 13:00:22 2016
From: report at bugs.python.org (=?utf-8?b?UmHDumwgTsO6w7FleiBkZSBBcmVuYXM=?=)
Date: Sun, 21 Feb 2016 18:00:22 +0000
Subject: [docs] [issue26401] Error in documentation for "compile" built-in
 function
In-Reply-To: <1456068943.64.0.547733660691.issue26401@psf.upfronthosting.co.za>
Message-ID: <1456077622.47.0.314986781158.issue26401@psf.upfronthosting.co.za>


Ra?l N??ez de Arenas added the comment:

I checked the sources at github and the change was introduced back in 2010, if I recall correctly, so maybe this change happened in 3.2? I can check again and try to determine the exact date and if at all possible the version.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26401>
_______________________________________

From report at bugs.python.org  Sun Feb 21 13:11:08 2016
From: report at bugs.python.org (SilentGhost)
Date: Sun, 21 Feb 2016 18:11:08 +0000
Subject: [docs] [issue26401] Error in documentation for "compile" built-in
 function
In-Reply-To: <1456068943.64.0.547733660691.issue26401@psf.upfronthosting.co.za>
Message-ID: <1456078268.84.0.763090541833.issue26401@psf.upfronthosting.co.za>


SilentGhost added the comment:

TypeError is raised in 3.4

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26401>
_______________________________________

From report at bugs.python.org  Sun Feb 21 13:18:22 2016
From: report at bugs.python.org (=?utf-8?b?UmHDumwgTsO6w7FleiBkZSBBcmVuYXM=?=)
Date: Sun, 21 Feb 2016 18:18:22 +0000
Subject: [docs] [issue26401] Error in documentation for "compile" built-in
 function
In-Reply-To: <1456068943.64.0.547733660691.issue26401@psf.upfronthosting.co.za>
Message-ID: <1456078702.9.0.0309708187448.issue26401@psf.upfronthosting.co.za>


Ra?l N??ez de Arenas added the comment:

I checked the Mercurial repository directly, and the change was introduced in 2014: http://bugs.python.org/issue22215

So, yes, looks like a 3.5 change and the versionchanged note suggested by Berker is a great idea!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26401>
_______________________________________

From report at bugs.python.org  Sun Feb 21 13:31:53 2016
From: report at bugs.python.org (SilentGhost)
Date: Sun, 21 Feb 2016 18:31:53 +0000
Subject: [docs] [issue26401] Error in documentation for "compile" built-in
 function
In-Reply-To: <1456068943.64.0.547733660691.issue26401@psf.upfronthosting.co.za>
Message-ID: <1456079513.9.0.300220648491.issue26401@psf.upfronthosting.co.za>


SilentGhost added the comment:

Updated patch.

----------
Added file: http://bugs.python.org/file41989/issue26401_2.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26401>
_______________________________________

From report at bugs.python.org  Sun Feb 21 15:00:24 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 21 Feb 2016 20:00:24 +0000
Subject: [docs] [issue26401] Error in documentation for "compile" built-in
 function
In-Reply-To: <1456068943.64.0.547733660691.issue26401@psf.upfronthosting.co.za>
Message-ID: <20160221200019.1711.21854@psf.io>


Roundup Robot added the comment:

New changeset 0cfac9efd895 by Berker Peksag in branch '3.5':
Issue #26401: Fix compile() documentation
https://hg.python.org/cpython/rev/0cfac9efd895

New changeset 45cf82f424ce by Berker Peksag in branch 'default':
Issue #26401: Fix compile() documentation
https://hg.python.org/cpython/rev/45cf82f424ce

----------
nosy: +python-dev

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26401>
_______________________________________

From report at bugs.python.org  Sun Feb 21 15:01:40 2016
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 21 Feb 2016 20:01:40 +0000
Subject: [docs] [issue26401] Error in documentation for "compile" built-in
 function
In-Reply-To: <1456068943.64.0.547733660691.issue26401@psf.upfronthosting.co.za>
Message-ID: <1456084900.76.0.33407698667.issue26401@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26401>
_______________________________________

From report at bugs.python.org  Sun Feb 21 15:17:03 2016
From: report at bugs.python.org (=?utf-8?b?UmHDumwgTsO6w7FleiBkZSBBcmVuYXM=?=)
Date: Sun, 21 Feb 2016 20:17:03 +0000
Subject: [docs] [issue26401] Error in documentation for "compile" built-in
 function
In-Reply-To: <1456068943.64.0.547733660691.issue26401@psf.upfronthosting.co.za>
Message-ID: <1456085823.77.0.60099866361.issue26401@psf.upfronthosting.co.za>


Ra?l N??ez de Arenas added the comment:

Thanks to you, Berker, and SilentGhost, for applying and preparing the patch!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26401>
_______________________________________

From report at bugs.python.org  Sun Feb 21 16:56:51 2016
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 21 Feb 2016 21:56:51 +0000
Subject: [docs] [issue26398] cgi.escape() Can Lead To XSS and HTML
 Vulnerabilities
In-Reply-To: <1456047959.51.0.622191858918.issue26398@psf.upfronthosting.co.za>
Message-ID: <1456091811.54.0.957420532526.issue26398@psf.upfronthosting.co.za>


Georg Brandl added the comment:

I don't think there is anything to be done here. cgi.escape() is documented properly, deprecated in Python 3.x, and changing its implementation is not really an option now.

----------
nosy: +georg.brandl

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26398>
_______________________________________

From report at bugs.python.org  Sun Feb 21 22:06:39 2016
From: report at bugs.python.org (Dhiraj)
Date: Mon, 22 Feb 2016 03:06:39 +0000
Subject: [docs] [issue26398] cgi.escape() Can Lead To XSS and HTML
 Vulnerabilities
In-Reply-To: <1456047959.51.0.622191858918.issue26398@psf.upfronthosting.co.za>
Message-ID: <1456110399.46.0.324092653289.issue26398@psf.upfronthosting.co.za>


Dhiraj added the comment:

Hello @Georg Brandl PFA you'll be happy to find that python3.x is still vulnerable to cgi.escape() the module is not able to escape some values and can lead to XSS also.
As @Martin Panter said now cgi.escape() is been replaced to html.escape()
so accordingly cgi.escape() should have a Pr-define value " quote = True "
which is not there in any Version of Python3.x or the module should be removed because we have html.escape() , Because many People still use's CGI in Web-Application.

Thank You

----------
Added file: http://bugs.python.org/file41996/cgi.escape_Dhiraj_Mishra.png

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26398>
_______________________________________

From report at bugs.python.org  Mon Feb 22 04:46:47 2016
From: report at bugs.python.org (Martin Panter)
Date: Mon, 22 Feb 2016 09:46:47 +0000
Subject: [docs] [issue26390] hashlib's pbkdf2_hmac documentation "rounds"
 does not match source
In-Reply-To: <1455840057.88.0.0946194046166.issue26390@psf.upfronthosting.co.za>
Message-ID: <1456134407.44.0.209962351133.issue26390@psf.upfronthosting.co.za>


Martin Panter added the comment:

Here is an updated patch. I also fixed the hash_name parameter, some more minor offences in the documentation, and added a test case.

----------
Added file: http://bugs.python.org/file42002/pbkdf2_6.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26390>
_______________________________________

From report at bugs.python.org  Mon Feb 22 05:12:13 2016
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 22 Feb 2016 10:12:13 +0000
Subject: [docs] [issue26261] NamedTemporaryFile documentation is vague about
 the `name` attribute
In-Reply-To: <1454347282.51.0.892341568817.issue26261@psf.upfronthosting.co.za>
Message-ID: <20160222101210.1985.51807@psf.io>


Roundup Robot added the comment:

New changeset f1982e1426ce by Martin Panter in branch '3.5':
Issue #26261: Clarify NamedTemporaryFile name attribute vs file.name
https://hg.python.org/cpython/rev/f1982e1426ce

New changeset 837bae8c8ae7 by Martin Panter in branch 'default':
Issue #26261: Merge NamedTemporaryFile docs from 3.5
https://hg.python.org/cpython/rev/837bae8c8ae7

New changeset 27a140558a47 by Martin Panter in branch '2.7':
Issue #26261: Clarify NamedTemporaryFile name attribute vs file.name
https://hg.python.org/cpython/rev/27a140558a47

----------
nosy: +python-dev

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26261>
_______________________________________

From report at bugs.python.org  Mon Feb 22 05:55:43 2016
From: report at bugs.python.org (Martin Panter)
Date: Mon, 22 Feb 2016 10:55:43 +0000
Subject: [docs] [issue26261] NamedTemporaryFile documentation is vague about
 the `name` attribute
In-Reply-To: <1454347282.51.0.892341568817.issue26261@psf.upfronthosting.co.za>
Message-ID: <1456138543.19.0.893958436835.issue26261@psf.upfronthosting.co.za>


Changes by Martin Panter <vadmium+py at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26261>
_______________________________________

From report at bugs.python.org  Mon Feb 22 08:24:39 2016
From: report at bugs.python.org (thefourtheye)
Date: Mon, 22 Feb 2016 13:24:39 +0000
Subject: [docs] [issue26408] pep-8 requires few corrections
Message-ID: <1456147479.45.0.358658656612.issue26408@psf.upfronthosting.co.za>


New submission from thefourtheye:

1. It doesn't have the Reference 4 used anywhere in the doc.

2. The `if` condition is not properly ended in the Programming Recommendation section.

3. Apart from that few grammatical changes are necessary I believe.

----------
assignee: docs at python
components: Documentation
files: mywork.patch
keywords: patch
messages: 260676
nosy: docs at python, thefourtheye
priority: normal
severity: normal
status: open
title: pep-8 requires few corrections
type: enhancement
Added file: http://bugs.python.org/file42005/mywork.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26408>
_______________________________________

From report at bugs.python.org  Mon Feb 22 08:35:56 2016
From: report at bugs.python.org (thefourtheye)
Date: Mon, 22 Feb 2016 13:35:56 +0000
Subject: [docs] [issue26408] pep-8 requires a few corrections
In-Reply-To: <1456147479.45.0.358658656612.issue26408@psf.upfronthosting.co.za>
Message-ID: <1456148156.7.0.433775810061.issue26408@psf.upfronthosting.co.za>


Changes by thefourtheye <thechargingvolcano at gmail.com>:


----------
title: pep-8 requires few corrections -> pep-8 requires a few corrections

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26408>
_______________________________________

From report at bugs.python.org  Mon Feb 22 08:43:37 2016
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 22 Feb 2016 13:43:37 +0000
Subject: [docs] [issue26408] pep-8 requires a few corrections
In-Reply-To: <1456147479.45.0.358658656612.issue26408@psf.upfronthosting.co.za>
Message-ID: <1456148617.33.0.561447391948.issue26408@psf.upfronthosting.co.za>


Georg Brandl added the comment:

I can't really comment on the grammar changes, but the rest looks good to me.

This is not very smooth, in both versions:

-Consistency within one module or function is most important.
+Consistency within one module or function is the most important thing.
 
-But most importantly: know when to be inconsistent -- sometimes the
-style guide just doesn't apply.  When in doubt, use your best
+But more importantly: know when to be inconsistent -- sometimes the
+style guide just isn't applicable.  When in doubt, use your best

(Consistency is already *most* important, but then comes something *more* important?)

----------
nosy: +georg.brandl

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26408>
_______________________________________

From report at bugs.python.org  Mon Feb 22 08:58:04 2016
From: report at bugs.python.org (Barry A. Warsaw)
Date: Mon, 22 Feb 2016 13:58:04 +0000
Subject: [docs] [issue26408] pep-8 requires a few corrections
In-Reply-To: <1456147479.45.0.358658656612.issue26408@psf.upfronthosting.co.za>
Message-ID: <1456149484.4.0.523247400838.issue26408@psf.upfronthosting.co.za>


Changes by Barry A. Warsaw <barry at python.org>:


----------
nosy: +barry

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26408>
_______________________________________

From report at bugs.python.org  Mon Feb 22 09:02:47 2016
From: report at bugs.python.org (Barry A. Warsaw)
Date: Mon, 22 Feb 2016 14:02:47 +0000
Subject: [docs] [issue26408] pep-8 requires a few corrections
In-Reply-To: <1456147479.45.0.358658656612.issue26408@psf.upfronthosting.co.za>
Message-ID: <1456149767.33.0.414485273893.issue26408@psf.upfronthosting.co.za>


Changes by Barry A. Warsaw <barry at python.org>:


----------
assignee: docs at python -> barry

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26408>
_______________________________________

From report at bugs.python.org  Mon Feb 22 09:03:04 2016
From: report at bugs.python.org (Barry A. Warsaw)
Date: Mon, 22 Feb 2016 14:03:04 +0000
Subject: [docs] [issue26408] pep-8 requires a few corrections
In-Reply-To: <1456147479.45.0.358658656612.issue26408@psf.upfronthosting.co.za>
Message-ID: <1456149784.09.0.126121444271.issue26408@psf.upfronthosting.co.za>


Barry A. Warsaw added the comment:

Thanks!  I like some of the changes, and may tweak a few others.  Thanks for the contribution.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26408>
_______________________________________

From report at bugs.python.org  Mon Feb 22 09:05:52 2016
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 22 Feb 2016 14:05:52 +0000
Subject: [docs] [issue26408] pep-8 requires a few corrections
In-Reply-To: <1456147479.45.0.358658656612.issue26408@psf.upfronthosting.co.za>
Message-ID: <20160222140549.2200.26657@psf.io>


Roundup Robot added the comment:

New changeset 43d612fc6b12 by Barry Warsaw in branch 'default':
Gramatical and other improvements given by thefourtheye.
https://hg.python.org/peps/rev/43d612fc6b12

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26408>
_______________________________________

From report at bugs.python.org  Mon Feb 22 09:20:48 2016
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 22 Feb 2016 14:20:48 +0000
Subject: [docs] [issue26408] pep-8 requires a few corrections
In-Reply-To: <1456147479.45.0.358658656612.issue26408@psf.upfronthosting.co.za>
Message-ID: <1456150848.11.0.582401983242.issue26408@psf.upfronthosting.co.za>


Georg Brandl added the comment:

-Consistency within one module or function is most important.
+Consistency within one module or function is the most important.

You left out "thing" from the patch; is that intended?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26408>
_______________________________________

From report at bugs.python.org  Mon Feb 22 10:11:34 2016
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 22 Feb 2016 15:11:34 +0000
Subject: [docs] [issue25080] The example-code for making XML-RPC requests
 through proxy, fail!
In-Reply-To: <1442059715.67.0.31958758043.issue25080@psf.upfronthosting.co.za>
Message-ID: <1456153894.48.0.806598233289.issue25080@psf.upfronthosting.co.za>


Berker Peksag added the comment:

This has been fixed in cf842a8ccb77. Thank you for reporting this, Kostis!

----------
nosy: +berker.peksag
resolution:  -> out of date
stage: needs patch -> resolved
status: open -> closed
versions:  -Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25080>
_______________________________________

From report at bugs.python.org  Mon Feb 22 11:29:09 2016
From: report at bugs.python.org (Barry A. Warsaw)
Date: Mon, 22 Feb 2016 16:29:09 +0000
Subject: [docs] [issue26408] pep-8 requires a few corrections
In-Reply-To: <1456150848.11.0.582401983242.issue26408@psf.upfronthosting.co.za>
Message-ID: <20160222112905.3a97be83@subdivisions.wooz.org>


Barry A. Warsaw added the comment:

On Feb 22, 2016, at 02:20 PM, Georg Brandl wrote:

>Georg Brandl added the comment:
>
>-Consistency within one module or function is most important.
>+Consistency within one module or function is the most important.
>
>You left out "thing" from the patch; is that intended?

Yes.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26408>
_______________________________________

From report at bugs.python.org  Mon Feb 22 12:42:35 2016
From: report at bugs.python.org (SilentGhost)
Date: Mon, 22 Feb 2016 17:42:35 +0000
Subject: [docs] [issue25910] Fixing links in documentation
In-Reply-To: <1450530544.1.0.9187941337.issue25910@psf.upfronthosting.co.za>
Message-ID: <1456162955.47.0.665166011893.issue25910@psf.upfronthosting.co.za>


Changes by SilentGhost <ghost.adh at gmail.com>:


----------
status: open -> languishing

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25910>
_______________________________________

From report at bugs.python.org  Mon Feb 22 17:16:11 2016
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Mon, 22 Feb 2016 22:16:11 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdIG92ZXIg4oCcLi4gdmVyc2lvbmNoYW5nZWTigJ0gd2hlcmUgYXBwcm9w?=
 =?utf-8?q?riate?=
In-Reply-To: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
Message-ID: <1456179371.42.0.264638558569.issue26366@psf.upfronthosting.co.za>


Fred L. Drake, Jr. added the comment:

If no one is planning to propose specific new markup for more fine-grained version annotations, this issue can be closed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From report at bugs.python.org  Mon Feb 22 20:49:25 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 23 Feb 2016 01:49:25 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdIG92ZXIg4oCcLi4gdmVyc2lvbmNoYW5nZWTigJ0gd2hlcmUgYXBwcm9w?=
 =?utf-8?q?riate?=
In-Reply-To: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
Message-ID: <1456192165.41.0.931204587166.issue26366@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Fred, thanks for chiming in.  Let's do close this one.

----------
nosy: +rhettinger
resolution:  -> not a bug
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From report at bugs.python.org  Mon Feb 22 23:32:57 2016
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Tue, 23 Feb 2016 04:32:57 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMjYzNjZdIFVzZSDigJwuLiB2ZXJzaW9uYWRkZWQ=?=
 =?utf-8?b?4oCdIG92ZXIg4oCcLi4gdmVyc2lvbmNoYW5nZWTigJ0gd2hlcmUgYXBwcm9w?=
 =?utf-8?q?riate?=
In-Reply-To: <1455551359.29.0.702516130467.issue26366@psf.upfronthosting.co.za>
Message-ID: <1456201977.04.0.943145615865.issue26366@psf.upfronthosting.co.za>


Fred L. Drake, Jr. added the comment:

For anyone following along only via the tracker, it's worth noting that proposals for new markup are welcome on the docs mailing list.  More information is available at:

    https://mail.python.org/mailman/listinfo/docs

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26366>
_______________________________________

From report at bugs.python.org  Tue Feb 23 08:06:53 2016
From: report at bugs.python.org (Dhiraj)
Date: Tue, 23 Feb 2016 13:06:53 +0000
Subject: [docs] [issue26398] cgi.escape() Can Lead To XSS and HTML
 Vulnerabilities
In-Reply-To: <1456047959.51.0.622191858918.issue26398@psf.upfronthosting.co.za>
Message-ID: <1456232813.61.0.618916582492.issue26398@psf.upfronthosting.co.za>


Dhiraj added the comment:

Even the IDLE of Python is Vulnerable to CGI.ESCAPE() Please have a look on attachments , I hope this would be Patch Soon.

Thank You

----------
nosy: +dstufft, gregory.p.smith
type:  -> security
Added file: http://bugs.python.org/file42013/Python-IDLE-CGI-Vulnerable.png

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26398>
_______________________________________

From james.stokes at electricnail.com  Mon Feb 22 13:20:13 2016
From: james.stokes at electricnail.com (James Stokes)
Date: Mon, 22 Feb 2016 10:20:13 -0800
Subject: [docs] typo in 3.5.1 Macintosh doc
Message-ID: <CAH67ZzOsThztOpEHbM+4FDabOfBD_XNkUeL+whUbK9SWUGesuA@mail.gmail.com>

In docs.python.org/3.5/using/Mac.html, the line 'A MacPython 3.4 folder in
your Applications folder' should be updated to '3.5'.

Thanks for all the great work you guys are doing to bring Python to the
world.

James S.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160222/e6dd7125/attachment.html>

From report at bugs.python.org  Tue Feb 23 12:41:45 2016
From: report at bugs.python.org (Gregory P. Smith)
Date: Tue, 23 Feb 2016 17:41:45 +0000
Subject: [docs] [issue26398] cgi.escape() Can Lead To XSS and HTML
 Vulnerabilities
In-Reply-To: <1456047959.51.0.622191858918.issue26398@psf.upfronthosting.co.za>
Message-ID: <1456249305.4.0.543853713874.issue26398@psf.upfronthosting.co.za>


Gregory P. Smith added the comment:

As pointed out, this is working as intended and is documented as such.  That it isn't what you want is why Python 3 has html.escape() instead.

----------
resolution:  -> duplicate
status: open -> closed
superseder:  -> cgi.escape Can Lead To XSS Vulnerabilities
versions: +Python 2.7, Python 3.4, Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26398>
_______________________________________

From report at bugs.python.org  Tue Feb 23 12:45:03 2016
From: report at bugs.python.org (Dhiraj)
Date: Tue, 23 Feb 2016 17:45:03 +0000
Subject: [docs] [issue26398] cgi.escape() Can Lead To XSS and HTML
 Vulnerabilities
In-Reply-To: <1456047959.51.0.622191858918.issue26398@psf.upfronthosting.co.za>
Message-ID: <1456249503.39.0.273354151779.issue26398@psf.upfronthosting.co.za>


Changes by Dhiraj <mishra.dhiraj95 at gmail.com>:


----------
resolution: duplicate -> fixed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26398>
_______________________________________

From report at bugs.python.org  Tue Feb 23 20:19:15 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 24 Feb 2016 01:19:15 +0000
Subject: [docs] [issue22088] base64 module still ignores non-alphabet
 characters
In-Reply-To: <1406414649.83.0.15731376973.issue22088@psf.upfronthosting.co.za>
Message-ID: <20160224011907.1640.75414@psf.io>


Roundup Robot added the comment:

New changeset c62526580ff0 by Martin Panter in branch '2.7':
Issue #22088: Clarify base-64 alphabets and which characters are discarded
https://hg.python.org/cpython/rev/c62526580ff0

New changeset c8933fbc9171 by Martin Panter in branch '3.5':
Issue #22088: Clarify base-64 alphabets and which characters are discarded
https://hg.python.org/cpython/rev/c8933fbc9171

New changeset 5ad27dcd5a97 by Martin Panter in branch 'default':
Issue #22088: Merge base64 docs from 3.5
https://hg.python.org/cpython/rev/5ad27dcd5a97

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22088>
_______________________________________

From report at bugs.python.org  Tue Feb 23 20:59:58 2016
From: report at bugs.python.org (Martin Panter)
Date: Wed, 24 Feb 2016 01:59:58 +0000
Subject: [docs] [issue22088] base64 module still ignores non-alphabet
 characters
In-Reply-To: <1406414649.83.0.15731376973.issue22088@psf.upfronthosting.co.za>
Message-ID: <1456279198.44.0.0287753213471.issue22088@psf.upfronthosting.co.za>


Changes by Martin Panter <vadmium+py at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22088>
_______________________________________

From report at bugs.python.org  Wed Feb 24 01:30:20 2016
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 24 Feb 2016 06:30:20 +0000
Subject: [docs] [issue5824] SocketServer.DatagramRequestHandler Broken under
 Linux
In-Reply-To: <1240525238.53.0.858571250541.issue5824@psf.upfronthosting.co.za>
Message-ID: <20160224063016.1958.69012@psf.io>


Roundup Robot added the comment:

New changeset 92ae4a305858 by Martin Panter in branch '2.7':
Issue #5824: Fix DatagramRequestHandler tests by binding the client socket
https://hg.python.org/cpython/rev/92ae4a305858

New changeset 0d9d8fdd9736 by Martin Panter in branch '3.5':
Issue #5824: Fix DatagramRequestHandler tests by binding the client socket
https://hg.python.org/cpython/rev/0d9d8fdd9736

New changeset 113e9c6fd64d by Martin Panter in branch 'default':
Issue #5824: Merge socketserver tests from 3.5
https://hg.python.org/cpython/rev/113e9c6fd64d

----------
nosy: +python-dev

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5824>
_______________________________________

From report at bugs.python.org  Wed Feb 24 03:44:22 2016
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 24 Feb 2016 08:44:22 +0000
Subject: [docs] [issue16823] Python quits on running tkinter code with
 threads
In-Reply-To: <1356924189.65.0.303016065786.issue16823@psf.upfronthosting.co.za>
Message-ID: <1456303462.37.0.0988085694897.issue16823@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

I don't know. I'm unable to reproduce the bug on Linux.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16823>
_______________________________________

From fatih91us at yahoo.de  Tue Feb 23 10:21:34 2016
From: fatih91us at yahoo.de (Prof.Dr.Mehmet ERDAS)
Date: Tue, 23 Feb 2016 15:21:34 +0000 (UTC)
Subject: [docs] How to Guide Python
References: <452375150.1305248.1456240894474.JavaMail.yahoo.ref@mail.yahoo.com>
Message-ID: <452375150.1305248.1456240894474.JavaMail.yahoo@mail.yahoo.com>

I am a beginner starting tolearn python programming Can you send me the python guide and samples?Kind regards/Mit freundlichen Gr?ssen.

Mehmet Erdas? B.Sc.M.Sc. MBA Ph.D. TU Braunschweig Lower Saxony METU TU Vienna
fatih91us at yahoo.de
erdasmehmet23 at gmail.com
Mobile: +49 (0)1789035440
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160223/6456f0ef/attachment-0001.html>

From mail at timgolden.me.uk  Wed Feb 24 08:11:35 2016
From: mail at timgolden.me.uk (Tim Golden)
Date: Wed, 24 Feb 2016 13:11:35 +0000
Subject: [docs] How to Guide Python
In-Reply-To: <452375150.1305248.1456240894474.JavaMail.yahoo@mail.yahoo.com>
References: <452375150.1305248.1456240894474.JavaMail.yahoo.ref@mail.yahoo.com>
 <452375150.1305248.1456240894474.JavaMail.yahoo@mail.yahoo.com>
Message-ID: <56CDAC07.7060102@timgolden.me.uk>

https://docs.python.org/3.5/tutorial/

TJG

On 23/02/2016 15:21, Prof.Dr.Mehmet ERDAS wrote:
> I am a beginner starting tolearn python programming Can you send me the
> python guide and samples
>  
> Kind regards/Mit freundlichen Gr?ssen.
> 
> Mehmet Erdas  B.Sc.M.Sc <http://b.sc.m.sc/>. MBA Ph.D. TU Braunschweig
> Lower Saxony METU TU Vienna
> fatih91us at yahoo.de <mailto:fatih91us at yahoo.de>
> erdasmehmet23 at gmail.com <mailto:erdasmehmet23 at gmail.com>
> Mobile: +49 (0)1789035440
> 
> 
> _______________________________________________
> docs mailing list
> docs at python.org
> https://mail.python.org/mailman/listinfo/docs
> 


From report at bugs.python.org  Wed Feb 24 08:37:42 2016
From: report at bugs.python.org (Jakub Wilk)
Date: Wed, 24 Feb 2016 13:37:42 +0000
Subject: [docs] [issue26426] email examples: incorrect use of
 email.headerregistry.Address
Message-ID: <1456321062.13.0.278509193885.issue26426@psf.upfronthosting.co.za>


New submission from Jakub Wilk:

https://docs.python.org/3/library/email-examples.html#examples-using-the-provisional-api contains the following code:

from email.headerregistry import Address
...
msg['From'] = Address("Pep? Le Pew", "pepe at example.com")
msg['To'] = (Address("Penelope Pussycat", "penelope at example.com"),
             Address("Fabrette Pussycat", "fabrette at example.com"))

But Address takes just the username, not the whole email address, as the second argument. So this should be written as:

msg['From'] = Address("Pep? Le Pew", "pepe", "example.com")
...

or:

msg['From'] = Address("Pep? Le Pew", addr_spec="pepe at example.com")
...

----------
assignee: docs at python
components: Documentation
messages: 260796
nosy: docs at python, jwilk
priority: normal
severity: normal
status: open
title: email examples: incorrect use of email.headerregistry.Address

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26426>
_______________________________________

From report at bugs.python.org  Wed Feb 24 08:45:47 2016
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 24 Feb 2016 13:45:47 +0000
Subject: [docs] [issue26426] email examples: incorrect use of
 email.headerregistry.Address
In-Reply-To: <1456321062.13.0.278509193885.issue26426@psf.upfronthosting.co.za>
Message-ID: <1456321547.6.0.55578810816.issue26426@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the report. This is a duplicate of issue 26176. Would you like to send a patch?

----------
nosy: +berker.peksag
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> EmailMessage example doesn't work

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26426>
_______________________________________

From report at bugs.python.org  Wed Feb 24 08:53:53 2016
From: report at bugs.python.org (Barry A. Warsaw)
Date: Wed, 24 Feb 2016 13:53:53 +0000
Subject: [docs] [issue26426] email examples: incorrect use of
 email.headerregistry.Address
In-Reply-To: <1456321062.13.0.278509193885.issue26426@psf.upfronthosting.co.za>
Message-ID: <1456322033.67.0.184447730724.issue26426@psf.upfronthosting.co.za>


Changes by Barry A. Warsaw <barry at python.org>:


----------
nosy: +barry

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26426>
_______________________________________

From report at bugs.python.org  Wed Feb 24 08:54:05 2016
From: report at bugs.python.org (Barry A. Warsaw)
Date: Wed, 24 Feb 2016 13:54:05 +0000
Subject: [docs] [issue26176] EmailMessage example doesn't work
In-Reply-To: <1453427916.73.0.91814079944.issue26176@psf.upfronthosting.co.za>
Message-ID: <1456322045.75.0.083950326775.issue26176@psf.upfronthosting.co.za>


Changes by Barry A. Warsaw <barry at python.org>:


----------
nosy: +barry

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26176>
_______________________________________

From report at bugs.python.org  Wed Feb 24 15:32:43 2016
From: report at bugs.python.org (Martin Panter)
Date: Wed, 24 Feb 2016 20:32:43 +0000
Subject: [docs] [issue5824] SocketServer.DatagramRequestHandler Broken under
 Linux
In-Reply-To: <1240525238.53.0.858571250541.issue5824@psf.upfronthosting.co.za>
Message-ID: <1456345963.07.0.580806403025.issue5824@psf.upfronthosting.co.za>


Changes by Martin Panter <vadmium+py at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5824>
_______________________________________

From report at bugs.python.org  Thu Feb 25 04:48:39 2016
From: report at bugs.python.org (=?utf-8?q?Thomas_G=C3=BCttler?=)
Date: Thu, 25 Feb 2016 09:48:39 +0000
Subject: [docs] [issue26433] urllib.urlencode() does not explain how to
 handle unicode
Message-ID: <1456393719.44.0.187138588042.issue26433@psf.upfronthosting.co.za>


New submission from Thomas G?ttler:

The current docs for Python2, don't explain how to handle unicode:

https://docs.python.org/2/library/urllib.html#urllib.urlencode

It seems to be a common problem. See http://stackoverflow.com/questions/6480723/urllib-urlencode-doesnt-like-unicode-values-how-about-this-workaround

It would be nice to document the most pythonic way to handle unicode in urllib.urlencode()

----------
assignee: docs at python
components: Documentation
messages: 260845
nosy: Thomas G?ttler, docs at python
priority: normal
severity: normal
status: open
title: urllib.urlencode() does not explain how to handle unicode
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26433>
_______________________________________

From report at bugs.python.org  Thu Feb 25 05:09:01 2016
From: report at bugs.python.org (Jakub Stasiak)
Date: Thu, 25 Feb 2016 10:09:01 +0000
Subject: [docs] [issue26435] Fix versionadded/versionchanged documentation
 directives
Message-ID: <1456394940.93.0.16954708831.issue26435@psf.upfronthosting.co.za>


New submission from Jakub Stasiak:

A double colon seems to be required for a directive to work, please find a patch attached.

----------
assignee: docs at python
components: Documentation
files: typos.patch
keywords: patch
messages: 260848
nosy: docs at python, jstasiak
priority: normal
severity: normal
status: open
title: Fix versionadded/versionchanged documentation directives
type: enhancement
versions: Python 3.6
Added file: http://bugs.python.org/file42027/typos.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26435>
_______________________________________

From report at bugs.python.org  Thu Feb 25 06:35:01 2016
From: report at bugs.python.org (Martin Panter)
Date: Thu, 25 Feb 2016 11:35:01 +0000
Subject: [docs] [issue26435] Fix versionadded/versionchanged documentation
 directives
In-Reply-To: <1456394940.93.0.16954708831.issue26435@psf.upfronthosting.co.za>
Message-ID: <1456400101.68.0.195835095512.issue26435@psf.upfronthosting.co.za>


Martin Panter added the comment:

Thanks for finding these. I presume they are also applicable to 3.5.

There is a similar problem with the range() documentation:

./Doc/library/stdtypes.rst:1301:   .. data: start
./Doc/library/stdtypes.rst:1306:   .. data: stop
./Doc/library/stdtypes.rst:1310:   .. data: step

Unfortunately it looks like this error causes the text to be silently dropped from the output. There are scripts that check for other errors (make -C Doc/ suspicious check), but it seems this error is not picked up.

----------
nosy: +martin.panter
stage:  -> patch review
versions: +Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26435>
_______________________________________

From report at bugs.python.org  Thu Feb 25 13:42:38 2016
From: report at bugs.python.org (Guido van Rossum)
Date: Thu, 25 Feb 2016 18:42:38 +0000
Subject: [docs] [issue26437] asyncio create_server() not always accepts the
 'port' parameter as str
In-Reply-To: <1456408319.2.0.804697554696.issue26437@psf.upfronthosting.co.za>
Message-ID: <1456425758.93.0.776001411868.issue26437@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

I don't know why it used to accept a string port, but I can't find anything in the docs indicating that is acceptable. I am guessing the doc authors assumed it was so obvious that a port is an integer they forgot to mention it.

I can guess that in the past some system API was used that considered the port a "servname" to be looked up in /etc/services (likely the getaddrinfo() call).

But if you were passing '12345' instead of 12345, well, you always had a latent bug in your program.

I don't think the code ought to be adjusted to explicitly reject string ports; but I do think the docs should be clarified on the issue.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26437>
_______________________________________

From report at bugs.python.org  Thu Feb 25 14:08:05 2016
From: report at bugs.python.org (Georg Brandl)
Date: Thu, 25 Feb 2016 19:08:05 +0000
Subject: [docs] [issue26435] Fix versionadded/versionchanged documentation
 directives
In-Reply-To: <1456394940.93.0.16954708831.issue26435@psf.upfronthosting.co.za>
Message-ID: <1456427285.54.0.597348765512.issue26435@psf.upfronthosting.co.za>


Georg Brandl added the comment:

These are interpreted as comments by docutils. "make suspicious" only checks for markup erroneously remaining in the output. "make check", which runs tools/rstlint.py, should pick them up though.

----------
nosy: +georg.brandl

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26435>
_______________________________________

From report at bugs.python.org  Thu Feb 25 14:15:39 2016
From: report at bugs.python.org (Georg Brandl)
Date: Thu, 25 Feb 2016 19:15:39 +0000
Subject: [docs] [issue26435] Fix versionadded/versionchanged documentation
 directives
In-Reply-To: <1456394940.93.0.16954708831.issue26435@psf.upfronthosting.co.za>
Message-ID: <1456427739.32.0.270652941249.issue26435@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Ok, that was a bug in rstlint. Fixed now - and now I can find quite a few instances, will fix them (most of them are in this patch).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26435>
_______________________________________

From report at bugs.python.org  Thu Feb 25 14:18:28 2016
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 25 Feb 2016 19:18:28 +0000
Subject: [docs] [issue26435] Fix versionadded/versionchanged documentation
 directives
In-Reply-To: <1456394940.93.0.16954708831.issue26435@psf.upfronthosting.co.za>
Message-ID: <20160225191820.96917.81010@psf.io>


Roundup Robot added the comment:

New changeset 1f8dc6f2b171 by Georg Brandl in branch '3.5':
Closes #26435: fix syntax in directives. Thanks to Jakub Stasiak.
https://hg.python.org/cpython/rev/1f8dc6f2b171

----------
nosy: +python-dev
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26435>
_______________________________________

From report at bugs.python.org  Thu Feb 25 20:14:08 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 26 Feb 2016 01:14:08 +0000
Subject: [docs] [issue26390] hashlib's pbkdf2_hmac documentation "rounds"
 does not match source
In-Reply-To: <1455840057.88.0.0946194046166.issue26390@psf.upfronthosting.co.za>
Message-ID: <20160226011403.2124.90765@psf.io>


Roundup Robot added the comment:

New changeset 7609aaf180b4 by Martin Panter in branch '3.5':
Issue #26390: Fix and test pbkdf2_hmac() parameter names
https://hg.python.org/cpython/rev/7609aaf180b4

New changeset a74420677e6b by Martin Panter in branch 'default':
Issue #26390: Merge pbkdf2_hmac() doc from 3.5
https://hg.python.org/cpython/rev/a74420677e6b

----------
nosy: +python-dev

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26390>
_______________________________________

From report at bugs.python.org  Thu Feb 25 21:15:20 2016
From: report at bugs.python.org (Martin Panter)
Date: Fri, 26 Feb 2016 02:15:20 +0000
Subject: [docs] [issue26390] hashlib's pbkdf2_hmac documentation "rounds"
 does not match source
In-Reply-To: <1455840057.88.0.0946194046166.issue26390@psf.upfronthosting.co.za>
Message-ID: <1456452920.08.0.957197956169.issue26390@psf.upfronthosting.co.za>


Changes by Martin Panter <vadmium+py at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26390>
_______________________________________

From report at bugs.python.org  Fri Feb 26 06:31:39 2016
From: report at bugs.python.org (ProgVal)
Date: Fri, 26 Feb 2016 11:31:39 +0000
Subject: [docs] [issue26442] Doc refers to xmlrpc.client but means
 xmlrpc.server
Message-ID: <1456486299.23.0.764792855205.issue26442@psf.upfronthosting.co.za>


New submission from ProgVal:

The doc of xmlrpc.server and xmlrpc.client both warn about XML vulnerabilities.

However, both say ?The xmlrpc.client module is not secure?, whereas the page for xml.server should say xmlrpc.server.

----------
assignee: docs at python
components: Documentation
messages: 260892
nosy: Valentin.Lorentz, docs at python
priority: normal
severity: normal
status: open
title: Doc refers to xmlrpc.client but means xmlrpc.server
versions: Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26442>
_______________________________________

From report at bugs.python.org  Fri Feb 26 11:58:49 2016
From: report at bugs.python.org (Ismail s)
Date: Fri, 26 Feb 2016 16:58:49 +0000
Subject: [docs] [issue26444] Fix 2 typos on ElementTree docs
Message-ID: <1456505929.01.0.140412198941.issue26444@psf.upfronthosting.co.za>


New submission from Ismail s:

'incrementall' has been changed to 'incrementally' (and text reflowed).
'keywword' has been changed to 'keyword'.

----------
assignee: docs at python
components: Documentation
files: work.patch
keywords: patch
messages: 260897
nosy: Ismail s, docs at python
priority: normal
severity: normal
status: open
title: Fix 2 typos on ElementTree docs
type: enhancement
versions: Python 3.6
Added file: http://bugs.python.org/file42033/work.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26444>
_______________________________________

From report at bugs.python.org  Fri Feb 26 13:13:27 2016
From: report at bugs.python.org (Georg Brandl)
Date: Fri, 26 Feb 2016 18:13:27 +0000
Subject: [docs] [issue26444] Fix 2 typos on ElementTree docs
In-Reply-To: <1456505929.01.0.140412198941.issue26444@psf.upfronthosting.co.za>
Message-ID: <1456510407.73.0.85043774446.issue26444@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Reflow is kinda bad for patch review :)

----------
nosy: +georg.brandl

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26444>
_______________________________________

From report at bugs.python.org  Fri Feb 26 13:15:11 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 26 Feb 2016 18:15:11 +0000
Subject: [docs] [issue26444] Fix 2 typos on ElementTree docs
In-Reply-To: <1456505929.01.0.140412198941.issue26444@psf.upfronthosting.co.za>
Message-ID: <20160226181501.83573.11409@psf.io>


Roundup Robot added the comment:

New changeset 29beb1554dec by Georg Brandl in branch '3.5':
Closes #26444: typo fixes.
https://hg.python.org/cpython/rev/29beb1554dec

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26444>
_______________________________________

From report at bugs.python.org  Fri Feb 26 13:16:48 2016
From: report at bugs.python.org (Georg Brandl)
Date: Fri, 26 Feb 2016 18:16:48 +0000
Subject: [docs] [issue26442] Doc refers to xmlrpc.client but means
 xmlrpc.server
In-Reply-To: <1456486299.23.0.764792855205.issue26442@psf.upfronthosting.co.za>
Message-ID: <1456510608.61.0.235537447653.issue26442@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Thanks!

----------
nosy: +georg.brandl

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26442>
_______________________________________

From report at bugs.python.org  Fri Feb 26 13:16:49 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 26 Feb 2016 18:16:49 +0000
Subject: [docs] [issue26442] Doc refers to xmlrpc.client but means
 xmlrpc.server
In-Reply-To: <1456486299.23.0.764792855205.issue26442@psf.upfronthosting.co.za>
Message-ID: <20160226181648.1953.61479@psf.io>


Roundup Robot added the comment:

New changeset 9b240ec2bd42 by Georg Brandl in branch '3.5':
Closes #26442: fix copy-paste.
https://hg.python.org/cpython/rev/9b240ec2bd42

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26442>
_______________________________________

From georg at python.org  Fri Feb 26 13:18:23 2016
From: georg at python.org (Georg Brandl)
Date: Fri, 26 Feb 2016 19:18:23 +0100
Subject: [docs] typo in 3.5.1 Macintosh doc
In-Reply-To: <CAH67ZzOsThztOpEHbM+4FDabOfBD_XNkUeL+whUbK9SWUGesuA@mail.gmail.com>
References: <CAH67ZzOsThztOpEHbM+4FDabOfBD_XNkUeL+whUbK9SWUGesuA@mail.gmail.com>
Message-ID: <56D096EF.3080209@python.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/22/2016 07:20 PM, James Stokes wrote:
> In docs.python.org/3.5/using/Mac.html 
> <http://docs.python.org/3.5/using/Mac.html>, the line 'A MacPython 3.4
> folder in your Applications folder' should be updated to '3.5'.
> 
> Thanks for all the great work you guys are doing to bring Python to the
> world.

Thanks for the report, this is now fixed (should be live soon).

cheers,
Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlbQlu8ACgkQN9GcIYhpnLBzgwCfRp1sHwKNI+Xph55NYSOiK1bz
t8YAn0QqTMH6PRW8ltxuA2KEZS2Q+nc8
=tToW
-----END PGP SIGNATURE-----

From report at bugs.python.org  Fri Feb 26 13:19:41 2016
From: report at bugs.python.org (Georg Brandl)
Date: Fri, 26 Feb 2016 18:19:41 +0000
Subject: [docs] [issue25910] Fixing links in documentation
In-Reply-To: <1450530544.1.0.9187941337.issue25910@psf.upfronthosting.co.za>
Message-ID: <1456510781.02.0.229395808531.issue25910@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


----------
status: languishing -> open

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25910>
_______________________________________

From report at bugs.python.org  Fri Feb 26 13:38:13 2016
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 26 Feb 2016 18:38:13 +0000
Subject: [docs] [issue25910] Fixing links in documentation
In-Reply-To: <1450530544.1.0.9187941337.issue25910@psf.upfronthosting.co.za>
Message-ID: <20160226183801.6262.65113@psf.io>


Roundup Robot added the comment:

New changeset ce5ef48b5140 by Georg Brandl in branch '3.5':
Closes #25910: fix dead and permanently redirected links in the docs. Thanks to SilentGhost for the patch.
https://hg.python.org/cpython/rev/ce5ef48b5140

----------
nosy: +python-dev
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25910>
_______________________________________

From report at bugs.python.org  Fri Feb 26 13:41:25 2016
From: report at bugs.python.org (Georg Brandl)
Date: Fri, 26 Feb 2016 18:41:25 +0000
Subject: [docs] [issue25910] Fixing links in documentation
In-Reply-To: <1450530544.1.0.9187941337.issue25910@psf.upfronthosting.co.za>
Message-ID: <1456512085.41.0.567533305853.issue25910@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Reopening, for fixing the rest of the broken ones.

----------
nosy: +georg.brandl
resolution: fixed -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25910>
_______________________________________

From report at bugs.python.org  Sat Feb 27 01:11:43 2016
From: report at bugs.python.org (Liang-Bo Wang)
Date: Sat, 27 Feb 2016 06:11:43 +0000
Subject: [docs] [issue26246] Code output toggle button uses removed jQuery
 method
In-Reply-To: <1454234717.37.0.159058452495.issue26246@psf.upfronthosting.co.za>
Message-ID: <1456553503.81.0.199798055272.issue26246@psf.upfronthosting.co.za>


Liang-Bo Wang added the comment:

Just FYI, I applied the patch to the zh-hant translation of the documentation and the code output toggle button is back and works as expected.

    https://docs.python.org.tw/3/tutorial/introduction.html#numbers

You can see the result of any other page by changing the URL domain from docs.python.org to docs.python.org.tw

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26246>
_______________________________________

From report at bugs.python.org  Sat Feb 27 01:46:44 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 27 Feb 2016 06:46:44 +0000
Subject: [docs] [issue26246] Code output toggle button uses removed jQuery
 method
In-Reply-To: <1454234717.37.0.159058452495.issue26246@psf.upfronthosting.co.za>
Message-ID: <20160227064641.26003.89235@psf.io>


Roundup Robot added the comment:

New changeset f0e20d942760 by Ezio Melotti in branch '3.4':
#26246: update copybutton.js after JQuery update.  Patch by Liang-Bo Wang.
https://hg.python.org/cpython/rev/f0e20d942760

New changeset ac175a7af60b by Ezio Melotti in branch '3.5':
#26246: merge with 3.4.
https://hg.python.org/cpython/rev/ac175a7af60b

New changeset 8c0761260d22 by Ezio Melotti in branch 'default':
#26246: merge with 3.5.
https://hg.python.org/cpython/rev/8c0761260d22

New changeset 20b5d153b894 by Ezio Melotti in branch '2.7':
#26246: update copybutton.js after JQuery update.  Patch by Liang-Bo Wang.
https://hg.python.org/cpython/rev/20b5d153b894

----------
nosy: +python-dev

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26246>
_______________________________________

From report at bugs.python.org  Sat Feb 27 01:51:36 2016
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 27 Feb 2016 06:51:36 +0000
Subject: [docs] [issue26246] Code output toggle button uses removed jQuery
 method
In-Reply-To: <1454234717.37.0.159058452495.issue26246@psf.upfronthosting.co.za>
Message-ID: <1456555896.33.0.840699999906.issue26246@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I applied the patch -- it should go live the next time the docs are updated.  Thanks for the report and the patch!

----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26246>
_______________________________________

From report at bugs.python.org  Sat Feb 27 02:33:41 2016
From: report at bugs.python.org (Liang-Bo Wang)
Date: Sat, 27 Feb 2016 07:33:41 +0000
Subject: [docs] [issue26246] Code output toggle button uses removed jQuery
 method
In-Reply-To: <1454234717.37.0.159058452495.issue26246@psf.upfronthosting.co.za>
Message-ID: <1456558421.18.0.890703678637.issue26246@psf.upfronthosting.co.za>


Liang-Bo Wang added the comment:

Thanks for the merge. 

I pulled the change and checked the result, but I found the patch missing a line to initiate the correct display state when the button was created. That is, it forgot to set `button.data('hidden', 'false');` when adding the button. 

This causes the first click on the button to have no effect. But the following clicks will work.

I filed the new patch to add this line back. I'm so sorry I missed this line :(

----------
Added file: http://bugs.python.org/file42036/copybutton_js_2.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26246>
_______________________________________

From kiran.dhananjaykd at gmail.com  Sat Feb 27 03:24:16 2016
From: kiran.dhananjaykd at gmail.com (Kiran Dhananjay)
Date: Sat, 27 Feb 2016 13:54:16 +0530
Subject: [docs] Typo in argparse module documentation
Message-ID: <CAN-4yWvZc3-4s=6acPatuACLYT43K9107R5ugtgOwo3x6_GDkg@mail.gmail.com>

https://docs.python.org/2/howto/argparse.html

python version : 2.7.11


   - Sadly, our help output isn?t very informative on the new ability our
   script has acquired, but that can always be fixed by improving the
   documentation for *out script* (e.g. via the help keyword argument).


I think "out script" above should be "our script".


Regards,
Kiran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160227/c627f92c/attachment.html>

From kiran.dhananjaykd at gmail.com  Sat Feb 27 03:40:06 2016
From: kiran.dhananjaykd at gmail.com (Kiran Dhananjay)
Date: Sat, 27 Feb 2016 14:10:06 +0530
Subject: [docs] Typo in "argparse tutorial" documentation
Message-ID: <CAN-4yWtR10K57o4GutQNLA3XfL9bBNh+02zMbG87mmO2Sxf6SA@mail.gmail.com>

Actually I found the typo in the "argparse tutorial" not the argparse
module documentation. My previous subject line was probably misleading,
sorry about that.

Regards,
Kiran

On Sat, Feb 27, 2016 at 1:54 PM, Kiran Dhananjay <
kiran.dhananjaykd at gmail.com> wrote:

> https://docs.python.org/2/howto/argparse.html
>
> python version : 2.7.11
>
>
>    - Sadly, our help output isn?t very informative on the new ability our
>    script has acquired, but that can always be fixed by improving the
>    documentation for *out script* (e.g. via the help keyword argument).
>
>
> I think "out script" above should be "our script".
>
>
> Regards,
> Kiran
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160227/93de2168/attachment.html>

From report at bugs.python.org  Sat Feb 27 04:15:56 2016
From: report at bugs.python.org (Martijn Pieters)
Date: Sat, 27 Feb 2016 09:15:56 +0000
Subject: [docs] [issue26449] Tutorial on Python Scopes and Namespaces uses
 confusing 'read-only' terminology
In-Reply-To: <1456564541.09.0.218031979167.issue26449@psf.upfronthosting.co.za>
Message-ID: <1456564556.64.0.922556819201.issue26449@psf.upfronthosting.co.za>


Changes by Martijn Pieters <mj at python.org>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26449>
_______________________________________

From report at bugs.python.org  Sat Feb 27 05:27:23 2016
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 27 Feb 2016 10:27:23 +0000
Subject: [docs] [issue26442] Doc refers to xmlrpc.client but means
 xmlrpc.server
In-Reply-To: <1456486299.23.0.764792855205.issue26442@psf.upfronthosting.co.za>
Message-ID: <1456568843.98.0.0580678726075.issue26442@psf.upfronthosting.co.za>


Changes by Terry J. Reedy <tjreedy at udel.edu>:


----------
versions:  -Python 3.2, Python 3.3, Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26442>
_______________________________________

From report at bugs.python.org  Sat Feb 27 15:20:32 2016
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 27 Feb 2016 20:20:32 +0000
Subject: [docs] [issue26449] Tutorial on Python Scopes and Namespaces uses
 confusing 'read-only' terminology
In-Reply-To: <1456564541.09.0.218031979167.issue26449@psf.upfronthosting.co.za>
Message-ID: <1456604432.22.0.809272574194.issue26449@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

FWIW, the learners in my Python classes seem to find the words "read-only" to be helpful.  Also, I think "not visible" conveys the wrong mental model ("shadowed" being a little more accurate).  

I also disagree with saying that "variables are never read-only". In fact, unless declared "nonlocal", the namespace for the nested scope can't be written to; likewise, we also have dict proxies in classes that are specifically designed to be read-only; further, there are many read-only attributes in Python.

The current paragraph is succinct and accurate.   That said, there is no doubt that creative people can find ways to misread it, so I think  there is room to add an extra paragraph that elaborates on the rules:

1) variable *lookups* will search from locals to nested scopes to globals to builtins, stopping at the first match or raising NameError if not found; and, 

2) variable *writes* always go into locals unless explicitly declared as being in another namespace with "nonlocal" or "global".

The docs can't smooth this over by changing a single misinterpreted word.  One way or another, either in the tutorial or in a FAQ, users need to learn why x=1 doesn't write to an enclosing scope without a namespace declaration and why self.x+=1 can read a class variable, increment the value, and then write to an instance variable.  Learning this is fundamental to understanding the language and it can't be glossed over by saying that the word "read-only" was confusing.  Everyone gets what "read-only" means; instead, the challenge is to grapple with what the rules are and why the language behaves this way.

----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26449>
_______________________________________

From report at bugs.python.org  Sat Feb 27 16:35:59 2016
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 27 Feb 2016 21:35:59 +0000
Subject: [docs] [issue26449] Tutorial on Python Scopes and Namespaces uses
 confusing 'read-only' terminology
In-Reply-To: <1456564541.09.0.218031979167.issue26449@psf.upfronthosting.co.za>
Message-ID: <1456608959.85.0.0935399830809.issue26449@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I agree with Raymond.  IMHO the term "read-only" does a good job at conveying the fact that you can still access/read the value of the variable but you can't assign to it.  "read-only" is about /what/ you can do with the variable, even though it would also be good to clarify /why/ you can only read.

----------
nosy: +ezio.melotti

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26449>
_______________________________________

From report at bugs.python.org  Sat Feb 27 18:03:17 2016
From: report at bugs.python.org (Martin Panter)
Date: Sat, 27 Feb 2016 23:03:17 +0000
Subject: [docs] [issue25910] Fixing links in documentation
In-Reply-To: <1450530544.1.0.9187941337.issue25910@psf.upfronthosting.co.za>
Message-ID: <1456614197.76.0.576313555845.issue25910@psf.upfronthosting.co.za>


Martin Panter added the comment:

BTW it looks like the suspicious.csv file needs updating to compensate for this change:

http://buildbot.python.org/all/builders/Docs%203.5/builds/654/steps/suspicious/logs/stdio

WARNING: [using/unix:31] ":Packaging" found in "https://en.opensuse.org/Portal:Packaging"
WARNING: Found 1/297 unused rules:
using/unix,,:Packaging,http://en.opensuse.org/Portal:Packaging

----------
nosy: +martin.panter

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25910>
_______________________________________

From report at bugs.python.org  Sat Feb 27 22:18:04 2016
From: report at bugs.python.org (Alex LordThorsen)
Date: Sun, 28 Feb 2016 03:18:04 +0000
Subject: [docs] [issue26451] CSV documentation doesn't open with an example
Message-ID: <1456629484.08.0.443868302354.issue26451@psf.upfronthosting.co.za>


New submission from Alex LordThorsen:

Had a friend get stuck on the CSV documentation. They didn't know what a CSV was (to start with) and couldn't find an example that made sense to them.  they went to other sources to figure out how to read CSV files in the end.

I made this patch in the hope that starting out with a very minimal example file format followed by an example python read will make landing on the CSV docs easier to follow for new programmers.

----------
assignee: docs at python
components: Documentation
files: csv_documentation.patch
keywords: patch
messages: 260960
nosy: Alex.LordThorsen, docs at python
priority: normal
severity: normal
status: open
title: CSV documentation doesn't open with an example
versions: Python 3.6
Added file: http://bugs.python.org/file42040/csv_documentation.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26451>
_______________________________________

From report at bugs.python.org  Sun Feb 28 02:42:57 2016
From: report at bugs.python.org (SilentGhost)
Date: Sun, 28 Feb 2016 07:42:57 +0000
Subject: [docs] [issue25910] Fixing links in documentation
In-Reply-To: <1450530544.1.0.9187941337.issue25910@psf.upfronthosting.co.za>
Message-ID: <1456645376.8.0.45473290284.issue25910@psf.upfronthosting.co.za>


SilentGhost added the comment:

Perhaps, I'm misreading the log output, but it seems to me that it's Doc/tools/susp-ignored.csv that needs updating. Here is the attached patch.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25910>
_______________________________________

From report at bugs.python.org  Sun Feb 28 15:06:34 2016
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 28 Feb 2016 20:06:34 +0000
Subject: [docs] [issue26449] Tutorial on Python Scopes and Namespaces uses
 confusing 'read-only' terminology
In-Reply-To: <1456564541.09.0.218031979167.issue26449@psf.upfronthosting.co.za>
Message-ID: <1456689994.19.0.97626517747.issue26449@psf.upfronthosting.co.za>


Georg Brandl added the comment:

I think rephrasing with "... can only be read" would keep the intended meaning, but avoid the problematic "the namespaces are readonly" meaning.

----------
nosy: +georg.brandl

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26449>
_______________________________________

From georg at python.org  Sun Feb 28 15:10:12 2016
From: georg at python.org (Georg Brandl)
Date: Sun, 28 Feb 2016 21:10:12 +0100
Subject: [docs] Typo in argparse module documentation
In-Reply-To: <CAN-4yWvZc3-4s=6acPatuACLYT43K9107R5ugtgOwo3x6_GDkg@mail.gmail.com>
References: <CAN-4yWvZc3-4s=6acPatuACLYT43K9107R5ugtgOwo3x6_GDkg@mail.gmail.com>
Message-ID: <56D35424.6050204@python.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/27/2016 09:24 AM, Kiran Dhananjay wrote:
> https://docs.python.org/2/howto/argparse.html
> 
> python version : 2.7.11
> 
> * Sadly, our help output isn?t very informative on the new ability our
> script has acquired, but that can always be fixed by improving the
> documentation for *out script* (e.g. via the |help| keyword argument).
> 
> 
> I think "out script" above should be "our script".

Hi Kiran,

thanks for the report, this is now fixed (should be live soon).

cheers,
Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlbTVCQACgkQN9GcIYhpnLAbngCgj25b/AE+UiVPs/XZAf2I6piX
NksAmwYDLIUeK8G5qrUqzxrqdESNaUyg
=DDdY
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sun Feb 28 15:13:55 2016
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 28 Feb 2016 20:13:55 +0000
Subject: [docs] [issue25910] Fixing links in documentation
In-Reply-To: <1450530544.1.0.9187941337.issue25910@psf.upfronthosting.co.za>
Message-ID: <20160228201348.47181.72550@psf.io>


Roundup Robot added the comment:

New changeset 8f8e86ea3abb by Georg Brandl in branch '3.5':
Update susp-ignore file (#25910).
https://hg.python.org/cpython/rev/8f8e86ea3abb

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25910>
_______________________________________

From report at bugs.python.org  Mon Feb 29 03:56:34 2016
From: report at bugs.python.org (Martijn Pieters)
Date: Mon, 29 Feb 2016 08:56:34 +0000
Subject: [docs] [issue26449] Tutorial on Python Scopes and Namespaces uses
 confusing 'read-only' terminology
In-Reply-To: <1456564541.09.0.218031979167.issue26449@psf.upfronthosting.co.za>
Message-ID: <1456736194.78.0.406739297058.issue26449@psf.upfronthosting.co.za>


Martijn Pieters added the comment:

+1 for "... can only be read". read-only can too easily be construed to mean that the variable cannot be set from *anywhere*, even the original scope. Another alternative would be "... is effectively read-only", but "... can only be read" is simpler.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26449>
_______________________________________

From report at bugs.python.org  Mon Feb 29 04:41:00 2016
From: report at bugs.python.org (Steve Holden)
Date: Mon, 29 Feb 2016 09:41:00 +0000
Subject: [docs] [issue26449] Tutorial on Python Scopes and Namespaces uses
 confusing 'read-only' terminology
In-Reply-To: <1456564541.09.0.218031979167.issue26449@psf.upfronthosting.co.za>
Message-ID: <1456738860.72.0.147030073792.issue26449@psf.upfronthosting.co.za>


Steve Holden added the comment:

I don't agree there is any place for the term "read-only" in this document. A reader who doesn't understand it or seeks clarification is likely to end up at a page like https://en.wikipedia.org/wiki/Read-only. I submit that nowhere except the documentation under discussion are they likely to find any suggestion that a read-only variable can in fact be changed, and hence I regard the discussion as extremely misleading.

Surely it would be better to focus on the fundamental point here, which is that IN THE ABSENCE OF A global OR nonlocal DECLARATION, ASSIGNMENT BINDS IN THE LOCAL NAMESPACE in a function.

If this point is correctly emphasised it should then be relatively easy to explain that in the absence of such an assignment in the function body in question, the standard name resolution algorithm operates, and that the global and non-local declarations change the effect of assignments to operate on the namespace that is identified by the standard name resolution algorithm.

It's too easy to confuse newcomers, and there seems to be general agreement that this piece is confusing. I'll be happy to attempt a rewrite of this section if we can agree on the goals.

----------
nosy: +holdenweb

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26449>
_______________________________________

From report at bugs.python.org  Mon Feb 29 05:26:28 2016
From: report at bugs.python.org (Albert Freeman)
Date: Mon, 29 Feb 2016 10:26:28 +0000
Subject: [docs] [issue26458] Is the default value assignment of a function
 parameter evaluated multiple times if it is Parameter=None
Message-ID: <1456741588.21.0.674537261973.issue26458@psf.upfronthosting.co.za>


New submission from Albert Freeman:

def f(a, L=[]):
    L.append(a)
    return L

Seems to behave differently to
def f(a, L=None):
    L = []
    L.append(a)
    return L
Which behaves the same as (as far as I noticed) to the below code in the documentation (In the tutorial under 4. More Control Flow Tools)
def f(a, L=None):
    if L is None:
        L = []
    L.append(a)
    return L

I am using CPython 3.5.1, what is the point of "if L is None:" in the lowermost above example? And why is None treated differently to []?

----------
assignee: docs at python
components: Documentation
messages: 261000
nosy: docs at python, tocretpa
priority: normal
severity: normal
status: open
title: Is the default value assignment of a function parameter evaluated multiple times if it is Parameter=None
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26458>
_______________________________________

From report at bugs.python.org  Mon Feb 29 05:30:45 2016
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 29 Feb 2016 10:30:45 +0000
Subject: [docs] [issue26458] Is the default value assignment of a function
 parameter evaluated multiple times if it is Parameter=None
In-Reply-To: <1456741588.21.0.674537261973.issue26458@psf.upfronthosting.co.za>
Message-ID: <1456741845.53.0.996396907156.issue26458@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

This is not a bug, see https://docs.python.org/3.6/faq/programming.html#why-are-default-values-shared-between-objects

In the first case L is evaluated once at compile time.
In the second case L is always set to a new empty list, regardless of what you pass as second argument to f.
In the third case L is set to a new empty list only if you don't pass a second argument (or if you pass None).

----------
nosy: +ezio.melotti
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed
type:  -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26458>
_______________________________________

From report at bugs.python.org  Mon Feb 29 09:32:02 2016
From: report at bugs.python.org (Maciej Fijalkowski)
Date: Mon, 29 Feb 2016 14:32:02 +0000
Subject: [docs] [issue26459] Windows build instructions are very inaccurate
Message-ID: <1456756322.44.0.126364143286.issue26459@psf.upfronthosting.co.za>


New submission from Maciej Fijalkowski:

I've tried following the dev guide (still not successful) to compile a debug version of cpython 2.7 and a couple issues that I run into:

* The VS2010 vs VS2008 confustion - the docs say "most versions before 3.3 use VS2008" - what does it mean by "most"? The current cpython trunk seems to work only on 2010 (with a variety of fun errors).

* VS2010 is hard to download, as is 2008 - direct links would help

* nowhere it's mentioned that you need to run stuff from VS console

* the readme and the devguide disagree on a few points - readme seems to be better, but also not ideal

* the docs don't say how to get svn.exe (that is install tortoiseHG, but then select extra tools from somewhere)

* the build seems to require perl, despite claiming it's not

Other things are misguiding too, but fixing all of the above would be a massive step forward

----------
assignee: docs at python
components: Documentation
messages: 261009
nosy: docs at python, fijall
priority: normal
severity: normal
status: open
title: Windows build instructions are very inaccurate
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26459>
_______________________________________

From report at bugs.python.org  Mon Feb 29 09:32:42 2016
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 29 Feb 2016 14:32:42 +0000
Subject: [docs] [issue26459] Windows build instructions are very inaccurate
In-Reply-To: <1456756322.44.0.126364143286.issue26459@psf.upfronthosting.co.za>
Message-ID: <1456756362.57.0.595895175133.issue26459@psf.upfronthosting.co.za>


Changes by STINNER Victor <victor.stinner at gmail.com>:


----------
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26459>
_______________________________________

From report at bugs.python.org  Mon Feb 29 09:44:15 2016
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 29 Feb 2016 14:44:15 +0000
Subject: [docs] [issue17231] Mark __del__ not being called in cycles as an
 impl detail
In-Reply-To: <1361254972.69.0.594313111975.issue17231@psf.upfronthosting.co.za>
Message-ID: <1456757055.64.0.503488127988.issue17231@psf.upfronthosting.co.za>


Changes by Berker Peksag <berker.peksag at gmail.com>:


----------
nosy: +berker.peksag

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue17231>
_______________________________________

From report at bugs.python.org  Mon Feb 29 09:44:23 2016
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 29 Feb 2016 14:44:23 +0000
Subject: [docs] [issue17232] Improve -O docs
In-Reply-To: <1361255101.21.0.948205073894.issue17232@psf.upfronthosting.co.za>
Message-ID: <1456757063.82.0.949463525712.issue17232@psf.upfronthosting.co.za>


Changes by Berker Peksag <berker.peksag at gmail.com>:


----------
nosy: +berker.peksag

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue17232>
_______________________________________

From report at bugs.python.org  Mon Feb 29 09:47:02 2016
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 29 Feb 2016 14:47:02 +0000
Subject: [docs] [issue17232] Improve -O docs
In-Reply-To: <1361255101.21.0.948205073894.issue17232@psf.upfronthosting.co.za>
Message-ID: <1456757222.65.0.0340841371669.issue17232@psf.upfronthosting.co.za>


Changes by STINNER Victor <victor.stinner at gmail.com>:


----------
nosy: +haypo

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue17232>
_______________________________________

From report at bugs.python.org  Mon Feb 29 09:47:07 2016
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 29 Feb 2016 14:47:07 +0000
Subject: [docs] [issue17231] Mark __del__ not being called in cycles as an
 impl detail
In-Reply-To: <1361254972.69.0.594313111975.issue17231@psf.upfronthosting.co.za>
Message-ID: <1456757227.32.0.496686313689.issue17231@psf.upfronthosting.co.za>


Changes by STINNER Victor <victor.stinner at gmail.com>:


----------
nosy: +haypo

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue17231>
_______________________________________

From report at bugs.python.org  Mon Feb 29 10:35:01 2016
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 29 Feb 2016 15:35:01 +0000
Subject: [docs] [issue24823] ctypes.create_string_buffer does not add NUL if
 len(init) == size
In-Reply-To: <1438942688.18.0.266077254276.issue24823@psf.upfronthosting.co.za>
Message-ID: <1456760101.02.0.925707933212.issue24823@psf.upfronthosting.co.za>


Changes by Berker Peksag <berker.peksag at gmail.com>:


----------
components:  -Devguide

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue24823>
_______________________________________

From report at bugs.python.org  Mon Feb 29 11:23:00 2016
From: report at bugs.python.org (Steve Dower)
Date: Mon, 29 Feb 2016 16:23:00 +0000
Subject: [docs] [issue26459] Windows build instructions are very inaccurate
In-Reply-To: <1456756322.44.0.126364143286.issue26459@psf.upfronthosting.co.za>
Message-ID: <1456762980.28.0.52630538873.issue26459@psf.upfronthosting.co.za>


Steve Dower added the comment:

Agreed. The PCBuild/readme.txt file should clear up a few of those points, but the docs aren't exactly beginner friendly (and by that I mean beginning Windows users, not beginning C developers).

We probably need someone to write a dedicated document for building Python 2.7 at this stage. The dev guide should only really be for versions under active development. Unless someone else gets there first, I'll look at making it more approachable.

----------
versions: +Python 3.6 -Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26459>
_______________________________________

From report at bugs.python.org  Mon Feb 29 17:26:03 2016
From: report at bugs.python.org (Maciej Szulik)
Date: Mon, 29 Feb 2016 22:26:03 +0000
Subject: [docs] [issue26176] EmailMessage example doesn't work
In-Reply-To: <1453427916.73.0.91814079944.issue26176@psf.upfronthosting.co.za>
Message-ID: <1456784763.38.0.945765054952.issue26176@psf.upfronthosting.co.za>


Changes by Maciej Szulik <soltysh at gmail.com>:


----------
nosy: +maciej.szulik

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26176>
_______________________________________

From report at bugs.python.org  Mon Feb 29 18:58:52 2016
From: report at bugs.python.org (Julien)
Date: Mon, 29 Feb 2016 23:58:52 +0000
Subject: [docs] [issue26462] Patch to enhance literal block language
 declaration
Message-ID: <1456790330.71.0.936150839602.issue26462@psf.upfronthosting.co.za>


New submission from Julien:

Hi,

As I don't like warnings, and sphinx-doc was verbose about "Could not parse literal_block as "python3". highlighting skipped.", I fixed most of them.

Bonus: It's graphically better, as an example the XML block here: https://docs.python.org/3.5/library/pyexpat.html is now nicely colored: http://www.afpy.org/doc/python/3.5/library/pyexpat.html

----------
assignee: docs at python
components: Documentation
files: literal_blocks_languages.patch
keywords: patch
messages: 261035
nosy: docs at python, sizeof
priority: normal
severity: normal
status: open
title: Patch to enhance literal block language declaration
type: enhancement
versions: Python 3.5
Added file: http://bugs.python.org/file42050/literal_blocks_languages.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26462>
_______________________________________