From report at bugs.python.org  Thu May  1 02:25:03 2014
From: report at bugs.python.org (Elias Zamaria)
Date: Thu, 01 May 2014 00:25:03 +0000
Subject: [docs] [issue19980] Improve help('non-topic') response
In-Reply-To: <1397486628.48.0.807014364675.issue19980@psf.upfronthosting.co.za>
Message-ID: <CAFdOKfvh6_Lt5g7Hr4aRsetyc=Vw9RtFZNFhPXH0qB5NON41HA@mail.gmail.com>


Elias Zamaria added the comment:

Sorry for the late response but I have been busy with various things. I may
be able to work on this but I don't know when or how long it will take me.
I would suggest that someone else work on it if anyone wants it done any
time soon. I am sorry about this.

On Mon, Apr 14, 2014 at 7:43 AM, Jessica McKellar <report at bugs.python.org>wrote:

>
> Jessica McKellar added the comment:
>
> Elias, thanks for your patch!
>
> I think it's important to add the second part of Terry's suggestion which
> gives the user a specific next step to take, namely:
>
> > Try help('help') for information on recognized strings or help(str) for
> help on the str class.
>
> Can you add that to your patch?
>
> Additionally, we'll want to make sure we don't accidentally break this new
> functionality. Can you add a few test cases, for example what happens when
> you run help on a module (e.g. help("os"), 2) help on an instance of a
> class (e.g. help(1)), and help on a string that doesn't have a special
> meaning, (e.g. help("abcxyz"))?
>
> I don't see any existing tests for help(), but it is an instance of
> site._Helper (as reported by type(help)), and site tests live in
> Lib/test/test_site.py. It also gets loaded into builtins, so tests could
> also live in Lib/test/test_builtins.py.
>
> ----------
> nosy: +Jessica.McKellar, jesstess
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <http://bugs.python.org/issue19980>
> _______________________________________
>

----------

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

From report at bugs.python.org  Thu May  1 03:32:55 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 01 May 2014 01:32:55 +0000
Subject: [docs] [issue2716] Document license under which audioop is used
In-Reply-To: <1209428570.75.0.48368829493.issue2716@psf.upfronthosting.co.za>
Message-ID: <1398907975.22.0.687299567358.issue2716@psf.upfronthosting.co.za>


Changes by Terry J. Reedy <tjreedy at udel.edu>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
priority: high -> normal
title: Reimplement audioop because of copyright issues -> Document license under which audioop is used

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

From report at bugs.python.org  Fri May  2 10:23:26 2014
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 02 May 2014 08:23:26 +0000
Subject: [docs] [issue15104] Unclear language in __main__ description
In-Reply-To: <1340092965.02.0.675870286607.issue15104@psf.upfronthosting.co.za>
Message-ID: <1399019005.85.0.347216102959.issue15104@psf.upfronthosting.co.za>


?ric Araujo added the comment:

Docs and indexing/cross-links in 2.7 should indeed be improved.  I had forgotten which of 2.6 or 2.7 added support for executing packages thanks to __main__.py files and the docs don't contain an answer that's comprehensive and easy to find.

----------
assignee: docs at python -> eric.araujo
nosy: +eric.araujo
stage: patch review -> needs patch

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

From report at bugs.python.org  Fri May  2 12:29:57 2014
From: report at bugs.python.org (=?utf-8?q?Jurko_Gospodneti=C4=87?=)
Date: Fri, 02 May 2014 10:29:57 +0000
Subject: [docs] [issue21415] Python __new__ method doc typo (it's a class
	and not a	static method)
Message-ID: <1399026596.96.0.389694886975.issue21415@psf.upfronthosting.co.za>


New submission from Jurko Gospodneti?:

Doc/reference/datamodel.rst documentation states that
the __new__ method is a static method (in Python, not
in C!) when it is in fact a class method.

A patch has been prepared in the
https://bitbucket.org/jurko/cpython repository.
branch: datamodel_doc_typo_fix
commit: 81c5ba188805e42292c3eb9cffa56fbd5b7c6aee

But it'll probably be easier for you to just change
that single word directly. :-D

Hope this helps.

Best regards,
  Jurko Gospodneti?

----------
assignee: docs at python
components: Documentation
hgrepos: 245
messages: 217748
nosy: Jurko.Gospodneti?, docs at python
priority: normal
severity: normal
status: open
title: Python __new__ method doc typo (it's a class and not a static method)
type: enhancement
versions: Python 3.5

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

From report at bugs.python.org  Fri May  2 12:31:10 2014
From: report at bugs.python.org (=?utf-8?q?Jurko_Gospodneti=C4=87?=)
Date: Fri, 02 May 2014 10:31:10 +0000
Subject: [docs] [issue21415] Python __new__ method doc typo (it's a class
	and not a	static method)
In-Reply-To: <1399026596.96.0.389694886975.issue21415@psf.upfronthosting.co.za>
Message-ID: <1399026670.59.0.5588545237.issue21415@psf.upfronthosting.co.za>


Changes by Jurko Gospodneti? <jurko.gospodnetic at gmail.com>:


----------
keywords: +patch
Added file: http://bugs.python.org/file35130/81c5ba188805.diff

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

From report at bugs.python.org  Fri May  2 14:07:35 2014
From: report at bugs.python.org (Steven D'Aprano)
Date: Fri, 02 May 2014 12:07:35 +0000
Subject: [docs] [issue21415] Python __new__ method doc typo (it's a class
	and not a	static method)
In-Reply-To: <1399026596.96.0.389694886975.issue21415@psf.upfronthosting.co.za>
Message-ID: <1399032455.08.0.160204449904.issue21415@psf.upfronthosting.co.za>


Steven D'Aprano added the comment:

Actually, no, it is a staticmethod. See Guido's tutorial from way back in version 2.2:

[quote]
__new__ is a static method. When defining it, you don't need to (but may!) use the phrase "__new__ = staticmethod(__new__)", because this is implied by its name (it is special-cased by the class constructor).
[end quote]

https://www.python.org/download/releases/2.2.3/descrintro


I believe that this explains why you have to use this idiom inside __new__ when using super():

    def __new__(cls, x):
        super().__new__(cls, x)

If __new__ were a classmethod, the first argument "cls" would be provided automatically.


If you try making __new__ a classmethod, it breaks:

py> class Test:
...     @classmethod
...     def __new__(cls):
...             pass
...
py> x = Test()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: __new__() takes 1 positional argument but 2 were given

whereas a staticmethod works fine.

----------
nosy: +steven.daprano
resolution:  -> not a bug
status: open -> closed

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

From report at bugs.python.org  Fri May  2 16:45:24 2014
From: report at bugs.python.org (eryksun)
Date: Fri, 02 May 2014 14:45:24 +0000
Subject: [docs] [issue21415] Python __new__ method doc typo (it's a class
	and not a	static method)
In-Reply-To: <1399026596.96.0.389694886975.issue21415@psf.upfronthosting.co.za>
Message-ID: <1399041924.91.0.331581890518.issue21415@psf.upfronthosting.co.za>


eryksun added the comment:

> I believe that this explains why you have to use this idiom 
> inside __new__ when using super():
> 
>     def __new__(cls, x):
>         super().__new__(cls, x)

Yes, if __new__ is defined and is a function, type_new replaces it with a staticmethod:

http://hg.python.org/cpython/file/04f714765c13/Objects/typeobject.c#l2437

For example:

    >>> class A: __new__ = lambda c: 0

    >>> type(vars(A)['__new__'])
    <class 'staticmethod'>

A heap type that defines __new__ has tp_new set to slot_tp_new. This looks up and calls __new__, with the class inserted as the first argument:

http://hg.python.org/cpython/file/04f714765c13/Objects/typeobject.c#l6036

If you use a classmethod, looking up __new__ returns a method bound to the class. When called, this inserts the class in the args yet again:

http://hg.python.org/cpython/file/04f714765c13/Objects/classobject.c#l321

----------
nosy: +eryksun

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

From report at bugs.python.org  Fri May  2 18:46:42 2014
From: report at bugs.python.org (Chris Rebert)
Date: Fri, 02 May 2014 16:46:42 +0000
Subject: [docs] [issue21347] Don't use a list argument together with
	shell=True in	subprocess' docs
In-Reply-To: <1398366522.65.0.954174735085.issue21347@psf.upfronthosting.co.za>
Message-ID: <1399049202.61.0.0841468718654.issue21347@psf.upfronthosting.co.za>


Changes by Chris Rebert <pybugs at rebertia.com>:


----------
nosy: +cvrebert

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

From report at bugs.python.org  Fri May  2 19:08:01 2014
From: report at bugs.python.org (akira)
Date: Fri, 02 May 2014 17:08:01 +0000
Subject: [docs] [issue21347] Don't use a list argument together with
	shell=True in	subprocess' docs
In-Reply-To: <1398366522.65.0.954174735085.issue21347@psf.upfronthosting.co.za>
Message-ID: <1399050481.64.0.396298610069.issue21347@psf.upfronthosting.co.za>


akira added the comment:

I've checked the same documentation patch applies to both default (3.5) and 2.7 branches.

There are no more instances of the misleading usage left (after applying the patch).

----------

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

From report at bugs.python.org  Fri May  2 19:54:00 2014
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 02 May 2014 17:54:00 +0000
Subject: [docs] [issue21404] Document options used to control compression
	level in	tarfile
In-Reply-To: <1398892016.48.0.640823521737.issue21404@psf.upfronthosting.co.za>
Message-ID: <1399053240.32.0.601918917721.issue21404@psf.upfronthosting.co.za>


?ric Araujo added the comment:

I'm reclassifying this ticket as a doc bug, would you mind opening a separate ticket for zipfile?

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
keywords: +easy
nosy: +docs at python, eric.araujo
stage:  -> needs patch
title: Compression level for tarfile/zipfile -> Document options used to control compression level in tarfile
versions: +Python 2.7, Python 3.5

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

From report at bugs.python.org  Fri May  2 20:01:11 2014
From: report at bugs.python.org (Sworddragon)
Date: Fri, 02 May 2014 18:01:11 +0000
Subject: [docs] [issue21404] Document options used to control compression
	level in	tarfile
In-Reply-To: <1398892016.48.0.640823521737.issue21404@psf.upfronthosting.co.za>
Message-ID: <1399053671.62.0.741471520421.issue21404@psf.upfronthosting.co.za>


Sworddragon added the comment:

Sure, here is the new ticket: http://bugs.python.org/issue21417

----------

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

From report at bugs.python.org  Fri May  2 20:07:51 2014
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 02 May 2014 18:07:51 +0000
Subject: [docs] [issue21366] Document that return in finally overwrites prev
	value
In-Reply-To: <1398615139.09.0.290952002497.issue21366@psf.upfronthosting.co.za>
Message-ID: <1399054071.23.0.91322611284.issue21366@psf.upfronthosting.co.za>


?ric Araujo added the comment:

Thanks, your proposed wording sounds good to me.  David (picked you seni-randomly as a senior core dev and native speaker), what do you think?

----------
nosy: +eric.araujo, r.david.murray

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

From report at bugs.python.org  Fri May  2 20:45:35 2014
From: report at bugs.python.org (R. David Murray)
Date: Fri, 02 May 2014 18:45:35 +0000
Subject: [docs] [issue21366] Document that return in finally overwrites prev
	value
In-Reply-To: <1398615139.09.0.290952002497.issue21366@psf.upfronthosting.co.za>
Message-ID: <1399056335.45.0.0819932244967.issue21366@psf.upfronthosting.co.za>


R. David Murray added the comment:

The precisionist in me isn't quite happy, but any wording I've come up with to make it more precise isn't as informative :)  (The 'real' situation is that the return value of the function is determined by the last return statement executed, which in turn is determined by the try/finally logic....but as far as I can see the suggested phrasing is equivalent to that in every respect that matters).

I also have an impulse to add "so don't do that" :)

----------

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

From report at bugs.python.org  Sat May  3 01:58:02 2014
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 02 May 2014 23:58:02 +0000
Subject: [docs] [issue21352] improve documentation indexing
In-Reply-To: <1398457661.12.0.679738685491.issue21352@psf.upfronthosting.co.za>
Message-ID: <1399075082.4.0.676430969784.issue21352@psf.upfronthosting.co.za>


?ric Araujo added the comment:

I have to agree the index pages are often frustrating for me too.

Not sure if this involves code changes in Sphinx itself or if we can improve the markup in the Python docs sources.

----------
nosy: +eric.araujo

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

From report at bugs.python.org  Sat May  3 03:23:26 2014
From: report at bugs.python.org (paul j3)
Date: Sat, 03 May 2014 01:23:26 +0000
Subject: [docs] [issue14191] argparse doesn't allow optionals within
	positionals
In-Reply-To: <1330843053.88.0.983162018395.issue14191@psf.upfronthosting.co.za>
Message-ID: <1399080206.09.0.194794393215.issue14191@psf.upfronthosting.co.za>


paul j3 added the comment:

I encountered a conflict when merging this patch with http://bugs.python.org/issue15112.  In my first testcase, 'cmd' and 'rest' failed the 'required' test in phase one of 'intermixed'.  That's because 15112 postponed parsing them (with nargs=0/suppressed).  

I got around that by temporarily setting the 'required' attribute to False.

The whole issue of when (or even whether) a positional that is satisfied with 0 arguments, is consumed, is a bit messy.

----------

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

From report at bugs.python.org  Sat May  3 11:11:13 2014
From: report at bugs.python.org (=?utf-8?q?Jurko_Gospodneti=C4=87?=)
Date: Sat, 03 May 2014 09:11:13 +0000
Subject: [docs] [issue21415] Python __new__ method doc typo (it's a class
	and not a	static method)
In-Reply-To: <1399026596.96.0.389694886975.issue21415@psf.upfronthosting.co.za>
Message-ID: <1399108273.26.0.566337008237.issue21415@psf.upfronthosting.co.za>


Jurko Gospodneti? added the comment:

Thanks for the detailed response! :-(

I should have tested more before reporting the issue.
Sorry for the noise. :-(

I saw the 'cls' argument and assumed it was a class
method. Having to explicitly specify cls did not
seem to be in contradiction with this since I assumed
__new__ is generally invoked on the class directly.

I still do not see why it had to be a static method
and has not been implemented as a class method, but I
guess I'll better ask that kind of a question on the
python user's newsgroup. :-)

Just in case it can help someone else, here's some
sample code what convinced me __new__ was indeed
implemented as a static method:

> class X:
>     pass
> X.__new__()   # TypeError: object.__new__(): not enough arguments
> X.__new__(X)  # creates a new X instance
> x = X()
> x.__new__()   # TypeError: object.__new__(): not enough arguments
> x.__new__(X)  # creates a new X instance

If __new__ had been a class method then calling
'x.__new__()' would have worked as well.

Thanks again for the replies!

Best regards,
  Jurko Gospodneti?

----------

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

From report at bugs.python.org  Sat May  3 15:57:07 2014
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Sat, 03 May 2014 13:57:07 +0000
Subject: [docs] [issue21352] improve documentation indexing
In-Reply-To: <1398457661.12.0.679738685491.issue21352@psf.upfronthosting.co.za>
Message-ID: <1399125427.33.0.193883631963.issue21352@psf.upfronthosting.co.za>


Changes by Tshepang Lekhonkhobe <tshepang at gmail.com>:


----------
nosy: +tshepang

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

From report at bugs.python.org  Sun May  4 09:42:40 2014
From: report at bugs.python.org (Jiong Du)
Date: Sun, 04 May 2014 07:42:40 +0000
Subject: [docs] [issue19576] "Non-Python created threads" documentation
	doesn't	mention PyEval_InitThreads()
In-Reply-To: <1384379370.85.0.232061958171.issue19576@psf.upfronthosting.co.za>
Message-ID: <1399189360.47.0.535298248584.issue19576@psf.upfronthosting.co.za>


Jiong Du added the comment:

this patch made a new issue<20891>

----------
nosy: +lolynx

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

From report at bugs.python.org  Sun May  4 21:05:46 2014
From: report at bugs.python.org (Bas Wijnen)
Date: Sun, 04 May 2014 19:05:46 +0000
Subject: [docs] [issue21430] Document ssl.pending()
Message-ID: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>


New submission from Bas Wijnen:

In order to use ssl sockets asynchronously, it is important to use the pending() method, otherwise the internal buffer will be ignored, and select may block for new data while it's already waiting.  See bug #16976 and http://stackoverflow.com/questions/21663705/how-to-use-select-with-python-ssl-socket-buffering

Using pending() works fine, but is entirely undocumented.  https://docs.python.org/2.7/library/ssl.html (and all other versions) don't even mention the existence of the method.  I hope this can be changed; using an undocumented feature isn't nice, but in this case there is no other good solution.

----------
assignee: docs at python
components: Documentation
messages: 217884
nosy: docs at python, shevek
priority: normal
severity: normal
status: open
title: Document ssl.pending()
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5

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

From report at bugs.python.org  Sun May  4 23:00:17 2014
From: report at bugs.python.org (Ned Deily)
Date: Sun, 04 May 2014 21:00:17 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1399237217.24.0.160429351083.issue21430@psf.upfronthosting.co.za>


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


----------
nosy: +pitrou

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

From report at bugs.python.org  Sun May  4 23:02:49 2014
From: report at bugs.python.org (Ned Deily)
Date: Sun, 04 May 2014 21:02:49 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1399237369.59.0.904948724884.issue21430@psf.upfronthosting.co.za>


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


----------
nosy: +christian.heimes

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

From report at bugs.python.org  Sun May  4 23:41:49 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Sun, 04 May 2014 21:41:49 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1399239709.49.0.542086593105.issue21430@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

pending() shouldn't be necessary for this. See https://docs.python.org/dev/library/ssl.html#notes-on-non-blocking-sockets

Generally, when using non-blocking sockets, you first try to read (or write) and then catch any exceptions that might be raised if the socket isn't ready.

----------

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

From report at bugs.python.org  Mon May  5 11:20:58 2014
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 05 May 2014 09:20:58 +0000
Subject: [docs] [issue21434] python -3 documentation is outdated
Message-ID: <1399281658.38.0.402381658113.issue21434@psf.upfronthosting.co.za>


New submission from Berker Peksag:

https://docs.python.org/2.7/using/cmdline.html#cmdoption-3

Currently, lib2to3 provides fixers for dict.has_key(), apply(), callable(),
execfile() and reduce() functions.

The "reload" fixer was added to Python 3.4 in issue 11797, but not backported to 2.7.

----------
assignee: docs at python
components: Documentation
files: cmdline-3.diff
keywords: patch
messages: 217914
nosy: berker.peksag, docs at python
priority: normal
severity: normal
stage: patch review
status: open
title: python -3 documentation is outdated
versions: Python 2.7
Added file: http://bugs.python.org/file35151/cmdline-3.diff

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

From 2657068483 at qq.com  Thu May  1 09:35:52 2014
From: 2657068483 at qq.com (2657068483 at qq.com)
Date: Thu, 1 May 2014 15:35:52 +0800
Subject: [docs] some advice
Message-ID: <2014050115354773629423@qq.com>

1.Provide suport for class method/static method/instance method by using self and cls keywords
   Define class method by the first argument cls, cancel the @classmethod, like :  def classInfo(cls):pass
   Define instance method by the first argument self, like : def save(self):pass
   Define static method by none special argument, cancel the @staticmethod, like : def getInstance():pass
2.Cancel property statement, use a new keyword ppt to define properties, like :
   ppt Name():
         def get():
               pass
         def set(value):
              pass
        def del():
             pass
3.Use a new keyword base to replace the function super().


2657068483 at qq.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140501/00bc0dab/attachment-0001.html>

From feliks.kluzniak at telia.com  Sun May  4 21:25:19 2014
From: feliks.kluzniak at telia.com (Feliks Kluzniak)
Date: Sun, 4 May 2014 21:25:19 +0200
Subject: [docs] The Language Reference Manual: a list of suggested
	improvements
Message-ID: <1E09EC01-05C6-4A2E-B77F-19447BFEA694@telia.com>

Hello!

I have been reading the Language Reference Manual in order to teach myself Python 3.  I noticed several minor errors, and a much larger number of linguistic or editorial infelicities.  I have listed them all in the enclosed document: I hope it will be useful.

Sincerely,
? Feliks Kluzniak

P.S. My apologies for not having the time to weed out those remarks which might already have been entered into the list of ?documentation bugs?.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PythonRefmanual_3_4_0_Errata.rtf
Type: text/rtf
Size: 36606 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20140504/3041c8b2/attachment-0001.bin>

From report at bugs.python.org  Mon May  5 15:32:12 2014
From: report at bugs.python.org (akira)
Date: Mon, 05 May 2014 13:32:12 +0000
Subject: [docs] [issue21437] document that asyncio.ProactorEventLoop doesn't
	support	SSL
Message-ID: <1399296732.42.0.791038898639.issue21437@psf.upfronthosting.co.za>


New submission from akira:

In Lib/asyncio/proactor_events.py:419 [1]:

  def _start_serving(self, protocol_factory, sock, ssl=None, server=None):
    if ssl:
      raise ValueError('IocpEventLoop is incompatible with SSL.')

[1]: http://hg.python.org/cpython/file/4f26430b03fd/Lib/asyncio/proactor_events.py#l419

ProactorEventLoop is mentioned in the docs that it should be used to run 
subprocesses on Windows. [2]

[2]: http://hg.python.org/cpython/file/4f26430b03fd/Doc/library/asyncio-subprocess.rst

It might be a good example to demonstrate the idiomatic way how two different 
event loops could be used (to support both subprocesses and ssl connections in 
the same program).

----------
assignee: docs at python
components: Documentation
messages: 217921
nosy: akira, docs at python
priority: normal
severity: normal
status: open
title: document that asyncio.ProactorEventLoop doesn't support SSL
type: enhancement
versions: Python 3.4, Python 3.5

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

From report at bugs.python.org  Mon May  5 16:35:20 2014
From: report at bugs.python.org (Zachary Ware)
Date: Mon, 05 May 2014 14:35:20 +0000
Subject: [docs] [issue21439] Numerous minor issues in Language Reference
In-Reply-To: <1399300451.92.0.450554829588.issue21439@psf.upfronthosting.co.za>
Message-ID: <1399300520.73.0.937744057253.issue21439@psf.upfronthosting.co.za>


Changes by Zachary Ware <zachary.ware at gmail.com>:


----------
nosy: +docs at python

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

From zachary.ware+pydocs at gmail.com  Mon May  5 16:39:58 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Mon, 5 May 2014 09:39:58 -0500
Subject: [docs] The Language Reference Manual: a list of suggested
	improvements
In-Reply-To: <1E09EC01-05C6-4A2E-B77F-19447BFEA694@telia.com>
References: <1E09EC01-05C6-4A2E-B77F-19447BFEA694@telia.com>
Message-ID: <CAKJDb-P_u1=mME=ffboSTFdnY=rK_PE7RFJmvxQPdG9JVE4kCw@mail.gmail.com>

Hi Feliks,

On Sun, May 4, 2014 at 2:25 PM, Feliks Kluzniak
<feliks.kluzniak at telia.com> wrote:
> Hello!
>
> I have been reading the Language Reference Manual in order to teach myself Python 3.  I noticed several minor errors, and a much larger number of linguistic or editorial infelicities.  I have listed them all in the enclosed document: I hope it will be useful.

Thank you for the report!  It will take some significant time to work
through all of the things you listed, but I've created issue21439 [1]
to make sure your suggestions are not lost.

>
> Sincerely,
> ? Feliks Kluzniak
>
> P.S. My apologies for not having the time to weed out those remarks which might already have been entered into the list of ?documentation bugs?.

That's alright; from a brief glance at your first few suggestions, I
suspect very few if any of them already have open issues on
bugs.python.org.

Regards,
-- 
Zach

[1] http://bugs.python.org/issue21439

From zachary.ware+pydocs at gmail.com  Mon May  5 16:25:05 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Mon, 5 May 2014 09:25:05 -0500
Subject: [docs] some advice
In-Reply-To: <2014050115354773629423@qq.com>
References: <2014050115354773629423@qq.com>
Message-ID: <CAKJDb-MS8yvnvjf8mWaVna+HrzVWib8fPiew5nXHVKq8MZyqsA@mail.gmail.com>

Hi,

On Thu, May 1, 2014 at 2:35 AM, 2657068483 at qq.com <2657068483 at qq.com> wrote:
> 1.Provide suport for class method/static method/instance method by using
> self and cls keywords
>    Define class method by the first argument cls, cancel the @classmethod,
> like :  def classInfo(cls):pass
>    Define instance method by the first argument self, like : def
> save(self):pass
>    Define static method by none special argument, cancel the @staticmethod,
> like : def getInstance():pass
> 2.Cancel property statement, use a new keyword ppt to define properties,
> like :
>    ppt Name():
>          def get():
>                pass
>          def set(value):
>               pass
>         def del():
>              pass
> 3.Use a new keyword base to replace the function super().

This is not the correct place to discuss these suggestions; this list
is meant for discussion of the Python documentation.  A more
appropriate venue would be python-ideas at python.org.  However, if you
start such a discussion on that list, be warned that these suggestions
will meet with heavy opposition: your suggestions would require very
fundamental changes to the way Python works, breaking all kinds of
code, introspection capabilities, and people's expectations.

Regards,
-- 
Zach

From report at bugs.python.org  Mon May  5 17:17:51 2014
From: report at bugs.python.org (Zachary Ware)
Date: Mon, 05 May 2014 15:17:51 +0000
Subject: [docs] [issue21366] Document that return in finally overwrites prev
	value
In-Reply-To: <1398615139.09.0.290952002497.issue21366@psf.upfronthosting.co.za>
Message-ID: <1399303071.08.0.083624637057.issue21366@psf.upfronthosting.co.za>


Zachary Ware added the comment:

How's this, or is it too much?

----------
keywords: +patch
nosy: +zach.ware
Added file: http://bugs.python.org/file35154/issue21366.diff

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

From report at bugs.python.org  Mon May  5 17:18:34 2014
From: report at bugs.python.org (Zachary Ware)
Date: Mon, 05 May 2014 15:18:34 +0000
Subject: [docs] [issue21366] Document that return in finally overwrites prev
	value
In-Reply-To: <1398615139.09.0.290952002497.issue21366@psf.upfronthosting.co.za>
Message-ID: <1399303114.44.0.673679387094.issue21366@psf.upfronthosting.co.za>


Changes by Zachary Ware <zachary.ware at gmail.com>:


----------
stage:  -> patch review
type: behavior -> enhancement
versions: +Python 3.4, Python 3.5

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

From report at bugs.python.org  Mon May  5 17:44:40 2014
From: report at bugs.python.org (R. David Murray)
Date: Mon, 05 May 2014 15:44:40 +0000
Subject: [docs] [issue21366] Document that return in finally overwrites prev
	value
In-Reply-To: <1398615139.09.0.290952002497.issue21366@psf.upfronthosting.co.za>
Message-ID: <1399304680.06.0.0125748844679.issue21366@psf.upfronthosting.co.za>


R. David Murray added the comment:

I would remove the parenthetical (it was so stated in immediately preceding paragraph and thus is redundant), and instead of "win", I would say "will always be the last one executed".

----------

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

From report at bugs.python.org  Mon May  5 20:28:03 2014
From: report at bugs.python.org (Jake Vanderplas)
Date: Mon, 05 May 2014 18:28:03 +0000
Subject: [docs] [issue21441] Buffer Protocol Documentation Error
Message-ID: <1399314483.29.0.410069597608.issue21441@psf.upfronthosting.co.za>


New submission from Jake Vanderplas:

The ``obj`` and ``buf`` structure elements are switched in the documentation of the Buffer Protocol.

Compare https://docs.python.org/3.3/c-api/buffer.html#Py_buffer to https://github.com/python/cpython/blob/master/Include/object.h#L179-180

----------
assignee: docs at python
components: Documentation
files: bufferdoc.patch
keywords: patch
messages: 217939
nosy: Jake.Vanderplas, docs at python
priority: normal
severity: normal
status: open
title: Buffer Protocol Documentation Error
versions: Python 3.3, Python 3.4, Python 3.5
Added file: http://bugs.python.org/file35158/bufferdoc.patch

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

From report at bugs.python.org  Mon May  5 22:19:57 2014
From: report at bugs.python.org (steven Michalske)
Date: Mon, 05 May 2014 20:19:57 +0000
Subject: [docs] [issue21443] asyncoio logging documentation clarifications.
Message-ID: <1399321197.68.0.955361534546.issue21443@psf.upfronthosting.co.za>


New submission from steven Michalske:

The asyncio documentation should comment on how to mute and increase some of it's logging.

18.5.7.3. Logging
The asyncio module logs information with the logging module in the logger 'asyncio'.


Adding a bit of text that mentions the following line would be great.
"""
The default verbosity will include messages at logging.INFO level.
To modify the verbosity of asyncio logging add a similar line to your application.
`logging.getLogger('asyncio').setLevel(logging.WARNING)`
"""


Note:
While this is clear to active users of the logging module, it is not clear to novices, who want INFO in their applications but not from asyncio.

----------
assignee: docs at python
components: Documentation
messages: 217952
nosy: docs at python, hardkrash
priority: normal
severity: normal
status: open
title: asyncoio logging documentation clarifications.
type: enhancement
versions: Python 3.4, Python 3.5

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

From report at bugs.python.org  Tue May  6 16:08:21 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 06 May 2014 14:08:21 +0000
Subject: [docs] [issue21366] Document that return in finally overwrites prev
	value
In-Reply-To: <1398615139.09.0.290952002497.issue21366@psf.upfronthosting.co.za>
Message-ID: <3gNN7n0d3Wz7LtY@mail.python.org>


Roundup Robot added the comment:

New changeset faaa8d569664 by Zachary Ware in branch '3.4':
Issue #21366: Document the fact that ``return`` in a ``finally`` clause
http://hg.python.org/cpython/rev/faaa8d569664

New changeset 685f92aad1dc by Zachary Ware in branch 'default':
Issue #21366: Document the fact that ``return`` in a ``finally`` clause
http://hg.python.org/cpython/rev/685f92aad1dc

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

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

From report at bugs.python.org  Tue May  6 16:10:28 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 06 May 2014 14:10:28 +0000
Subject: [docs] [issue21366] Document that return in finally overwrites prev
	value
In-Reply-To: <1398615139.09.0.290952002497.issue21366@psf.upfronthosting.co.za>
Message-ID: <3gNNBC4tZlzRGY@mail.python.org>


Roundup Robot added the comment:

New changeset 7fabe3652ee0 by Zachary Ware in branch '2.7':
Issue #21366: Document the fact that ``return`` in a ``finally`` clause
http://hg.python.org/cpython/rev/7fabe3652ee0

----------

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

From report at bugs.python.org  Tue May  6 16:12:14 2014
From: report at bugs.python.org (Zachary Ware)
Date: Tue, 06 May 2014 14:12:14 +0000
Subject: [docs] [issue21366] Document that return in finally overwrites prev
	value
In-Reply-To: <1398615139.09.0.290952002497.issue21366@psf.upfronthosting.co.za>
Message-ID: <1399385534.7.0.731432491091.issue21366@psf.upfronthosting.co.za>


Zachary Ware added the comment:

Done. Thanks pointing out just how redundant that parenthetical was (I don't know how that slipped through my brain...), David.  And thank you Jon for the report!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 2.7

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

From report at bugs.python.org  Tue May  6 18:59:17 2014
From: report at bugs.python.org (Tim Golden)
Date: Tue, 06 May 2014 16:59:17 +0000
Subject: [docs] [issue21382] Signal module doesnt raises ValueError Exception
In-Reply-To: <1398759436.39.0.420418396293.issue21382@psf.upfronthosting.co.za>
Message-ID: <1399395557.07.0.990988116158.issue21382@psf.upfronthosting.co.za>


Tim Golden added the comment:

To be honest I can't get excited about this one. The only sensible change is to remove the rather specific comment about ValueError and just leave the fact that only certain signals are valid. 

Because the C code defines module-level constants on the basis of whether the platform C-lib defines them, different platforms will have different module attributes. It would be unusual for us to list all the combinations.

Adding Brian Curtin as he made the original change.

----------
nosy: +brian.curtin, tim.golden

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

From report at bugs.python.org  Tue May  6 21:30:39 2014
From: report at bugs.python.org (Tim Golden)
Date: Tue, 06 May 2014 19:30:39 +0000
Subject: [docs] [issue13030] Be more generic when identifying the Windows
	main dir in	installation doc
In-Reply-To: <1316727111.41.0.373563358156.issue13030@psf.upfronthosting.co.za>
Message-ID: <1399404639.22.0.163709916471.issue13030@psf.upfronthosting.co.za>


Tim Golden added the comment:

This is essentially superseded now by the work done over on distutils-sig and by the PyPA. (Which has included considering the differeng terminology of installation vs other paths on Windows vs Unix).

----------
resolution:  -> wont fix
stage: needs patch -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue May  6 21:45:51 2014
From: report at bugs.python.org (Ned Deily)
Date: Tue, 06 May 2014 19:45:51 +0000
Subject: [docs] [issue21443] asyncio logging documentation clarifications
In-Reply-To: <1399321197.68.0.955361534546.issue21443@psf.upfronthosting.co.za>
Message-ID: <1399405551.78.0.632560223901.issue21443@psf.upfronthosting.co.za>


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


----------
stage:  -> needs patch
title: asyncoio logging documentation clarifications. -> asyncio logging documentation clarifications

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

From report at bugs.python.org  Wed May  7 03:29:35 2014
From: report at bugs.python.org (R. David Murray)
Date: Wed, 07 May 2014 01:29:35 +0000
Subject: [docs] [issue21300] Docs (incorrectly) suggest email.policy.default
	is the	default policy
In-Reply-To: <1397829088.9.0.524887326408.issue21300@psf.upfronthosting.co.za>
Message-ID: <1399426175.26.0.968333810262.issue21300@psf.upfronthosting.co.za>


Changes by R. David Murray <rdmurray at bitdance.com>:


----------
components: +email
nosy: +barry

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

From report at bugs.python.org  Wed May  7 03:33:12 2014
From: report at bugs.python.org (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Wed, 07 May 2014 01:33:12 +0000
Subject: [docs] [issue21415] Python __new__ method doc typo (it's a class
	and not a	static method)
In-Reply-To: <1399026596.96.0.389694886975.issue21415@psf.upfronthosting.co.za>
Message-ID: <1399426392.09.0.803993837232.issue21415@psf.upfronthosting.co.za>


Changes by Jes?s Cea Avi?n <jcea at jcea.es>:


----------
nosy: +jcea

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

From report at bugs.python.org  Wed May  7 03:34:18 2014
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 07 May 2014 01:34:18 +0000
Subject: [docs] [issue21300] Docs (incorrectly) suggest email.policy.default
	is the	default policy
In-Reply-To: <1397829088.9.0.524887326408.issue21300@psf.upfronthosting.co.za>
Message-ID: <3gNgMD6qJnz7Ljb@mail.python.org>


Roundup Robot added the comment:

New changeset d994d75cce95 by R David Murray in branch '3.4':
#21300: Clean up the docs for the email "policy" arguments.
http://hg.python.org/cpython/rev/d994d75cce95

New changeset 63fa945119cb by R David Murray in branch 'default':
Merge: #21300: Clean up the docs for the email "policy" arguments.
http://hg.python.org/cpython/rev/63fa945119cb

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

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

From report at bugs.python.org  Wed May  7 03:35:21 2014
From: report at bugs.python.org (R. David Murray)
Date: Wed, 07 May 2014 01:35:21 +0000
Subject: [docs] [issue21300] Docs (incorrectly) suggest email.policy.default
	is the	default policy
In-Reply-To: <1397829088.9.0.524887326408.issue21300@psf.upfronthosting.co.za>
Message-ID: <1399426521.0.0.490419899381.issue21300@psf.upfronthosting.co.za>


R. David Murray added the comment:

Thanks for the heads up.

policy.default will become the default policy eventually, but first the new stuff has to get out of provisional status (which I expect will happen in 3.5).

I did a pass over the documentation of all of the policy arguments and cleaned things up.  The policy args got added at different points during development and this is the first time I looked at all of them together.  There were a number of inconsistencies (and a couple more errors).

----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
versions:  -Python 3.3

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

From report at bugs.python.org  Thu May  8 15:37:55 2014
From: report at bugs.python.org (Merlijn van Deen)
Date: Thu, 08 May 2014 13:37:55 +0000
Subject: [docs] [issue21300] Docs (incorrectly) suggest email.policy.default
	is the	default policy
In-Reply-To: <1397829088.9.0.524887326408.issue21300@psf.upfronthosting.co.za>
Message-ID: <1399556274.87.0.57882916967.issue21300@psf.upfronthosting.co.za>


Merlijn van Deen added the comment:

Small typo that slipped in:

'udpate' instead of 'update' on the following lines:

http://hg.python.org/cpython/rev/63fa945119cb#l2.18
http://hg.python.org/cpython/rev/63fa945119cb#l2.43
http://hg.python.org/cpython/rev/63fa945119cb#l2.66

----------

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

From report at bugs.python.org  Thu May  8 16:06:34 2014
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 08 May 2014 14:06:34 +0000
Subject: [docs] [issue21300] Docs (incorrectly) suggest email.policy.default
	is the	default policy
In-Reply-To: <1397829088.9.0.524887326408.issue21300@psf.upfronthosting.co.za>
Message-ID: <3gPc0n01g7z7Ljr@mail.python.org>


Roundup Robot added the comment:

New changeset 9e55089aa505 by R David Murray in branch '3.4':
#21300: fix typo
http://hg.python.org/cpython/rev/9e55089aa505

New changeset 232938736a31 by R David Murray in branch 'default':
Merge #21300: fix typo
http://hg.python.org/cpython/rev/232938736a31

----------

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

From report at bugs.python.org  Thu May  8 16:07:12 2014
From: report at bugs.python.org (R. David Murray)
Date: Thu, 08 May 2014 14:07:12 +0000
Subject: [docs] [issue21300] Docs (incorrectly) suggest email.policy.default
	is the	default policy
In-Reply-To: <1397829088.9.0.524887326408.issue21300@psf.upfronthosting.co.za>
Message-ID: <1399558032.67.0.568670050973.issue21300@psf.upfronthosting.co.za>


R. David Murray added the comment:

That was actually copy and paste of an existing typo, which I've also now fixed.  Thanks.

----------

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

From report at bugs.python.org  Thu May  8 21:05:06 2014
From: report at bugs.python.org (John Isidore)
Date: Thu, 08 May 2014 19:05:06 +0000
Subject: [docs] [issue21454] asyncio's loop.connect_read_pipe makes
	pipes	non-blocking contrary to the documentation
Message-ID: <1399575906.07.0.344601032189.issue21454@psf.upfronthosting.co.za>


New submission from John Isidore:

the documentation for BaseEventLoop.connect_read_pipe says: 

> "pipe is file-like object **already switched** to nonblocking."

http://hg.python.org/cpython/file/232938736a31/Doc/library/asyncio-eventloop.rst#l453

But it looks like connect_read_pipe() accepts blocking pipes and switches
them to non-blocking mode:

> "It looks like connect_read_pipe() (eventually) sets the fd to non-blocking. So it does work."

https://code.google.com/p/tulip/source/detail?r=0a716436176993a12cf861b6cafffe8a31bc1127

If it is indeed the case then the documentation should mention that it
accepts blocking pipes and makes them non-blocking.

May it break other processes by making the file non-blocking if it is a pty
that is shared between processes? 

Related: "Don't set shared file descriptors to non-blocking I/O mode."
http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/dont-set-shared-file-descriptors-to-non-blocking-mode.html

----------
assignee: docs at python
components: Documentation
messages: 218120
nosy: John Isidore, docs at python, gvanrossum
priority: normal
severity: normal
status: open
title: asyncio's loop.connect_read_pipe makes pipes non-blocking contrary to the documentation
type: behavior
versions: Python 3.4, Python 3.5

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

From report at bugs.python.org  Thu May  8 22:21:36 2014
From: report at bugs.python.org (Guido van Rossum)
Date: Thu, 08 May 2014 20:21:36 +0000
Subject: [docs] [issue21454] asyncio's loop.connect_read_pipe makes
	pipes	non-blocking contrary to the documentation
In-Reply-To: <1399575906.07.0.344601032189.issue21454@psf.upfronthosting.co.za>
Message-ID: <1399580496.84.0.381200936639.issue21454@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Thanks for the report, that should be easy to fix.

Regarding PTYs, we're aware: https://code.google.com/p/tulip/issues/detail?id=147

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

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

From report at bugs.python.org  Fri May  9 14:49:13 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 09 May 2014 12:49:13 +0000
Subject: [docs] [issue20837] Ambiguity words in base64 documentation
In-Reply-To: <1393803500.52.0.641070246037.issue20837@psf.upfronthosting.co.za>
Message-ID: <1399639753.27.0.737186864941.issue20837@psf.upfronthosting.co.za>


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


----------
stage:  -> patch review
type:  -> enhancement

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

From bothenta at gmail.com  Fri May  9 10:40:50 2014
From: bothenta at gmail.com (1 2)
Date: Fri, 9 May 2014 16:40:50 +0800
Subject: [docs] Where can I get help about python3?
In-Reply-To: <CAPKGKcNcPRi5dfeuCK_Q-zjD-=D3yXZpRVAdQ1j9sqA3uObJUg@mail.gmail.com>
References: <CAPKGKcOerVtCUir0O6LzZhZvFU+oQrgBfPc+-FmE6EQVugA1qQ@mail.gmail.com>
 <CAPKGKcNcPRi5dfeuCK_Q-zjD-=D3yXZpRVAdQ1j9sqA3uObJUg@mail.gmail.com>
Message-ID: <CAPKGKcOQrT+1EfyLQ=ya5ZnVkZvMZ0MR4Pxs57DKqvB5snd5Sg@mail.gmail.com>

Hi there,
  I am just a rookie who just started to learn python and I am going to
start right from python3. Pls, help
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140509/8bd93384/attachment.html>

From zachary.ware+pydocs at gmail.com  Fri May  9 15:46:18 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Fri, 9 May 2014 08:46:18 -0500
Subject: [docs] Where can I get help about python3?
In-Reply-To: <CAPKGKcOQrT+1EfyLQ=ya5ZnVkZvMZ0MR4Pxs57DKqvB5snd5Sg@mail.gmail.com>
References: <CAPKGKcOerVtCUir0O6LzZhZvFU+oQrgBfPc+-FmE6EQVugA1qQ@mail.gmail.com>
 <CAPKGKcNcPRi5dfeuCK_Q-zjD-=D3yXZpRVAdQ1j9sqA3uObJUg@mail.gmail.com>
 <CAPKGKcOQrT+1EfyLQ=ya5ZnVkZvMZ0MR4Pxs57DKqvB5snd5Sg@mail.gmail.com>
Message-ID: <CAKJDb-N2Y+jzv0MLSdA7NEvqeoZTvMJm04mnk9WRmtUHhzjVQg@mail.gmail.com>

Hi,

On Fri, May 9, 2014 at 3:40 AM, 1 2 <bothenta at gmail.com> wrote:
> Hi there,
>   I am just a rookie who just started to learn python and I am going to
> start right from python3. Pls, help

You can email the Python Tutor list, tutor at python.org, which is a
friendly place with several highly experienced Pythonistas who are
willing to help.  Be sure to ask specific questions though, just
saying "help!" isn't likely to get you much help :).  Also be aware
that the list itself will be your tutor; it is not a place to find an
individual tutor.

And finally, please remember that *this* list (docs at python.org) is
meant for discussions about Python's documentation.  General usage
questions, or other Python-related queries can be sent to
python-list at python.org.

Welcome to Python!  We hope you enjoy learning and using our language!
-- 
Zach

From report at bugs.python.org  Fri May  9 19:27:03 2014
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 09 May 2014 17:27:03 +0000
Subject: [docs] [issue21434] python -3 documentation is outdated
In-Reply-To: <1399281658.38.0.402381658113.issue21434@psf.upfronthosting.co.za>
Message-ID: <1399656423.17.0.234322684401.issue21434@psf.upfronthosting.co.za>


?ric Araujo added the comment:

Aside: callable was added back in 3.2; warnings for that are now obsolete, and people often replaced it with bogus alternatives (like using hasattr on the object instead of its type).

----------
nosy: +eric.araujo

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

From report at bugs.python.org  Fri May  9 19:31:43 2014
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 09 May 2014 17:31:43 +0000
Subject: [docs] [issue21439] Numerous minor issues in Language Reference
In-Reply-To: <1399300451.92.0.450554829588.issue21439@psf.upfronthosting.co.za>
Message-ID: <1399656702.83.0.164562970403.issue21439@psf.upfronthosting.co.za>


?ric Araujo added the comment:

Attaching plain text version.

----------
nosy: +eric.araujo
Added file: http://bugs.python.org/file35201/PythonRefmanual_3_4_0_Errata.txt

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

From report at bugs.python.org  Fri May  9 19:36:21 2014
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 09 May 2014 17:36:21 +0000
Subject: [docs] [issue21439] Numerous minor issues in Language Reference
In-Reply-To: <1399300451.92.0.450554829588.issue21439@psf.upfronthosting.co.za>
Message-ID: <1399656981.5.0.469928291148.issue21439@psf.upfronthosting.co.za>


?ric Araujo added the comment:

BTW my opinion of the proposed changes is that many of them are good (obvious typos, reports of things unclear to a beginner, etc) but I don?t agree with some typographic changes, I find that some grammar changes are pedantic, and there are even a few misunderstandings of Python.

----------

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

From report at bugs.python.org  Sat May 10 03:14:04 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 10 May 2014 01:14:04 +0000
Subject: [docs] [issue21439] Numerous minor issues in Language Reference
In-Reply-To: <1399300451.92.0.450554829588.issue21439@psf.upfronthosting.co.za>
Message-ID: <1399684444.76.0.556085973276.issue21439@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

I suggest at least a patch per chapter (3.x.y, 4.x.y, 6.x.y, ...).

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

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

From report at bugs.python.org  Sat May 10 13:34:04 2014
From: report at bugs.python.org (Apteris)
Date: Sat, 10 May 2014 11:34:04 +0000
Subject: [docs] [issue21466] General Index link to del statement is wrong
Message-ID: <1399721644.32.0.749674038876.issue21466@psf.upfronthosting.co.za>


New submission from Apteris:

In the documentation index, https://docs.python.org/2/genindex-D.html, the link to the del statement documentation is not 

https://docs.python.org/2/reference/simple_stmts.html#del

as it presumably should be, but

https://docs.python.org/2/reference/datamodel.html#index-25

Affects all versions, but with a different wrong link in each one, as follows:
Python 2.7: https://docs.python.org/2/reference/datamodel.html#index-25
Python 3.2: https://docs.python.org/3.2/reference/datamodel.html#index-21
Python 3.3: https://docs.python.org/3.3/reference/datamodel.html#index-22
Python 3.4: https://docs.python.org/3.4/reference/datamodel.html#index-22
Python 3.5: https://docs.python.org/3.5/reference/datamodel.html#index-22

The del statement is in each case documented at https://docs.python.org/[version number]/reference/simple_stmts.html#del.

----------
assignee: docs at python
components: Documentation
messages: 218217
nosy: apteris, docs at python
priority: normal
severity: normal
status: open
title: General Index link to del statement is wrong
type: behavior
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5

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

From report at bugs.python.org  Sat May 10 14:54:56 2014
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 10 May 2014 12:54:56 +0000
Subject: [docs] [issue21466] General Index link to del statement is wrong
In-Reply-To: <1399721644.32.0.749674038876.issue21466@psf.upfronthosting.co.za>
Message-ID: <1399726496.88.0.866306837691.issue21466@psf.upfronthosting.co.za>


Changes by Berker Peksag <berker.peksag at gmail.com>:


----------
versions:  -Python 3.1, Python 3.2, Python 3.3

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

From report at bugs.python.org  Sat May 10 22:28:39 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 10 May 2014 20:28:39 +0000
Subject: [docs] [issue21439] Numerous minor issues in Language Reference
In-Reply-To: <1399300451.92.0.450554829588.issue21439@psf.upfronthosting.co.za>
Message-ID: <1399753719.05.0.533726167504.issue21439@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

I also don't agree with most of the typographic changes and, like ?ric find some of the grammar changes to be pedantic.

The OP refers to his own changes as "editorial infelicities".  This should have been a warning sign.

The OP further warns, "I have been reading the Language Reference Manual in order to teach myself Python 3" which explains why ?ric has found " a few misunderstandings of Python".

If the OP cares enough to prepare a chapter by chapter patch (as suggested by Terry), I would be happy to review them one by one, applying any that are actual readability improvements.

----------
assignee: zach.ware -> rhettinger
nosy: +rhettinger
priority: normal -> low
versions:  -Python 3.4

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

From report at bugs.python.org  Sun May 11 01:52:56 2014
From: report at bugs.python.org (Rose Ames)
Date: Sat, 10 May 2014 23:52:56 +0000
Subject: [docs] [issue21221] Minor struct_time documentation bug
In-Reply-To: <1397500160.88.0.743491348049.issue21221@psf.upfronthosting.co.za>
Message-ID: <1399765976.84.0.26214720409.issue21221@psf.upfronthosting.co.za>


Changes by Rose Ames <rose at happyspork.com>:


----------
keywords: +patch
Added file: http://bugs.python.org/file35211/tm_isdst.patch

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

From report at bugs.python.org  Sun May 11 02:01:28 2014
From: report at bugs.python.org (Alexander Belopolsky)
Date: Sun, 11 May 2014 00:01:28 +0000
Subject: [docs] [issue21221] Minor struct_time documentation bug
In-Reply-To: <1397500160.88.0.743491348049.issue21221@psf.upfronthosting.co.za>
Message-ID: <1399766488.41.0.0324657212944.issue21221@psf.upfronthosting.co.za>


Alexander Belopolsky added the comment:

> .. 0 when it is not.  -1 indicates that ..

It does not read well when the sentence starts with a number.  Consider rephrasing as "The value of -1 .." or something like that.

----------

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

From report at bugs.python.org  Sun May 11 02:06:28 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 11 May 2014 00:06:28 +0000
Subject: [docs] [issue21198] Minor tarfile documentation bug
In-Reply-To: <1397148227.41.0.631676560193.issue21198@psf.upfronthosting.co.za>
Message-ID: <1399766788.32.0.00626530724178.issue21198@psf.upfronthosting.co.za>


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


----------
stage:  -> needs patch
type:  -> enhancement

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

From report at bugs.python.org  Sun May 11 03:47:24 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 11 May 2014 01:47:24 +0000
Subject: [docs] [issue20872] dbm/gdbm/ndbm close methods are not document
In-Reply-To: <1394297879.28.0.882591650164.issue20872@psf.upfronthosting.co.za>
Message-ID: <1399772844.83.0.419419837228.issue20872@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation
keywords: +easy
nosy: +docs at python
stage:  -> needs patch
type:  -> enhancement

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

From report at bugs.python.org  Sun May 11 20:19:23 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 11 May 2014 18:19:23 +0000
Subject: [docs] [issue21466] General Index link to del statement is wrong
In-Reply-To: <1399721644.32.0.749674038876.issue21466@psf.upfronthosting.co.za>
Message-ID: <3gRYT63SQcz7Ljb@mail.python.org>


Roundup Robot added the comment:

New changeset 951775c68b1b by Benjamin Peterson in branch '2.7':
remove confusing delete indexing (closes #21466)
http://hg.python.org/cpython/rev/951775c68b1b

New changeset 2e26703d7d2a by Benjamin Peterson in branch '3.4':
remove confusing delete indexing (closes #21466)
http://hg.python.org/cpython/rev/2e26703d7d2a

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

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

From report at bugs.python.org  Mon May 12 00:51:28 2014
From: report at bugs.python.org (Rose Ames)
Date: Sun, 11 May 2014 22:51:28 +0000
Subject: [docs] [issue21221] Minor struct_time documentation bug
In-Reply-To: <1397500160.88.0.743491348049.issue21221@psf.upfronthosting.co.za>
Message-ID: <1399848688.19.0.792494577397.issue21221@psf.upfronthosting.co.za>


Rose Ames added the comment:

Thanks for the quick feedback!  Altered to "A value of -1..."

----------
nosy: +superluser
Added file: http://bugs.python.org/file35219/tm_isdst2.patch

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

From report at bugs.python.org  Mon May 12 11:29:13 2014
From: report at bugs.python.org (Jakub Wilk)
Date: Mon, 12 May 2014 09:29:13 +0000
Subject: [docs] [issue21221] Minor struct_time documentation bug
In-Reply-To: <1397500160.88.0.743491348049.issue21221@psf.upfronthosting.co.za>
Message-ID: <1399886953.23.0.936753360355.issue21221@psf.upfronthosting.co.za>


Changes by Jakub Wilk <jwilk at jwilk.net>:


----------
nosy: +jwilk

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

From report at bugs.python.org  Mon May 12 16:51:22 2014
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 12 May 2014 14:51:22 +0000
Subject: [docs] [issue21198] Minor tarfile documentation bug
In-Reply-To: <1397148227.41.0.631676560193.issue21198@psf.upfronthosting.co.za>
Message-ID: <1399906282.38.0.12755598513.issue21198@psf.upfronthosting.co.za>


Changes by Berker Peksag <berker.peksag at gmail.com>:


----------
nosy: +berker.peksag, serhiy.storchaka
stage: needs patch -> patch review
Added file: http://bugs.python.org/file35223/issue21198.diff

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

From report at bugs.python.org  Mon May 12 17:01:39 2014
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 12 May 2014 15:01:39 +0000
Subject: [docs] [issue21479] Document TarFile.open() as a classmethod
Message-ID: <1399906899.24.0.584343681531.issue21479@psf.upfronthosting.co.za>


New submission from Berker Peksag:

The patch also updates the signature of TarFile.open().

----------
assignee: docs at python
components: Documentation
files: tarfile-open-classmethod.diff
keywords: patch
messages: 218323
nosy: berker.peksag, docs at python, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Document TarFile.open() as a classmethod
versions: Python 2.7, Python 3.4, Python 3.5
Added file: http://bugs.python.org/file35225/tarfile-open-classmethod.diff

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

From report at bugs.python.org  Mon May 12 17:34:47 2014
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 12 May 2014 15:34:47 +0000
Subject: [docs] [issue20872] dbm/gdbm/ndbm close methods are not document
In-Reply-To: <1394297879.28.0.882591650164.issue20872@psf.upfronthosting.co.za>
Message-ID: <1399908887.64.0.858914373173.issue20872@psf.upfronthosting.co.za>


Changes by Berker Peksag <berker.peksag at gmail.com>:


----------
keywords: +patch
nosy: +berker.peksag
stage: needs patch -> patch review
versions:  -Python 3.3
Added file: http://bugs.python.org/file35226/issue20872.diff

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

From report at bugs.python.org  Mon May 12 18:10:09 2014
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 12 May 2014 16:10:09 +0000
Subject: [docs] [issue20969] Author of EPUB version of Python docs is set to
	Unknown	instead of PSF
In-Reply-To: <1395153249.12.0.327856107433.issue20969@psf.upfronthosting.co.za>
Message-ID: <1399911009.03.0.255908468545.issue20969@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Here's a patch. I followed Antoine's name suggestion.

PSF would more suitable for the "epub_publisher" option:

http://sphinx-doc.org/config.html#confval-epub_publisher

----------
keywords: +patch
nosy: +berker.peksag
stage: needs patch -> patch review
Added file: http://bugs.python.org/file35227/issue20969.diff

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

From report at bugs.python.org  Mon May 12 18:58:01 2014
From: report at bugs.python.org (Feliks)
Date: Mon, 12 May 2014 16:58:01 +0000
Subject: [docs] [issue21484] More clarity needed about difference between "x
	+= e"	and "x = x + e"
Message-ID: <1399913881.84.0.586979222354.issue21484@psf.upfronthosting.co.za>


New submission from Feliks:

In Sec. 7.2.1 of the Language Reference, in the description of "+=" we have: "Also, when possible, the actual operation is performed in-place, meaning that rather than creating a new object and assigning that to the target, the old object is modified instead."
Although this is quite accurate, not all the consequences are immediately obvious, and sometimes they are quite serious.  I would suggest adding a note that points the reader's attention in particular to the phenomenon exhibited in the following example:
>>> def f(ls):  ls += [2]
... 
>>> def g(ls):  ls = ls + [2]
... 
>>> a = [1]
>>> g(a)
>>> a
[1]
>>> f(a)
>>> a
[1, 2]

----------
assignee: docs at python
components: Documentation
messages: 218338
nosy: Kluzniak, docs at python
priority: normal
severity: normal
status: open
title: More clarity needed about difference between "x += e" and "x = x + e"
type: enhancement
versions: Python 3.4

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

From report at bugs.python.org  Mon May 12 19:11:22 2014
From: report at bugs.python.org (Josh Rosenberg)
Date: Mon, 12 May 2014 17:11:22 +0000
Subject: [docs] [issue21484] More clarity needed about difference between "x
	+= e"	and "x = x + e"
In-Reply-To: <1399913881.84.0.586979222354.issue21484@psf.upfronthosting.co.za>
Message-ID: <1399914682.35.0.79435782779.issue21484@psf.upfronthosting.co.za>


Josh Rosenberg added the comment:

It seems to me like that is one of the most obvious consequences. How is this not an immediately obvious consequence?

----------
nosy: +josh.rosenberg

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

From report at bugs.python.org  Mon May 12 19:59:23 2014
From: report at bugs.python.org (akira)
Date: Mon, 12 May 2014 17:59:23 +0000
Subject: [docs] [issue21485] remove unnecesary .flush() calls in the
	asyncio	subprocess code example
Message-ID: <1399917563.48.0.572590350966.issue21485@psf.upfronthosting.co.za>


New submission from akira:

The current code example contains [1]:

    print("Python failed with exit code %s:" % exitcode)
    sys.stdout.flush()
    sys.stdout.buffer.flush()
    sys.stdout.buffer.write(stdout)
    sys.stdout.buffer.flush()

that looks bizarre.

Either a comment should be added that explains why the `.flush()` calls
are necessary or they should be removed.

I've attached the documentation patch that removes the calls.

[1] http://hg.python.org/cpython/file/2af5a52b9b87/Doc/library/asyncio-subprocess.rst#l227

----------
assignee: docs at python
components: Documentation
files: docs-subprocess-remove-unnecessary-flush-from-code-example.patch
keywords: patch
messages: 218342
nosy: akira, docs at python
priority: normal
severity: normal
status: open
title: remove unnecesary .flush() calls in the asyncio subprocess code example
versions: Python 3.4, Python 3.5
Added file: http://bugs.python.org/file35230/docs-subprocess-remove-unnecessary-flush-from-code-example.patch

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

From report at bugs.python.org  Mon May 12 21:09:40 2014
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 12 May 2014 19:09:40 +0000
Subject: [docs] [issue21485] remove unnecesary .flush() calls in the
	asyncio	subprocess code example
In-Reply-To: <1399917563.48.0.572590350966.issue21485@psf.upfronthosting.co.za>
Message-ID: <1399921780.93.0.645673758816.issue21485@psf.upfronthosting.co.za>


Changes by Berker Peksag <berker.peksag at gmail.com>:


----------
nosy: +giampaolo.rodola, gvanrossum, haypo, pitrou, yselivanov

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

From report at bugs.python.org  Mon May 12 23:25:35 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 12 May 2014 21:25:35 +0000
Subject: [docs] [issue21485] remove unnecesary .flush() calls in the
	asyncio	subprocess code example
In-Reply-To: <1399917563.48.0.572590350966.issue21485@psf.upfronthosting.co.za>
Message-ID: <3gSFYV3RwJz7LjP@mail.python.org>


Roundup Robot added the comment:

New changeset c0404f0da01a by Victor Stinner in branch '3.4':
Issue #21485: remove unnecesary .flush() calls in the asyncio subprocess code
http://hg.python.org/cpython/rev/c0404f0da01a

New changeset 3c26389d741c by Victor Stinner in branch 'default':
(Merge 3.4) Issue #21485: remove unnecesary .flush() calls in the asyncio
http://hg.python.org/cpython/rev/3c26389d741c

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

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

From report at bugs.python.org  Mon May 12 23:26:08 2014
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 12 May 2014 21:26:08 +0000
Subject: [docs] [issue21485] remove unnecesary .flush() calls in the
	asyncio	subprocess code example
In-Reply-To: <1399917563.48.0.572590350966.issue21485@psf.upfronthosting.co.za>
Message-ID: <1399929968.57.0.0264177491948.issue21485@psf.upfronthosting.co.za>


STINNER Victor added the comment:

I wrote the example and the first call to buffer.flush() is a mistake. Thanks for your patch, I applied it.

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

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

From report at bugs.python.org  Tue May 13 01:18:57 2014
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 12 May 2014 23:18:57 +0000
Subject: [docs] [issue21437] document that asyncio.ProactorEventLoop doesn't
	support	SSL
In-Reply-To: <1399296732.42.0.791038898639.issue21437@psf.upfronthosting.co.za>
Message-ID: <1399936737.81.0.935227933984.issue21437@psf.upfronthosting.co.za>


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


----------
nosy: +gvanrossum, haypo, yselivanov

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

From report at bugs.python.org  Tue May 13 01:37:30 2014
From: report at bugs.python.org (Brad Aylsworth)
Date: Mon, 12 May 2014 23:37:30 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
Message-ID: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>


New submission from Brad Aylsworth:

The documentation page for codecs (https://docs.python.org/2/library/codecs.html) shows keyword arguments for codecs.encode and codecs.decode, but they throw an error if keyword arguments are used. codecs.decode.__doc__ reports 'decode(obj, [encoding[,errors]]) -> object.

This happens on both 2.7.6 and 3.4.0.

----------
assignee: docs at python
components: Documentation
messages: 218380
nosy: Ouaouaron, docs at python
priority: normal
severity: normal
status: open
title: codecs.encode/decode documentation inconsistency
type: resource usage
versions: Python 2.7

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

From report at bugs.python.org  Tue May 13 03:03:38 2014
From: report at bugs.python.org (Eric Snow)
Date: Tue, 13 May 2014 01:03:38 +0000
Subject: [docs] [issue21415] Python __new__ method doc typo (it's a class
	and not a	static method)
In-Reply-To: <1399026596.96.0.389694886975.issue21415@psf.upfronthosting.co.za>
Message-ID: <1399943018.5.0.638087447386.issue21415@psf.upfronthosting.co.za>


Eric Snow added the comment:

FYI, __new__() is a staticmethod to accommodate subclassing.  Several things that happen at instantiation-time (when __new__() is called), including memory allocation, are tied to the class that is passed in and may be different for subclasses.   For example:

class Spam(int):
    def __new__(cls, value):
        self = super().__new__(Spam, value)
        self._eggs = 10
        return self

Spam is passed in instead of int (as would happen if it were a classmethod), resulting in extra memory being allocated for _eggs (and for __dict__ among other things).

----------
nosy: +eric.snow

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

From report at bugs.python.org  Tue May 13 06:23:40 2014
From: report at bugs.python.org (Alexey)
Date: Tue, 13 May 2014 04:23:40 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1399955020.37.0.966410970552.issue21430@psf.upfronthosting.co.za>


Alexey added the comment:

Please document this method.

I'm developing xmpp client using python 3.4 and it's ssl module. Stuck with this same issue for a few days just because of a lack of documentation.

I'm asking you: why should I know about this method not from python documentation, but from search engine and perl's forum (http://www.perlmonks.org/?node_id=845342) ?

----------
nosy: +Animus

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

From report at bugs.python.org  Tue May 13 07:59:23 2014
From: report at bugs.python.org (Bas Wijnen)
Date: Tue, 13 May 2014 05:59:23 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1399960763.71.0.426583405135.issue21430@psf.upfronthosting.co.za>


Bas Wijnen added the comment:

The documentation about non-blocking is clear enough, thank you for pointing it out.

However, I would ask to write anything in there that contains the word "pending".  The reason is that I didn't find anything in the documentation, looked in the source, found the pending() method and searched the documentation to see how it was defined.  If I would have found an explanation that I shouldn't be using it, even if that wasn't the documentation of the method, I would have done the right thing in my program.

----------

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

From report at bugs.python.org  Tue May 13 11:52:15 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 13 May 2014 09:52:15 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1399974735.04.0.758144557155.issue21430@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

For the record, SSLSocket.pending() was added in b59825d9db8f with the commit message "get SSL support to work again". It isn't used anywhere in the stdlib. It isn't used by asyncio, Tornado or Twisted. It isn't necessary to write non-blocking SSL applications, and it can actually lead to misunderstandings as some messages on this issue show.

I'd rather deprecate the method than start documentating it.

----------

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

From report at bugs.python.org  Tue May 13 12:25:02 2014
From: report at bugs.python.org (Feliks)
Date: Tue, 13 May 2014 10:25:02 +0000
Subject: [docs] [issue21484] More clarity needed about difference between "x
	+= e"	and "x = x + e"
In-Reply-To: <1399913881.84.0.586979222354.issue21484@psf.upfronthosting.co.za>
Message-ID: <1399976702.67.0.241531647636.issue21484@psf.upfronthosting.co.za>


Feliks added the comment:

Well, there is some anecdotal evidence. ;-)  I happen to have a lot of experience with a lot of programming languages, and I was bitten by this.

Let's put it like this: it is quite easy to overlook the significance of the sentence in question.  One looks at the paragraph, reads the stuff about evaluation, thinks "of course" and moves on.

If the sentence were in a new paragraph, and instead of with "Also" began with something like "More importantly", then it might have drawn more attention.

After all, the drastic semantic difference between the two forms is quite unlike what one is used to from programming in, say, C.  I think it would be helpful if it were stressed a little bit more.

----------

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

From report at bugs.python.org  Tue May 13 12:47:46 2014
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 13 May 2014 10:47:46 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
In-Reply-To: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>
Message-ID: <1399978066.68.0.973274515779.issue21488@psf.upfronthosting.co.za>


Changes by Berker Peksag <berker.peksag at gmail.com>:


----------
keywords: +patch
nosy: +berker.peksag, ncoghlan
stage:  -> patch review
type: resource usage -> behavior
versions: +Python 3.4, Python 3.5
Added file: http://bugs.python.org/file35240/issue21488.diff

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

From report at bugs.python.org  Tue May 13 12:49:11 2014
From: report at bugs.python.org (Alexey Gorshkov)
Date: Tue, 13 May 2014 10:49:11 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1399978151.14.0.0324160818786.issue21430@psf.upfronthosting.co.za>


Alexey Gorshkov added the comment:

Ok. As https://docs.python.org/dev/library/ssl.html#notes-on-non-blocking-sockets says: "Calling select() tells you that the OS-level socket can be read from (or written to)", and here is situation: len(select([ssl_socket],[],[], 0.2)[0]) returns 0, but ssl layer has pending data and "SSLWantWriteError or SSLWantReadError instead of BlockingIOError" are not raised, because there is no error.. How should app know what it's need to do another recv() call? Are You suggesting to make loop like this (as for non-blocking socket)?

while True:
    ssl_socket.recv(4096)
    if something:
        break


what I think is: pending() method - is fine solution for knowing needed information about ssl layer status.

SSL_pending(3) is not deprecated in OpenSSL, and I do not see reason why it should be deprecated in python. I do not think it should be deprecated only because it is not used. And it is not need to tell about asyncio, Tornado or Twisted.

----------

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

From report at bugs.python.org  Tue May 13 12:58:05 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 13 May 2014 10:58:05 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1399978684.99.0.12215301056.issue21430@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Alexey, to quote your own link, here is the proper way:
http://www.perlmonks.org/?node_id=845640

> And it is not need to tell about asyncio, Tornado or Twisted.

Of course it is :-) It is generally far better to use an existing non-blocking I/O framework, than grow your own event loop.

----------

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

From report at bugs.python.org  Tue May 13 16:48:18 2014
From: report at bugs.python.org (Brett Cannon)
Date: Tue, 13 May 2014 14:48:18 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
In-Reply-To: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>
Message-ID: <1399992498.09.0.566499565057.issue21488@psf.upfronthosting.co.za>


Brett Cannon added the comment:

Berker's patch LGTM, so assigning to him to commit.

----------
assignee: docs at python -> berker.peksag
nosy: +brett.cannon
stage: patch review -> commit review

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

From bothenta at gmail.com  Sat May 10 02:44:42 2014
From: bothenta at gmail.com (1 2)
Date: Sat, 10 May 2014 08:44:42 +0800
Subject: [docs] Where can I get help about python3?
In-Reply-To: <CAKJDb-N2Y+jzv0MLSdA7NEvqeoZTvMJm04mnk9WRmtUHhzjVQg@mail.gmail.com>
References: <CAPKGKcOerVtCUir0O6LzZhZvFU+oQrgBfPc+-FmE6EQVugA1qQ@mail.gmail.com>
 <CAPKGKcNcPRi5dfeuCK_Q-zjD-=D3yXZpRVAdQ1j9sqA3uObJUg@mail.gmail.com>
 <CAPKGKcOQrT+1EfyLQ=ya5ZnVkZvMZ0MR4Pxs57DKqvB5snd5Sg@mail.gmail.com>
 <CAKJDb-N2Y+jzv0MLSdA7NEvqeoZTvMJm04mnk9WRmtUHhzjVQg@mail.gmail.com>
Message-ID: <CAPKGKcM8MBiZv8fiw3dpMGX0amMR32rvn9R=eBOddGjetUcdKA@mail.gmail.com>

Thanks a lot :-)
On May 9, 2014 9:46 PM, "Zachary Ware" <zachary.ware+pydocs at gmail.com>
wrote:

> Hi,
>
> On Fri, May 9, 2014 at 3:40 AM, 1 2 <bothenta at gmail.com> wrote:
> > Hi there,
> >   I am just a rookie who just started to learn python and I am going to
> > start right from python3. Pls, help
>
> You can email the Python Tutor list, tutor at python.org, which is a
> friendly place with several highly experienced Pythonistas who are
> willing to help.  Be sure to ask specific questions though, just
> saying "help!" isn't likely to get you much help :).  Also be aware
> that the list itself will be your tutor; it is not a place to find an
> individual tutor.
>
> And finally, please remember that *this* list (docs at python.org) is
> meant for discussions about Python's documentation.  General usage
> questions, or other Python-related queries can be sent to
> python-list at python.org.
>
> Welcome to Python!  We hope you enjoy learning and using our language!
> --
> Zach
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140510/6b168c2f/attachment-0001.html>

From alex at codecondo.com  Sat May 10 16:17:21 2014
From: alex at codecondo.com (alex at codecondo.com)
Date: Sat, 10 May 2014 17:17:21 +0300
Subject: [docs] Hey.
Message-ID: <eb9320f79e34786faee8b802f4f51cd7@codecondo.com>

Hey guys,

was just wondering whether it's possible to have one of my articles to 
be added to the official Python Wiki?

http://codecondo.com/10-ways-to-learn-python/

it's been getting a lot of positive feedback lately, and looks like it's 
helping a lot of beginners to get started. I hand curated that list a 
couple of weeks ago, would definitely be cool to see it as a reference 
for newcomers who begin their journey through the Wiki.

peace,
Alex

From sakthiprofessional at gmail.com  Mon May 12 12:17:12 2014
From: sakthiprofessional at gmail.com (Sakthipriyan Vairamani)
Date: Mon, 12 May 2014 10:17:12 +0000
Subject: [docs] Python 2.5 Documentation links broken
Message-ID: <CABpAV1dg=ZKDZ=9MbNjGATxjxif_qxVCOn3AR1QCO7+yhZFF=w@mail.gmail.com>

I tried to access the Python 2.5 documentation from the links on the
following pages

https://www.python.org/doc/2.5/download/
https://www.python.org/doc/2.5/

I checked Tutorial, Library reference and Language Reference. They all
return 404 page.

- Thanks and Regards,

*Sakthipriyan*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140512/26e03d06/attachment.html>

From chris at grierwhite.com  Tue May 13 00:08:17 2014
From: chris at grierwhite.com (Christopher J. White)
Date: Mon, 12 May 2014 18:08:17 -0400
Subject: [docs] Python doc google search results 3.0 vs 2.6
Message-ID: <53714651.2080103@grierwhite.com>

Hi folks,

Not sure if this is a bug or just a weirdness with google.  When I do a 
google search such as "python subprocess", the first result that comes 
back looks like the following:

Showing results for python subprocess


      17.1. /subprocess/ - /Python/ 3.4.0 documentation
      <https://docs.python.org/2/library/subprocess.html>

https://docs.*python*.org/2/library/*subprocess*.html

The /subprocess/ module allows you to spawn new processes, connect to 
their input/output/error pipes, and obtain their return codes. This 
module intends to ...

Notice the header says 3.4.0 but the link goes to python.org/2, and in 
fact when you click you are looking at the 2.x version docs.

I noticed this crop up about a week ago, I see it on lots of searches.  
I don't see any reference to 3.4.0 in the source for that file, so I'm 
not sure how it could be a python.org issue, but I'm not a search engine 
expert.

...cj

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140512/8ce25204/attachment.html>

From sf65 at gmx.com  Tue May 13 20:50:26 2014
From: sf65 at gmx.com (Steve Foley)
Date: Tue, 13 May 2014 14:50:26 -0400
Subject: [docs] mmap example
Message-ID: <20140513185026.260960@gmx.com>

Hello, I would like to submit an example for the mmap docs page. It demonstrates the use of shared memory and message passing between processes. Thanks!

------------------------------------------------------------------------------------

import mmap, os, select

NUM_CHILDREN = 30
MSG_LEN = 8
BUF_LEN = NUM_CHILDREN * MSG_LEN

buf = mmap.mmap(-1, BUF_LEN)
p = select.poll()

def write_buffer(i):
 ? ?msg = '%s\t%d\n' % (i, os.getpid())
 ? ?offset = MSG_LEN * i
 ? ?buf.seek(offset)
 ? ?buf.write(msg)

def child(i, pipeout):
 ? ?write_buffer(i)
 ? ?os.write(pipeout, 'OK\0'.encode())
 ? ?os._exit(0)

def fork(i, p):
 ? ?pipein, pipeout = os.pipe()
 ? ?if os.fork() == 0:
 ? ? ? ?child(i, pipeout)
 ? ?else:
 ? ? ? ?p.register(pipein)

def loop(msgs, p):
 ? ?while msgs:
 ? ? ? ?for fd, event in p.poll():
 ? ? ? ? ? ?p.unregister(fd)
 ? ? ? ? ? ?msgs = msgs - 1

for i in range(NUM_CHILDREN):
 ? ?fork(i, p)

loop(NUM_CHILDREN, p)

buf.seek(0)
print buf.read(BUF_LEN) 

From zachary.ware+pydocs at gmail.com  Tue May 13 21:09:30 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Tue, 13 May 2014 14:09:30 -0500
Subject: [docs] mmap example
In-Reply-To: <20140513185026.260960@gmx.com>
References: <20140513185026.260960@gmx.com>
Message-ID: <CAKJDb-MQ545JXhtmQYqwytF-uWp=Td2siZ7odc9Z7ph0H+PfLg@mail.gmail.com>

Hi Steve,

On Tue, May 13, 2014 at 1:50 PM, Steve Foley <sf65 at gmx.com> wrote:
> Hello, I would like to submit an example for the mmap docs page. It demonstrates the use of shared memory and message passing between processes. Thanks!

Would you mind creating an issue on bugs.python.org for this, and
submitting your example as a patch?  With an issue on the tracker, the
right people can be made aware of your suggestion and appropriate
action taken.

Regards,
-- 
Zach

From report at bugs.python.org  Tue May 13 21:18:53 2014
From: report at bugs.python.org (Steve Foley)
Date: Tue, 13 May 2014 19:18:53 +0000
Subject: [docs] [issue21501] submitting mmap example for use in documentation
Message-ID: <1400008733.4.0.146542624997.issue21501@psf.upfronthosting.co.za>


New submission from Steve Foley:

Hello, I would like to submit an example for the mmap docs page. It demonstrates the use of shared memory and message passing between processes. Thanks!

--------------------

import mmap, os, select

NUM_CHILDREN = 30
MSG_LEN = 8
BUF_LEN = NUM_CHILDREN * MSG_LEN

buf = mmap.mmap(-1, BUF_LEN)
p = select.poll()

def write_buffer(i):
    msg = '%s\t%d\n' % (i, os.getpid())
    offset = MSG_LEN * i
    buf.seek(offset)
    buf.write(msg)

def child(i, pipeout):
    write_buffer(i)
    os.write(pipeout, 'OK\0'.encode())
    os._exit(0)

def fork(i, p):
    pipein, pipeout = os.pipe()
    if os.fork() == 0:
        child(i, pipeout)
    else:
        p.register(pipein)

def loop(msgs, p):
    while msgs:
        for fd, event in p.poll():
            p.unregister(fd)
            msgs = msgs - 1

for i in range(NUM_CHILDREN):
    fork(i, p)

loop(NUM_CHILDREN, p)

buf.seek(0)
print buf.read(BUF_LEN)

----------
assignee: docs at python
components: Documentation
messages: 218478
nosy: docs at python, hudson
priority: normal
severity: normal
status: open
title: submitting mmap example for use in documentation
type: enhancement
versions: Python 2.7

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

From report at bugs.python.org  Tue May 13 22:13:23 2014
From: report at bugs.python.org (Steve Foley)
Date: Tue, 13 May 2014 20:13:23 +0000
Subject: [docs] [issue21501] submitting mmap example for use in documentation
In-Reply-To: <1400008733.4.0.146542624997.issue21501@psf.upfronthosting.co.za>
Message-ID: <1400012003.54.0.605655314952.issue21501@psf.upfronthosting.co.za>


Steve Foley added the comment:

sorry! this is the correct version ;-)

-------------------------------------------

import mmap, os, select

NUM_CHILDREN = 30
MSG_LEN = 9
BUF_LEN = NUM_CHILDREN * MSG_LEN

buf = mmap.mmap(-1, BUF_LEN)
p = select.poll()

def write_buffer(i):
    msg = '%s\t%d\n' % (i, os.getpid())
    offset = MSG_LEN * i
    buf.seek(offset)
    buf.write(msg)

def child(i, pipeout):
    write_buffer(i)
    os.write(pipeout, 'OK\0'.encode())
    os._exit(0)

def fork(i, p):
    pipein, pipeout = os.pipe()
    if os.fork() == 0:
        child(i, pipeout)
    else:
        p.register(pipein)

def loop(msgs, p):
    msgs = NUM_CHILDREN
    while msgs:
        for fd, event in p.poll():
            p.unregister(fd)
            msgs = msgs - 1


for i in range(NUM_CHILDREN):
    fork(i, p)

loop(NUM_CHILDREN, p)

buf.seek(0)
print buf.read(BUF_LEN)

----------

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

From report at bugs.python.org  Tue May 13 23:36:43 2014
From: report at bugs.python.org (Stefan Krah)
Date: Tue, 13 May 2014 21:36:43 +0000
Subject: [docs] [issue15871] Online docs: make index search always available.
In-Reply-To: <1346951666.84.0.523873961498.issue15871@psf.upfronthosting.co.za>
Message-ID: <1400017003.57.0.41490953126.issue15871@psf.upfronthosting.co.za>


Changes by Stefan Krah <stefan-usenet at bytereef.org>:


----------
nosy:  -skrah

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

From zachary.ware+pydocs at gmail.com  Wed May 14 01:10:51 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Tue, 13 May 2014 18:10:51 -0500
Subject: [docs] Hey.
In-Reply-To: <eb9320f79e34786faee8b802f4f51cd7@codecondo.com>
References: <eb9320f79e34786faee8b802f4f51cd7@codecondo.com>
Message-ID: <CAKJDb-OjcYjz5E=t2ZTrb+Lz+o=VStWsbdD35t=G7QOTT4APFw@mail.gmail.com>

Hi Alex,

On Sat, May 10, 2014 at 9:17 AM,  <alex at codecondo.com> wrote:
> Hey guys,
>
> was just wondering whether it's possible to have one of my articles to be
> added to the official Python Wiki?
>
> http://codecondo.com/10-ways-to-learn-python/
>
> it's been getting a lot of positive feedback lately, and looks like it's
> helping a lot of beginners to get started. I hand curated that list a couple
> of weeks ago, would definitely be cool to see it as a reference for
> newcomers who begin their journey through the Wiki.

This list is more concerned with the docs.python.org documentation,
not as much with the wiki.python.org Wiki.  Registration on the Wiki
is open to all, so you are free to edit as you like.

Regards,
-- 
Zach

From zachary.ware+pydocs at gmail.com  Wed May 14 01:17:27 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Tue, 13 May 2014 18:17:27 -0500
Subject: [docs] Python doc google search results 3.0 vs 2.6
In-Reply-To: <53714651.2080103@grierwhite.com>
References: <53714651.2080103@grierwhite.com>
Message-ID: <CAKJDb-Nbc5miwEXM67=smmOnk=cGrBxBWkZswzDc22coebn-GQ@mail.gmail.com>

Hi Chris,

On Mon, May 12, 2014 at 5:08 PM, Christopher J. White
<chris at grierwhite.com> wrote:
> Hi folks,
>
> Not sure if this is a bug or just a weirdness with google.  When I do a
> google search such as "python subprocess", the first result that comes back
> looks like the following:
>
> Showing results for python subprocess
>
> 17.1. subprocess - Python 3.4.0 documentation
>
> https://docs.python.org/2/library/subprocess.html
>
> The subprocess module allows you to spawn new processes, connect to their
> input/output/error pipes, and obtain their return codes. This module intends
> to ...
>
> Notice the header says 3.4.0 but the link goes to python.org/2, and in fact
> when you click you are looking at the 2.x version docs.
>
> I noticed this crop up about a week ago, I see it on lots of searches.  I
> don't see any reference to 3.4.0 in the source for that file, so I'm not
> sure how it could be a python.org issue, but I'm not a search engine expert.

This a known issue with Google that has been discussed a few times in
various places, but we have yet to figure out some way to fix it on
our end.  If you have any suggestions, please let us know! :)

Thanks for the report,
-- 
Zach

From sf65 at gmx.com  Tue May 13 21:14:32 2014
From: sf65 at gmx.com (Steve Foley)
Date: Tue, 13 May 2014 15:14:32 -0400
Subject: [docs] mmap example
Message-ID: <20140513191432.260980@gmx.com>

sure, will do right now, thanks for the reply

> ----- Original Message -----
> From: Zachary Ware
> Sent: 05/13/14 03:09 PM
> To: docs
> Subject: Re: [docs] mmap example
> 
> Hi Steve,
> 
> On Tue, May 13, 2014 at 1:50 PM, Steve Foley <sf65 at gmx.com> wrote:
> > Hello, I would like to submit an example for the mmap docs page. It demonstrates the use of shared memory and message passing between processes. Thanks!
> 
> Would you mind creating an issue on bugs.python.org for this, and
> submitting your example as a patch? With an issue on the tracker, the
> right people can be made aware of your suggestion and appropriate
> action taken.
> 
> Regards,
> -- 
> Zach


From sf65 at gmx.com  Tue May 13 21:39:22 2014
From: sf65 at gmx.com (Steve Foley)
Date: Tue, 13 May 2014 15:39:22 -0400
Subject: [docs] mmap example
Message-ID: <20140513193923.260970@gmx.com>

http://bugs.python.org/issue21501



> ----- Original Message -----
> From: Zachary Ware
> Sent: 05/13/14 03:09 PM
> To: docs
> Subject: Re: [docs] mmap example
> 
> Hi Steve,
> 
> On Tue, May 13, 2014 at 1:50 PM, Steve Foley <sf65 at gmx.com> wrote:
> > Hello, I would like to submit an example for the mmap docs page. It demonstrates the use of shared memory and message passing between processes. Thanks!
> 
> Would you mind creating an issue on bugs.python.org for this, and
> submitting your example as a patch? With an issue on the tracker, the
> right people can be made aware of your suggestion and appropriate
> action taken.
> 
> Regards,
> -- 
> Zach

From report at bugs.python.org  Wed May 14 09:08:18 2014
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 14 May 2014 07:08:18 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
In-Reply-To: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>
Message-ID: <1400051298.7.0.699609230803.issue21488@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Brett, if you granted Berker commit privileges, you forgot to update the developer log and issue tracker...

That said, the patch LGTM too.

----------

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

From report at bugs.python.org  Wed May 14 09:37:05 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 14 May 2014 07:37:05 +0000
Subject: [docs] [issue21034] Python docs reference the Distribute package
	which has	been deprecated in favor of Setuptools
In-Reply-To: <1395564519.98.0.0028723182567.issue21034@psf.upfronthosting.co.za>
Message-ID: <1400053025.71.0.75709286359.issue21034@psf.upfronthosting.co.za>


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


----------
nosy: +eric.araujo
stage:  -> patch review
type:  -> enhancement

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

From report at bugs.python.org  Wed May 14 11:19:22 2014
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 14 May 2014 09:19:22 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
In-Reply-To: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>
Message-ID: <1400059162.84.0.364257555982.issue21488@psf.upfronthosting.co.za>


STINNER Victor added the comment:

For Python 3.5, I would prefer to patch the code to support keywords instead.

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

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

From victor.stinner at gmail.com  Wed May 14 11:21:46 2014
From: victor.stinner at gmail.com (victor.stinner at gmail.com)
Date: Wed, 14 May 2014 09:21:46 -0000
Subject: [docs] codecs.encode/decode documentation inconsistency (issue
	21488)
Message-ID: <20140514092146.950.88108@psf.upfronthosting.co.za>


http://bugs.python.org/review/21488/diff/11863/Doc/library/codecs.rst
File Doc/library/codecs.rst (right):

http://bugs.python.org/review/21488/diff/11863/Doc/library/codecs.rst#newcode29
Doc/library/codecs.rst:29: encoding is ``utf-8``.
You should also mention the default error handler:

The default *encoding* is ``'utf-8'`` and the default *error* handler is
``'strict'``.

http://bugs.python.org/review/21488/diff/11863/Doc/library/codecs.rst#newcode40
Doc/library/codecs.rst:40: encoding is ``utf-8``.
The default *encoding* is ``'utf-8'`` and the default *error* handler is
``'strict'``.

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

From report at bugs.python.org  Wed May 14 11:21:57 2014
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 14 May 2014 09:21:57 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
In-Reply-To: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>
Message-ID: <1400059317.21.0.421186874444.issue21488@psf.upfronthosting.co.za>


STINNER Victor added the comment:

I sent a review on Rietveld.

----------

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

From report at bugs.python.org  Wed May 14 11:29:13 2014
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 14 May 2014 09:29:13 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
In-Reply-To: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>
Message-ID: <1400059753.71.0.267290424743.issue21488@psf.upfronthosting.co.za>


STINNER Victor added the comment:

codecs_decode_encode_kw.patch: Patch for Python 3.5 adding support of keyword arguments on codecs.encode and codecs.decode.

----------
Added file: http://bugs.python.org/file35250/codecs_decode_encode_kw.patch

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

From berker.peksag at gmail.com  Wed May 14 13:16:36 2014
From: berker.peksag at gmail.com (berker.peksag at gmail.com)
Date: Wed, 14 May 2014 11:16:36 -0000
Subject: [docs] codecs.encode/decode documentation inconsistency (issue
	21488)
Message-ID: <20140514111636.1242.82611@psf.upfronthosting.co.za>

On 2014/05/14 11:21:46, haypo wrote:
> http://bugs.python.org/review/21488/diff/11863/Doc/library/codecs.rst
> File Doc/library/codecs.rst (right):
> 
>
http://bugs.python.org/review/21488/diff/11863/Doc/library/codecs.rst#newcode29
> Doc/library/codecs.rst:29: encoding is ``utf-8``.
> You should also mention the default error handler:
> 
> The default *encoding* is ``'utf-8'`` and the default *error* handler
is
> ``'strict'``.
> 
>
http://bugs.python.org/review/21488/diff/11863/Doc/library/codecs.rst#newcode40
> Doc/library/codecs.rst:40: encoding is ``utf-8``.
> The default *encoding* is ``'utf-8'`` and the default *error* handler
is
> ``'strict'``.

The errors argument already documented in the next paragraph:

"The default error handler is strict meaning that encoding errors raise
[...]"

https://docs.python.org/3.5/library/codecs.html#codecs.encode

Do you want me to add the "and the default *error* handler is
``'strict'``" part anyway?

Will update the patch for style changes.

Thanks for the review, Victor.

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

From report at bugs.python.org  Wed May 14 15:41:36 2014
From: report at bugs.python.org (Brett Cannon)
Date: Wed, 14 May 2014 13:41:36 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
In-Reply-To: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>
Message-ID: <1400074896.13.0.5116101392.issue21488@psf.upfronthosting.co.za>


Brett Cannon added the comment:

Nope, I forgot Berker had triage rights but not commit rights.

----------
assignee: berker.peksag -> docs at python

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

From victor.stinner at gmail.com  Wed May 14 15:44:43 2014
From: victor.stinner at gmail.com (victor.stinner at gmail.com)
Date: Wed, 14 May 2014 13:44:43 -0000
Subject: [docs] codecs.encode/decode documentation inconsistency (issue
	21488)
Message-ID: <20140514134443.14581.87969@psf.upfronthosting.co.za>

On 2014/05/14 13:16:36, berkerpeksag wrote:
> The errors argument already documented in the next paragraph:

Oh ok, sorry. So your patch is good.


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

From report at bugs.python.org  Wed May 14 16:10:37 2014
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 14 May 2014 14:10:37 +0000
Subject: [docs] [issue21347] Don't use a list argument together with
	shell=True in	subprocess' docs
In-Reply-To: <1398366522.65.0.954174735085.issue21347@psf.upfronthosting.co.za>
Message-ID: <3gTHph4lyvz7Lk1@mail.python.org>


Roundup Robot added the comment:

New changeset 5ef9a2c711f5 by R David Murray in branch '2.7':
#21347: use string not list in shell=True example.
http://hg.python.org/cpython/rev/5ef9a2c711f5

New changeset 3b27f3acf0c4 by R David Murray in branch '3.4':
#21347: use string not list in shell=True example.
http://hg.python.org/cpython/rev/3b27f3acf0c4

New changeset 217006c5455f by R David Murray in branch 'default':
Merge: #21347: use string not list in shell=True example.
http://hg.python.org/cpython/rev/217006c5455f

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

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

From report at bugs.python.org  Wed May 14 16:11:07 2014
From: report at bugs.python.org (R. David Murray)
Date: Wed, 14 May 2014 14:11:07 +0000
Subject: [docs] [issue21347] Don't use a list argument together with
	shell=True in	subprocess' docs
In-Reply-To: <1398366522.65.0.954174735085.issue21347@psf.upfronthosting.co.za>
Message-ID: <1400076667.9.0.108522616933.issue21347@psf.upfronthosting.co.za>


R. David Murray added the comment:

Thanks, Akira.

----------
nosy: +r.david.murray
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Wed May 14 16:33:43 2014
From: report at bugs.python.org (Steve)
Date: Wed, 14 May 2014 14:33:43 +0000
Subject: [docs] [issue21508] C API PyArg_ParseTuple doc is innacurate
Message-ID: <1400078023.63.0.359608332224.issue21508@psf.upfronthosting.co.za>


New submission from Steve:

PyArg_ParseTuple is defined as returning an "int", but the documentation talks about returning a true/false value, and failling on false.  In addition to being inaccurate, considering that most other functions fail on !=0 ("true"), it can lead to confusion.

Doc:
int PyArg_ParseTuple(PyObject *args, const char *format, ...)
Parse the parameters of a function that takes only positional parameters into local variables. Returns true on success; on failure, it returns false and raises the appropriate exception.

----------
assignee: docs at python
components: Documentation
messages: 218536
nosy: Banger, docs at python
priority: normal
severity: normal
status: open
title: C API PyArg_ParseTuple doc is innacurate
type: enhancement
versions: Python 3.3, Python 3.4, Python 3.5

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

From report at bugs.python.org  Wed May 14 17:09:57 2014
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 14 May 2014 15:09:57 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
In-Reply-To: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>
Message-ID: <3gTK78313Xz7LnZ@mail.python.org>


Roundup Robot added the comment:

New changeset cc5e3b93c35a by Victor Stinner in branch '2.7':
Issue #21488: Fix doc of codecs.decode() and codecs.encode(), no keyword support.
http://hg.python.org/cpython/rev/cc5e3b93c35a

New changeset 2e116176a81f by Victor Stinner in branch '3.4':
Issue #21488: Fix doc of codecs.decode() and codecs.encode(), no keyword support.
http://hg.python.org/cpython/rev/2e116176a81f

New changeset 889896471498 by Victor Stinner in branch 'default':
Merge 3.4: ignore change specific to 3.4 for #21488, I had a different patch for Python 3.5
http://hg.python.org/cpython/rev/889896471498

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

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

From report at bugs.python.org  Wed May 14 17:10:59 2014
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 14 May 2014 15:10:59 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
In-Reply-To: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>
Message-ID: <3gTK8M17fZz7Lk1@mail.python.org>


Roundup Robot added the comment:

New changeset 6ceedbd88b5f by Victor Stinner in branch '3.4':
Issue #21488: Add support of keyword arguments for codecs.encode and codecs.decode
http://hg.python.org/cpython/rev/6ceedbd88b5f

----------

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

From report at bugs.python.org  Wed May 14 17:11:44 2014
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 14 May 2014 15:11:44 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
In-Reply-To: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>
Message-ID: <1400080304.72.0.587325549681.issue21488@psf.upfronthosting.co.za>


STINNER Victor added the comment:

I applied all patches and added Brad Aylsworth to Misc/ACKS. Thanks Brad!

Note: I adapted the change for Python 2.7: the default encoding is ASCII, not UTF-8.

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

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

From report at bugs.python.org  Wed May 14 17:13:56 2014
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 14 May 2014 15:13:56 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
In-Reply-To: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>
Message-ID: <3gTKCm0xyKz7LjV@mail.python.org>


Roundup Robot added the comment:

New changeset 0d38044c0b02 by Victor Stinner in branch 'default':
Issue #21488: Add support of keyword arguments for codecs.encode and codecs.decode
http://hg.python.org/cpython/rev/0d38044c0b02

----------

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

From report at bugs.python.org  Wed May 14 17:14:34 2014
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 14 May 2014 15:14:34 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
In-Reply-To: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>
Message-ID: <1400080474.81.0.448380123946.issue21488@psf.upfronthosting.co.za>


STINNER Victor added the comment:

Ooops, I applied  codecs_decode_encode_kw.patch to the branch 3.4 instead of default :-/ I should now be fixed.

----------

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

From report at bugs.python.org  Wed May 14 17:17:00 2014
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 14 May 2014 15:17:00 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
In-Reply-To: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>
Message-ID: <1400080620.92.0.122927782091.issue21488@psf.upfronthosting.co.za>


Changes by Berker Peksag <berker.peksag at gmail.com>:


----------
stage: commit review -> resolved

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

From report at bugs.python.org  Wed May 14 23:37:35 2014
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 14 May 2014 21:37:35 +0000
Subject: [docs] [issue21488] codecs.encode/decode documentation inconsistency
In-Reply-To: <1399937850.38.0.349005624478.issue21488@psf.upfronthosting.co.za>
Message-ID: <3gTTkQ5n2xz7Ljq@mail.python.org>


Roundup Robot added the comment:

New changeset 0a6f0aaeb96a by Victor Stinner in branch '2.7':
Issue #21488: Oops, the patch for codecs.encode/decode doc was written by
http://hg.python.org/cpython/rev/0a6f0aaeb96a

New changeset 91dca6b9ef0f by Victor Stinner in branch '3.4':
Issue #21488: Oops, the patch for codecs.encode/decode doc was written by
http://hg.python.org/cpython/rev/91dca6b9ef0f

----------

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

From report at bugs.python.org  Thu May 15 04:18:32 2014
From: report at bugs.python.org (Josh Rosenberg)
Date: Thu, 15 May 2014 02:18:32 +0000
Subject: [docs] [issue21508] C API PyArg_ParseTuple doc is innacurate
In-Reply-To: <1400078023.63.0.359608332224.issue21508@psf.upfronthosting.co.za>
Message-ID: <1400120312.28.0.766994433431.issue21508@psf.upfronthosting.co.za>


Josh Rosenberg added the comment:

You'd prefer it say it returns 1 on success and 0 on failure? Or non-zero on success, zero on failure?

Is true/false that bad? After all, C says 0 is false, all other integer values are true; phrasing it as zero vs. non-zero may be slightly more technically accurate, but it's also a bit less readable, while 1 vs. 0 constrains the implementation (so you couldn't introduce a third "success but with additional info" state, similar to the third possible return from a "O&" converter function).

----------
nosy: +josh.rosenberg

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

From report at bugs.python.org  Thu May 15 07:19:05 2014
From: report at bugs.python.org (Jayanth Koushik)
Date: Thu, 15 May 2014 05:19:05 +0000
Subject: [docs] [issue21510] fma documentation should provide better example.
Message-ID: <1400131145.93.0.338142878224.issue21510@psf.upfronthosting.co.za>


New submission from Jayanth Koushik:

The documentation for decimal.fma provides an example which fails to illustrate the most important feature of the function i.e. single rounding. In fact:

    Decimal(2).fma(3, 5) == Decimal(2)*3 + 5

An example such as this would make it much more clear:

    >>> getcontext().prec = 2
    >>> getcontext().rounding = ROUND_DOWN
    >>> Decimal('1.5')*Decimal('1.5') + Decimal('1.05')
    Decimal('3.2')
    >>> Decimal('1.5').fma(Decimal('1.5'), Decimal('1.05'))
    Decimal('3.3')

----------
assignee: docs at python
components: Documentation
messages: 218592
nosy: docs at python, jayanthkoushik
priority: normal
severity: normal
status: open
title: fma documentation should provide better example.
type: enhancement
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5

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

From report at bugs.python.org  Thu May 15 13:35:11 2014
From: report at bugs.python.org (Mark Dickinson)
Date: Thu, 15 May 2014 11:35:11 +0000
Subject: [docs] [issue21510] fma documentation should provide better example.
In-Reply-To: <1400131145.93.0.338142878224.issue21510@psf.upfronthosting.co.za>
Message-ID: <1400153711.71.0.874495652395.issue21510@psf.upfronthosting.co.za>


Changes by Mark Dickinson <dickinsm at gmail.com>:


----------
nosy: +mark.dickinson, skrah

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

From report at bugs.python.org  Thu May 15 13:37:04 2014
From: report at bugs.python.org (Mark Dickinson)
Date: Thu, 15 May 2014 11:37:04 +0000
Subject: [docs] [issue21510] fma documentation should provide better example.
In-Reply-To: <1400131145.93.0.338142878224.issue21510@psf.upfronthosting.co.za>
Message-ID: <1400153824.63.0.901174680173.issue21510@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

I wouldn't want to drop the simple example: I suspect that many of those looking at fma won't have the first idea what it does, and that first example shows clearly that it's a fused multiply-add.

But +1 for an example that demonstrates the single rounding, either in the online docs or the docstring (or both).

----------

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

From report at bugs.python.org  Thu May 15 13:41:03 2014
From: report at bugs.python.org (Jayanth Koushik)
Date: Thu, 15 May 2014 11:41:03 +0000
Subject: [docs] [issue21510] fma documentation should provide better example.
In-Reply-To: <1400131145.93.0.338142878224.issue21510@psf.upfronthosting.co.za>
Message-ID: <1400154063.78.0.495867988579.issue21510@psf.upfronthosting.co.za>


Jayanth Koushik added the comment:

@Mark: I agree. And perhaps it is also worth mentioning (on an unrelated note), that the decimal fma is not based on the internal cmath fma (it could not be) and unlike the cmath fma, it is no faster than an unfused multiply-add.

----------

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

From report at bugs.python.org  Thu May 15 17:13:47 2014
From: report at bugs.python.org (Steve)
Date: Thu, 15 May 2014 15:13:47 +0000
Subject: [docs] [issue21508] C API PyArg_ParseTuple doc is innacurate
In-Reply-To: <1400078023.63.0.359608332224.issue21508@psf.upfronthosting.co.za>
Message-ID: <1400166827.18.0.642641732438.issue21508@psf.upfronthosting.co.za>


Steve added the comment:

I would prefer the function to return "bool".  But what I prefer is irrelevant, what counts is accuracy and clarity.  And to this end, the return type and the comment have to match.

For a int return value, the document should mention a condition relative to an integer value (e.g.: ==0, !=0, ==-1, <0, ==42, etc).

In this particular case, to minimize the changes, success should be defined as !=0 and failure ==0.

Although there is a bigger problem that I mentioned in that the Python C API uses two different return value standards: in most places, ==0 is success, in this case (and some other places) ==0 is a failure.

As for "implementation constraints" I don't see how making the documentation accurate affects that in any way.  If ever the implementation is expanded, the documentation will need to change.  The only alternative is to make the doc vague or simply wrong.

----------

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

From report at bugs.python.org  Fri May 16 02:46:32 2014
From: report at bugs.python.org (Josh Rosenberg)
Date: Fri, 16 May 2014 00:46:32 +0000
Subject: [docs] [issue21508] C API PyArg_ParseTuple doc is innacurate
In-Reply-To: <1400078023.63.0.359608332224.issue21508@psf.upfronthosting.co.za>
Message-ID: <1400201192.35.0.465995291459.issue21508@psf.upfronthosting.co.za>


Josh Rosenberg added the comment:

Changing the docs isn't the main hurdle; the problem is that if we told people they could test == 1, rather than != 0, then new success return codes couldn't be added without a long period of warning.

I don't think the convention is consistently 0 means success BTW. Frankly, 0 means success is just confusing in general (since it reverses the normal C convention, even if it agrees with the errno convention).

bool is sadly out, since Python is forever stuck in 1990, and will never know the joys of C99.

----------

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

From report at bugs.python.org  Fri May 16 06:31:09 2014
From: report at bugs.python.org (Chris Rebert)
Date: Fri, 16 May 2014 04:31:09 +0000
Subject: [docs] [issue18820] json.dump() ignores its 'default' option
	when	serializing dictionary keys
In-Reply-To: <1377253830.03.0.463497944995.issue18820@psf.upfronthosting.co.za>
Message-ID: <1400214669.35.0.469553430802.issue18820@psf.upfronthosting.co.za>


Changes by Chris Rebert <pybugs at rebertia.com>:


----------
nosy: +cvrebert

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

From report at bugs.python.org  Fri May 16 06:52:48 2014
From: report at bugs.python.org (Chris Rebert)
Date: Fri, 16 May 2014 04:52:48 +0000
Subject: [docs] [issue21514] update json module docs in light of RFC 7159 &
	ECMA-404
Message-ID: <1400215968.18.0.723032535405.issue21514@psf.upfronthosting.co.za>


New submission from Chris Rebert:

json module docs: https://docs.python.org/3/library/json.html

New superseding JSON RFC: https://tools.ietf.org/html/rfc7159
Errata to the new RFC: http://www.rfc-editor.org/errata_search.php?rfc=7159
ECMA-404: http://www.ecma-international.org/publications/standards/Ecma-404.htm

These updated specs are of particular relevance to the Standard Compliance section of the json module docs. There are also a bunch of new interoperability notes in the RFC that could probably bear repeating in the module's docs.

----------
assignee: docs at python
components: Documentation
messages: 218644
nosy: cvrebert, docs at python
priority: normal
severity: normal
status: open
title: update json module docs in light of RFC 7159 & ECMA-404
versions: Python 2.7, Python 3.5

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

From report at bugs.python.org  Fri May 16 07:54:47 2014
From: report at bugs.python.org (Chris Rebert)
Date: Fri, 16 May 2014 05:54:47 +0000
Subject: [docs] [issue13826] Having a shlex example in the subprocess.Popen
	docs is	confusing
In-Reply-To: <1326983115.48.0.551767400168.issue13826@psf.upfronthosting.co.za>
Message-ID: <1400219687.95.0.41707359046.issue13826@psf.upfronthosting.co.za>


Changes by Chris Rebert <pybugs at rebertia.com>:


----------
nosy: +cvrebert

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

From report at bugs.python.org  Fri May 16 09:15:07 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 16 May 2014 07:15:07 +0000
Subject: [docs] [issue21514] update json module docs in light of RFC 7159 &
	ECMA-404
In-Reply-To: <1400215968.18.0.723032535405.issue21514@psf.upfronthosting.co.za>
Message-ID: <1400224507.89.0.897423047315.issue21514@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti, pitrou, rhettinger
stage:  -> needs patch
type:  -> enhancement
versions: +Python 3.4

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

From report at bugs.python.org  Fri May 16 20:58:22 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 16 May 2014 18:58:22 +0000
Subject: [docs] [issue21484] More clarity needed about difference between "x
	+= e"	and "x = x + e"
In-Reply-To: <1399913881.84.0.586979222354.issue21484@psf.upfronthosting.co.za>
Message-ID: <1400266702.81.0.571391032527.issue21484@psf.upfronthosting.co.za>


Changes by Terry J. Reedy <tjreedy at udel.edu>:


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

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

From report at bugs.python.org  Sat May 17 20:48:25 2014
From: report at bugs.python.org (Steffen Ullrich)
Date: Sat, 17 May 2014 18:48:25 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1400352505.29.0.620906477277.issue21430@psf.upfronthosting.co.za>


Steffen Ullrich added the comment:

Data transport in SSL is not done with plain TCP, but with encoded frames inside TCP. To get decoded data one has to first receive the full frame, even if one is only interested in the first bytes. Example:
 - server does an SSL_write with 200 bytes. This will result in a frame which contain all the 200 bytes. 
 - if the client does a SSL_read (e.g. recv) to get 100 bytes the underlying SSL stack will read the full frame, but return only 100 bytes of the 200 bytes.
 - if the client then would call select to check if more data are available this would fail, because select checks the data on the socket only. But pending would return that there are still 100 bytes available for read in the SSL stack.

So to make use of select with SSL the application would have to check first with pending, if there are already buffered data, and only if there are no buffered data it should call select to check if there are data on the socket.

But, one could skip the call of pending if all SSL_read (recv) are at least 16k, because this is the maximum size of an SSL frame and SSL_read will not read more than one SSL frame at a time (actually I'm not sure if python calls only SSL_read once within recv, but I assume so).

You might have a look at the examples and documentation for non-blocking I/O for Perls  IO::Socket::SSL package (disclaimer: I'm the maintainer):  http://search.cpan.org/~sullr/IO-Socket-SSL-1.987/lib/IO/Socket/SSL.pm

----------
nosy: +noxxi

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

From report at bugs.python.org  Sat May 17 21:12:57 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 17 May 2014 19:12:57 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1400353977.76.0.853349315537.issue21430@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

> So to make use of select with SSL the application would have to check first
> with pending, if there are already buffered data,

What's the point of checking? Just call SSL_read() and catch the SSL_ERROR_WANT_{READ,WRITE} to determine that no data is available; as a bonus it also tells you whether you have to select() for read or for write.

----------

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

From report at bugs.python.org  Sat May 17 21:39:01 2014
From: report at bugs.python.org (Bas Wijnen)
Date: Sat, 17 May 2014 19:39:01 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1400355541.0.0.515464542416.issue21430@psf.upfronthosting.co.za>


Bas Wijnen added the comment:

After trying to use this, I think ssl.pending is a valuable function that should be supported and documented.

My use case is a half-synchronous system, where I want most calls to block but asynchronous events are possible as well.  Switching the socket between blocking and non-blocking all the time is annoying and results in code that is harder to read.

With ssl.pending, I can simply repeat the read as long as data is pending.  Setting my buffer size high might technically work, but that seems too fragile.  I don't like using an undocumented function either, but I'm hoping that gets fixed. ;-)

----------

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

From report at bugs.python.org  Sun May 18 00:41:05 2014
From: report at bugs.python.org (Steffen Ullrich)
Date: Sat, 17 May 2014 22:41:05 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1400366465.51.0.501057367372.issue21430@psf.upfronthosting.co.za>


Steffen Ullrich added the comment:

> What's the point of checking? Just call SSL_read() and catch the SSL_ERROR_WANT_{READ,WRITE} to determine that no data is available; as a bonus it also tells you whether you have to select() for read or for write.

A common scenario with non-blocking sockets is to have lots of sockets at the same time and a central select loop. And whenever a socket gets ready it usually reads only as much as is needed for its current task and then returns to the select-loop. 

I was trying to point out that for SSL enabled sockets this approach will no longer work and might cause odd stalling of connections, because select will not show the socket as readable although data are there for read. I don't think it is enough to just document pending, but it should be documented that the behavior with SSL sockets with select differs from the behavior one is used from normal TCP sockets.

----------

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

From report at bugs.python.org  Sun May 18 00:46:21 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 17 May 2014 22:46:21 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1400366465.51.0.501057367372.issue21430@psf.upfronthosting.co.za>
Message-ID: <1400366778.2337.9.camel@fsol>


Antoine Pitrou added the comment:

> I was trying to point out that for SSL enabled sockets this approach
> will no longer work and might cause odd stalling of connections,
> because select will not show the socket as readable although data are
> there for read.

You are right, this is worth mentioning in the documentation.

----------

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

From report at bugs.python.org  Sun May 18 00:52:13 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Sat, 17 May 2014 22:52:13 +0000
Subject: [docs] [issue19980] Improve help('non-topic') response
In-Reply-To: <1386984892.27.0.919528696836.issue19980@psf.upfronthosting.co.za>
Message-ID: <1400367133.57.0.0831863041007.issue19980@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

I propose the following.  help('') returns help on strings in the same way that help([]) and help({}) returns help on lists and dicts respectively, further help(''.method) returns help on the string method or an attribute error, so this appears to me consistent.  help('doh') returns enhanced output along the lines Terry suggested in msg206157.  help('module') gives the path to the module as well as the help output, if any, as I think this could be useful in cases where you're looking for problems and have a stdlib module masked by a file of your own.  Thoughts?

If we can come to an agreement I'll try and work up a patch.

Note that I've tried looking at the test code and it didn't make much sense to me, pointers welcome.

I've also just signed the contributor's agreement.

----------
nosy: +BreamoreBoy

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

From report at bugs.python.org  Sun May 18 00:57:01 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 17 May 2014 22:57:01 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <3gWMLh5Zhmz7LjZ@mail.python.org>


Roundup Robot added the comment:

New changeset b820b1b282b2 by Antoine Pitrou in branch '3.4':
Issue #21430: additions to the description of non-blocking SSL sockets
http://hg.python.org/cpython/rev/b820b1b282b2

New changeset 077e64b23592 by Antoine Pitrou in branch 'default':
Issue #21430: additions to the description of non-blocking SSL sockets
http://hg.python.org/cpython/rev/077e64b23592

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

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

From report at bugs.python.org  Sun May 18 05:54:02 2014
From: report at bugs.python.org (Alexey Gorshkov)
Date: Sun, 18 May 2014 03:54:02 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1400385242.73.0.0783850417275.issue21430@psf.upfronthosting.co.za>


Alexey Gorshkov added the comment:

>Issue #21430: additions to the description of non-blocking SSL sockets

I do not see any mention of .pending() in Your commit.

Is this some personal hate to subject?

Are You going to document this method or not? Documenting it on line of text.

If You are not going to document this method, will You accept my patch for documentation adding this method?

Simply saying: This issue is here, people wand documentation for what must be documented for over a 5 years now (http://bugs.python.org/issue1251).

----------

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

From will at wmarler.com  Sat May 17 00:38:29 2014
From: will at wmarler.com (Will Marler)
Date: Fri, 16 May 2014 16:38:29 -0600
Subject: [docs] Feature request: make searching for "@" return information
	on decorators
Message-ID: <CACjWF0Qut-PjueQuceyjv5hhQZjAEdFYJ-wiRDR1huWkPj0dtQ@mail.gmail.com>

TL;DR: see the subject line

I'm new to Python and was reading code that used this:

@property
def ...

and I didn't know what it meant. I looked in the python.org docs for "@"
and "@property" and didn't get any results, so I turned to Google and found
a good page on stackoverflow about how "@property" worked (
http://stackoverflow.com/questions/17330160/python-how-does-the-property-decorator-work
).

However, I still did not understand "@". I eventually asked a colleague (I
try to RTFM before asking), and he said "oh ya, that's a decorator." Once I
knew that "@" = "decorator," I could search for "decorator" in the docs and
get useful results. In fact, I found a LOT of great results; this isn't a
request for more information on decorators :).

I probably spent 15-20 minutes before learning @ = decorator, and I'm sure
this is something that plagues other newbies. Can the docs (or search
functionality) be updated so someone searching on "@" as a single search
term will get information on decorators? Search results could include a
direction to the decorator entry in the glossary?, the function/class
definition pages, etc.

Thanks,

Will
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140516/fdd3c702/attachment.html>

From report at bugs.python.org  Sun May 18 11:33:22 2014
From: report at bugs.python.org (Antoine Pitrou)
Date: Sun, 18 May 2014 09:33:22 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1400405602.4.0.83775980718.issue21430@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

I'm not intending to document the pending() method. Apparently the only people wanting to use it are/were confused about how exactly to write non-blocking SSL code, which is not a good hint.

----------
resolution:  -> wont fix
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sun May 18 17:49:10 2014
From: report at bugs.python.org (Bas Wijnen)
Date: Sun, 18 May 2014 15:49:10 +0000
Subject: [docs] [issue21430] Document ssl.pending()
In-Reply-To: <1399230346.59.0.136279071434.issue21430@psf.upfronthosting.co.za>
Message-ID: <1400428150.26.0.711411746446.issue21430@psf.upfronthosting.co.za>


Bas Wijnen added the comment:

Alexey: please be more civil.

Antoine: In that case, can you please explain how you would recommend me to implement my use case, where most of my calls are master-initiated and blocking, but some slave-initiated events must be non-blocking?  Should I make a lot of calls to sslsocket.setblocking() to switch it on and off all the time?  AFAIK that is a system call (or isn't it?); while that won't make any real difference in performance in Python, it doesn't feel right to make system calls when there's technically no need for it.

Also, as I suggested previously, if you don't document the method, could you please add the word "pending" somewhere in the text?  This ensures people looking for documentation of what they see in the source will find this explanation.  It may also be good to add a note to the source code that this function should not be used.

----------

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

From report at bugs.python.org  Mon May 19 01:49:08 2014
From: report at bugs.python.org (Alex Gaynor)
Date: Sun, 18 May 2014 23:49:08 +0000
Subject: [docs] [issue21528] Fix a number of typos in the documentation
Message-ID: <1400456947.04.0.361173205763.issue21528@psf.upfronthosting.co.za>


New submission from Alex Gaynor:

Attached patch is against the default branch, and fixes a number of typos.

----------
assignee: docs at python
components: Documentation
files: typos.diff
keywords: needs review, patch
messages: 218769
nosy: alex, docs at python
priority: normal
severity: normal
status: open
title: Fix a number of typos in the documentation
versions: Python 3.5
Added file: http://bugs.python.org/file35289/typos.diff

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

From report at bugs.python.org  Mon May 19 02:44:06 2014
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 19 May 2014 00:44:06 +0000
Subject: [docs] [issue20620] Update the min()/max() docs for the new default
	argument
In-Reply-To: <1392322129.66.0.847659571757.issue20620@psf.upfronthosting.co.za>
Message-ID: <1400460246.0.0.118880492579.issue20620@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Rebased patch.

----------
versions: +Python 3.5
Added file: http://bugs.python.org/file35291/issue20620_v3.diff

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

From report at bugs.python.org  Mon May 19 02:44:21 2014
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 19 May 2014 00:44:21 +0000
Subject: [docs] [issue20620] Update the min()/max() docs for the new default
	argument
In-Reply-To: <1392322129.66.0.847659571757.issue20620@psf.upfronthosting.co.za>
Message-ID: <1400460261.36.0.964200813361.issue20620@psf.upfronthosting.co.za>


Changes by Berker Peksag <berker.peksag at gmail.com>:


Removed file: http://bugs.python.org/file34081/issue20620.diff

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

From report at bugs.python.org  Mon May 19 03:29:23 2014
From: report at bugs.python.org (Ethan Furman)
Date: Mon, 19 May 2014 01:29:23 +0000
Subject: [docs] [issue17352] Be clear that __prepare__ must be declared as a
	class	method
In-Reply-To: <1362409892.83.0.717786566871.issue17352@psf.upfronthosting.co.za>
Message-ID: <1400462963.85.0.115170715406.issue17352@psf.upfronthosting.co.za>


Changes by Ethan Furman <ethan at stoneleaf.us>:


----------
nosy: +ethan.furman

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

From report at bugs.python.org  Mon May 19 03:31:22 2014
From: report at bugs.python.org (Ethan Furman)
Date: Mon, 19 May 2014 01:31:22 +0000
Subject: [docs] [issue18334] type(name, bases,
	dict) does not call metaclass' __prepare__ attribute
In-Reply-To: <1372641138.46.0.644775856541.issue18334@psf.upfronthosting.co.za>
Message-ID: <1400463082.34.0.117313801265.issue18334@psf.upfronthosting.co.za>


Changes by Ethan Furman <ethan at stoneleaf.us>:


----------
nosy: +ethan.furman

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

From report at bugs.python.org  Mon May 19 03:34:10 2014
From: report at bugs.python.org (Ethan Furman)
Date: Mon, 19 May 2014 01:34:10 +0000
Subject: [docs] [issue17422] language reference should specify restrictions
	on class	namespace
In-Reply-To: <1363293215.19.0.289288553848.issue17422@psf.upfronthosting.co.za>
Message-ID: <1400463250.55.0.558347523016.issue17422@psf.upfronthosting.co.za>


Changes by Ethan Furman <ethan at stoneleaf.us>:


----------
nosy: +ethan.furman

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

From obrientony2 at gmail.com  Sun May 18 11:02:24 2014
From: obrientony2 at gmail.com (Tony O'Brien)
Date: Sun, 18 May 2014 19:02:24 +1000
Subject: [docs] PDF / Zip documentation files not found from
	https://docs.python.org/3/download.html
Message-ID: <CA+pXZ5jUnf21th4Tzm8-03s3Cs8T06nOWPyov0T7yeCUFLPXDA@mail.gmail.com>

Thanks for the software. Fantastic

Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140518/55ecf400/attachment-0001.html>

From Watschi_15 at gmx.de  Sun May 18 15:19:01 2014
From: Watschi_15 at gmx.de (Wiebke Walbaum)
Date: Sun, 18 May 2014 15:19:01 +0200
Subject: [docs] Downloads not available
Message-ID: <5378B345.60607@gmx.de>

Hello,

I just wanted to download the Python 3.4 1rc1 Documentation, but the 
links all lead to 404 Not Found :(
It would be nice if you could fix that.

Yours sincerely
Wiebke

---
Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz ist aktiv.
http://www.avast.com


From Shambhu.Rajak at sandisk.com  Sun May 18 17:38:06 2014
From: Shambhu.Rajak at sandisk.com (Shambhu Rajak)
Date: Sun, 18 May 2014 15:38:06 +0000
Subject: [docs] Cannot Download Documentation from the given URL
Message-ID: <39F9E8A5546B9448A82E55FBEBE3EC45B8437B@SACMBXIP02.sdcorp.global.sandisk.com>

Dear Python Team,

I am not able to download the complete python documentation as PDF from the URL: https://docs.python.org/2/download.html

Thanks & Regards,
Shambhu Rajak

________________________________

PLEASE NOTE: The information contained in this electronic mail message is intended only for the use of the designated recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify the sender by telephone or e-mail (as shown above) immediately and destroy any and all copies of this message in your possession (whether hard copies or electronically stored copies).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140518/734b867e/attachment.html>

From report at bugs.python.org  Mon May 19 10:10:15 2014
From: report at bugs.python.org (Wolfgang Maier)
Date: Mon, 19 May 2014 08:10:15 +0000
Subject: [docs] [issue21533] built-in types dict docs - construct dict from
	iterable, not iterator
Message-ID: <1400487015.16.0.760931173475.issue21533@psf.upfronthosting.co.za>


New submission from Wolfgang Maier:

The docs for Python3.4 havethis to say about the arguments to the dict constructor:

class dict(**kwarg)
class dict(mapping, **kwarg)
class dict(iterable, **kwarg)

    Return a new dictionary initialized from an optional positional argument and a possibly empty set of keyword arguments.

    If no positional argument is given, an empty dictionary is created. If a positional argument is given and it is a mapping object, a dictionary is created with the same key-value pairs as the mapping object. Otherwise, the positional argument must be an iterator object. Each item in the iterable must itself be an iterator with exactly two objects. The first object of each item becomes a key in the new dictionary, and the second object the corresponding value. If a key occurs more than once, the last value for that key becomes the corresponding value in the new dictionary.

This paragraph uses the term iterator twice when it should talk about an iterable instead.
I'm attaching the patch for this.

Best,
Wolfgang

----------
assignee: docs at python
components: Documentation
files: dict_doc.patch
keywords: patch
messages: 218784
nosy: docs at python, wolma
priority: normal
severity: normal
status: open
title: built-in types dict docs - construct dict from iterable, not iterator
Added file: http://bugs.python.org/file35292/dict_doc.patch

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

From report at bugs.python.org  Mon May 19 15:24:17 2014
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 19 May 2014 13:24:17 +0000
Subject: [docs] [issue21528] Fix a number of typos in the documentation
In-Reply-To: <1400456947.04.0.361173205763.issue21528@psf.upfronthosting.co.za>
Message-ID: <1400505857.43.0.682196255492.issue21528@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Looks all good to me.

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

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

From fzczx123 at 163.com  Mon May 19 07:28:38 2014
From: fzczx123 at 163.com (=?GBK?B?sszX08/S?=)
Date: Mon, 19 May 2014 13:28:38 +0800 (CST)
Subject: [docs] Can't download documentation
Message-ID: <7396394b.7e.14612f3fe83.Coremail.fzczx123@163.com>

 I can't download documentation from https://docs.python.org/3/download.html and https://docs.python.org/2/download.html
Got 404 error. I'm in China.
By the way I want a epub version of python2 documentation, is there something like this?





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140519/1609c3e5/attachment.html>

From gregory.duhamel at gmail.com  Mon May 19 09:56:17 2014
From: gregory.duhamel at gmail.com (Gregory Duhamel)
Date: Mon, 19 May 2014 09:56:17 +0200
Subject: [docs] Dead link for 3.4.1 RC1 ?
Message-ID: <CABjkQaMj0VCwNOHLv8+=kbbu75y95_tNYf93FKuV+yB97q9m9A@mail.gmail.com>

Hello,

Just seen that link present on the following page seems to be dead at the
moment :

https://docs.python.org/3/download.html

Can you have a look ?

Thanks a lot for your great work.

Regards,
Gregory.


-- 
Gregory Duhamel
Tel : 0630807054
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140519/1e24d591/attachment.html>

From jagadeesh.softwaredeveloper at gmail.com  Mon May 19 13:14:30 2014
From: jagadeesh.softwaredeveloper at gmail.com (Jagadeesh Prasad)
Date: Mon, 19 May 2014 16:44:30 +0530
Subject: [docs] Regarding Python Documentation Downloads
Message-ID: <CAEQWaE4jaMcDTB=iVYomAC6d_Y7ARmqKnCStryqJPMmm40v+zA@mail.gmail.com>

Hello,

I'm looking of the Python documentation download, I found the download link
in your official website: *www.python.org <http://www.python.org>. *But
when i click on the *download link *provided in the URL
*https://docs.python.org/3/download.html
<https://docs.python.org/3/download.html>  , *the page is redirecting
to URL* https://docs.python.org/3/archives/python-3.4.1-docs-pdf-letter.zip
<https://docs.python.org/3/archives/python-3.4.1-docs-pdf-letter.zip> *with
error
404 Not Found
?Please let me know is this a bug or downloads has been moved to any other
URL's. If so please provide me the new download URL.?


Regards,
Jagadeesh Prasad Vegi
Available @ 9133 8888 98
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140519/556b59bc/attachment.html>

From livid at v2ex.com  Mon May 19 08:12:56 2014
From: livid at v2ex.com (Livid)
Date: Sun, 18 May 2014 23:12:56 -0700
Subject: [docs] Docs 404
Message-ID: <9D732A97-62AC-4AB0-88BE-B518DDAA9332@v2ex.com>

Hi,

All files linked from these pages are now 404?

https://docs.python.org/3/download.html

https://docs.python.org/2/download.html


@Livid
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/docs/attachments/20140518/9f4222d2/attachment.sig>

From joesvrcek at gmail.com  Mon May 19 14:12:24 2014
From: joesvrcek at gmail.com (Joseph Svrcek)
Date: Mon, 19 May 2014 08:12:24 -0400
Subject: [docs] 404 in https://docs.python.org/2.7/download.html
Message-ID: <CAEgu94Gh7Ab8sqp5zwkhZy6dPfVdRZ3q1A63MHqh+wsi7Midiw@mail.gmail.com>

All of the links on this page, https://docs.python.org/2.7/download.html,
seem to be broken.  Is there an updated location for these resources?

Thank you.

-Joe Svrcek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140519/02492f63/attachment.html>

From as4dmoosvi at gmail.com  Sun May 18 17:27:06 2014
From: as4dmoosvi at gmail.com (as4dmoosvi at gmail.com)
Date: Sun, 18 May 2014 08:27:06 -0700 (PDT)
Subject: [docs] (no subject)
Message-ID: <5378d14a.c266b40a.5e3f.25af@mx.google.com>


Hello, 

I would like to inform you that the download links on the page 'https://docs.python.org/2/download.html' are broken. I am getting a 404 error.
Please have them fixed as soon as possible. Thank you.

Regards, 

Asad


From report at bugs.python.org  Mon May 19 15:41:39 2014
From: report at bugs.python.org (Zachary Ware)
Date: Mon, 19 May 2014 13:41:39 +0000
Subject: [docs] [issue21534] 404 on documentation download links
Message-ID: <1400506899.65.0.0656735087144.issue21534@psf.upfronthosting.co.za>


New submission from Zachary Ware:

docs@ has received several reports from people unable to download documentation from docs.python.org/[23]/download.html since the release of 3.4.1rc1 and 2.7.7rc1.

----------
assignee: docs at python
components: Documentation
messages: 218792
nosy: benjamin.peterson, docs at python, georg.brandl, larry, zach.ware
priority: high
severity: normal
status: open
title: 404 on documentation download links
type: behavior
versions: Python 2.7, Python 3.4

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

From zachary.ware+pydocs at gmail.com  Mon May 19 15:50:04 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Mon, 19 May 2014 08:50:04 -0500
Subject: [docs] Python Documentation download 404
Message-ID: <CAKJDb-PjSDGj1mhqbdx9apHZUVvMi8uaV29uT_d0Z+RPRD3s0w@mail.gmail.com>

(Note: I have Bcc'd the 8 people who have reported this issue so far)

Thank you all for the reports!  I have opened
http://bugs.python.org/issue21534 to make sure this is fixed; I expect
it should be resolved fairly quickly.

Regards,
-- 
Zach

From inman.daniel.e at gmail.com  Mon May 19 16:21:11 2014
From: inman.daniel.e at gmail.com (Daniel Inman)
Date: Mon, 19 May 2014 10:21:11 -0400
Subject: [docs] 404 Not Found
Message-ID: <CAG_N7TjwZZ81PTqVox8qW0AYnxriYG3HWUoncHvwtzchUtTqmQ@mail.gmail.com>

Hey there!

Just thought someone on this list should know: when you go to
https://docs.python.org/2/download.html and try to download any of the
files listed it returns a 404 error. Not sure if the links just aren't
pointing to the correct directory or what.

-- 
Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140519/245b6198/attachment.html>

From cclauss at me.com  Mon May 19 15:37:30 2014
From: cclauss at me.com (cclauss)
Date: Mon, 19 May 2014 15:37:30 +0200
Subject: [docs] Broken link for Python 3.4.1 EPUB download
Message-ID: <D21A7B46-CDA2-42C3-B6A2-1B07AB134A90@me.com>

https://docs.python.org/3/download.html can not download the EPUB document.

Thanks, CCC - +41-79-799-1210
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140519/badaeeaa/attachment.html>

From salism3 at gmail.com  Mon May 19 20:03:55 2014
From: salism3 at gmail.com (Islam Otmani)
Date: Mon, 19 May 2014 19:03:55 +0100
Subject: [docs] Documents download gives 404 Not found
Message-ID: <CAAt8irvkt7zx9YuW+4h2sK9vT_oTOjobuk0QUoKYeHiiqyzpyg@mail.gmail.com>

Hello,

I just wanted to let you know that I attempted to download the docs but got
a dead-link via the following page:
https://docs.python.org/2/download.html

Thanks in advance,
Islam.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140519/f1911cd7/attachment.html>

From report at bugs.python.org  Mon May 19 21:57:24 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 19 May 2014 19:57:24 +0000
Subject: [docs] [issue21484] More clarity needed about difference between "x
	+= e"	and "x = x + e"
In-Reply-To: <1399913881.84.0.586979222354.issue21484@psf.upfronthosting.co.za>
Message-ID: <1400529443.85.0.248410530983.issue21484@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

I agree with Josh.  If anything this belongs in a wiki entry, faq page, or stack overflow question.

----------
nosy: +rhettinger
resolution:  -> rejected
status: open -> closed

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

From report at bugs.python.org  Mon May 19 23:21:34 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 19 May 2014 21:21:34 +0000
Subject: [docs] [issue20620] Update the min()/max() docs for the new default
	argument
In-Reply-To: <1392322129.66.0.847659571757.issue20620@psf.upfronthosting.co.za>
Message-ID: <3gXY7d6GNwz7Ljc@mail.python.org>


Roundup Robot added the comment:

New changeset b60258f4499c by Raymond Hettinger in branch '3.4':
Issue 20620: Update the min()/max() docs for the new default argument.
http://hg.python.org/cpython/rev/b60258f4499c

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

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

From report at bugs.python.org  Mon May 19 23:22:15 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 19 May 2014 21:22:15 +0000
Subject: [docs] [issue20620] Update the min()/max() docs for the new default
	argument
In-Reply-To: <1392322129.66.0.847659571757.issue20620@psf.upfronthosting.co.za>
Message-ID: <1400534535.12.0.808859450591.issue20620@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Thanks for the patch.

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

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

From report at bugs.python.org  Tue May 20 00:45:15 2014
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 19 May 2014 22:45:15 +0000
Subject: [docs] [issue20620] Update the min()/max() docs for the new default
	argument
In-Reply-To: <1392322129.66.0.847659571757.issue20620@psf.upfronthosting.co.za>
Message-ID: <1400539515.48.0.392755587774.issue20620@psf.upfronthosting.co.za>


Changes by Berker Peksag <berker.peksag at gmail.com>:


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

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

From report at bugs.python.org  Tue May 20 07:59:44 2014
From: report at bugs.python.org (Florent Xicluna)
Date: Tue, 20 May 2014 05:59:44 +0000
Subject: [docs] [issue21540] PEP 8 should recommend "is not" and "not in"
Message-ID: <1400565584.02.0.148226279911.issue21540@psf.upfronthosting.co.za>


New submission from Florent Xicluna:

Python accepts both syntaxes:

    if not item in some_list and not item is None:
        return item

and

    if item not in some_list and item is not None:
        return item


In the first form, you identify 5 operators: "not", "in", "and", "not" and "in"
In the second form, you find only 3 operators: "not in", "and", "is not"


Of course CPython does internal optimization, and it compiles both expressions to the same bytecode.

However the second form is more readable and less error-prone. It is plain English.

I propose to add such advice to the section "Programming Recommendations" of PEP 8.

----------
assignee: docs at python
components: Documentation
messages: 218837
nosy: barry, docs at python, flox, ncoghlan
priority: normal
severity: normal
status: open
title: PEP 8 should recommend "is not" and "not in"
type: enhancement

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

From report at bugs.python.org  Tue May 20 08:28:01 2014
From: report at bugs.python.org (Florent Xicluna)
Date: Tue, 20 May 2014 06:28:01 +0000
Subject: [docs] [issue21540] PEP 8 should recommend "is not" and "not in"
In-Reply-To: <1400565584.02.0.148226279911.issue21540@psf.upfronthosting.co.za>
Message-ID: <1400567281.39.0.714136422897.issue21540@psf.upfronthosting.co.za>


Changes by Florent Xicluna <florent.xicluna at gmail.com>:


----------
assignee: docs at python -> 

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

From report at bugs.python.org  Tue May 20 15:16:44 2014
From: report at bugs.python.org (Steven Myint)
Date: Tue, 20 May 2014 13:16:44 +0000
Subject: [docs] [issue21540] PEP 8 should recommend "is not" and "not in"
In-Reply-To: <1400565584.02.0.148226279911.issue21540@psf.upfronthosting.co.za>
Message-ID: <1400591804.75.0.757246658588.issue21540@psf.upfronthosting.co.za>


Changes by Steven Myint <code at stevenmyint.com>:


----------
nosy: +myint

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

From report at bugs.python.org  Tue May 20 16:30:29 2014
From: report at bugs.python.org (Ian Cordasco)
Date: Tue, 20 May 2014 14:30:29 +0000
Subject: [docs] [issue21540] PEP 8 should recommend "is not" and "not in"
In-Reply-To: <1400565584.02.0.148226279911.issue21540@psf.upfronthosting.co.za>
Message-ID: <1400596229.36.0.83103915195.issue21540@psf.upfronthosting.co.za>


Changes by Ian Cordasco <graffatcolmingov at gmail.com>:


----------
nosy: +icordasc

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

From phillipruppert at gmail.com  Tue May 20 02:53:01 2014
From: phillipruppert at gmail.com (Phillip Ruppert)
Date: Mon, 19 May 2014 20:53:01 -0400
Subject: [docs] Documentation PDF Links are broken
Message-ID: <A775FC6C-F195-4FC8-8FF8-D2C1DD69CD1A@gmail.com>

I get 404s on the download links on this page.

Download ? Python v2.7.7rc1 documentation


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140519/61d4d698/attachment-0001.html>

From thomas2010college at yahoo.com  Tue May 20 03:44:20 2014
From: thomas2010college at yahoo.com (Thomas T)
Date: Mon, 19 May 2014 18:44:20 -0700 (PDT)
Subject: [docs] Broken LInks
Message-ID: <1400550260.62983.YahooMailBasic@web122002.mail.ne1.yahoo.com>

I tried several times to download the documentation for Python but each time I got a server error that it didn't exist - that is, the files I wanted to download. 

I tried both the zip and tar files and text files, but to no avail.

Thank you for your time and consideration.

Sincerely, Tom Tuckhorn

From markjballard at googlemail.com  Tue May 20 11:47:21 2014
From: markjballard at googlemail.com (Mark Ballard)
Date: Tue, 20 May 2014 10:47:21 +0100
Subject: [docs] rlcompleter documentation
Message-ID: <CAMJSjjv_RUAkHDrEA+MS6rJT2jS0MwCpKTaD9uwVEY=m6gDGSw@mail.gmail.com>

rlcompleter documentation doesn't show adequately how to switch it off.

This is important because rlcompleter is for some an unwelcome change
to the python interpreter.

It is unwelcome because it is poorly implemented.

It has disabled the tab key you would normally use to indent code in
the interpreter. It also appears to have broken the interpreter's
ability to accept cut-and-paste code on the command line
(http://www.gossamer-threads.com/lists/python/python/1086863). These
are both essential features for learners, for skething code and so on.

So I need to get rid of it.

But the Python documentation does not tell you how to switch it off:

https://docs.python.org/3/tutorial/interactive.html

(It has some surreal discussion that appears to refer to the missing
tab indent feature: 13.2. Alternatives to the Interactive Interpreter.
But sympathy is not much use here.)

That text includes a link from the words that say rlcompleter is
'automatically enabled'. This implies it will tell how to switch it
off as well.

It leads here:

https://docs.python.org/3/library/site.html#rlcompleter-config

(It is of course obvious that the rlcompleter is automatically
enabled. But I would challenge anyone who would  criticize this. The
Python documentation needs more statements of the obvious like, for
example, how to switch the rlcompleter off.)

The link goes to an arcane description of "site-specific" functions
that would be enough by now to deter most novices.

Persistence will get you to a description of the rlcompleter that says
you can turn it off by changing an attribute in your "sitecustomize or
usercustomize module or your PYTHONSTARTUP file".

So, determined now to find my Python startup file (that sounds like
something more substantial, more likely to be identified than these
customize modules), I follow the link to the given help page for
PYTHONSTARTUP:

https://docs.python.org/3/using/cmdline.html#envvar-PYTHONSTARTUP

That doesn't tell me where to find PYTHONSTARTUP. It even suggests I
might not have such a file at all!

I am by now so far from my original, simple problem that I'm beginning
to wish I'd taken a ball of string and unravelled it as I went so I
could find my way back again.

The Python interpreter help pages don't tell you how to switch
rlcompleter off either.

Looky here:

"
help> module rlcompleter
no Python documentation found for 'module rlcompleter'
"

It does suggest to me the documention is treated as an afterthought.
If whoever implemented this function was *answerable* to some sort of
appointed documentation representative then not only would the disable
function have been properly documented, but they might have been
forced to implement the disable feature properly because they would
have been forced to address awkward questions posed by someone with
such authority that they couldn't simply say, 'sod off documentation
worm, don't you know who I am - I've got far more important things to
do than bother with your pathetic, snivelling questions". Just a
thought.

From franz.strohmaier at stmk.gv.at  Tue May 20 15:21:40 2014
From: franz.strohmaier at stmk.gv.at (Strohmaier Franz)
Date: Tue, 20 May 2014 15:21:40 +0200
Subject: [docs] Download Python 2.7.7rc1 Documentation 404
Message-ID: <8B0D358D24AA1D4293118AA0E9C3D3CD0103FBC5A430@EXMBX2.stlrg.gv.at>

Hi there
Not even one of the links on this page is working: https://docs.python.org/2.7/download.html


e.g.: https://docs.python.org/2.7/archives/python-2.7.7rc1-docs-pdf-a4.zip results in
404 Not Found
________________________________
nginx


Regards Franz

Franz Strohmaier

Amt der Steierm?rkischen Landesregierung
Abteilung 1 Organisation und Informationstechnik
Burggasse 2 II/203
A-8010 Graz
Tel.: +43 316 877 3381
Mobil: +43 676 8666 3381
Fax: +43 316 877 3992

[cid:image001.png at 01CF7432.44DE4D40]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140520/0d1e8583/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1001 bytes
Desc: image001.png
URL: <http://mail.python.org/pipermail/docs/attachments/20140520/0d1e8583/attachment-0001.png>

From report at bugs.python.org  Tue May 20 19:00:19 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 20 May 2014 17:00:19 +0000
Subject: [docs] [issue21528] Fix a number of typos in the documentation
In-Reply-To: <1400456947.04.0.361173205763.issue21528@psf.upfronthosting.co.za>
Message-ID: <3gY3Hk2gH5z7LjN@mail.python.org>


Roundup Robot added the comment:

New changeset db302b88fdb6 by Donald Stufft in branch 'default':
Fix Issue #21528 - Fix documentation typos
http://hg.python.org/cpython/rev/db302b88fdb6

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

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

From report at bugs.python.org  Tue May 20 19:06:56 2014
From: report at bugs.python.org (Donald Stufft)
Date: Tue, 20 May 2014 17:06:56 +0000
Subject: [docs] [issue21528] Fix a number of typos in the documentation
In-Reply-To: <1400456947.04.0.361173205763.issue21528@psf.upfronthosting.co.za>
Message-ID: <1400605616.32.0.65058269416.issue21528@psf.upfronthosting.co.za>


Changes by Donald Stufft <donald at stufft.io>:


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

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

From bhavishadawada at nyu.edu  Tue May 20 22:12:03 2014
From: bhavishadawada at nyu.edu (Bhavisha Mukesh Dawada)
Date: Tue, 20 May 2014 16:12:03 -0400
Subject: [docs] Issue is downloading Python Doc
Message-ID: <CAF=jRAOq4zfoxC6wGa4=i_ubce8+ei2KkF5ib=_CX8jbA1NTRg@mail.gmail.com>

Hi Sir,

Can you give me a link to download python doc pdf verison. I am not able to
find a link to download the pdf version.

Thanks,
*Bhavisha M. Dawada*

MS Graduate Student | Masters in Computer Science
New York University| New York
(*: (201) 736 0584 |* **: **bhavishadawada at nyu.edu <bhavishadawada at nyu.edu>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140520/801b2a6c/attachment-0001.html>

From libertkc at westinghouse.com  Tue May 20 22:22:24 2014
From: libertkc at westinghouse.com (Liberty, Kirk C)
Date: Tue, 20 May 2014 16:22:24 -0400
Subject: [docs] Cannot download help files
Message-ID: <6044294FD99D0A4E81F9044BA11FB7331B65DFD482@SWEC9984.w-intra.net>

Hello,

I am trying to download the PDF help file, but its link, and all the others, return a 404 error. If there is another location where I can download the docs please advise me of it.

Sincerely,
Kirk Liberty
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140520/3c61ae1b/attachment-0001.html>

From fk1qaz at gmail.com  Tue May 20 22:27:21 2014
From: fk1qaz at gmail.com (=?UTF-8?B?5Yav5Yev?=)
Date: Tue, 20 May 2014 16:27:21 -0400
Subject: [docs] failed to download the python documentation
Message-ID: <CAM0kg7a6=tQjjVQsaFXb8UaYdeO+nB98oNEM_VVeqGHgWZgoYg@mail.gmail.com>

Hi there,

I am a newbie really want to learn python, I see the documentation on
python website are really interesting and are friendly to beginners like
me, however when I want to download it in the pdf format, I failed, the
webpage says 404 not found, I tried different network and different
browser, unfortunately all failed. So I am wondering that if you guys could
send me a copy of version 2.7 documentation in A4 format.

With Regards,

Kai
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140520/279a953b/attachment-0001.html>

From dylanjacobson97 at gmail.com  Tue May 20 22:41:06 2014
From: dylanjacobson97 at gmail.com (Dylan Arkham)
Date: Tue, 20 May 2014 13:41:06 -0700
Subject: [docs] I can't download the 2.7.6 Documentation
Message-ID: <CAPsxdBonFNFpww4i8tqkwFESsF=dgNeJVTWcxmVjNufsFwkbtw@mail.gmail.com>

I went to https://docs.python.org/2/download.html and whenever I try to
download one of the .zip files I get a 404 error. Are these docs no longer
available?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140520/d163632a/attachment-0001.html>

From mail at nick-g.com  Tue May 20 22:48:54 2014
From: mail at nick-g.com (Nick Gillett)
Date: Tue, 20 May 2014 13:48:54 -0700
Subject: [docs] broken links
Message-ID: <B26C166A-C890-4967-A9F1-824CA940D2F9@nick-g.com>

The links on the 
Download Python 2.7.7rc1 Documentation
page are not working. Just get a 404 error when trying to download any of the PDFs.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140520/1c4e4b7d/attachment-0001.html>

From report at bugs.python.org  Tue May 20 23:37:34 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 20 May 2014 21:37:34 +0000
Subject: [docs] [issue21545] Tutorial: examples and comment about mutation
	methods
Message-ID: <1400621853.89.0.606116768213.issue21545@psf.upfronthosting.co.za>


New submission from Terry J. Reedy:

The Tutorial section More on Lists
https://docs.python.org/3.4/tutorial/datastructures.html#more-on-lists includes list.pop but ignores it in the example and final comment. I think the examples should be augmented and the comment modified.

1. (simplest) End the example block with

>>> a.pop()
1234.5
>>> a
[-1, 1, 66.25, 333, 333]

2. The comment says "You might have noticed that methods like insert, remove or sort that modify the list have no return value printed ? they return None. [1] This is a design principle for all mutable data structures in Python." [The footnote says "[1] Other languages may return the mutated object, which allows method chaining, such as d->insert("a")->remove("b")->sort();."]

Inserting 'only' before 'modify' makes the statement true even now with .pop added. I think 'the default' should be added before 'None', but that would be optional. I do not think .pop needs to be explicitly mentioned here since the point of the comment is to explain the lack of a printed return value, and .pop does have a printed return value.

----------
assignee: docs at python
components: Documentation
messages: 218857
nosy: docs at python, ncoghlan, terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Tutorial: examples and comment about mutation methods
type: behavior
versions: Python 2.7, Python 3.4, Python 3.5

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

From report at bugs.python.org  Wed May 21 00:10:16 2014
From: report at bugs.python.org (Barry A. Warsaw)
Date: Tue, 20 May 2014 22:10:16 +0000
Subject: [docs] [issue21540] PEP 8 should recommend "is not" and "not in"
In-Reply-To: <1400565584.02.0.148226279911.issue21540@psf.upfronthosting.co.za>
Message-ID: <1400623815.69.0.275466036516.issue21540@psf.upfronthosting.co.za>


Barry A. Warsaw added the comment:

Agreed!  I'll update the PEP.  Thanks.

----------
assignee:  -> barry

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

From report at bugs.python.org  Wed May 21 00:14:34 2014
From: report at bugs.python.org (Barry A. Warsaw)
Date: Tue, 20 May 2014 22:14:34 +0000
Subject: [docs] [issue21540] PEP 8 should recommend "is not" and "not in"
In-Reply-To: <1400565584.02.0.148226279911.issue21540@psf.upfronthosting.co.za>
Message-ID: <1400624074.84.0.940021307206.issue21540@psf.upfronthosting.co.za>


Changes by Barry A. Warsaw <barry at python.org>:


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

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

From report at bugs.python.org  Wed May 21 00:56:53 2014
From: report at bugs.python.org (Chris Rebert)
Date: Tue, 20 May 2014 22:56:53 +0000
Subject: [docs] [issue21545] Tutorial: examples and comment about mutation
	methods
In-Reply-To: <1400621853.89.0.606116768213.issue21545@psf.upfronthosting.co.za>
Message-ID: <1400626613.69.0.91086515041.issue21545@psf.upfronthosting.co.za>


Changes by Chris Rebert <pybugs at rebertia.com>:


----------
nosy: +cvrebert

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

From report at bugs.python.org  Wed May 21 08:39:20 2014
From: report at bugs.python.org (Joshua Landau)
Date: Wed, 21 May 2014 06:39:20 +0000
Subject: [docs] [issue21547] '!s' formatting documentation bug
Message-ID: <1400654359.7.0.699720681212.issue21547@psf.upfronthosting.co.za>


New submission from Joshua Landau:

In the docs for 2.x about the formatting syntax:

    https://docs.python.org/2/library/string.html#format-string-syntax

it says

    "Two conversion flags are currently supported: '!s' which calls str() on the value, and '!r' which calls repr()."

but for unicode formatters, '!s' calls unicode() instead.

See http://stackoverflow.com/questions/23773816/why-python-str-format-doesnt-call-str for the question that found this.

----------
assignee: docs at python
components: Documentation
messages: 218863
nosy: Joshua.Landau, docs at python
priority: normal
severity: normal
status: open
title: '!s' formatting documentation bug
versions: Python 2.7

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

From report at bugs.python.org  Wed May 21 16:21:36 2014
From: report at bugs.python.org (Eric V. Smith)
Date: Wed, 21 May 2014 14:21:36 +0000
Subject: [docs] [issue21547] '!s' formatting documentation bug
In-Reply-To: <1400654359.7.0.699720681212.issue21547@psf.upfronthosting.co.za>
Message-ID: <1400682096.83.0.850451554067.issue21547@psf.upfronthosting.co.za>


Eric V. Smith added the comment:

I suggest using whatever language explains what "u'%s' %obj" does. It's the same behavior.

>From the SO question, given:

class A(object):
    def __str__(self):
        return 'as str'

    def __unicode__(self):
        return u'as unicode'

Then:

>>> '%s' % A()
'as str'
>>> u'%s' % A()
u'as unicode'

and:

>>> '{!s}'.format(A())
'as str'
>>> u'{!s}'.format(A())
u'as unicode'

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

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

From report at bugs.python.org  Thu May 22 03:43:03 2014
From: report at bugs.python.org (Steven Barker)
Date: Thu, 22 May 2014 01:43:03 +0000
Subject: [docs] [issue21547] '!s' formatting documentation bug
In-Reply-To: <1400654359.7.0.699720681212.issue21547@psf.upfronthosting.co.za>
Message-ID: <1400722983.04.0.928920645364.issue21547@psf.upfronthosting.co.za>


Steven Barker added the comment:

The behavior of !s with the format() methods isn't exactly the same as %s with % formatting. With the latter, the conversion depends on the type of the result string, which in turn depends on whether the format string *or any of the values values* is unicode:

    >>> class X():
        def __str__(self): return "str"
        def __unicode__(self): return u"unicode"

    >>> "%s %s" % ("foo", X())
    'foo str'
    >>> "%s %s" % (u"foo", X())
    u'foo unicode'
    >>> u"%s %s" % ("foo", X())
    u'foo unicode'
    >>> u"%s %s" % (u"foo", X())
    u'foo unicode'

The format methods are more consistent, always returning the same type as the format string regardless of the types of the arguments (and using the appropriate converter):

    >>> "{} {!s}".format("foo", X())
    'foo str'
    >>> "{} {!s}".format(u"foo", X())
    'foo str'
    >>> u"{} {!s}".format("foo", X())
    u'foo unicode'
    >>> u"{} {!s}".format(u"foo", X())
    u'foo unicode'

The documentation for %s conversion (in the second table here: https://docs.python.org/2/library/stdtypes.html#string-formatting-operations ) also suggests that it always uses str(), though the footnote for that table entry alludes to the behavior shown above without ever mentioning using unicode() for conversions explicitly.

----------
nosy: +Steven.Barker

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

From report at bugs.python.org  Thu May 22 16:36:01 2014
From: report at bugs.python.org (David Harrigan)
Date: Thu, 22 May 2014 14:36:01 +0000
Subject: [docs] [issue21545] Tutorial: examples and comment about mutation
	methods
In-Reply-To: <1400621853.89.0.606116768213.issue21545@psf.upfronthosting.co.za>
Message-ID: <1400769361.84.0.870792024842.issue21545@psf.upfronthosting.co.za>


David Harrigan added the comment:

I've added the example and modified the final comment.

----------
keywords: +patch
nosy: +David.Harrigan
Added file: http://bugs.python.org/file35311/datastructures.patch

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

From report at bugs.python.org  Thu May 22 19:39:05 2014
From: report at bugs.python.org (Erik Kusko)
Date: Thu, 22 May 2014 17:39:05 +0000
Subject: [docs] [issue21554] Possible Error in "Brief Tour of the Standard
	Library"
Message-ID: <1400780345.53.0.941799194043.issue21554@psf.upfronthosting.co.za>


New submission from Erik Kusko:

In https://docs.python.org/3/tutorial/stdlib.html, there is an example:

>>> import shutil
>>> shutil.copyfile('data.db', 'archive.db')
>>> shutil.move('/build/executables', 'installdir')

Should it not be:

>>> import shutil
>>> shutil.copyfile('data.db', 'archive.db')
'archive.db'
>>> shutil.move('/build/executables', 'installdir')
'installdir'

?  I am run under Windows, so I don't know if the behavior is different than under Linux.  Under Windows the destination file and destination directory, respectively, are echoed to stdout.

----------
assignee: docs at python
components: Documentation
messages: 218904
nosy: Pitmaster, docs at python
priority: normal
severity: normal
status: open
title: Possible Error in "Brief Tour of the Standard Library"
type: enhancement
versions: Python 3.3

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

From report at bugs.python.org  Thu May 22 19:43:24 2014
From: report at bugs.python.org (R. David Murray)
Date: Thu, 22 May 2014 17:43:24 +0000
Subject: [docs] [issue21554] Possible Error in "Brief Tour of the Standard
	Library"
In-Reply-To: <1400780345.53.0.941799194043.issue21554@psf.upfronthosting.co.za>
Message-ID: <1400780604.47.0.0134095495632.issue21554@psf.upfronthosting.co.za>


R. David Murray added the comment:

Yes, this is a recent enhancement and the example was not updated to match.

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

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

From aagapov.jr at gmail.com  Wed May 21 17:35:12 2014
From: aagapov.jr at gmail.com (Alexey Agapov)
Date: Wed, 21 May 2014 19:35:12 +0400
Subject: [docs] 2x documentation download problem
Message-ID: <CAF_OpVPDYLqDiwCU_=3jsFtxMgn7OhcEM8u5=BREk=_tKjXVJw@mail.gmail.com>

Hi,

I'm not quite sure I'm writing to the correct address, but I would like to
ask a question about a download issue. All the download links on this
page<https://docs.python.org/2/download.html> lead
to 404. Is there a way to download the 2x Python documentation from
anywhere else on the website?

Thank you for your time,
Alex Agapov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140521/f82afa6b/attachment-0001.html>

From janmollowitz at googlemail.com  Wed May 21 23:24:47 2014
From: janmollowitz at googlemail.com (Jan Mollowitz)
Date: Wed, 21 May 2014 23:24:47 +0200
Subject: [docs] All documentation download links for python-2.7.7rc1 are
	broken
Message-ID: <537D199F.5020403@gmail.com>

Hello,

just wanted to let you know that each of the eight file links at

https://docs.python.org/2/download.html

points to a 404 not found page.

Example URL pointed to:
https://docs.python.org/2/archives/python-2.7.7rc1-docs-pdf-letter.zip

With best regards,

Jan Mollowitz

From MHenshaw at palatiumcare.com  Wed May 21 23:11:33 2014
From: MHenshaw at palatiumcare.com (Mike Henshaw)
Date: Wed, 21 May 2014 16:11:33 -0500
Subject: [docs] Pythong 2.7.7rc1 Documentation Download Links broken
Message-ID: <1015023DE542E34784EBC6E568409B5E01998DA9BB97@server01>

None of the download links for the Python 2.7.7rc1 (stable) work.

Have a dynamite day.

Michael Henshaw
AdCom Technologies Inc.
1119 Superior Ave.
Sheboygan, WI 53081
(920) 694-0039 Ext. 217
(920) 208-6839 Fax

http://www.adcomtechnologies.com/

Note:  The information in this E-mail message is legally privileged and confidential information intended only for the use of the individual(s) to whom it is directed as named above. If you, the reader of this message, are not the intended recipient, you are hereby notified that you should not further disseminate, distribute, or forward this E-mail message. If you have received this E-mail in error, please notify us.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140521/912a1ac6/attachment-0001.html>

From nllamb at msn.com  Thu May 22 00:34:58 2014
From: nllamb at msn.com (Nick Lamb)
Date: Wed, 21 May 2014 18:34:58 -0400
Subject: [docs] Links Broken
Message-ID: <BAY175-W35F66861787AD80FA4BC3AC53C0@phx.gbl>

All of the links at the main download page for python 2 seem down/broken.
https://docs.python.org/2/download.html

I get: 

404 Not Found
nginx


from the first download (.bz form):
https://docs.python.org/2/archives/python-2.7.7rc1-docs-pdf-letter.tar.bz2

Note that all of the links display the same error.


Thanks,
-Nick
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140521/8ae2bd63/attachment-0001.html>

From lorenzo.marrese at gmail.com  Thu May 22 21:15:31 2014
From: lorenzo.marrese at gmail.com (Lorenzo Marrese)
Date: Thu, 22 May 2014 15:15:31 -0400
Subject: [docs] Download PDF
Message-ID: <CA+-bXWVf67ghqXSb4bfVCejV5SQ2cyq=A9FpU9YXM5tRg_rVSA@mail.gmail.com>

Hi,

I would like to download the python 2.7 documentation in US letter paper
size PDF .zip. However I keep getting an error and it won't let me download
it, saying it is not there. If possible, could you email me a .zip file?

Thank you,
Lorenzo
lorenzo.marrese at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140522/0939baa9/attachment.html>

From report at bugs.python.org  Thu May 22 21:47:29 2014
From: report at bugs.python.org (Zachary Ware)
Date: Thu, 22 May 2014 19:47:29 +0000
Subject: [docs] [issue21534] 404 on documentation download links
In-Reply-To: <1400506899.65.0.0656735087144.issue21534@psf.upfronthosting.co.za>
Message-ID: <1400788049.67.0.95331279805.issue21534@psf.upfronthosting.co.za>


Zachary Ware added the comment:

Reports continue to pour in on docs@, 25 reports for 2.7.7rc1 and 3.4.1 so far by my count.

Is there anything I can do to help on this?  It looks to me like the files just haven't been uploaded, but I don't know where exactly they should be uploaded to, nor do I have the keys to do it.

----------
assignee: docs at python -> 
priority: high -> critical

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

From report at bugs.python.org  Thu May 22 22:06:44 2014
From: report at bugs.python.org (Ned Deily)
Date: Thu, 22 May 2014 20:06:44 +0000
Subject: [docs] [issue21534] 404 on documentation download links
In-Reply-To: <1400506899.65.0.0656735087144.issue21534@psf.upfronthosting.co.za>
Message-ID: <1400789204.7.0.761001857331.issue21534@psf.upfronthosting.co.za>


Ned Deily added the comment:

At the moment, the links for 3.4.1 documentation downloads at https://docs.python.org/3/download.html appear to be working AFAICT; anyone see otherwise?  However, the 2.7.7rc1 links are broken (https://docs.python.org/2/download.html).  Benjamin?

----------
nosy: +ned.deily

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

From report at bugs.python.org  Thu May 22 22:19:41 2014
From: report at bugs.python.org (David Harrigan)
Date: Thu, 22 May 2014 20:19:41 +0000
Subject: [docs] [issue21554] Possible Error in "Brief Tour of the Standard
	Library"
In-Reply-To: <1400780345.53.0.941799194043.issue21554@psf.upfronthosting.co.za>
Message-ID: <1400789981.6.0.230066718423.issue21554@psf.upfronthosting.co.za>


Changes by David Harrigan <dharrigan118 at gmail.com>:


----------
keywords: +patch
Added file: http://bugs.python.org/file35318/stdlib.patch

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

From report at bugs.python.org  Thu May 22 22:23:03 2014
From: report at bugs.python.org (Zachary Ware)
Date: Thu, 22 May 2014 20:23:03 +0000
Subject: [docs] [issue21534] 404 on documentation download links
In-Reply-To: <1400506899.65.0.0656735087144.issue21534@psf.upfronthosting.co.za>
Message-ID: <1400790183.08.0.209930185717.issue21534@psf.upfronthosting.co.za>


Zachary Ware added the comment:

You're right, Ned; 3.4.1 is working for me now, but 2.7.7rc1 is still broken. (Sorry for not checking again!)

----------

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

From report at bugs.python.org  Thu May 22 23:33:48 2014
From: report at bugs.python.org (Chris Rebert)
Date: Thu, 22 May 2014 21:33:48 +0000
Subject: [docs] [issue21557] os.popen & os.system lack shell-related
	security warnings
Message-ID: <1400794428.31.0.170474236819.issue21557@psf.upfronthosting.co.za>


New submission from Chris Rebert:

Since these functions run shell commands, which is a common vector for security-related bugs (see
* http://cwe.mitre.org/data/definitions/78.html
* http://cwe.mitre.org/data/definitions/88.html
), I suggest that they should have security warning boxes analogous to the one for the `subprocess` module:
https://docs.python.org/2/library/subprocess.html#frequently-used-arguments

----------
assignee: docs at python
components: Documentation
messages: 218921
nosy: cvrebert, docs at python
priority: normal
severity: normal
status: open
title: os.popen & os.system lack shell-related security warnings
versions: Python 2.7, Python 3.5

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

From report at bugs.python.org  Fri May 23 00:27:58 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 May 2014 22:27:58 +0000
Subject: [docs] [issue21554] Possible Error in "Brief Tour of the Standard
	Library"
In-Reply-To: <1400780345.53.0.941799194043.issue21554@psf.upfronthosting.co.za>
Message-ID: <1400797678.88.0.475547639877.issue21554@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/issue21554>
_______________________________________

From report at bugs.python.org  Fri May 23 00:38:05 2014
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 22 May 2014 22:38:05 +0000
Subject: [docs] [issue21554] Possible Error in "Brief Tour of the Standard
	Library"
In-Reply-To: <1400780345.53.0.941799194043.issue21554@psf.upfronthosting.co.za>
Message-ID: <3gZQhX3sQ1z7Lr6@mail.python.org>


Roundup Robot added the comment:

New changeset e07e347688a0 by Raymond Hettinger in branch '3.4':
Issue 21554:  Repair an out-of-date tutorial example to reflect changes in shutil.
http://hg.python.org/cpython/rev/e07e347688a0

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

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

From report at bugs.python.org  Fri May 23 00:38:54 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 May 2014 22:38:54 +0000
Subject: [docs] [issue21554] Possible Error in "Brief Tour of the Standard
	Library"
In-Reply-To: <1400780345.53.0.941799194043.issue21554@psf.upfronthosting.co.za>
Message-ID: <1400798334.13.0.866450614577.issue21554@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Fixed.

Thanks for the clear bug report.

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

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

From report at bugs.python.org  Fri May 23 00:42:01 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 May 2014 22:42:01 +0000
Subject: [docs] [issue21545] Tutorial: examples and comment about mutation
	methods
In-Reply-To: <1400621853.89.0.606116768213.issue21545@psf.upfronthosting.co.za>
Message-ID: <1400798521.69.0.864533755709.issue21545@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

That looks good and is ready to apply.

----------
nosy: +rhettinger

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

From report at bugs.python.org  Fri May 23 01:00:51 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 May 2014 23:00:51 +0000
Subject: [docs] [issue21198] Minor tarfile documentation bug
In-Reply-To: <1397148227.41.0.631676560193.issue21198@psf.upfronthosting.co.za>
Message-ID: <1400799651.3.0.457154586879.issue21198@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/issue21198>
_______________________________________

From report at bugs.python.org  Fri May 23 01:04:40 2014
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 22 May 2014 23:04:40 +0000
Subject: [docs] [issue21198] Minor tarfile documentation bug
In-Reply-To: <1397148227.41.0.631676560193.issue21198@psf.upfronthosting.co.za>
Message-ID: <3gZRHC3wKqz7LrR@mail.python.org>


Roundup Robot added the comment:

New changeset 630bc60cba04 by Raymond Hettinger in branch '3.4':
Issue 21198: Minor tarfile documentation bug.
http://hg.python.org/cpython/rev/630bc60cba04

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

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

From report at bugs.python.org  Fri May 23 01:06:11 2014
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 22 May 2014 23:06:11 +0000
Subject: [docs] [issue21198] Minor tarfile documentation bug
In-Reply-To: <1397148227.41.0.631676560193.issue21198@psf.upfronthosting.co.za>
Message-ID: <3gZRJy3yR3z7LjM@mail.python.org>


Roundup Robot added the comment:

New changeset 5c1fb67f2edf by Raymond Hettinger in branch '2.7':
Issue 21198: Minor tarfile documentation bug.
http://hg.python.org/cpython/rev/5c1fb67f2edf

----------

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

From report at bugs.python.org  Fri May 23 01:06:48 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 May 2014 23:06:48 +0000
Subject: [docs] [issue21198] Minor tarfile documentation bug
In-Reply-To: <1397148227.41.0.631676560193.issue21198@psf.upfronthosting.co.za>
Message-ID: <1400800008.48.0.811131976047.issue21198@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Thanks for the report and the patch.
Fixed now :-)

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

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

From report at bugs.python.org  Fri May 23 01:07:19 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 May 2014 23:07:19 +0000
Subject: [docs] [issue21479] Document TarFile.open() as a classmethod
In-Reply-To: <1399906899.24.0.584343681531.issue21479@psf.upfronthosting.co.za>
Message-ID: <1400800039.49.0.529662645561.issue21479@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/issue21479>
_______________________________________

From report at bugs.python.org  Fri May 23 03:25:22 2014
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 23 May 2014 01:25:22 +0000
Subject: [docs] [issue21198] Minor tarfile documentation bug
In-Reply-To: <1397148227.41.0.631676560193.issue21198@psf.upfronthosting.co.za>
Message-ID: <1400808322.87.0.0340230083354.issue21198@psf.upfronthosting.co.za>


Changes by Berker Peksag <berker.peksag at gmail.com>:


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

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

From report at bugs.python.org  Fri May 23 04:43:42 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 23 May 2014 02:43:42 +0000
Subject: [docs] [issue21479] Document TarFile.open() as a classmethod
In-Reply-To: <1399906899.24.0.584343681531.issue21479@psf.upfronthosting.co.za>
Message-ID: <3gZX7w1Cn2z7Lp9@mail.python.org>


Roundup Robot added the comment:

New changeset e6a9beaff8c9 by Raymond Hettinger in branch '2.7':
Issue 21479: Fix markup for the TarFile.open() classmethod.
http://hg.python.org/cpython/rev/e6a9beaff8c9

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

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

From report at bugs.python.org  Fri May 23 04:47:21 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 23 May 2014 02:47:21 +0000
Subject: [docs] [issue21479] Document TarFile.open() as a classmethod
In-Reply-To: <1399906899.24.0.584343681531.issue21479@psf.upfronthosting.co.za>
Message-ID: <3gZXD917N7z7Lp9@mail.python.org>


Roundup Robot added the comment:

New changeset 37d2a6bcf7ae by Raymond Hettinger in branch '3.4':
Issue 21479: Fix markup for the TarFile.open() classmethod.
http://hg.python.org/cpython/rev/37d2a6bcf7ae

----------

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

From report at bugs.python.org  Fri May 23 04:47:48 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 May 2014 02:47:48 +0000
Subject: [docs] [issue21479] Document TarFile.open() as a classmethod
In-Reply-To: <1399906899.24.0.584343681531.issue21479@psf.upfronthosting.co.za>
Message-ID: <1400813268.44.0.336107497995.issue21479@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri May 23 05:01:33 2014
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 23 May 2014 03:01:33 +0000
Subject: [docs] [issue21479] Document TarFile.open() as a classmethod
In-Reply-To: <1399906899.24.0.584343681531.issue21479@psf.upfronthosting.co.za>
Message-ID: <1400814093.52.0.992250409437.issue21479@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for committing this, Raymond.

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

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

From report at bugs.python.org  Fri May 23 05:58:48 2014
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 23 May 2014 03:58:48 +0000
Subject: [docs] [issue21558] Fix a typo in the contextlib docs
Message-ID: <1400817528.11.0.0994185866372.issue21558@psf.upfronthosting.co.za>


New submission from Berker Peksag:

>From the code example at https://docs.python.org/3.5/library/contextlib.html#supporting-a-variable-number-of-context-managers

"if need_special resource:" (see line 4) should be "if need_special_resource:".

Related changeset: http://hg.python.org/cpython/rev/5d91d87b5969

----------
assignee: docs at python
components: Documentation
files: contextlib-typo.diff
keywords: patch
messages: 218944
nosy: berker.peksag, docs at python
priority: normal
severity: normal
stage: patch review
status: open
title: Fix a typo in the contextlib docs
versions: Python 3.4, Python 3.5
Added file: http://bugs.python.org/file35322/contextlib-typo.diff

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

From report at bugs.python.org  Fri May 23 06:35:16 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 23 May 2014 04:35:16 +0000
Subject: [docs] [issue21545] Tutorial: examples and comment about mutation
	methods
In-Reply-To: <1400621853.89.0.606116768213.issue21545@psf.upfronthosting.co.za>
Message-ID: <3gZZcf6ntfz7Lpy@mail.python.org>


Roundup Robot added the comment:

New changeset 6fc09f30b514 by Terry Jan Reedy in branch '2.7':
Issue #21545: Add .pop example and tweak comment about pure mutation methods.
http://hg.python.org/cpython/rev/6fc09f30b514

New changeset 3f2b6034b73a by Terry Jan Reedy in branch '3.4':
Issue #21545: Add .pop example and tweak comment about pure mutation methods.
http://hg.python.org/cpython/rev/3f2b6034b73a

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

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

From report at bugs.python.org  Fri May 23 06:38:02 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 23 May 2014 04:38:02 +0000
Subject: [docs] [issue21545] Tutorial: examples and comment about mutation
	methods
In-Reply-To: <1400621853.89.0.606116768213.issue21545@psf.upfronthosting.co.za>
Message-ID: <1400819882.72.0.971903020954.issue21545@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Thanks David. If this is not to be your last contribution, and we hope not, please fill out the contributor agreement, if you have hot already, at
https://www.python.org/psf/contrib/contrib-form/

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

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

From report at bugs.python.org  Fri May 23 12:34:39 2014
From: report at bugs.python.org (theme)
Date: Fri, 23 May 2014 10:34:39 +0000
Subject: [docs] [issue21559] OverflowError should not happen for integer
	operations
Message-ID: <1400841279.05.0.350458307747.issue21559@psf.upfronthosting.co.za>


New submission from theme:

>From the documentation at https://docs.python.org/3.4/library/exceptions.html#OverflowError all integer operations should not throw OverflowError no matter what. However, there are so many issues here that describe library functions and built-in functions doing exactly that (just search this website for OverflowError).
This might cause an expected uncaught exception that the cause cannot be deduced after reading the documentation.
There are 2 ways to fix this: either change the documentation, or change something in the core of the interpreter.
Note: I don't know what versions of python this affects, but I have tested this on python 3.4.0 on windows. (the version that was downloadable from www.python.org/downloads/)

----------
assignee: docs at python
components: Documentation, Interpreter Core
messages: 218957
nosy: docs at python, theme
priority: normal
severity: normal
status: open
title: OverflowError should not happen for integer operations
type: behavior
versions: Python 3.4

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

From report at bugs.python.org  Fri May 23 12:35:32 2014
From: report at bugs.python.org (theme)
Date: Fri, 23 May 2014 10:35:32 +0000
Subject: [docs] [issue21559] OverflowError should not happen for integer
	operations
In-Reply-To: <1400841279.05.0.350458307747.issue21559@psf.upfronthosting.co.za>
Message-ID: <1400841332.46.0.680793271672.issue21559@psf.upfronthosting.co.za>


Changes by theme <theemathas at gmail.com>:


----------
components: +Library (Lib)

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

From report at bugs.python.org  Fri May 23 13:18:32 2014
From: report at bugs.python.org (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Fri, 23 May 2014 11:18:32 +0000
Subject: [docs] [issue21558] Fix a typo in the contextlib docs
In-Reply-To: <1400817528.11.0.0994185866372.issue21558@psf.upfronthosting.co.za>
Message-ID: <1400843912.53.0.750427027877.issue21558@psf.upfronthosting.co.za>


Changes by Jes?s Cea Avi?n <jcea at jcea.es>:


----------
nosy: +jcea

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

From report at bugs.python.org  Fri May 23 14:37:02 2014
From: report at bugs.python.org (David Harrigan)
Date: Fri, 23 May 2014 12:37:02 +0000
Subject: [docs] [issue21545] Tutorial: examples and comment about mutation
	methods
In-Reply-To: <1400621853.89.0.606116768213.issue21545@psf.upfronthosting.co.za>
Message-ID: <1400848622.33.0.766933325236.issue21545@psf.upfronthosting.co.za>


David Harrigan added the comment:

Thanks for the info, I've signed the agreement.

----------

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

From brodiej at amazon.com  Thu May 22 23:22:31 2014
From: brodiej at amazon.com (Brodie, John)
Date: Thu, 22 May 2014 21:22:31 +0000
Subject: [docs] links broken
Message-ID: <1233990826F8834E8C982640EF9F5772E858C0@ex10-mbx-31007.ant.amazon.com>

All of the download link on this page are broken:  https://docs.python.org/2/download.html



John Brodie
Sr. Hardware Engineer
Amazon.com
(206) 922-0247

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140522/aee1310a/attachment-0001.html>

From dadsetan.ali at gmail.com  Fri May 23 08:43:56 2014
From: dadsetan.ali at gmail.com (Ali Dadsetan)
Date: Fri, 23 May 2014 11:13:56 +0430
Subject: [docs] Broken Links
Message-ID: <CAM5-Sw0PitVzh0w7TH4hSeY_z+FLtCs5ZhnsqB06EyrubtD7YA@mail.gmail.com>

Dear Sir/Madam

It seems that all of download links for python
2.7<https://docs.python.org/2.7/download.html>documentations are dead.
As the update date for this documentation is
today, I felt I should report this. Thanks for your considerations.

Sincerely,
Ali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140523/fff7eff8/attachment-0001.html>

From steve.s.6318 at gmail.com  Fri May 23 09:52:21 2014
From: steve.s.6318 at gmail.com (steve spaulding)
Date: Fri, 23 May 2014 09:52:21 +0200
Subject: [docs] no file error on download page
Message-ID: <CAKq_eR+uYsBshFiAGpw2A8pxrEti_d24YGSDJn3EvS76onzFpg@mail.gmail.com>

hello:

i was attempting to download the python 2.7 documentation and i am getting
a "Failes - No file", from this location:

https://docs.python.org/2/download.html

I tried both the tar ball and zip for html, and pdf with the same results.

thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140523/d94b76e0/attachment-0001.html>

From guido at vonrudorff.de  Fri May 23 10:24:59 2014
From: guido at vonrudorff.de (Guido Falk von Rudorff)
Date: Fri, 23 May 2014 10:24:59 +0200
Subject: [docs] Downloadable Documentation broken
Message-ID: <833D3A24-ED54-47CB-A5BC-A0E4F4934F8F@vonrudorff.de>

Dear Sir or Madam,

none of the links on [1] is currently valid, as nginx returns a 404. Do I have missed anything?

Kind regards,

Guido Falk von Rudorff

[ 1 ] https://docs.python.org/2/download.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140523/bf06d9a3/attachment-0001.html>

From debayly at gmail.com  Fri May 23 16:19:38 2014
From: debayly at gmail.com (Devin Bayly)
Date: Fri, 23 May 2014 07:19:38 -0700
Subject: [docs] Download Python 2.7.7rc1 Documentation
Message-ID: <CAOy+FmYZGMxWi0NHNnU3dus_SO+OQabg5vqpkTf3eBooOsnURw@mail.gmail.com>

Hello there,

I am interested in having a copy of the Python Documentation for Offline
work, but each of the links on this page return a 404 error.

Would you send me a copy of the documentation?

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140523/cba09221/attachment-0001.html>

From shakyanipun at gmail.com  Fri May 23 16:55:47 2014
From: shakyanipun at gmail.com (Nipun Shakya)
Date: Fri, 23 May 2014 20:40:47 +0545
Subject: [docs] Python docs 2.7.7rc1 cannot be downloaded
Message-ID: <537F6173.5030901@gmail.com>

Respected sir, the download page https://docs.python.org/2/download.html 
containing any format of python docs cannot be downloaded. The following 
error is generated when tried to download:


  404 Not Found

------------------------------------------------------------------------
nginx

I hope the problem is resolved soon.

Regards, Nipun Shakya
Nepdroid Innovations


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140523/2ad40d9a/attachment-0001.html>

From khoguan at gmail.com  Fri May 23 17:12:31 2014
From: khoguan at gmail.com (Khoguan Phuann)
Date: Fri, 23 May 2014 23:12:31 +0800
Subject: [docs] Python 3 doc webpage sidebar << mark issue
Message-ID: <312C0850-F025-4350-A98F-C19773BDD190@gmail.com>

To the webmasters of  Python 3 documentation website,

Hello, I'd like to report a sidebar << mark issue arising from https://docs.python.org/3/index.html
webpages.

I read the Python 3 official documentation on iPad. When I view it without zooming in,
the page looks fine. But the font is too small for my eyesight, so I use 2-finger pinch
to zoom in. Then I find that the << mark at the middle of the grey border of the sidebar floats astray and intrudes into the main documentation area.

This is the original, normal view. Please note the normal position of the << mark
which I circle with red.



And this is the zoomed-in view. Please also note the abnormal floating position of
the << mark.



When I read the Python 3 doc, the floating << is really distracting. Would you please
resolve this issue? Compare with Python 2 doc webpage, there's no this kind of
issue when it's zoomed in, see:



Thanks a lot for your efforts in creating and maintaining this wonderful site.
And I'd appreciate your listening to me and adjusting the CSS for the Python 3
webpages.

Best regards,

Khoguan Pan
khoguan at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140523/2c5c0827/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Python3_doc.jpg
Type: image/jpg
Size: 177773 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20140523/2c5c0827/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Python3_doc_zoomin.jpg
Type: image/jpg
Size: 173887 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20140523/2c5c0827/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Python2_doc.png
Type: image/png
Size: 103885 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20140523/2c5c0827/attachment-0001.png>

From report at bugs.python.org  Fri May 23 20:46:56 2014
From: report at bugs.python.org (Charles Merriam)
Date: Fri, 23 May 2014 18:46:56 +0000
Subject: [docs] [issue21562] curses getsxy() should be curses getxy()
	in	https://docs.python.org/3/library/curses.html#curses.cursxy
Message-ID: <1400870816.3.0.300590440768.issue21562@psf.upfronthosting.co.za>


New submission from Charles Merriam:

https://docs.python.org/3/library/curses.html#curses.cursxy

The symbol 'getsxy' does not exist in the curses library.  The correct symbol is 'getxy'.

----------
assignee: docs at python
components: Documentation
messages: 218986
nosy: Charles.Merriam, docs at python
priority: normal
severity: normal
status: open
title: curses getsxy() should be curses getxy() in https://docs.python.org/3/library/curses.html#curses.cursxy
type: behavior
versions: Python 3.4

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

From report at bugs.python.org  Fri May 23 21:32:13 2014
From: report at bugs.python.org (Ned Deily)
Date: Fri, 23 May 2014 19:32:13 +0000
Subject: [docs] [issue8243] curses writing to window's bottom right position
	raises:	`_curses.error: addstr() returned ERR'
In-Reply-To: <1352121880.55.0.191535515397.issue8243@psf.upfronthosting.co.za>
Message-ID: <1400873533.07.0.170767527845.issue8243@psf.upfronthosting.co.za>


Ned Deily added the comment:

FTR, the previous issue is Issue441429.  A documentation patch would be welcomed.

----------
assignee:  -> docs at python
components: +Documentation
keywords: +easy
nosy: +docs at python, ned.deily
stage:  -> needs patch
versions: +Python 3.5 -Python 3.2, Python 3.3

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

From report at bugs.python.org  Fri May 23 21:33:21 2014
From: report at bugs.python.org (Ned Deily)
Date: Fri, 23 May 2014 19:33:21 +0000
Subject: [docs] [issue21562] curses getsxy() should be curses getxy()
	in	https://docs.python.org/3/library/curses.html#curses.cursxy
In-Reply-To: <1400870816.3.0.300590440768.issue21562@psf.upfronthosting.co.za>
Message-ID: <1400873601.27.0.759214086193.issue21562@psf.upfronthosting.co.za>


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


----------
keywords: +easy
versions: +Python 3.5

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

From report at bugs.python.org  Fri May 23 22:32:22 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 23 May 2014 20:32:22 +0000
Subject: [docs] [issue21533] built-in types dict docs - construct dict from
	iterable, not iterator
In-Reply-To: <1400487015.16.0.760931173475.issue21533@psf.upfronthosting.co.za>
Message-ID: <1400877142.15.0.717343603975.issue21533@psf.upfronthosting.co.za>


Changes by Terry J. Reedy <tjreedy at udel.edu>:


----------
assignee: docs at python -> terry.reedy
nosy: +terry.reedy
stage:  -> commit review
versions: +Python 2.7, Python 3.4, Python 3.5

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

From report at bugs.python.org  Fri May 23 23:00:07 2014
From: report at bugs.python.org (Charles Merriam)
Date: Fri, 23 May 2014 21:00:07 +0000
Subject: [docs] [issue8243] curses writing to window's bottom right position
	raises:	`_curses.error: addstr() returned ERR'
In-Reply-To: <1400873533.07.0.170767527845.issue8243@psf.upfronthosting.co.za>
Message-ID: <CACYynckUmWFcgR1XiAXkC=s0e1c0pvCFzO-eNa+4sKzDMFxMGw@mail.gmail.com>


Charles Merriam added the comment:

My typo.  Documentation verbiage was included in the bug report.
Submitting a patch to the documentation is a harder than just
rewriting the library.  I speak English, MarkDown, HTML, JavaScript,
and even RST.  I don't speak Sphinx, DocBook, or TeX.

On Fri, May 23, 2014 at 12:32 PM, Ned Deily <report at bugs.python.org> wrote:
>
> Ned Deily added the comment:
>
> FTR, the previous issue is Issue441429.  A documentation patch would be welcomed.
>
> ----------
> assignee:  -> docs at python
> components: +Documentation
> keywords: +easy
> nosy: +docs at python, ned.deily
> stage:  -> needs patch
> versions: +Python 3.5 -Python 3.2, Python 3.3
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <http://bugs.python.org/issue8243>
> _______________________________________

----------
nosy: +CharlesMerriam

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

From report at bugs.python.org  Fri May 23 23:09:12 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 23 May 2014 21:09:12 +0000
Subject: [docs] [issue21558] Fix a typo in the contextlib docs
In-Reply-To: <1400817528.11.0.0994185866372.issue21558@psf.upfronthosting.co.za>
Message-ID: <1400879352.01.0.523743327715.issue21558@psf.upfronthosting.co.za>


Changes by Terry J. Reedy <tjreedy at udel.edu>:


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

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

From report at bugs.python.org  Fri May 23 23:18:44 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 23 May 2014 21:18:44 +0000
Subject: [docs] [issue21559] OverflowError should not happen for integer
	operations
In-Reply-To: <1400841279.05.0.350458307747.issue21559@psf.upfronthosting.co.za>
Message-ID: <1400879924.0.0.391392290675.issue21559@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

In 2.7, it was only *long integers* that could not overflow. In both python 2 and 3, the comment only applys to operations on integers and not to integers converted to floats. Perhaps that could be clarified. If have any example from running Python where (long) integer operations raising OverflowError and there is no issue about the bug, please open one. If there are any issues that describe such exceptions as not bugs, please list them also.

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

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

From report at bugs.python.org  Sat May 24 02:39:42 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 24 May 2014 00:39:42 +0000
Subject: [docs] [issue21558] Fix a typo in the contextlib docs
In-Reply-To: <1400817528.11.0.0994185866372.issue21558@psf.upfronthosting.co.za>
Message-ID: <1400891982.58.0.164802334914.issue21558@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Berker, feel free to assign all these micro-doc fixes to me.   Also, if you want to combine a number of clear-cut, non-controversial fixes into just one patch and tracker item, that might save us both some time.

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

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

From report at bugs.python.org  Sat May 24 06:44:26 2014
From: report at bugs.python.org (theme)
Date: Sat, 24 May 2014 04:44:26 +0000
Subject: [docs] [issue21559] OverflowError should not happen for integer
	operations
In-Reply-To: <1400841279.05.0.350458307747.issue21559@psf.upfronthosting.co.za>
Message-ID: <1400906665.92.0.845782684644.issue21559@psf.upfronthosting.co.za>


theme added the comment:

This is a (non-comprehensive) list of issues that describe or imply that OverflowError on integers is normal.

- http://bugs.python.org/issue7267 "Attached patch works around the inital issue (u'{0:c}'.format(256)) by raising OverflowError on int.__format__('c') if the value is not in range(0, 256)."
- http://bugs.python.org/issue20539 "Patch applied to the default branch (but with OverflowError instead of ValueError for large positive inputs)."
- http://bugs.python.org/issue21444 "CPython has historically imposed some artificial implementation specific details in order make the implementation cleaner and faster internally (i.e. a limit on the number of function arguments, sys.maxsize limits, etc.)"
- http://bugs.python.org/issue15988 (No message explicitly telling that OverflowError is the right error to raise. However, it is implied that only the error message, not the error type, should be changed)

There might be other similar issues out there.
Am I opening a can of worms?

----------

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

From report at bugs.python.org  Sat May 24 12:50:14 2014
From: report at bugs.python.org (Stefan Krah)
Date: Sat, 24 May 2014 10:50:14 +0000
Subject: [docs] [issue21559] OverflowError should not happen for integer
	operations
In-Reply-To: <1400841279.05.0.350458307747.issue21559@psf.upfronthosting.co.za>
Message-ID: <1400928614.48.0.757683192689.issue21559@psf.upfronthosting.co.za>


Stefan Krah added the comment:

OverflowError vs. ValueError is a debatable issue (msg215873). In my
view ValueError should be raised in most of the cases.

I do not see anything wrong with the docs though, since the link
you posted talks about "arithmetic operations".

----------
nosy: +skrah

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

From report at bugs.python.org  Sat May 24 14:10:16 2014
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 24 May 2014 12:10:16 +0000
Subject: [docs] [issue8243] curses writing to window's bottom right position
	raises:	`_curses.error: addstr() returned ERR'
In-Reply-To: <1352121880.55.0.191535515397.issue8243@psf.upfronthosting.co.za>
Message-ID: <1400933416.58.0.371155173195.issue8243@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Knowledge of RST should be more than enough; there is not much Sphinx-specific markup, and even that you won't pick up easily while looking at the file.

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

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

From report at bugs.python.org  Sat May 24 14:10:27 2014
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 24 May 2014 12:10:27 +0000
Subject: [docs] [issue8243] curses writing to window's bottom right position
	raises:	`_curses.error: addstr() returned ERR'
In-Reply-To: <1352121880.55.0.191535515397.issue8243@psf.upfronthosting.co.za>
Message-ID: <1400933427.84.0.011285546481.issue8243@psf.upfronthosting.co.za>


Georg Brandl added the comment:

you WILL pick up, of course.

----------

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

From report at bugs.python.org  Sat May 24 23:50:56 2014
From: report at bugs.python.org (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Sat, 24 May 2014 21:50:56 +0000
Subject: [docs] [issue21562] curses getsxy() should be curses getxy()
	in	https://docs.python.org/3/library/curses.html#curses.cursxy
In-Reply-To: <1400870816.3.0.300590440768.issue21562@psf.upfronthosting.co.za>
Message-ID: <1400968256.6.0.23320460431.issue21562@psf.upfronthosting.co.za>


Jes?s Cea Avi?n added the comment:

Python 3.5. File "_cursesmodule.c", line 3522.

Marking this bug as invalid. Please, reopen if you think I am mistaken.

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

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

From report at bugs.python.org  Sat May 24 23:51:38 2014
From: report at bugs.python.org (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Sat, 24 May 2014 21:51:38 +0000
Subject: [docs] [issue21562] curses getsxy() should be curses getxy()
	in	https://docs.python.org/3/library/curses.html#curses.cursxy
In-Reply-To: <1400870816.3.0.300590440768.issue21562@psf.upfronthosting.co.za>
Message-ID: <1400968298.97.0.468249634524.issue21562@psf.upfronthosting.co.za>


Changes by Jes?s Cea Avi?n <jcea at jcea.es>:


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

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

From report at bugs.python.org  Sun May 25 00:15:42 2014
From: report at bugs.python.org (Benjamin Peterson)
Date: Sat, 24 May 2014 22:15:42 +0000
Subject: [docs] [issue21534] 404 on documentation download links
In-Reply-To: <1400506899.65.0.0656735087144.issue21534@psf.upfronthosting.co.za>
Message-ID: <1400969742.04.0.666247988409.issue21534@psf.upfronthosting.co.za>


Changes by Benjamin Peterson <benjamin at python.org>:


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

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

From report at bugs.python.org  Sun May 25 04:41:36 2014
From: report at bugs.python.org (theme)
Date: Sun, 25 May 2014 02:41:36 +0000
Subject: [docs] [issue21559] OverflowError should not happen for integer
	operations
In-Reply-To: <1400841279.05.0.350458307747.issue21559@psf.upfronthosting.co.za>
Message-ID: <1400985695.79.0.849169048304.issue21559@psf.upfronthosting.co.za>


theme added the comment:

skrah: I am not sure what link are you referring to.
However, no matter which link you are talking about, the documentation still doesn't match the behavior no matter how you interpret it.

Some possible interpretations of the documentation on OverflowError:

- OverflowError is raised only by "arithmetic operations" on non-integers in the strictest sense possible (e.g. +,-,*,/,**) , which does not include library functions. This interpretation seems absurd to me.

- OverflowError is raised by arithmetic operations on "non-integers", where "integers" refer only to python integers, which never overflow, and excludes C integers. This seems pretty awkward, since this implies that the behavior of library functions regarding overflows is implementation-defined (aka undefined behavior) to some extent, and I don't think this is good.

- OverflowError is raised by arithmetic operations on non-integers, which can be initiated by either the user, a user script or a library function. However, the issues linked in msg219024 involve library functions that obviously deals only with integers. Resolving behaviors to match this interpretation seems pretty logical to me, but will most likely cause a lot of implementation issues.

----------

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

From report at bugs.python.org  Sun May 25 12:05:03 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 25 May 2014 10:05:03 +0000
Subject: [docs] [issue18918] help('FILES') finds no documentation
In-Reply-To: <1378269620.52.0.763555902483.issue18918@psf.upfronthosting.co.za>
Message-ID: <3gbxrF6R1mz7LlQ@mail.python.org>


Roundup Robot added the comment:

New changeset 3fa76139c908 by Serhiy Storchaka in branch '3.4':
Issue #18918: Removed non-existing topic from a list of available topics.
http://hg.python.org/cpython/rev/3fa76139c908

New changeset e5bac5b2f38d by Serhiy Storchaka in branch 'default':
Issue #18918: Removed non-existing topic from a list of available topics.
http://hg.python.org/cpython/rev/e5bac5b2f38d

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

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

From report at bugs.python.org  Sun May 25 12:13:33 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 25 May 2014 10:13:33 +0000
Subject: [docs] [issue18918] help('FILES') finds no documentation
In-Reply-To: <1378269620.52.0.763555902483.issue18918@psf.upfronthosting.co.za>
Message-ID: <1401012813.35.0.206111555124.issue18918@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Fixed in Python 3. Thanks Claudiu.

But it is not clear why this topic is absent in 2.7.

----------
nosy: +serhiy.storchaka
versions:  -Python 3.3, Python 3.4

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

From report at bugs.python.org  Sun May 25 14:36:25 2014
From: report at bugs.python.org (Jan-Philip Gehrcke)
Date: Sun, 25 May 2014 12:36:25 +0000
Subject: [docs] [issue21575] list.sort() should show arguments in tutorial
Message-ID: <1401021385.55.0.784639264396.issue21575@psf.upfronthosting.co.za>


New submission from Jan-Philip Gehrcke:

Currently, the tutorial for the list sort method does not show allowed arguments:


    list.sort()
        Sort the items of the list in place.

(see e.g. https://docs.python.org/3.4/tutorial/datastructures.html)

Is there a reason why we do not show the arguments there? For simplicity? One should note that a web search for Python's list methods ranks that page pretty high. We could list the defaults, as in the built-in help:

     L.sort(cmp=None, key=None, reverse=False)

And could link to https://docs.python.org/2/library/functions.html#sorted for an explanation.

----------
assignee: docs at python
components: Documentation
messages: 219085
nosy: docs at python, eric.araujo, ezio.melotti, georg.brandl, jgehrcke
priority: normal
severity: normal
status: open
title: list.sort() should show arguments in tutorial
versions: Python 2.7, Python 3.4, Python 3.5

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

From report at bugs.python.org  Sun May 25 21:08:06 2014
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 25 May 2014 19:08:06 +0000
Subject: [docs] [issue21575] list.sort() should show arguments in tutorial
In-Reply-To: <1401021385.55.0.784639264396.issue21575@psf.upfronthosting.co.za>
Message-ID: <1401044886.44.0.578770652665.issue21575@psf.upfronthosting.co.za>


?ric Araujo added the comment:

I assume it is on purpose that the tutorial does not show all methods with all their arguments.  It could overwhelm readers with too much information, and would also duplicate the full doc that?s in the reference.

A link from this tutorial page to the list reference (and maybe the sorting howto) could be a good addition.

----------

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

From report at bugs.python.org  Mon May 26 03:06:35 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 26 May 2014 01:06:35 +0000
Subject: [docs] [issue21558] Fix a typo in the contextlib docs
In-Reply-To: <1400817528.11.0.0994185866372.issue21558@psf.upfronthosting.co.za>
Message-ID: <3gcKrV4Wsxz7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset ebeade01bd8e by Raymond Hettinger in branch '3.4':
Issue 21558:  Fix a typo in the contextlib docs
http://hg.python.org/cpython/rev/ebeade01bd8e

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

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

From report at bugs.python.org  Mon May 26 03:07:27 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 26 May 2014 01:07:27 +0000
Subject: [docs] [issue21558] Fix a typo in the contextlib docs
In-Reply-To: <1400817528.11.0.0994185866372.issue21558@psf.upfronthosting.co.za>
Message-ID: <1401066447.51.0.975675915303.issue21558@psf.upfronthosting.co.za>


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


----------
nosy: +ncoghlan
resolution:  -> fixed
status: open -> closed

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

From report at bugs.python.org  Mon May 26 03:41:28 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 26 May 2014 01:41:28 +0000
Subject: [docs] [issue21575] list.sort() should show arguments in tutorial
In-Reply-To: <1401021385.55.0.784639264396.issue21575@psf.upfronthosting.co.za>
Message-ID: <1401068488.3.0.517039614345.issue21575@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

> Is there a reason why we do not show the arguments there?

It was likely an oversight.   I think it should be updated so that people know the options are there.

----------
nosy: +rhettinger

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

From report at bugs.python.org  Mon May 26 03:45:28 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 26 May 2014 01:45:28 +0000
Subject: [docs] [issue21575] list.sort() should show arguments in tutorial
In-Reply-To: <1401021385.55.0.784639264396.issue21575@psf.upfronthosting.co.za>
Message-ID: <1401068728.99.0.0383977692321.issue21575@psf.upfronthosting.co.za>


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


----------
keywords: +patch
Added file: http://bugs.python.org/file35358/sort_tut.diff

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

From report at bugs.python.org  Mon May 26 07:02:11 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 26 May 2014 05:02:11 +0000
Subject: [docs] [issue16774] Additional recipes for itertools docs
In-Reply-To: <1356381615.1.0.91798699559.issue16774@psf.upfronthosting.co.za>
Message-ID: <1401080531.12.0.365600547474.issue16774@psf.upfronthosting.co.za>


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


----------
versions: +Python 3.5 -Python 2.7, Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon May 26 07:04:09 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 26 May 2014 05:04:09 +0000
Subject: [docs] [issue16774] Additional recipes for itertools docs
In-Reply-To: <1356381615.1.0.91798699559.issue16774@psf.upfronthosting.co.za>
Message-ID: <3gcR6c4By8z7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset 2781fb146f4a by Raymond Hettinger in branch 'default':
Issue 16774:  Add a new itertools recipe (suggested by Alexey Kachayev).
http://hg.python.org/cpython/rev/2781fb146f4a

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

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

From report at bugs.python.org  Mon May 26 07:05:16 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 26 May 2014 05:05:16 +0000
Subject: [docs] [issue16774] Additional recipes for itertools docs
In-Reply-To: <1356381615.1.0.91798699559.issue16774@psf.upfronthosting.co.za>
Message-ID: <1401080716.73.0.684821105533.issue16774@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

In the end, I decided to add a variant of take_last().

Thank you for the suggestion.

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

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

From report at bugs.python.org  Mon May 26 07:20:35 2014
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 26 May 2014 05:20:35 +0000
Subject: [docs] [issue21558] Fix a typo in the contextlib docs
In-Reply-To: <1400817528.11.0.0994185866372.issue21558@psf.upfronthosting.co.za>
Message-ID: <1401081635.93.0.0566533260501.issue21558@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks Raymond, will do.

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

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

From report at bugs.python.org  Mon May 26 07:52:24 2014
From: report at bugs.python.org (Martin Panter)
Date: Mon, 26 May 2014 05:52:24 +0000
Subject: [docs] [issue21580] PhotoImage(data=...) apparently has to be UTF-8
	or	Base-64 encoded
Message-ID: <1401083544.46.0.470654104454.issue21580@psf.upfronthosting.co.za>


New submission from Martin Panter:

At the bottom of the ?tkinter? doc page it mentions the ?data? option is available. However I was unable to get it to work well when passing a plain bytes() string in. It seems the bytes() string gets interpreted as UTF-8 somewhere along the line, although the underlying TCL library apparenly handles byte strings fine itself. Passing binary GIF and PNG data in Python would usually produce strange exceptions, crashes, and blank images for me.

I found this message with a simple patch which might be useful, though I?m not familiar with the code involved to understand the implications:
https://mail.python.org/pipermail/tkinter-discuss/2012-April/003108.html

Even if that fix is not appropriate, can I suggest adding to the documentation to say the data should be encoded with one of these options that seem to work? The Base-64 one is probably better.

PhotoImage(data=data.decode("latin-1).encode("utf-8"))
PhotoImage(data=base64.encodebytes(data))

----------
assignee: docs at python
components: Documentation, Tkinter
messages: 219133
nosy: docs at python, vadmium
priority: normal
severity: normal
status: open
title: PhotoImage(data=...) apparently has to be UTF-8 or Base-64 encoded
versions: Python 3.4

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

From report at bugs.python.org  Mon May 26 10:15:16 2014
From: report at bugs.python.org (Jan-Philip Gehrcke)
Date: Mon, 26 May 2014 08:15:16 +0000
Subject: [docs] [issue21575] list.sort() should show arguments in tutorial
In-Reply-To: <1401021385.55.0.784639264396.issue21575@psf.upfronthosting.co.za>
Message-ID: <1401092116.59.0.361728616759.issue21575@psf.upfronthosting.co.za>


Jan-Philip Gehrcke added the comment:

I have updated the patch with a cross-reference to the sorted() built-in, which explains the arguments.

W.r.t. to ?ric's suggestion: the sorted() doc refers to the sorting howto in the wiki. Now everything is connected.

----------
Added file: http://bugs.python.org/file35365/sort_tut_02.diff

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

From report at bugs.python.org  Mon May 26 10:16:00 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 26 May 2014 08:16:00 +0000
Subject: [docs] [issue21575] list.sort() should show arguments in tutorial
In-Reply-To: <1401021385.55.0.784639264396.issue21575@psf.upfronthosting.co.za>
Message-ID: <1401092160.25.0.697980326612.issue21575@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon May 26 10:20:56 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 26 May 2014 08:20:56 +0000
Subject: [docs] [issue21580] PhotoImage(data=...) apparently has to be UTF-8
	or	Base-64 encoded
In-Reply-To: <1401083544.46.0.470654104454.issue21580@psf.upfronthosting.co.za>
Message-ID: <1401092456.31.0.0968705101755.issue21580@psf.upfronthosting.co.za>


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


----------
nosy: +gpolo, serhiy.storchaka

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

From report at bugs.python.org  Mon May 26 12:10:52 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 26 May 2014 10:10:52 +0000
Subject: [docs] [issue21054] Improve indexing of syntax symbols
In-Reply-To: <1395703578.43.0.642568496743.issue21054@psf.upfronthosting.co.za>
Message-ID: <1401099052.42.0.909008827386.issue21054@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

All the current dependences are currently fixed.
Are you planning to add more in the future or can this issue be closed?

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, ezio.melotti
type:  -> enhancement

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

From report at bugs.python.org  Mon May 26 12:19:31 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 26 May 2014 10:19:31 +0000
Subject: [docs] [issue21072] Python docs and downloads not available for
	Egypt
In-Reply-To: <1395872823.34.0.614292416852.issue21072@psf.upfronthosting.co.za>
Message-ID: <1401099571.68.0.807863623569.issue21072@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

IIUC there was a similar issue from China, and on the old site we fixed it by adding http://legacy.python.org/getit/.
I don't know what was made to this page to make it work from China and if it still exists on the new website, but maybe the same trick could be used in this case as well?

Leo, can you check if the link I posted above works for you and try http://legacy.python.org/download/ as well?

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

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

From report at bugs.python.org  Mon May 26 12:38:37 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 26 May 2014 10:38:37 +0000
Subject: [docs] [issue21434] python -3 documentation is outdated
In-Reply-To: <1399281658.38.0.402381658113.issue21434@psf.upfronthosting.co.za>
Message-ID: <1401100717.04.0.516095325399.issue21434@psf.upfronthosting.co.za>


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


----------
nosy: +terry.reedy
stage: patch review -> commit review
type:  -> enhancement

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

From report at bugs.python.org  Mon May 26 16:20:19 2014
From: report at bugs.python.org (Mark Lawrence)
Date: Mon, 26 May 2014 14:20:19 +0000
Subject: [docs] [issue19980] Improve help('non-topic') response
In-Reply-To: <1386984892.27.0.919528696836.issue19980@psf.upfronthosting.co.za>
Message-ID: <1401114019.15.0.364569858201.issue19980@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

Anybody?

----------

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

From report at bugs.python.org  Mon May 26 16:27:38 2014
From: report at bugs.python.org (Leo Butcher)
Date: Mon, 26 May 2014 14:27:38 +0000
Subject: [docs] [issue21072] Python docs and downloads not available for
	Egypt
In-Reply-To: <1401099571.68.0.807863623569.issue21072@psf.upfronthosting.co.za>
Message-ID: <CAKP0wtrdLY8=aDjOSCLM2vF7-_qPeVp933ANh+bZkabfEMzaOA@mail.gmail.com>


Leo Butcher added the comment:

Still not working, they both timeout
also the docs subdomain is the same

On Mon, May 26, 2014 at 12:19 PM, Ezio Melotti <report at bugs.python.org>wrote:

>
> Ezio Melotti added the comment:
>
> IIUC there was a similar issue from China, and on the old site we fixed it
> by adding http://legacy.python.org/getit/.
> I don't know what was made to this page to make it work from China and if
> it still exists on the new website, but maybe the same trick could be used
> in this case as well?
>
> Leo, can you check if the link I posted above works for you and try
> http://legacy.python.org/download/ as well?
>
> ----------
> nosy: +ezio.melotti
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <http://bugs.python.org/issue21072>
> _______________________________________
>

----------

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

From report at bugs.python.org  Mon May 26 18:15:44 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 26 May 2014 16:15:44 +0000
Subject: [docs] [issue21054] Improve indexing of syntax symbols
In-Reply-To: <1395703578.43.0.642568496743.issue21054@psf.upfronthosting.co.za>
Message-ID: <1401120943.92.0.428508172448.issue21054@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

I plan to add more.

----------

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

From report at bugs.python.org  Mon May 26 19:05:26 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 26 May 2014 17:05:26 +0000
Subject: [docs] [issue21434] python -3 documentation is outdated
In-Reply-To: <1399281658.38.0.402381658113.issue21434@psf.upfronthosting.co.za>
Message-ID: <1401123926.03.0.791916019449.issue21434@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

This is documentation for the 2.7 '-3' command line option, which I presume has not changed at least since 2.7.0, rather than for 2to3, which has changed in different 3.x releases. If I am correct, the list of things -3 warns about has not changed. It might be more appropriate to rewrite the intro sentence to something like

"Warn about Python 3.x incompatibilities which were not fixed by the original version of :ref:`2to3 <2to3-reference>`."

Benjamin, what do you think?

----------
nosy: +benjamin.peterson

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

From report at bugs.python.org  Mon May 26 19:45:52 2014
From: report at bugs.python.org (Jessica McKellar)
Date: Mon, 26 May 2014 17:45:52 +0000
Subject: [docs] [issue19980] Improve help('non-topic') response
In-Reply-To: <1386984892.27.0.919528696836.issue19980@psf.upfronthosting.co.za>
Message-ID: <1401126352.26.0.0358724381507.issue19980@psf.upfronthosting.co.za>


Jessica McKellar added the comment:

@BreamoreBoy, thanks for following up on this!


> I propose the following.  help('') returns help on strings in the same way that help([]) and help({}) returns help on lists and dicts respectively,

Sounds good.

> further help(''.method) returns help on the string method or an attribute error, so this appears to me consistent.

This already happens (which I think you are saying, but it's a bit confusing in reading your message which functionality you are proposing to add and which functionality you are restating that already exists).

> help('doh') returns enhanced output along the lines Terry suggested in msg206157.

Sounds good.

> help('module') gives the path to the module as well as the help output, if any, as I think this could be useful in cases where you're looking for problems and have a stdlib module masked by a file of your own.

I think you are stating the current functionality?

> Note that I've tried looking at the test code and it didn't make much sense to me, pointers welcome.

Do you have specific questions?

Terry suggests that help() tests for functionality using pydoc live in test_pydoc.py, and that help() tests for functionality not using pydoc live in test_site.py.

----------

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

From report at bugs.python.org  Tue May 27 00:01:47 2014
From: report at bugs.python.org (Daniel Fisher)
Date: Mon, 26 May 2014 22:01:47 +0000
Subject: [docs] [issue21586] Minor error "How To Sockets"
Message-ID: <1401141706.98.0.611136529928.issue21586@psf.upfronthosting.co.za>


New submission from Daniel Fisher:

There is a minor error in the documentation page "https://docs.python.org/2/howto/sockets.html"

Line 31 of the sample program of the program listed under "Using a Socket" reads chucks.append(chunk). It should read chunks.append(chunk). Without this minor correction, the sample program will not run.

----------
assignee: docs at python
components: Documentation
messages: 219182
nosy: Daniel.Fisher, docs at python
priority: normal
severity: normal
status: open
title: Minor error "How To Sockets"
versions: Python 2.7

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

From report at bugs.python.org  Tue May 27 00:11:21 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 26 May 2014 22:11:21 +0000
Subject: [docs] [issue21586] Minor error "How To Sockets"
In-Reply-To: <1401141706.98.0.611136529928.issue21586@psf.upfronthosting.co.za>
Message-ID: <3gcsvs0j9Dz7Ljb@mail.python.org>


Roundup Robot added the comment:

New changeset dc2a123d538a by Benjamin Peterson in branch '2.7':
fix typo in variable name (closes #21586)
http://hg.python.org/cpython/rev/dc2a123d538a

New changeset 62eb4828fdf7 by Benjamin Peterson in branch '3.4':
fix typo in variable name (closes #21586)
http://hg.python.org/cpython/rev/62eb4828fdf7

New changeset 487e8e071551 by Benjamin Peterson in branch 'default':
merge 3.4 (#21586)
http://hg.python.org/cpython/rev/487e8e071551

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

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

From report at bugs.python.org  Tue May 27 00:39:03 2014
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 26 May 2014 22:39:03 +0000
Subject: [docs] [issue21434] python -3 documentation is outdated
In-Reply-To: <1399281658.38.0.402381658113.issue21434@psf.upfronthosting.co.za>
Message-ID: <3gctWp3nHRz7Lrq@mail.python.org>


Roundup Robot added the comment:

New changeset ae2e8bfda7d7 by Benjamin Peterson in branch '2.7':
remove list of example incompatibilities (closes #21434)
http://hg.python.org/cpython/rev/ae2e8bfda7d7

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

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

From report at bugs.python.org  Tue May 27 03:44:12 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 27 May 2014 01:44:12 +0000
Subject: [docs] [issue21575] list.sort() should show arguments in tutorial
In-Reply-To: <1401021385.55.0.784639264396.issue21575@psf.upfronthosting.co.za>
Message-ID: <3gcydR09R6z7LjM@mail.python.org>


Roundup Robot added the comment:

New changeset 1b96949bfc97 by Raymond Hettinger in branch 'default':
Issue 21575:  Show list.sort() arguments in the tutorial.
http://hg.python.org/cpython/rev/1b96949bfc97

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

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

From report at bugs.python.org  Tue May 27 03:49:36 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 27 May 2014 01:49:36 +0000
Subject: [docs] [issue21575] list.sort() should show arguments in tutorial
In-Reply-To: <1401021385.55.0.784639264396.issue21575@psf.upfronthosting.co.za>
Message-ID: <3gcylg71yfz7Lkm@mail.python.org>


Roundup Robot added the comment:

New changeset be77b213ace0 by Raymond Hettinger in branch '2.7':
Issue 21575:  Show list.sort() arguments in the tutorial.
http://hg.python.org/cpython/rev/be77b213ace0

----------

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

From report at bugs.python.org  Tue May 27 03:50:09 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 27 May 2014 01:50:09 +0000
Subject: [docs] [issue21575] list.sort() should show arguments in tutorial
In-Reply-To: <1401021385.55.0.784639264396.issue21575@psf.upfronthosting.co.za>
Message-ID: <1401155409.59.0.885330304364.issue21575@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue May 27 07:21:18 2014
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 27 May 2014 05:21:18 +0000
Subject: [docs] [issue21439] Numerous minor issues in Language Reference
In-Reply-To: <1399300451.92.0.450554829588.issue21439@psf.upfronthosting.co.za>
Message-ID: <3gd3Rx59r5z7LjM@mail.python.org>


Roundup Robot added the comment:

New changeset 053ba3c2c190 by Raymond Hettinger in branch '3.4':
Issue 21439:  Minor issues in the reference manual.
http://hg.python.org/cpython/rev/053ba3c2c190

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

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

From report at bugs.python.org  Tue May 27 07:22:37 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 27 May 2014 05:22:37 +0000
Subject: [docs] [issue21439] Numerous minor issues in Language Reference
In-Reply-To: <1399300451.92.0.450554829588.issue21439@psf.upfronthosting.co.za>
Message-ID: <1401168157.55.0.213497507611.issue21439@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Most of the comments ended-up being useful and we applied.

----------
resolution:  -> fixed
status: open -> closed
versions: +Python 3.4

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

From report at bugs.python.org  Tue May 27 14:22:37 2014
From: report at bugs.python.org (Claudiu.Popa)
Date: Tue, 27 May 2014 12:22:37 +0000
Subject: [docs] [issue21589] Use better idiom in unittest example
Message-ID: <1401193357.7.0.00487480253361.issue21589@psf.upfronthosting.co.za>


New submission from Claudiu.Popa:

Hello.

This patch proposes using `assertIn` in the first unittest example, instead of `assertTrue(x in seq)`. This is clearer and recommending it first is better for beginners.

----------
assignee: docs at python
components: Documentation
files: unittest_better_idiom.patch
keywords: patch
messages: 219216
nosy: Claudiu.Popa, docs at python
priority: normal
severity: normal
status: open
title: Use better idiom in unittest example
type: enhancement
versions: Python 3.5
Added file: http://bugs.python.org/file35378/unittest_better_idiom.patch

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

From report at bugs.python.org  Tue May 27 14:29:16 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 27 May 2014 12:29:16 +0000
Subject: [docs] [issue21589] Use better idiom in unittest example
In-Reply-To: <1401193357.7.0.00487480253361.issue21589@psf.upfronthosting.co.za>
Message-ID: <1401193756.28.0.184869393125.issue21589@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

This is a duplicate of #11468.

----------
nosy: +ezio.melotti, rhettinger
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Improve unittest basic example in the doc

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

From report at bugs.python.org  Tue May 27 14:55:10 2014
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 27 May 2014 12:55:10 +0000
Subject: [docs] [issue11468] Improve unittest basic example in the doc
In-Reply-To: <1299867342.41.0.388080450116.issue11468@psf.upfronthosting.co.za>
Message-ID: <1401195310.97.0.375159294718.issue11468@psf.upfronthosting.co.za>


Changes by Berker Peksag <berker.peksag at gmail.com>:


----------
versions: +Python 3.5 -Python 3.3

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

From marchwiak1 at llnl.gov  Sat May 24 02:12:54 2014
From: marchwiak1 at llnl.gov (Marchwiak, Patrick D.)
Date: Sat, 24 May 2014 00:12:54 +0000
Subject: [docs] 404 when trying to download latest 2.7 HTML docs
Message-ID: <CFA53216.1029B%marchwiak1@llnl.gov>

Hi,

I?m trying to download https://docs.python.org/2/archives/python-2.7.7rc1-docs-html.zip and I?m getting a 404.

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140524/04aefcee/attachment-0001.html>

From afrtec at gmail.com  Sat May 24 12:13:56 2014
From: afrtec at gmail.com (afrtec)
Date: Sat, 24 May 2014 12:13:56 +0200
Subject: [docs] 404 Problem on doc download links
Message-ID: <CAM-AXqW=O4E9xNrUnnV4vKae7+U6fmwSBzdyekKLsB6BdVA9YA@mail.gmail.com>

Hi,

I keep getting a 404 on documentation for 2.7rc1 download links of all
files.


Afrtec Consulting,
+260955 110627.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140524/f7497c86/attachment-0001.html>

From mike at mikepage.us  Sat May 24 22:13:58 2014
From: mike at mikepage.us (mike at mikepage.us)
Date: Sat, 24 May 2014 14:13:58 -0600
Subject: [docs] Downlaod docs
Message-ID: <159AD961-D5C5-46E6-B382-FF45E4045A1E@mikepage.us>

Nothing from 
https://docs.python.org/2/download.html
will download. They all come up 404.

Mike Page
Theory and Practice, LLC
www.linkedin.com/in/MikePageHPC
mike at mikepage.us
303-944-8291




From A.Molina at F5.com  Sun May 25 14:05:55 2014
From: A.Molina at F5.com (Arturo Gomez Molina)
Date: Sun, 25 May 2014 12:05:55 +0000
Subject: [docs] Downloads is not working for 2.7.7
Message-ID: <8426A878D801CA43AB68F80BA752AB1D7DC0DEBB@SEAEMBX01.olympus.F5Net.com>

As i said in subject. Downloads don't work.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140525/ff706567/attachment-0001.html>

From geerard.ponnet at gmail.com  Mon May 26 00:55:43 2014
From: geerard.ponnet at gmail.com (geerard ponnet)
Date: Mon, 26 May 2014 00:55:43 +0200
Subject: [docs] typo
Message-ID: <CA+WAgvSy4cWktSdk4NN44_6D1s=kwGmAH+9KxKEiK=fffGQB6Q@mail.gmail.com>

Hi,

on http://docs.python.org/3/howto/sockets.html
Part: Using a Socket, code listing, in function myreceive:

chucks.append(chunk)

chunks.append(chunk)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140526/5af1550c/attachment-0001.html>

From berker.peksag at gmail.com  Tue May 27 14:57:56 2014
From: berker.peksag at gmail.com (berker.peksag at gmail.com)
Date: Tue, 27 May 2014 12:57:56 -0000
Subject: [docs] Improve unittest basic example in the doc (issue 11468)
Message-ID: <20140527125756.24351.92130@psf.upfronthosting.co.za>


http://bugs.python.org/review/11468/diff/2986/Doc/library/unittest.rst
File Doc/library/unittest.rst (right):

http://bugs.python.org/review/11468/diff/2986/Doc/library/unittest.rst#newcode131
Doc/library/unittest.rst:131: self.assertEqual(s.split(), ['hello',
'world'])
I think this is a good example to use assertListEqual.

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

From berker.peksag at gmail.com  Tue May 27 21:10:51 2014
From: berker.peksag at gmail.com (berker.peksag at gmail.com)
Date: Tue, 27 May 2014 19:10:51 -0000
Subject: [docs] Improve unittest basic example in the doc (issue 11468)
Message-ID: <20140527191051.25965.54532@psf.upfronthosting.co.za>

On 2014/05/27 19:15:24, Zach Ware wrote:
> http://bugs.python.org/review/11468/diff/2986/Doc/library/unittest.rst
> File Doc/library/unittest.rst (right):
> 
>
http://bugs.python.org/review/11468/diff/2986/Doc/library/unittest.rst#newcode131
> Doc/library/unittest.rst:131: self.assertEqual(s.split(), ['hello',
'world'])
> On 2014/05/27 14:57:56, berkerpeksag wrote:
> > I think this is a good example to use assertListEqual.
> 
> There should be no need to use assertListEqual explicitly, assertEqual
uses the
> type-specific equality functions under the hood:

Ah, yes, you're right. Thanks.

>  >>> unittest.TestCase().assertEqual('hello world'.split(),
['goodbye',
> 'world'])
> 
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
>   File "P:\Python34\lib\unittest\case.py", line 797, in assertEqual
>     assertion_func(first, second, msg=msg)
>   File "P:\Python34\lib\unittest\case.py", line 995, in
assertListEqual
>     self.assertSequenceEqual(list1, list2, msg, seq_type=list)
>   File "P:\Python34\lib\unittest\case.py", line 977, in
assertSequenceEqual
>     self.fail(msg)
>   File "P:\Python34\lib\unittest\case.py", line 642, in fail
>     raise self.failureException(msg)
> AssertionError: Lists differ: ['hello', 'world'] != ['goodbye',
'world']
> 
> First differing element 0:
> hello
> goodbye
> 
> - ['hello', 'world']
> + ['goodbye', 'world']

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

From report at bugs.python.org  Tue May 27 19:11:39 2014
From: report at bugs.python.org (Zachary Ware)
Date: Tue, 27 May 2014 17:11:39 +0000
Subject: [docs] [issue21439] Numerous minor issues in Language Reference
In-Reply-To: <1399300451.92.0.450554829588.issue21439@psf.upfronthosting.co.za>
Message-ID: <1401210699.25.0.156836397731.issue21439@psf.upfronthosting.co.za>


Changes by Zachary Ware <zachary.ware at gmail.com>:


----------
stage: test needed -> commit review

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

From report at bugs.python.org  Tue May 27 19:11:26 2014
From: report at bugs.python.org (Zachary Ware)
Date: Tue, 27 May 2014 17:11:26 +0000
Subject: [docs] [issue21439] Numerous minor issues in Language Reference
In-Reply-To: <1399300451.92.0.450554829588.issue21439@psf.upfronthosting.co.za>
Message-ID: <1401210686.41.0.411862522143.issue21439@psf.upfronthosting.co.za>


Zachary Ware added the comment:

A few comments on the committed patch.  The quoted diff is trimmed to just the hunks I have comments on.

On Tue, May 27, 2014 at 12:21 AM, raymond.hettinger <python-checkins at python.org> wrote:
> diff --git a/Doc/reference/compound_stmts.rst b/Doc/reference/compound_stmts.rst
> --- a/Doc/reference/compound_stmts.rst
> +++ b/Doc/reference/compound_stmts.rst
> @@ -170,17 +170,25 @@
>  A :keyword:`break` statement executed in the first suite terminates the loop
>  without executing the :keyword:`else` clause's suite.  A :keyword:`continue`
>  statement executed in the first suite skips the rest of the suite and continues
> -with the next item, or with the :keyword:`else` clause if there was no next
> +with the next item, or with the :keyword:`else` clause if there is no next
>  item.
>
> -The suite may assign to the variable(s) in the target list; this does not affect
> -the next item assigned to it.
> +The for-loop makes assignments to the variables(s) in the target list.
> +This overwrites all previous assignments to those variables including
> +those made in the suite of the for-loop::
> +
> +   for i in range(10):
> +       print(i)
> +       i = 5             # this will not affect the for-loop
> +                         # be i will be overwritten with the next

Typo here, looks like an unfinished thought. "because" rather than "be"?

> +                         # index in the range
> +
>
>  .. index::
>     builtin: range
>
>  Names in the target list are not deleted when the loop is finished, but if the
> -sequence is empty, it will not have been assigned to at all by the loop.  Hint:
> +sequence is empty, they will not have been assigned to at all by the loop.  Hint:
>  the built-in function :func:`range` returns an iterator of integers suitable to
>  emulate the effect of Pascal's ``for i := a to b do``; e.g., ``list(range(3))``
>  returns the list ``[0, 1, 2]``.

> diff --git a/Doc/reference/expressions.rst b/Doc/reference/expressions.rst
> --- a/Doc/reference/expressions.rst
> +++ b/Doc/reference/expressions.rst
> @@ -520,11 +521,11 @@
>
>  The primary must evaluate to an object of a type that supports attribute
>  references, which most objects do.  This object is then asked to produce the
> -attribute whose name is the identifier (which can be customized by overriding
> -the :meth:`__getattr__` method).  If this attribute is not available, the
> -exception :exc:`AttributeError` is raised.  Otherwise, the type and value of the
> -object produced is determined by the object.  Multiple evaluations of the same
> -attribute reference may yield different objects.
> +attribute whose name is the identifier.  This production can be customized by
> +overriding the :meth:`__getattr__` method).  If this attribute is not available,

Orphaned ')' on this line.

> +the exception :exc:`AttributeError` is raised.  Otherwise, the type and value of
> +the object produced is determined by the object.  Multiple evaluations of the
> +same attribute reference may yield different objects.
>
>
>  .. _subscriptions:
> @@ -1244,10 +1245,9 @@
>     lambda_expr: "lambda" [`parameter_list`]: `expression`
>     lambda_expr_nocond: "lambda" [`parameter_list`]: `expression_nocond`
>
> -Lambda expressions (sometimes called lambda forms) have the same syntactic position as
> -expressions.  They are a shorthand to create anonymous functions; the expression
> -``lambda arguments: expression`` yields a function object.  The unnamed object
> -behaves like a function object defined with ::
> +Lambda expressions (sometimes called lambda forms) are create anonymous

Unfinished thought here; "are create" -> "are used to create"?

> +functions. The expression ``lambda arguments: expression`` yields a function
> +object.  The unnamed object behaves like a function object defined with ::

While we're here, the object is in fact named, its name (__name__) is "<lambda>".  It's not a valid identifier, but it is its name.

>
>     def <lambda>(arguments):
>         return expression
> @@ -1310,13 +1310,15 @@
>
>  .. index:: pair: operator; precedence
>
> -The following table summarizes the operator precedences in Python, from lowest
> +The following table summarizes the operator precedence in Python, from lowest

This sentence still doesn't read correctly to me; the simplest fix that makes sense to my brain is to remove "the" ("... summarizes operator precedence ...").  I would welcome any other better wording.

>  precedence (least binding) to highest precedence (most binding).  Operators in
>  the same box have the same precedence.  Unless the syntax is explicitly given,
>  operators are binary.  Operators in the same box group left to right (except for
> -comparisons, including tests, which all have the same precedence and chain from
> -left to right --- see section :ref:`comparisons` --- and exponentiation, which
> -groups from right to left).
> +exponentiation, which groups from right to left).
> +
> +Note that comparisons, membership tests, and identity tests, all have the same
> +precedence and have a left-to-right chaining feature as described in the
> +:ref:`comparisons` section.
>
>
>  +-----------------------------------------------+-------------------------------------+
> diff --git a/Doc/reference/simple_stmts.rst b/Doc/reference/simple_stmts.rst
> --- a/Doc/reference/simple_stmts.rst
> +++ b/Doc/reference/simple_stmts.rst
> @@ -7,7 +7,7 @@
>
>  .. index:: pair: simple; statement
>
> -Simple statements are comprised within a single logical line. Several simple
> +A simple statement is comprised within a single logical line. Several simple

I agree with the OP that "comprised within" doesn't cut it.  Does his suggestion of "must fit" instead of "is comprised" work or is there a better wording?

>  statements may occur on a single line separated by semicolons.  The syntax for
>  simple statements is:
>

----------

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

From report at bugs.python.org  Tue May 27 19:17:19 2014
From: report at bugs.python.org (Zachary Ware)
Date: Tue, 27 May 2014 17:17:19 +0000
Subject: [docs] [issue11468] Improve unittest basic example in the doc
In-Reply-To: <1299867342.41.0.388080450116.issue11468@psf.upfronthosting.co.za>
Message-ID: <1401211039.39.0.0529957282743.issue11468@psf.upfronthosting.co.za>


Changes by Zachary Ware <zachary.ware at gmail.com>:


----------
nosy: +zach.ware

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

From zachary.ware at gmail.com  Tue May 27 19:15:24 2014
From: zachary.ware at gmail.com (zachary.ware at gmail.com)
Date: Tue, 27 May 2014 17:15:24 -0000
Subject: [docs] Improve unittest basic example in the doc (issue 11468)
Message-ID: <20140527171524.24177.79101@psf.upfronthosting.co.za>


http://bugs.python.org/review/11468/diff/2986/Doc/library/unittest.rst
File Doc/library/unittest.rst (right):

http://bugs.python.org/review/11468/diff/2986/Doc/library/unittest.rst#newcode131
Doc/library/unittest.rst:131: self.assertEqual(s.split(), ['hello',
'world'])
On 2014/05/27 14:57:56, berkerpeksag wrote:
> I think this is a good example to use assertListEqual.

There should be no need to use assertListEqual explicitly, assertEqual
uses the type-specific equality functions under the hood:

 >>> unittest.TestCase().assertEqual('hello world'.split(), ['goodbye',
'world'])

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "P:\Python34\lib\unittest\case.py", line 797, in assertEqual
    assertion_func(first, second, msg=msg)
  File "P:\Python34\lib\unittest\case.py", line 995, in assertListEqual
    self.assertSequenceEqual(list1, list2, msg, seq_type=list)
  File "P:\Python34\lib\unittest\case.py", line 977, in
assertSequenceEqual
    self.fail(msg)
  File "P:\Python34\lib\unittest\case.py", line 642, in fail
    raise self.failureException(msg)
AssertionError: Lists differ: ['hello', 'world'] != ['goodbye', 'world']

First differing element 0:
hello
goodbye

- ['hello', 'world']
+ ['goodbye', 'world']

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

From zachary.ware+pydocs at gmail.com  Tue May 27 23:02:42 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Tue, 27 May 2014 16:02:42 -0500
Subject: [docs] typo
In-Reply-To: <CA+WAgvSy4cWktSdk4NN44_6D1s=kwGmAH+9KxKEiK=fffGQB6Q@mail.gmail.com>
References: <CA+WAgvSy4cWktSdk4NN44_6D1s=kwGmAH+9KxKEiK=fffGQB6Q@mail.gmail.com>
Message-ID: <CAKJDb-NPjF=OOJJpzJmcHpJ6Rr14U-uvFN1PL-X6Ab5=PdbdLg@mail.gmail.com>

Hi,

On Sun, May 25, 2014 at 5:55 PM, geerard ponnet
<geerard.ponnet at gmail.com> wrote:
> Hi,
>
> on http://docs.python.org/3/howto/sockets.html
> Part: Using a Socket, code listing, in function myreceive:
>
> chucks.append(chunk)
>
> chunks.append(chunk)

Thanks for the report!  This has already been fixed.

Regards,
-- 
Zach

From report at bugs.python.org  Tue May 27 23:48:30 2014
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 27 May 2014 21:48:30 +0000
Subject: [docs] [issue11468] Improve unittest basic example in the doc
In-Reply-To: <1299867342.41.0.388080450116.issue11468@psf.upfronthosting.co.za>
Message-ID: <1401227310.45.0.855611716418.issue11468@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

FWIW, I'm going to test some other module (math or somesuch) rather than the built-in string methods.  The normal use of unittest is to import both the unittest module and the module under test.  I want to show that pattern (which is somewhat different from doctests where the tests are typically in the same file as the code being tested).

----------

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

From report at bugs.python.org  Wed May 28 16:39:26 2014
From: report at bugs.python.org (Joshua Landau)
Date: Wed, 28 May 2014 14:39:26 +0000
Subject: [docs] [issue21593] Clarify re.search documentation first match
Message-ID: <1401287966.38.0.860641123785.issue21593@psf.upfronthosting.co.za>


New submission from Joshua Landau:

The documentation for re.search does not state that it returns the first match. This should be added, or a clarification added if this is implementation-defined.

https://docs.python.org/3/library/re.html#re.search

---

See also

http://stackoverflow.com/questions/23906400/is-regular-expression-search-guaranteed-to-return-first-match

----------
assignee: docs at python
components: Documentation
messages: 219270
nosy: Joshua.Landau, docs at python
priority: normal
severity: normal
status: open
title: Clarify re.search documentation first match
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5

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

From report at bugs.python.org  Wed May 28 18:16:43 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 28 May 2014 16:16:43 +0000
Subject: [docs] [issue21580] PhotoImage(data=...) apparently has to be UTF-8
	or	Base-64 encoded
In-Reply-To: <1401083544.46.0.470654104454.issue21580@psf.upfronthosting.co.za>
Message-ID: <1401293803.08.0.0721207945079.issue21580@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

All works to me.

>>> import tkinter
>>> b = tkinter.Button()
>>> with open('Lib/test/imghdrdata/python.gif', 'rb') as f: data = f.read()
... 
>>> img = tkinter.PhotoImage(data=data)
>>> b['image'] = img
>>> b.pack()

Could you please provide an example which demonstrates the issue?

----------
stage:  -> test needed

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

From report at bugs.python.org  Wed May 28 18:22:29 2014
From: report at bugs.python.org (Sebastian Kreft)
Date: Wed, 28 May 2014 16:22:29 +0000
Subject: [docs] [issue21596] asyncio.wait fails when futures list is empty
Message-ID: <1401294149.12.0.93780466725.issue21596@psf.upfronthosting.co.za>


New submission from Sebastian Kreft:

Passing an empty list/set of futures to asyncio.wait raises an Exception, which is a little annoying in some use cases.

Probably this was the intended behavior as I see there's a test case for that. If such, then I would propose to document that behavior.

----------
assignee: docs at python
components: Documentation
messages: 219290
nosy: Sebastian.Kreft.Deezer, docs at python
priority: normal
severity: normal
status: open
title: asyncio.wait fails when futures list is empty
versions: Python 3.4

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

From john at ashworthsatellites.com  Wed May 28 17:01:07 2014
From: john at ashworthsatellites.com (john at ashworthsatellites.com)
Date: Wed, 28 May 2014 08:01:07 -0700
Subject: [docs] Bug in tutorial doc
Message-ID: <20140528080107.d4a448afb03c93b23c340bae0fa3aa12.8ae81b9e9b.wbe@email07.europe.secureserver.net>

An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140528/c1a04403/attachment-0001.html>

From john at ashworthsatellites.com  Wed May 28 17:04:16 2014
From: john at ashworthsatellites.com (john at ashworthsatellites.com)
Date: Wed, 28 May 2014 08:04:16 -0700
Subject: [docs] [FWD: Bug in tutorial doc] - continued
Message-ID: <20140528080416.d4a448afb03c93b23c340bae0fa3aa12.a2c5cbdb17.wbe@email07.europe.secureserver.net>

An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140528/2e9da9db/attachment-0001.html>

From john at ashworthsatellites.com  Wed May 28 17:19:22 2014
From: john at ashworthsatellites.com (john at ashworthsatellites.com)
Date: Wed, 28 May 2014 08:19:22 -0700
Subject: [docs] [FWD: [FWD: Bug in tutorial doc] - continued] -
	understanding has dawned
Message-ID: <20140528081922.d4a448afb03c93b23c340bae0fa3aa12.72f5b1552d.wbe@email07.europe.secureserver.net>

An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140528/b1c3ec23/attachment-0001.html>

From drtondo at t3works.com  Wed May 28 18:08:29 2014
From: drtondo at t3works.com (Dr CL Tondo)
Date: Wed, 28 May 2014 12:08:29 -0400
Subject: [docs] Python 3.4 question
Message-ID: <129a01cf7a8f$11337250$339a56f0$@t3works.com>

Hi,

 

I installed Python 3.4  in Windows 7 but it gives me a syntax error on a
one-line file p014a.py

The same file runs fine with Python 2.7 in Windows XP.

The p014a.log contains the result of running Python 3.4 with the -v option.

Thanks for your help.

 

CL  Tondo

drtondo at t3works.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140528/d0a2b130/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: p014a.log
Type: application/octet-stream
Size: 8343 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20140528/d0a2b130/attachment-0001.obj>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: p014a.py
URL: <http://mail.python.org/pipermail/docs/attachments/20140528/d0a2b130/attachment-0001.ksh>

From drtondo at t3works.com  Wed May 28 18:36:01 2014
From: drtondo at t3works.com (Dr CL Tondo)
Date: Wed, 28 May 2014 12:36:01 -0400
Subject: [docs] FW: Python 3.4 question - print is now a function...
Message-ID: <12a901cf7a92$e95eed00$bc1cc700$@t3works.com>

Hi,

 

I found out that print is a function starting with Python 3.0

It could have been flagged as a deprecated command instead

of a plain "syntax error."

 

CL  Tondo

 

From: Dr CL Tondo [mailto:drtondo at t3works.com] 
Sent: Wednesday, May 28, 2014 12:08 PM
To: docs at python.org
Subject: Python 3.4 question

 

Hi,

 

I installed Python 3.4  in Windows 7 but it gives me a syntax error on a
one-line file p014a.py

The same file runs fine with Python 2.7 in Windows XP.

The p014a.log contains the result of running Python 3.4 with the -v option.

Thanks for your help.

 

CL  Tondo

drtondo at t3works.com

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

From zachary.ware+pydocs at gmail.com  Wed May 28 19:14:24 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Wed, 28 May 2014 12:14:24 -0500
Subject: [docs] Python 2.7.7rc1 Documentation Download 404 errors
Message-ID: <CAKJDb-NYSAbM3vDotMWKRtVJ5ZgrVr2zrXZBq+B4gSTKxYJ-qw@mail.gmail.com>

(Note: All reporters from the past several days are Bcc'd on this email)

This issue has been fixed and the documentation archives for 2.7.7rc1
are now available for download.

Thank you for your report, hopefully this won't be a problem when the
next RC release comes around!

Regards,
-- 
Zach

From mike at mikepage.us  Wed May 28 19:15:39 2014
From: mike at mikepage.us (mike at mikepage.us)
Date: Wed, 28 May 2014 11:15:39 -0600
Subject: [docs] Python 2.7.7rc1 Documentation Download 404 errors
In-Reply-To: <CAKJDb-NYSAbM3vDotMWKRtVJ5ZgrVr2zrXZBq+B4gSTKxYJ-qw@mail.gmail.com>
References: <CAKJDb-NYSAbM3vDotMWKRtVJ5ZgrVr2zrXZBq+B4gSTKxYJ-qw@mail.gmail.com>
Message-ID: <C85F626B-1DD9-47E8-842D-BFF99ED2ED2B@mikepage.us>

Tahnks for taking care of the docs issue.

Anything for 3.4?

Mike Page
Theory and Practice, LLC
www.linkedin.com/in/MikePageHPC
mike at mikepage.us
303-944-8291



On May 28, 2014, at 11:14 AM, Zachary Ware <zachary.ware+pydocs at gmail.com> wrote:

> (Note: All reporters from the past several days are Bcc'd on this email)
> 
> This issue has been fixed and the documentation archives for 2.7.7rc1
> are now available for download.
> 
> Thank you for your report, hopefully this won't be a problem when the
> next RC release comes around!
> 
> Regards,
> -- 
> Zach


From zachary.ware+pydocs at gmail.com  Wed May 28 19:18:55 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Wed, 28 May 2014 12:18:55 -0500
Subject: [docs] Python 2.7.7rc1 Documentation Download 404 errors
In-Reply-To: <C85F626B-1DD9-47E8-842D-BFF99ED2ED2B@mikepage.us>
References: <CAKJDb-NYSAbM3vDotMWKRtVJ5ZgrVr2zrXZBq+B4gSTKxYJ-qw@mail.gmail.com>
 <C85F626B-1DD9-47E8-842D-BFF99ED2ED2B@mikepage.us>
Message-ID: <CAKJDb-OYwwyhAObfA8ZJtONQeXzS20mbTCaiMnYmD9nb10Lx_Q@mail.gmail.com>

On Wed, May 28, 2014 at 12:15 PM, mike at mikepage.us <mike at mikepage.us> wrote:
> Tahnks for taking care of the docs issue.
>
> Anything for 3.4?

Should be working as well -- 3.4.1rc1 probably still isn't available
(if you can get to a 3.4.1rc1 documentation download page at all), but
3.4.1 final's documentation is downloadable.

Regards,
-- 
Zach

From zachary.ware+pydocs at gmail.com  Wed May 28 19:30:12 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Wed, 28 May 2014 12:30:12 -0500
Subject: [docs] FW: Python 3.4 question - print is now a function...
In-Reply-To: <12a901cf7a92$e95eed00$bc1cc700$@t3works.com>
References: <12a901cf7a92$e95eed00$bc1cc700$@t3works.com>
Message-ID: <CAKJDb-P+mJyf398emMLkrDcz+kB025=oxR9bxcJhvAJ2shg+0w@mail.gmail.com>

Hi,

On Wed, May 28, 2014 at 11:36 AM, Dr CL Tondo <drtondo at t3works.com> wrote:
> Hi,
> I found out that print is a function starting with Python 3.0
> It could have been flagged as a deprecated command instead
> of a plain ?syntax error.?

First, I'd like to note that this list is not the proper venue for
usage questions such as this one; this list (docs at python.org) is
intended for discussion of the Python documentation.  A better choice
would have been python-list at python.org, which is meant for any and all
discussion pertaining to Python.

That said, I'm glad you figured out your issue yourself!  For a bit of
history, Python 3.0 was used as an opportunity to break backward
compatibility with Python 2.x and clean up many many dark and dusty
corners of the language, and as such was effectively released as a
brand new language: hence the lack of deprecation warnings.  As
further justification for the SyntaxError not being a deprecation
warning, in Python 3, print is just the same as any other function:
you'll get the same SyntaxError from this in any version of Python:

   >>> def foo(arg):
   ...     return arg
   ...
   >>> foo 'test'
     File "<stdin>", line 1
       foo 'test'
                ^
   SyntaxError: invalid syntax

For Python 3 to produce a deprecation notice for print, the
SyntaxError constructor would have to somehow special case the name
'print', which would just be ugly :)

I hope this helps things make a bit more sense, and I hope you enjoy
using Python!

Regards,
--
Zach

From mike at mikepage.us  Wed May 28 19:43:53 2014
From: mike at mikepage.us (Mike Page)
Date: Wed, 28 May 2014 11:43:53 -0600
Subject: [docs] Python 2.7.7rc1 Documentation Download 404 errors
In-Reply-To: <CAKJDb-OYwwyhAObfA8ZJtONQeXzS20mbTCaiMnYmD9nb10Lx_Q@mail.gmail.com>
References: <CAKJDb-NYSAbM3vDotMWKRtVJ5ZgrVr2zrXZBq+B4gSTKxYJ-qw@mail.gmail.com>
 <C85F626B-1DD9-47E8-842D-BFF99ED2ED2B@mikepage.us>
 <CAKJDb-OYwwyhAObfA8ZJtONQeXzS20mbTCaiMnYmD9nb10Lx_Q@mail.gmail.com>
Message-ID: <F847D597-3526-49BC-9F01-F3C3490B45CC@mikepage.us>

Thanks. I will give it a try. 

Mike Page
Theory and Practice
www.linkedin.com/in/MikePageHPC
mike at mikepage.us
303.944.8291

Sent from my iPhone

> On May 28, 2014, at 11:18 AM, Zachary Ware <zachary.ware+pydocs at gmail.com> wrote:
> 
>> On Wed, May 28, 2014 at 12:15 PM, mike at mikepage.us <mike at mikepage.us> wrote:
>> Tahnks for taking care of the docs issue.
>> 
>> Anything for 3.4?
> 
> Should be working as well -- 3.4.1rc1 probably still isn't available
> (if you can get to a 3.4.1rc1 documentation download page at all), but
> 3.4.1 final's documentation is downloadable.
> 
> Regards,
> -- 
> Zach

From report at bugs.python.org  Wed May 28 22:32:12 2014
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 28 May 2014 20:32:12 +0000
Subject: [docs] [issue21596] asyncio.wait fails when futures list is empty
In-Reply-To: <1401294149.12.0.93780466725.issue21596@psf.upfronthosting.co.za>
Message-ID: <1401309132.15.0.208270968717.issue21596@psf.upfronthosting.co.za>


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


----------
nosy: +giampaolo.rodola, gvanrossum, haypo, pitrou, yselivanov

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

From debayly at gmail.com  Wed May 28 20:59:38 2014
From: debayly at gmail.com (Devin Bayly)
Date: Wed, 28 May 2014 11:59:38 -0700
Subject: [docs] Python 2.7.7rc1 Documentation Download 404 errors
In-Reply-To: <CAKJDb-NYSAbM3vDotMWKRtVJ5ZgrVr2zrXZBq+B4gSTKxYJ-qw@mail.gmail.com>
References: <CAKJDb-NYSAbM3vDotMWKRtVJ5ZgrVr2zrXZBq+B4gSTKxYJ-qw@mail.gmail.com>
Message-ID: <CAOy+Fmay6AX_o1dMyN0T2yxXm-_SjXzSDc9K3PrSvZst96PAYg@mail.gmail.com>

thanks so much!


On Wed, May 28, 2014 at 10:14 AM, Zachary Ware <
zachary.ware+pydocs at gmail.com> wrote:

> (Note: All reporters from the past several days are Bcc'd on this email)
>
> This issue has been fixed and the documentation archives for 2.7.7rc1
> are now available for download.
>
> Thank you for your report, hopefully this won't be a problem when the
> next RC release comes around!
>
> Regards,
> --
> Zach
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140528/157bc30d/attachment.html>

From lorenzo.marrese at gmail.com  Wed May 28 23:01:53 2014
From: lorenzo.marrese at gmail.com (Lorenzo Marrese)
Date: Wed, 28 May 2014 17:01:53 -0400
Subject: [docs] Python 2.7.7rc1 Documentation Download 404 errors
In-Reply-To: <CAKJDb-NYSAbM3vDotMWKRtVJ5ZgrVr2zrXZBq+B4gSTKxYJ-qw@mail.gmail.com>
References: <CAKJDb-NYSAbM3vDotMWKRtVJ5ZgrVr2zrXZBq+B4gSTKxYJ-qw@mail.gmail.com>
Message-ID: <CA+-bXWVML_5CfSNhKBCBjguGfGtmjXr7sA=iFmM9w7x_kR8V3g@mail.gmail.com>

Thank you I appreciate the update.


On Wed, May 28, 2014 at 1:14 PM, Zachary Ware <zachary.ware+pydocs at gmail.com
> wrote:

> (Note: All reporters from the past several days are Bcc'd on this email)
>
> This issue has been fixed and the documentation archives for 2.7.7rc1
> are now available for download.
>
> Thank you for your report, hopefully this won't be a problem when the
> next RC release comes around!
>
> Regards,
> --
> Zach
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140528/64efe5bf/attachment.html>

From report at bugs.python.org  Thu May 29 00:05:25 2014
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 28 May 2014 22:05:25 +0000
Subject: [docs] [issue21376] asyncio docs refer to wrong TimeoutError
In-Reply-To: <1398708357.06.0.922465155945.issue21376@psf.upfronthosting.co.za>
Message-ID: <3gf5h41nYzz7Lmy@mail.python.org>


Roundup Robot added the comment:

New changeset 6d90e8df01f4 by Victor Stinner in branch '3.4':
Issue #21376: document asyncio.TimeoutError
http://hg.python.org/cpython/rev/6d90e8df01f4

New changeset 03bb1077b362 by Victor Stinner in branch 'default':
(Merge 3.4) Issue #21376: document asyncio.TimeoutError
http://hg.python.org/cpython/rev/03bb1077b362

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

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

From report at bugs.python.org  Thu May 29 00:06:16 2014
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 28 May 2014 22:06:16 +0000
Subject: [docs] [issue21376] asyncio docs refer to wrong TimeoutError
In-Reply-To: <1398708357.06.0.922465155945.issue21376@psf.upfronthosting.co.za>
Message-ID: <1401314776.82.0.45437489908.issue21376@psf.upfronthosting.co.za>


STINNER Victor added the comment:

Thanks for the report. In fact, asyncio.TimeoutError was not documented at all. It should now be fixed.

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

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

From report at bugs.python.org  Thu May 29 00:07:10 2014
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 28 May 2014 22:07:10 +0000
Subject: [docs] [issue21443] asyncio logging documentation clarifications
In-Reply-To: <1399321197.68.0.955361534546.issue21443@psf.upfronthosting.co.za>
Message-ID: <1401314830.29.0.49333355936.issue21443@psf.upfronthosting.co.za>


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


----------
nosy: +giampaolo.rodola, gvanrossum, haypo, pitrou, yselivanov

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

From report at bugs.python.org  Thu May 29 00:09:03 2014
From: report at bugs.python.org (Guido van Rossum)
Date: Wed, 28 May 2014 22:09:03 +0000
Subject: [docs] [issue21443] asyncio logging documentation clarifications
In-Reply-To: <1399321197.68.0.955361534546.issue21443@psf.upfronthosting.co.za>
Message-ID: <1401314943.71.0.237865247857.issue21443@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Good idea.

----------

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

From report at bugs.python.org  Thu May 29 00:19:21 2014
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 28 May 2014 22:19:21 +0000
Subject: [docs] [issue21454] asyncio's loop.connect_read_pipe makes
	pipes	non-blocking contrary to the documentation
In-Reply-To: <1399575906.07.0.344601032189.issue21454@psf.upfronthosting.co.za>
Message-ID: <3gf6086X0zz7Ljy@mail.python.org>


Roundup Robot added the comment:

New changeset 16f399588b2a by Victor Stinner in branch '3.4':
Issue #21454: Fix asyncio.BaseEventLoop.connect_read_pipe doc
http://hg.python.org/cpython/rev/16f399588b2a

New changeset 8391f99208f6 by Victor Stinner in branch 'default':
(Merge 3.4) Issue #21454: Fix asyncio.BaseEventLoop.connect_read_pipe doc
http://hg.python.org/cpython/rev/8391f99208f6

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

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

From report at bugs.python.org  Thu May 29 00:20:03 2014
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 28 May 2014 22:20:03 +0000
Subject: [docs] [issue21454] asyncio's loop.connect_read_pipe makes
	pipes	non-blocking contrary to the documentation
In-Reply-To: <1399575906.07.0.344601032189.issue21454@psf.upfronthosting.co.za>
Message-ID: <1401315603.86.0.538572889712.issue21454@psf.upfronthosting.co.za>


STINNER Victor added the comment:

Yes, the documentation was wrong. It should now be fixed. Thanks for the report.

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

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

From report at bugs.python.org  Thu May 29 00:30:35 2014
From: report at bugs.python.org (Martin Panter)
Date: Wed, 28 May 2014 22:30:35 +0000
Subject: [docs] [issue21580] PhotoImage(data=...) apparently has to be UTF-8
	or	Base-64 encoded
In-Reply-To: <1401083544.46.0.470654104454.issue21580@psf.upfronthosting.co.za>
Message-ID: <1401316235.79.0.72789168359.issue21580@psf.upfronthosting.co.za>


Martin Panter added the comment:

Thanks for looking at this. Originally the issue was found by reading the GIF and PNG images on various web pages, such as <http://www.weatherzone.com.au/vic/north-central/castlemaine>. However I was also able to produce the problem with the other formats of that Python logo:

$ python3 -Wall -bt
Python 3.4.1 (default, May 19 2014, 17:40:19) 
[GCC 4.9.0 20140507 (prerelease)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tkinter; tk = tkinter.Tk(); text = tkinter.Text(tk); text.pack()
>>> with open("/lib/python3.4/test/imghdrdata/python.png", "rb") as file: data = file.read()
... 
>>> image = tkinter.PhotoImage(format="png", data=data)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.4/tkinter/__init__.py", line 3384, in __init__
    Image.__init__(self, 'photo', name, cnf, master, **kw)
  File "/usr/lib/python3.4/tkinter/__init__.py", line 3340, in __init__
    self.tk.call(('image', 'create', imgtype, name,) + options)
_tkinter.TclError: CRC check failed
>>> u8png = tkinter.PhotoImage(format="png", data=data.decode("latin-1").encode("utf-8"))
>>> text.image_create(tkinter.END, image=u8png)
'pyimage2'

The same problem occurs with the PGM and PPM logos, and the Base-64 encoding trick does not work with those; only UTF-8 encoding. However as you discovered, the GIF format logo works no problem when passed unencoded, although it continues to work if I use my UTF-8 encoding trick, which is a bit strange. Perhaps the internal UTF-8 decoding step is passing the invalid UTF-8 straight through?

----------

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

From report at bugs.python.org  Thu May 29 07:08:32 2014
From: report at bugs.python.org (Vajrasky Kok)
Date: Thu, 29 May 2014 05:08:32 +0000
Subject: [docs] [issue21601] Cancel method for Asyncio Task is not documented
Message-ID: <1401340112.56.0.394123736.issue21601@psf.upfronthosting.co.za>


New submission from Vajrasky Kok:

https://docs.python.org/3.5/library/asyncio-task.html#task

The cancel method is not documented although it is a part of public API. Here is the patch to fix the doc.

----------
assignee: docs at python
components: Documentation
files: fix_doc_asyncio_task.patch
keywords: patch
messages: 219333
nosy: docs at python, haypo, vajrasky
priority: normal
severity: normal
status: open
title: Cancel method for Asyncio Task is not documented
versions: Python 3.4, Python 3.5
Added file: http://bugs.python.org/file35397/fix_doc_asyncio_task.patch

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

From nipun at nepdroid.com  Thu May 29 06:40:18 2014
From: nipun at nepdroid.com (Nipun Shakya)
Date: Thu, 29 May 2014 10:25:18 +0545
Subject: [docs] Python 2.7.7rc1 Documentation Download 404 errors
In-Reply-To: <CAKJDb-NYSAbM3vDotMWKRtVJ5ZgrVr2zrXZBq+B4gSTKxYJ-qw@mail.gmail.com>
References: <CAKJDb-NYSAbM3vDotMWKRtVJ5ZgrVr2zrXZBq+B4gSTKxYJ-qw@mail.gmail.com>
Message-ID: <CAN8u9hQHty2x7Os6HLbpiYGWGC719vGpV5pMV9ZHmw-fQDy9iQ@mail.gmail.com>

Thanks Zachary Ware. :)


On Wed, May 28, 2014 at 10:59 PM, Zachary Ware <
zachary.ware+pydocs at gmail.com> wrote:

> (Note: All reporters from the past several days are Bcc'd on this email)
>
> This issue has been fixed and the documentation archives for 2.7.7rc1
> are now available for download.
>
> Thank you for your report, hopefully this won't be a problem when the
> next RC release comes around!
>
> Regards,
> --
> Zach
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140529/e7e06288/attachment.html>

From report at bugs.python.org  Thu May 29 10:41:08 2014
From: report at bugs.python.org (=?utf-8?q?Wilfried_L=C3=BCbbe?=)
Date: Thu, 29 May 2014 08:41:08 +0000
Subject: [docs] [issue21604] Misleading 2to3 fixer name in
	documentation:	standard_error
Message-ID: <1401352868.06.0.396054178232.issue21604@psf.upfronthosting.co.za>


New submission from Wilfried L?bbe:

The documentation https://docs.python.org/2/library/2to3.html#2to3fixer-standard_error calls the fixer "standard_error". But really its name is "standarderror" (the filename is "fix_standarderror.py").

Py3.4.1 and Py3.4 docs are the same: https://docs.python.org/3.4/library/2to3.html#2to3fixer-standard_error
https://docs.python.org/3.5/library/2to3.html#2to3fixer-standard_error

----------
assignee: docs at python
components: Documentation
messages: 219341
nosy: docs at python, wluebbe
priority: normal
severity: normal
status: open
title: Misleading 2to3 fixer name in documentation: standard_error
versions: Python 2.7, Python 3.4, Python 3.5

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

From report at bugs.python.org  Thu May 29 16:27:25 2014
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 29 May 2014 14:27:25 +0000
Subject: [docs] [issue21580] PhotoImage(data=...) apparently has to be UTF-8
	or	Base-64 encoded
In-Reply-To: <1401083544.46.0.470654104454.issue21580@psf.upfronthosting.co.za>
Message-ID: <1401373645.46.0.279309018312.issue21580@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Here is a patch which fixes passing Python bytes to Tcl in Python 3. However it will be not easy to fix this issue in Python 2.

See also issue21605 which adds tests for Tkinter images (some of them fails without this patch).

----------
assignee: docs at python -> serhiy.storchaka
dependencies: +Add tests for Tkinter images
keywords: +patch
stage: test needed -> patch review
type:  -> behavior
versions: +Python 2.7, Python 3.5
Added file: http://bugs.python.org/file35402/tkinter_bytes.patch

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

From report at bugs.python.org  Thu May 29 21:36:02 2014
From: report at bugs.python.org (Zachary Ware)
Date: Thu, 29 May 2014 19:36:02 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
In-Reply-To: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>
Message-ID: <1401392162.75.0.0543377498444.issue14097@psf.upfronthosting.co.za>


Changes by Zachary Ware <zachary.ware at gmail.com>:


----------
nosy: +zach.ware

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

From zachary.ware+pydocs at gmail.com  Thu May 29 21:42:19 2014
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Thu, 29 May 2014 14:42:19 -0500
Subject: [docs] [FWD: [FWD: Bug in tutorial doc] - continued] -
 understanding has dawned
In-Reply-To: <20140528081922.d4a448afb03c93b23c340bae0fa3aa12.72f5b1552d.wbe@email07.europe.secureserver.net>
References: <20140528081922.d4a448afb03c93b23c340bae0fa3aa12.72f5b1552d.wbe@email07.europe.secureserver.net>
Message-ID: <CAKJDb-NQNHzLnDp78ZgMVOzxihDLd8wKN4B6HtvmyaoDh=q-wg@mail.gmail.com>

Hi John,

On Wed, May 28, 2014 at 10:19 AM,  <john at ashworthsatellites.com> wrote:
> OK. The examples are correct. However, the documentation assumes familiarity
> with Icon. It would be helpful if the rules for the slice notation were
> explicitly stated, i.e. the second index is that of the character after the
> end of the slice. Would it be possible to add a little sentence to that
> effect?

Thanks for the report!  Sorry about the confusion caused by the
outdated tutorial, but I'm glad you figured it out for yourself.

The Python 3 tutorial has a better explanation that still applies to
Python 2, which will eventually be backported to the Python 2.7
tutorial; see http://bugs.python.org/issue14097.

Welcome to Python, I hope you enjoy using it!

Regards,
-- 
Zach

From report at bugs.python.org  Thu May 29 23:03:13 2014
From: report at bugs.python.org (Miquel Garcia)
Date: Thu, 29 May 2014 21:03:13 +0000
Subject: [docs] [issue21609] Documentation for datetime.datetime uses
	microseconds	instead of microsecond
Message-ID: <1401397393.28.0.277127762562.issue21609@psf.upfronthosting.co.za>


New submission from Miquel Garcia:

In browsing the documentation for datetime.datetime:

https://docs.python.org/2/library/datetime.html

It states that the datetime.datetime.microseconds returns the number of microseconds but in trying (Python 2.7.1 r271:86832):

import datetime
print datetime.datetime.now().microseconds

The interpreter returns 

AttributeError: 'datetime.datetime' object has no attribute 'microseconds'

The correct way to access the number of microseconds is by:

datetime.datetime.now().microsecond # Note the final 's'

which is not consistent with the documentation.

Many thanks

Miquel

----------
assignee: docs at python
components: Documentation
messages: 219366
nosy: Miquel.Garcia, docs at python
priority: normal
severity: normal
status: open
title: Documentation for datetime.datetime uses microseconds instead of microsecond
versions: Python 2.7

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

From report at bugs.python.org  Thu May 29 23:13:36 2014
From: report at bugs.python.org (SilentGhost)
Date: Thu, 29 May 2014 21:13:36 +0000
Subject: [docs] [issue21609] Documentation for datetime.datetime uses
	microseconds	instead of microsecond
In-Reply-To: <1401397393.28.0.277127762562.issue21609@psf.upfronthosting.co.za>
Message-ID: <1401398016.44.0.953956683284.issue21609@psf.upfronthosting.co.za>


SilentGhost added the comment:

Could you provide an actual quote where it refers to datetime.datetime.microseconds? Are you not by any chance confusing it with datetime.timedelta.microseconds?

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

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

From report at bugs.python.org  Thu May 29 23:18:07 2014
From: report at bugs.python.org (Miquel Garcia)
Date: Thu, 29 May 2014 21:18:07 +0000
Subject: [docs] [issue21609] Documentation for datetime.datetime uses
	microseconds	instead of microsecond
In-Reply-To: <1401397393.28.0.277127762562.issue21609@psf.upfronthosting.co.za>
Message-ID: <1401398287.65.0.831510281551.issue21609@psf.upfronthosting.co.za>


Miquel Garcia added the comment:

My mistake. Yes you are right, I was confused with the timedelta class. 

Sorry for the confusion. Many thanks!

Miquel

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

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

From drewpca at google.com  Fri May 30 02:45:28 2014
From: drewpca at google.com (Drew Perttula)
Date: Thu, 29 May 2014 17:45:28 -0700
Subject: [docs] doc error on assertItemsEqual
Message-ID: <CAGyFws6+UaSAd=fQ2K9RZJMK4VE0XX9uJd-4y4bW2=8=6xLLtw@mail.gmail.com>

The 2.7.3 source says
    def assertItemsEqual(self, expected_seq, actual_seq, msg=None):

but
https://docs.python.org/2/library/unittest.html#unittest.TestCase.assertItemsEqual
says
    assertItemsEqual(actual, expected, msg=None)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140529/6173d81e/attachment-0001.html>

From report at bugs.python.org  Fri May 30 10:58:56 2014
From: report at bugs.python.org (Dmitry Andreychuk)
Date: Fri, 30 May 2014 08:58:56 +0000
Subject: [docs] [issue21611] int() docstring - unclear what number is
Message-ID: <1401440335.97.0.776400017562.issue21611@psf.upfronthosting.co.za>


New submission from Dmitry Andreychuk:

https://docs.python.org/3.4/library/functions.html?highlight=int#int

The docstring for int() function has these sentences:
"If x is a number, return x.__int__()."
"If x is not a number or if base is given..."

Unfortunately the docstring doesn't describe how the function decides if x is a number or not.

After searching and experimenting I came to conclusion that it is the presence of x.__int__() method makes int() treat x as a number. But I'm not sure it's a precise requirement or just something that happens to work with current implementation.

I think there should be a precise definition of what is considered to be a number there.

----------
assignee: docs at python
components: Documentation
messages: 219379
nosy: and, docs at python
priority: normal
severity: normal
status: open
title: int() docstring - unclear what number is
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5

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

From report at bugs.python.org  Fri May 30 20:22:48 2014
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 30 May 2014 18:22:48 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
In-Reply-To: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>
Message-ID: <1401474167.97.0.163085293225.issue14097@psf.upfronthosting.co.za>


Zachary Ware added the comment:

How's this for a 2.7 backport?  The least direct part of the backport is the section on division; I pretty much had to completely rewrite the paragraph in 2.x terms and I'm not certain that I took the best approach.

----------
stage: commit review -> patch review
versions:  -Python 3.3, Python 3.4
Added file: http://bugs.python.org/file35414/issue14097-2.7.diff

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

From report at bugs.python.org  Fri May 30 21:51:50 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 30 May 2014 19:51:50 +0000
Subject: [docs] [issue21593] Clarify re.search documentation first match
In-Reply-To: <1401287966.38.0.860641123785.issue21593@psf.upfronthosting.co.za>
Message-ID: <1401479510.13.0.832085158443.issue21593@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Since I am 99.999% sure that first is intended, I will change 'a location' to 'the first location'.

----------
assignee: docs at python -> terry.reedy
nosy: +terry.reedy
stage:  -> needs patch
type:  -> enhancement
versions:  -Python 3.1, Python 3.2, Python 3.3

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

From report at bugs.python.org  Fri May 30 22:20:52 2014
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 30 May 2014 20:20:52 +0000
Subject: [docs] [issue21593] Clarify re.search documentation first match
In-Reply-To: <1401287966.38.0.860641123785.issue21593@psf.upfronthosting.co.za>
Message-ID: <3ggHGW1QD2z7Ljp@mail.python.org>


Roundup Robot added the comment:

New changeset f7bb1d73a341 by Terry Jan Reedy in branch '2.7':
Issue #21593: (from StackOverflow) minor doc clarification for re.search.
http://hg.python.org/cpython/rev/f7bb1d73a341

New changeset 6013a112aba0 by Terry Jan Reedy in branch '3.4':
Issue #21593: (from StackOverflow) minor doc clarification for re.search.
http://hg.python.org/cpython/rev/6013a112aba0

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

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

From report at bugs.python.org  Sat May 31 02:13:27 2014
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 31 May 2014 00:13:27 +0000
Subject: [docs] [issue21593] Clarify re.search documentation first match
In-Reply-To: <1401287966.38.0.860641123785.issue21593@psf.upfronthosting.co.za>
Message-ID: <1401495206.88.0.376358067616.issue21593@psf.upfronthosting.co.za>


Changes by Terry J. Reedy <tjreedy at udel.edu>:


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

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

From report at bugs.python.org  Sat May 31 18:21:29 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 31 May 2014 16:21:29 +0000
Subject: [docs] [issue21604] Misleading 2to3 fixer name in
	documentation:	standard_error
In-Reply-To: <1401352868.06.0.396054178232.issue21604@psf.upfronthosting.co.za>
Message-ID: <1401553289.42.0.631678344648.issue21604@psf.upfronthosting.co.za>


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


----------
keywords: +easy
nosy: +jesstess
stage:  -> needs patch
type:  -> enhancement

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

From report at bugs.python.org  Sat May 31 18:23:47 2014
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 31 May 2014 16:23:47 +0000
Subject: [docs] [issue21611] int() docstring - unclear what number is
In-Reply-To: <1401440335.97.0.776400017562.issue21611@psf.upfronthosting.co.za>
Message-ID: <1401553427.4.0.561924441245.issue21611@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti, zach.ware
type:  -> enhancement
versions:  -Python 3.1, Python 3.2, Python 3.3

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

From report at bugs.python.org  Sat May 31 22:17:23 2014
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 31 May 2014 20:17:23 +0000
Subject: [docs] [issue21604] Misleading 2to3 fixer name in
	documentation:	standard_error
In-Reply-To: <1401352868.06.0.396054178232.issue21604@psf.upfronthosting.co.za>
Message-ID: <3ggv802TD0z7LkH@mail.python.org>


Roundup Robot added the comment:

New changeset 8fa8c290c165 by Benjamin Peterson in branch '2.7':
give the correct fixer name (closes #21604)
http://hg.python.org/cpython/rev/8fa8c290c165

New changeset 5d21491733d8 by Benjamin Peterson in branch '3.4':
give the correct fixer name (closes #21604)
http://hg.python.org/cpython/rev/5d21491733d8

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

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

From john at ashworthsatellites.com  Fri May 30 10:05:29 2014
From: john at ashworthsatellites.com (john at ashworthsatellites.com)
Date: Fri, 30 May 2014 01:05:29 -0700
Subject: [docs] [FWD: [FWD: Bug in tutorial doc] - continued] -
 understanding has dawned
Message-ID: <20140530010529.d4a448afb03c93b23c340bae0fa3aa12.7c9dcd4dda.wbe@email07.europe.secureserver.net>

An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20140530/eeee2d70/attachment.html>