From report at bugs.python.org  Thu Aug  1 13:23:32 2013
From: report at bugs.python.org (uglemat)
Date: Thu, 01 Aug 2013 11:23:32 +0000
Subject: [docs] [issue18612] More elaborate documentation on how list
	comprehensions	and generator expressions relate to each other
Message-ID: <1375356212.93.0.797789110077.issue18612@psf.upfronthosting.co.za>


New submission from uglemat:

Today there are list comprehensions, set comprehensions, dict comprehensions and then... there are generator expressions, which apparently was called 'generator comprehensions' in the original PEP, don't know why that was changed. Some questions arises:

 * Are generator expressions a type of list comprehension, or are generator expressions to be considered their own thing.

 * Does 'list comprehension' mean a type of comprehension that happens to return a list, or is it to be considered more of a general concept.

I usually talk about 'list comprehension' as a type of comprehension, and 'generator expression' as another type of comprehension, and after investigating whether or not that is correct I couldn't find an answer. On the wikipedia article on list comprension (http://en.wikipedia.org/wiki/List_comprehension#Python) they list generator expressions as well, indicating that it's a type of list comprehension. I think there's a lot of confusion to be had here, and that the documentation should clarify what exactly is meant by 'list comprehensions', regardless of what happens to be the case.

I haven't really a bug report before, so forgive me if I'm doing something wrong. :)

----------
assignee: docs at python
components: Documentation
messages: 194048
nosy: docs at python, uglemat
priority: normal
severity: normal
status: open
title: More elaborate documentation on how list comprehensions and generator expressions relate to each other
versions: Python 3.5

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

From report at bugs.python.org  Thu Aug  1 14:37:23 2013
From: report at bugs.python.org (R. David Murray)
Date: Thu, 01 Aug 2013 12:37:23 +0000
Subject: [docs] [issue18612] More elaborate documentation on how list
	comprehensions	and generator expressions relate to each other
In-Reply-To: <1375356212.93.0.797789110077.issue18612@psf.upfronthosting.co.za>
Message-ID: <1375360642.97.0.509501336354.issue18612@psf.upfronthosting.co.za>


R. David Murray added the comment:

Well, you haven't done anything wrong, but I'm not sure what we can do in response to the report.  What how will the answer to the question serve you?  What will you know after getting the answer that you didn't know before getting the answer?  I'm trying here to understand what it is that is missing from your mental model of Python that needs to be filled in, because the syntax and behavior of these constructs is documented, and it has never occurred to me to wonder whether or not a generator expression "is" a comprehension or not.

I'm making things up here, but I suspect we call generator expressions that because while they share the base syntax and much of the same semantics as the things we call comprehensions, (a) they produce an iterable (a generator object) instead instead of a fully realized object and (b) you can specify a generator expression without explicit surrounding punctuation (eg: "myfunc(x for x in range(7))").  That is, the 'comprehensions' are conceptually a notation for "specifying" a collection object using a compact notation, while a generator expression is a way of "creating" a generator-iterable *function* that must then be iterated to produce the collection object implicitly specified by the expression.  I'm not sure I'm being clear, because the distinction is subtle and perhaps not meaningful...the difference in naming might just be an historical accident :)

And, because it is not entirely clear, I'm not sure it is a good idea to try to document it.  Again, what enlightenment would derive from a clear explanation?

----------
nosy: +r.david.murray
versions: +Python 2.7, Python 3.3, Python 3.4 -Python 3.5

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

From report at bugs.python.org  Thu Aug  1 14:42:35 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Thu, 01 Aug 2013 12:42:35 +0000
Subject: [docs] [issue12645] test.support. import_fresh_module - incorrect
	doc
In-Reply-To: <1311789815.76.0.639942891335.issue12645@psf.upfronthosting.co.za>
Message-ID: <1375360954.84.0.771246589439.issue12645@psf.upfronthosting.co.za>


Eli Bendersky added the comment:

Ben, would you like to provide an updated patch?

----------

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

From report at bugs.python.org  Thu Aug  1 15:00:44 2013
From: report at bugs.python.org (uglemat)
Date: Thu, 01 Aug 2013 13:00:44 +0000
Subject: [docs] [issue18612] More elaborate documentation on how list
	comprehensions	and generator expressions relate to each other
In-Reply-To: <1375356212.93.0.797789110077.issue18612@psf.upfronthosting.co.za>
Message-ID: <1375362044.65.0.916069751782.issue18612@psf.upfronthosting.co.za>


uglemat added the comment:

Yeah I think the differences are pretty easy to comprehend. To be honest the reason I came here is that I had an argument where someone commented on my code (where I used a generator expression) saying something akin to "list comprehensions are nice", so I replied "actually, that's a generator expression, which are very similar but behave differently". The response was that the two concepts are one and the same. I couldn't really say that that's incorrect, but I think it's very confusing for beginners if people are talking about generator expressions like they are list expressions because they behave so differently and the documentation for list comprehensions doesn't mention generator expressions. I was kind of longing for a definite answer so I could say "Nay, thou shall differentiate between list comprehensions and generator expressions". Is it right to correct someone and say that generator expressions are in fact *not* generator expressions? Maybe I'm blowing this out of proportions. :)

----------
versions: +Python 3.5 -Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Thu Aug  1 15:05:17 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 01 Aug 2013 13:05:17 +0000
Subject: [docs] [issue10434] Document the rules for "public names"
In-Reply-To: <1289919338.9.0.394057770971.issue10434@psf.upfronthosting.co.za>
Message-ID: <1375362317.81.0.560638431698.issue10434@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

PEP 8 now covers the developer side of things: http://www.python.org/dev/peps/pep-0008/#public-and-internal-interfaces

A user facing counterpart describing our backwards compatibility policy is still desirable. Updating PEP 5 wouldn't go astray, since that's *supposed* to serve that purpose :)

----------
nosy: +ncoghlan

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

From report at bugs.python.org  Thu Aug  1 15:05:31 2013
From: report at bugs.python.org (uglemat)
Date: Thu, 01 Aug 2013 13:05:31 +0000
Subject: [docs] [issue18612] More elaborate documentation on how list
	comprehensions	and generator expressions relate to each other
In-Reply-To: <1375356212.93.0.797789110077.issue18612@psf.upfronthosting.co.za>
Message-ID: <1375362331.76.0.275902634818.issue18612@psf.upfronthosting.co.za>


uglemat added the comment:

> Is it right to correct someone and say that generator expressions are in fact *not* generator expressions?

Ups, I meant "Is it right to correct someone and say that generator expressions are in fact *not* list comprehensions?"

All these expressions and comprehensions are making me dissy :)

----------

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

From report at bugs.python.org  Thu Aug  1 15:20:28 2013
From: report at bugs.python.org (R. David Murray)
Date: Thu, 01 Aug 2013 13:20:28 +0000
Subject: [docs] [issue18612] More elaborate documentation on how list
	comprehensions	and generator expressions relate to each other
In-Reply-To: <1375356212.93.0.797789110077.issue18612@psf.upfronthosting.co.za>
Message-ID: <1375363228.87.0.646528199026.issue18612@psf.upfronthosting.co.za>


R. David Murray added the comment:

Well, it is the case that if you substitute a list comprehension for a generator expression in arbitrary code, most of the time it would work but occasionally it wouldn't, because the runtime behavior is different (lazy production versus all-at-once production).  So yes, the two are not the same thing, and it is important to understand the differences in behavior between them.  Calling a generator expression a list comprehension indicates someone's mental model of how Python works has a couple holes in it, IMO :)

----------

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

From report at bugs.python.org  Thu Aug  1 21:05:24 2013
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Thu, 01 Aug 2013 19:05:24 +0000
Subject: [docs] [issue18558] Iterable glossary entry needs clarification
In-Reply-To: <1374796651.89.0.668716719647.issue18558@psf.upfronthosting.co.za>
Message-ID: <1375383924.01.0.00621420986944.issue18558@psf.upfronthosting.co.za>


Stephen Paul Chappell added the comment:

If my program needed to know if an object is iterable, it would be tempting to define and call the following function instead of using collections.abc.Iterable:

    def iterable(obj):
        try:
            iter(obj)
        except TypeError:
            return False
        return True

Something tells me that is not what the author of collections.abc.Iterable intended.

----------

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

From report at bugs.python.org  Thu Aug  1 21:14:54 2013
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 01 Aug 2013 19:14:54 +0000
Subject: [docs] [issue18589] cross-referencing doesn't work between the
	extending	guide and c-api
In-Reply-To: <1375122124.66.0.67649436332.issue18589@psf.upfronthosting.co.za>
Message-ID: <3c5h5n4G35z7LjP@mail.python.org>


Roundup Robot added the comment:

New changeset a381721299a3 by Antoine Pitrou in branch '3.3':
Issue #18589: fix hyperlinking of type slots (tp_*)
http://hg.python.org/cpython/rev/a381721299a3

New changeset 36ff479e429c by Antoine Pitrou in branch 'default':
Issue #18589: fix hyperlinking of type slots (tp_*)
http://hg.python.org/cpython/rev/36ff479e429c

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

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

From report at bugs.python.org  Thu Aug  1 21:17:32 2013
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 01 Aug 2013 19:17:32 +0000
Subject: [docs] [issue18589] cross-referencing doesn't work between the
	extending	guide and c-api
In-Reply-To: <1375122124.66.0.67649436332.issue18589@psf.upfronthosting.co.za>
Message-ID: <3c5h8q6c5xz7LjQ@mail.python.org>


Roundup Robot added the comment:

New changeset bb546f6d8ab4 by Antoine Pitrou in branch '2.7':
Issue #18589: fix hyperlinking of type slots (tp_*)
http://hg.python.org/cpython/rev/bb546f6d8ab4

----------

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

From report at bugs.python.org  Thu Aug  1 21:17:52 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 01 Aug 2013 19:17:52 +0000
Subject: [docs] [issue18589] cross-referencing doesn't work between the
	extending	guide and c-api
In-Reply-To: <1375122124.66.0.67649436332.issue18589@psf.upfronthosting.co.za>
Message-ID: <1375384672.23.0.590086546322.issue18589@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


----------
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Thu Aug  1 22:26:32 2013
From: report at bugs.python.org (R. David Murray)
Date: Thu, 01 Aug 2013 20:26:32 +0000
Subject: [docs] [issue18558] Iterable glossary entry needs clarification
In-Reply-To: <1374796651.89.0.668716719647.issue18558@psf.upfronthosting.co.za>
Message-ID: <1375388792.26.0.533463547564.issue18558@psf.upfronthosting.co.za>


R. David Murray added the comment:

That would give you a false positive, though.  It would return True for the 'y' in my example, which is not iterable.  So Iterable's behavior here is an example of the Python design rule "resist the temptation to guess".

As Terry said, new classes should implement an __iter__ method.  The __getitem__ iteration support is for backward compatibility.

----------

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

From report at bugs.python.org  Thu Aug  1 22:30:44 2013
From: report at bugs.python.org (Chris Curvey)
Date: Thu, 01 Aug 2013 20:30:44 +0000
Subject: [docs] [issue18620] multiprocessing page leaves out important part
	of Pool	example
Message-ID: <1375389044.82.0.349700607179.issue18620@psf.upfronthosting.co.za>


New submission from Chris Curvey:

on http://docs.python.org/2/library/multiprocessing.html, there is a bit about how to use a Pool properly, which looks like this

pool = Pool(processes=4)              # start 4 worker processes
result = pool.apply_async(f, [10])

What this neglects to mention is that only one process will get any of the work.  If you really want four processes in the pool to work, you have to call apply_async four times.  For example:

results = []
pool = Pool(processes=4)
for i in xrange(4):
    results.append(pool.apply_async(f, [10]))

hat tip to http://stackoverflow.com/questions/12483512/python-multiprocessing-apply-async-only-uses-one-process

----------
assignee: docs at python
components: Documentation
messages: 194115
nosy: Chris.Curvey, docs at python
priority: normal
severity: normal
status: open
title: multiprocessing page leaves out important part of Pool example
type: enhancement

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

From report at bugs.python.org  Thu Aug  1 23:46:12 2013
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Thu, 01 Aug 2013 21:46:12 +0000
Subject: [docs] [issue18558] Iterable glossary entry needs clarification
In-Reply-To: <1374796651.89.0.668716719647.issue18558@psf.upfronthosting.co.za>
Message-ID: <1375393572.01.0.442284358787.issue18558@psf.upfronthosting.co.za>


Stephen Paul Chappell added the comment:

Maybe this would have been more appropriate as a question on StackOverflow:

What is the proper way of asking if an object is iterable if it does not support the iterator protocol but does support the old getitem protocol? One might argue that it is better to ask for forgiveness rather than permission, but that does not really answer the question.

My impression of collections.abc.Iterable is that programmers can use it to ask if an object is iterable. Some argue that it is better to ask for forgiveness rather that permission and would suggest pretending that an object is iterable until it is proven otherwise. However, what do we use collections.abc.Iterable?s for then?

The true question is really, ?What is the proper way of asking if an object is iterable if it does not support the iterator protocol but does support the old getitem protocol?? More generically, how can you ask an object if it supports ANY iteration protocol? The query probably should have been posted on StackOverflow and not here.

This may not be a problem with collections.abc.Iterable, and thus the issue should be closed. However, the previous question remains, and it is apparent that it cannot be answered with the abstract class as it currently is. Maybe the solution is to just ask for forgiveness where appropriate.

----------

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

From report at bugs.python.org  Fri Aug  2 01:29:18 2013
From: report at bugs.python.org (R. David Murray)
Date: Thu, 01 Aug 2013 23:29:18 +0000
Subject: [docs] [issue18558] Iterable glossary entry needs clarification
In-Reply-To: <1374796651.89.0.668716719647.issue18558@psf.upfronthosting.co.za>
Message-ID: <1375399758.79.0.488038477513.issue18558@psf.upfronthosting.co.za>


R. David Murray added the comment:

?What is the proper way of asking if an object is iterable if it does not support the iterator protocol but does support the old getitem protocol??

The *only* answer to that question is to try to iterate it, and see if you get a KeyError on "0".  Since this results in obtaining the first element if it *is* iterable, and in the general case you cannot "reset" an iterable, there is no way to look before you leap.  You have to catch the error after it occurs.

This question and answer probably do belong on Stack Overflow or python-list, but the glossary entry still needs improvement, since the Iterable docs reference it :)

----------

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

From report at bugs.python.org  Fri Aug  2 01:44:13 2013
From: report at bugs.python.org (Kevin Harms)
Date: Thu, 01 Aug 2013 23:44:13 +0000
Subject: [docs] [issue14956] custom PYTHONPATH may break apps embedding
	Python
In-Reply-To: <1338321412.45.0.331737203349.issue14956@psf.upfronthosting.co.za>
Message-ID: <1375400653.72.0.512111597617.issue14956@psf.upfronthosting.co.za>


Kevin Harms added the comment:

As far as I can tell, this issue is not resolved. It would be very nice for the C API to have the equivalent for -E for security reasons. I would like to make a setgid binary and do not want users to be able to set PYTHON* variables to force loading of custom code.

----------
nosy: +Kevin.Harms

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

From report at bugs.python.org  Fri Aug  2 02:32:30 2013
From: report at bugs.python.org (Demian Brecht)
Date: Fri, 02 Aug 2013 00:32:30 +0000
Subject: [docs] [issue17145] memoryview(array.array)
In-Reply-To: <1360170754.31.0.614797074916.issue17145@psf.upfronthosting.co.za>
Message-ID: <1375403550.77.0.697244610446.issue17145@psf.upfronthosting.co.za>


Demian Brecht added the comment:

Bump. If the patch (or request) is invalid, might be worthwhile closing this issue (although I still think it's valid ;)).

----------

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

From report at bugs.python.org  Fri Aug  2 06:43:38 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Fri, 02 Aug 2013 04:43:38 +0000
Subject: [docs] [issue18627] Typo in Modules/hashlib.h
Message-ID: <1375418618.45.0.59595383081.issue18627@psf.upfronthosting.co.za>


New submission from Vajrasky Kok:

Got typo in Modules/hashlib.h. See this patch for detail:

--- a/Modules/hashlib.h	Wed Jul 31 20:48:26 2013 -0400
+++ b/Modules/hashlib.h	Fri Aug 02 12:39:00 2013 +0800
@@ -2,7 +2,7 @@
 
 /*
  * Given a PyObject* obj, fill in the Py_buffer* viewp with the result
- * of PyObject_GetBuffer.  Sets and exception and issues a return NULL
+ * of PyObject_GetBuffer.  Sets an exception and issues a return NULL
  * on any errors.
  */
 #define GET_BUFFER_VIEW_OR_ERROUT(obj, viewp) do { \

----------
assignee: docs at python
components: Documentation
messages: 194151
nosy: docs at python, vajrasky
priority: normal
severity: normal
status: open
title: Typo in Modules/hashlib.h
versions: Python 3.4

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

From report at bugs.python.org  Fri Aug  2 06:49:44 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 02 Aug 2013 04:49:44 +0000
Subject: [docs] [issue18628] PEP 8 and encodings
Message-ID: <1375418984.87.0.318628832877.issue18628@psf.upfronthosting.co.za>


New submission from Terry J. Reedy:

Three related doc change proposals. The Versions only apply to the third as the first two are for PEP 8.

1. PEP 8 has a section entitled "Encodings (PEP 263)" with a link to the verbose PEP. I think it would be better if it were "Source Encoding" with a link to the 'current' Reference Manual section 2.1.4. Encoding declarations. The latter gets right to the point.

2. This section twice uses the informal and undefined term 'coding cookie'. It is not in the ref manual section above, nor in the glossary, nor in the index. (Dave Angel asked about the definition on python-list. Before searching on the web, he first thought it meant BOM.) I suggest changing "a coding cookie" to "an encoding declaration".

3. The index has several entries that begin with 'encode', including one that just says 'encodings'. The last is the one that points to 2.1.4., but one would only guess by process of elimination. I think 'encoding (source file)' or 'encoding declarations (source file)' would be clearer.

----------
assignee: docs at python
components: Documentation
messages: 194152
nosy: docs at python, ncoghlan, terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: PEP 8 and encodings
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Aug  2 07:13:54 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 02 Aug 2013 05:13:54 +0000
Subject: [docs] [issue18627] Typo in Modules/hashlib.h
In-Reply-To: <1375418618.45.0.59595383081.issue18627@psf.upfronthosting.co.za>
Message-ID: <3c5xNx6Tc7z7LjT@mail.python.org>


Roundup Robot added the comment:

New changeset 3716d64f846b by Ned Deily in branch '3.3':
Issue #18627: Fix typo noticed by Vajrasky Kok.
http://hg.python.org/cpython/rev/3716d64f846b

New changeset 454e9db1c750 by Ned Deily in branch 'default':
Closes #18627: merge from 3.3
http://hg.python.org/cpython/rev/454e9db1c750

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Fri Aug  2 07:14:55 2013
From: report at bugs.python.org (Ned Deily)
Date: Fri, 02 Aug 2013 05:14:55 +0000
Subject: [docs] [issue18627] Typo in Modules/hashlib.h
In-Reply-To: <1375418618.45.0.59595383081.issue18627@psf.upfronthosting.co.za>
Message-ID: <1375420495.56.0.439634338643.issue18627@psf.upfronthosting.co.za>


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


----------
versions: +Python 3.3

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

From report at bugs.python.org  Fri Aug  2 12:20:55 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 02 Aug 2013 10:20:55 +0000
Subject: [docs] [issue18628] PEP 8 and encodings
In-Reply-To: <1375418984.87.0.318628832877.issue18628@psf.upfronthosting.co.za>
Message-ID: <1375438855.43.0.713971357615.issue18628@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Aug  2 12:32:14 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 02 Aug 2013 10:32:14 +0000
Subject: [docs] [issue18628] Better index entry for encoding declarations
In-Reply-To: <1375418984.87.0.318628832877.issue18628@psf.upfronthosting.co.za>
Message-ID: <1375439534.67.0.220882919968.issue18628@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

I changed the section heading in PEP 8 to "Source File Encoding" and the sole remaining use of "a coding cookie" to "an encoding declaration". No link, since it would need separate links for Python 2 and 3, and that just gets messing. Now it uses the right terminology, it should be easier to look up.

So, this is now just a regular docs bug for Terry's third point about the (lack of a suitable) index entry :)

----------
assignee: ncoghlan -> docs at python
title: PEP 8 and encodings -> Better index entry for encoding declarations

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

From report at bugs.python.org  Sat Aug  3 11:30:40 2013
From: report at bugs.python.org (Phil Connell)
Date: Sat, 03 Aug 2013 09:30:40 +0000
Subject: [docs] [issue18566] In unittest.TestCase docs for setUp() and
	tearDown()	don't mention AssertionError
In-Reply-To: <1374901937.1.0.747872580847.issue18566@psf.upfronthosting.co.za>
Message-ID: <1375522240.18.0.435540916757.issue18566@psf.upfronthosting.co.za>


Changes by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

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

From report at bugs.python.org  Sat Aug  3 11:43:09 2013
From: report at bugs.python.org (Jason R. Coombs)
Date: Sat, 03 Aug 2013 09:43:09 +0000
Subject: [docs] [issue18532] hashlib.HASH objects should officially expose
	the hash	name
In-Reply-To: <1374524940.42.0.582552143445.issue18532@psf.upfronthosting.co.za>
Message-ID: <1375522988.99.0.101223106292.issue18532@psf.upfronthosting.co.za>


Jason R. Coombs added the comment:

It's not obvious to me if the authors originally intended to have the 'name' attribute as a formal interface, so I've decided the change should probably be added to Python 3.4. Here's a diff I've put together: http://paste.jaraco.com/tMdQ2

It updates the documentation and adds a test to guarantee the interface. I'm unsure about the RST syntax, so I would appreciate a review of the syntax there. Also, I haven't run the test yet, but I'll do that at a later date.

----------

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

From report at bugs.python.org  Sat Aug  3 11:43:46 2013
From: report at bugs.python.org (Jason R. Coombs)
Date: Sat, 03 Aug 2013 09:43:46 +0000
Subject: [docs] [issue18532] hashlib.HASH objects should officially expose
	the hash	name
In-Reply-To: <1374524940.42.0.582552143445.issue18532@psf.upfronthosting.co.za>
Message-ID: <1375523026.41.0.690883440912.issue18532@psf.upfronthosting.co.za>


Changes by Jason R. Coombs <jaraco at jaraco.com>:


----------
keywords: +needs review
stage: needs patch -> patch review

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

From report at bugs.python.org  Sat Aug  3 15:31:31 2013
From: report at bugs.python.org (=?utf-8?q?Charles-Fran=C3=A7ois_Natali?=)
Date: Sat, 03 Aug 2013 13:31:31 +0000
Subject: [docs] [issue15233] atexit: guarantee order of execution of
	registered	functions?
In-Reply-To: <1341129521.95.0.805489135584.issue15233@psf.upfronthosting.co.za>
Message-ID: <1375536691.51.0.555057210352.issue15233@psf.upfronthosting.co.za>


Charles-Fran?ois Natali added the comment:

Unless anyone objects, I'll backport it soonish.

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

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

From report at bugs.python.org  Sat Aug  3 22:42:06 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 03 Aug 2013 20:42:06 +0000
Subject: [docs] [issue18646] Improve tutorial entry on 'Lambda Forms'.
Message-ID: <1375562526.59.0.207872880438.issue18646@psf.upfronthosting.co.za>


New submission from Terry J. Reedy:

[0. On mailing lists, 'lambda expression' is used rather than 'lambda form'. Docs use both. Consistency across docs is a broader issue than this one. So leave title alone for this one.]

1. (first sentence) "By popular demand, a few features commonly found in functional programming languages like Lisp have been added to Python." (in early Python 1!) I think this should just be deleted. See 4. below as a replacement.

2. " With the lambda keyword, small anonymous functions can be created."
Change to
"Small anonymous functions can be created with the lambda keyword."

3. change "Here?s a function that returns" to "This function returns"

3.5 add a sentence about the different between def and lambda (the name attribute.

4. Add sentences about the purposes of lambda. Add an example that illustrates passing functions. 

>>> pairs = [(1, 'one'), (2, 'two'), (3, 'three'), (4, 'four')]
>>> pairs.sort(key=lambda pair: pair[1])
>>> pairs
[(4, 'four'), (1, 'one'), (3, 'three'), (2, 'two')]

----------
assignee: docs at python
components: Documentation
files: tut-lambda.diff
keywords: patch
messages: 194296
nosy: docs at python, terry.reedy
priority: normal
severity: normal
stage: patch review
status: open
title: Improve tutorial entry on 'Lambda Forms'.
type: behavior
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file31142/tut-lambda.diff

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

From report at bugs.python.org  Sun Aug  4 00:27:14 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Sat, 03 Aug 2013 22:27:14 +0000
Subject: [docs] [issue13368] Possible problem in documentation of module
	subprocess, method send_signal
In-Reply-To: <1320722594.89.0.739080107592.issue13368@psf.upfronthosting.co.za>
Message-ID: <1375568834.51.0.95637155017.issue13368@psf.upfronthosting.co.za>


Eli Bendersky added the comment:

Brian - gentle ping

----------

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

From report at bugs.python.org  Sun Aug  4 02:54:49 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 04 Aug 2013 00:54:49 +0000
Subject: [docs] [issue17359] Mention "__main__.py" explicitly in command
	line docs
In-Reply-To: <1362512425.64.0.937549165034.issue17359@psf.upfronthosting.co.za>
Message-ID: <1375577689.3.0.537582067418.issue17359@psf.upfronthosting.co.za>


Changes by Eli Bendersky <eliben at gmail.com>:


----------
nosy:  -eli.bendersky

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

From report at bugs.python.org  Sun Aug  4 03:55:30 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 04 Aug 2013 01:55:30 +0000
Subject: [docs] [issue17902] Document that _elementtree C API cannot use
	custom	TreeBuilder for iterparse or IncrementalParser
In-Reply-To: <1367614578.64.0.34953241054.issue17902@psf.upfronthosting.co.za>
Message-ID: <3c74v55gcnzStl@mail.python.org>


Roundup Robot added the comment:

New changeset a5a5ba4f71ad by Eli Bendersky in branch '3.3':
Issue #17902: Clarify doc of ElementTree.iterparse
http://hg.python.org/cpython/rev/a5a5ba4f71ad

New changeset 96f45011957e by Eli Bendersky in branch 'default':
Issue #17902: Clarify doc of ElementTree.iterparse and IncrementalParser
http://hg.python.org/cpython/rev/96f45011957e

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

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

From report at bugs.python.org  Sun Aug  4 03:55:45 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 04 Aug 2013 01:55:45 +0000
Subject: [docs] [issue17902] Document that _elementtree C API cannot use
	custom	TreeBuilder for iterparse or IncrementalParser
In-Reply-To: <1367614578.64.0.34953241054.issue17902@psf.upfronthosting.co.za>
Message-ID: <1375581345.84.0.336723452348.issue17902@psf.upfronthosting.co.za>


Changes by Eli Bendersky <eliben at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Sun Aug  4 10:56:17 2013
From: report at bugs.python.org (Mark Dickinson)
Date: Sun, 04 Aug 2013 08:56:17 +0000
Subject: [docs] [issue17576] PyNumber_Index() is not int-subclass friendly
	(or	operator.index() docos lie)
In-Reply-To: <1364595911.19.0.826873230127.issue17576@psf.upfronthosting.co.za>
Message-ID: <1375606577.3.0.541077109007.issue17576@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

See the related python-dev discussion started by Mark Shannon here:

http://mail.python.org/pipermail/python-dev/2013-March/125022.html

and continuing well into April here:

http://mail.python.org/pipermail/python-dev/2013-April/125042.html

The consensus that emerged from that thread seems to be that calls to operator.index and to int() should always return something of exact type int.

The attached patch:

- Raises TypeError for implicit calls to nb_int that fail to return something of exact type int.  (Results of direct calls to __int__ are not checked.)

- Ensures that *all* conversions from a non-int to an int via nb_int make use of the nb_int slot, even for int subclasses.  Prior to this patch, some of the PyLong_As... functions would bypass __int__ for int subclasses.

- Adds a new private _PyLong_FromNbInt function to Objects/longobject.c, so that we have a single place for performing these conversions and making type checks, and refactors existing uses of the nb_int slot to go via this function.

- Makes corresponding changes for nb_index, which should address the original bug report.

I guess this may be too dangerous a change for Python 3.4.  In that case, I propose raising warnings instead of TypeErrors for Python 3.4 and turning those into TypeErrors in Python 3.5.

One other question:  should direct calls to __int__ and __index__ also have their return values type-checked?  That doesn't seem to happen at the moment for other magic methods (see below), so it would seem consistent to only do the type checking for interpreter-generated implicit calls to __int__ and __index__.  Nick: any opinion?

>>> class A:
...     def __len__(self): return "a string"
...     def __bool__(self): return "another string"
... 
>>> a = A()
>>> a.__len__()
'a string'
>>> a.__bool__()
'another string'
>>> len(a)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: 'str' object cannot be interpreted as an integer
>>> bool(a)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: __bool__ should return bool, returned str

----------
assignee: docs at python -> mark.dickinson
components: +Interpreter Core -Documentation
keywords: +patch
nosy: +ncoghlan
Added file: http://bugs.python.org/file31147/issue17576.patch

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

From report at bugs.python.org  Sun Aug  4 12:07:25 2013
From: report at bugs.python.org (Mark Dickinson)
Date: Sun, 04 Aug 2013 10:07:25 +0000
Subject: [docs] [issue17576] PyNumber_Index() is not int-subclass friendly
	(or	operator.index() docos lie)
In-Reply-To: <1364595911.19.0.826873230127.issue17576@psf.upfronthosting.co.za>
Message-ID: <1375610845.51.0.566366228358.issue17576@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

New patch that replaces the TypeErrors with warnings and fixes a refleak in the original patch.

----------
Added file: http://bugs.python.org/file31149/issue17576_v2.patch

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

From report at bugs.python.org  Sun Aug  4 13:29:25 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 04 Aug 2013 11:29:25 +0000
Subject: [docs] [issue17576] PyNumber_Index() is not int-subclass friendly
	(or	operator.index() docos lie)
In-Reply-To: <1364595911.19.0.826873230127.issue17576@psf.upfronthosting.co.za>
Message-ID: <1375615765.09.0.934256182267.issue17576@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

The deprecation warning version looks good to me.

Something I'll mention explicitly (regarding the PyCon discussions that Eric mentioned above), is that we unfortunately couldn't do something like this for the various concrete APIs with overly permissive subclass checks. For those APIs, calling them directly was often the *right* thing for simple subtypes implemented in C to use to call up to the parent implementation.

This case is different, as it's the *abstract* APIs that currently have the overly permissive checks.

----------

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

From report at bugs.python.org  Sun Aug  4 21:31:04 2013
From: report at bugs.python.org (Madison May)
Date: Sun, 04 Aug 2013 19:31:04 +0000
Subject: [docs] [issue18657] Remove duplicate ACKS entries
Message-ID: <1375644664.94.0.607349544003.issue18657@psf.upfronthosting.co.za>


New submission from Madison May:

The title says it all.  I used collections.Counter to check for duplicates in ACKS and cleaned up a few double entries.

----------
assignee: docs at python
components: Documentation
messages: 194410
nosy: docs at python, madison.may
priority: normal
severity: normal
status: open
title: Remove duplicate ACKS entries
versions: Python 3.4, Python 3.5

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

From report at bugs.python.org  Sun Aug  4 21:34:22 2013
From: report at bugs.python.org (R. David Murray)
Date: Sun, 04 Aug 2013 19:34:22 +0000
Subject: [docs] [issue18657] Remove duplicate ACKS entries
In-Reply-To: <1375644664.94.0.607349544003.issue18657@psf.upfronthosting.co.za>
Message-ID: <1375644862.39.0.664010166967.issue18657@psf.upfronthosting.co.za>


R. David Murray added the comment:

Did you intend to attach a patch?

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

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

From report at bugs.python.org  Sun Aug  4 21:38:43 2013
From: report at bugs.python.org (Madison May)
Date: Sun, 04 Aug 2013 19:38:43 +0000
Subject: [docs] [issue18657] Remove duplicate ACKS entries
In-Reply-To: <1375644664.94.0.607349544003.issue18657@psf.upfronthosting.co.za>
Message-ID: <1375645123.32.0.63816213465.issue18657@psf.upfronthosting.co.za>


Madison May added the comment:

Now with 100% more patch.  Thanks for the catch, David.

----------
keywords: +patch
Added file: http://bugs.python.org/file31157/ACKS_duplicates.patch

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

From report at bugs.python.org  Sun Aug  4 21:50:21 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 04 Aug 2013 19:50:21 +0000
Subject: [docs] [issue18657] Remove duplicate ACKS entries
In-Reply-To: <1375644664.94.0.607349544003.issue18657@psf.upfronthosting.co.za>
Message-ID: <3c7XlJ3CgvzS7H@mail.python.org>


Roundup Robot added the comment:

New changeset 2ec323dadca2 by R David Murray in branch '3.3':
#18657: remove duplicate entries from Misc/ACKS.
http://hg.python.org/cpython/rev/2ec323dadca2

New changeset f4f81ebc3de9 by R David Murray in branch 'default':
Merge: #18657: remove duplicate entries from Misc/ACKS.
http://hg.python.org/cpython/rev/f4f81ebc3de9

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

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

From report at bugs.python.org  Sun Aug  4 21:50:53 2013
From: report at bugs.python.org (R. David Murray)
Date: Sun, 04 Aug 2013 19:50:53 +0000
Subject: [docs] [issue18657] Remove duplicate ACKS entries
In-Reply-To: <1375644664.94.0.607349544003.issue18657@psf.upfronthosting.co.za>
Message-ID: <1375645853.18.0.234539329669.issue18657@psf.upfronthosting.co.za>


R. David Murray added the comment:

Thanks, Madison.

----------
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
type:  -> behavior
versions: +Python 3.3 -Python 3.5

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

From report at bugs.python.org  Mon Aug  5 01:01:47 2013
From: report at bugs.python.org (Ben Finney)
Date: Sun, 04 Aug 2013 23:01:47 +0000
Subject: [docs] [issue12645] test.support. import_fresh_module - incorrect
	doc
In-Reply-To: <1375360954.84.0.771246589439.issue12645@psf.upfronthosting.co.za>
Message-ID: <20130804230031.GB6856@benfinney.id.au>


Ben Finney added the comment:

On 01-Aug-2013, Eli Bendersky wrote:

> Ben, would you like to provide an updated patch?

Unfortunately, contributions are not accepted under the Apache Software
Foundation License (as I had thought), but also require assigning extra
privileges to the Python Software Foundation under a special agreement.

I'm not able to do this in good conscience, so it seems the Python Software
Foundation will reject my contribution.

----------

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

From report at bugs.python.org  Mon Aug  5 08:54:54 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 05 Aug 2013 06:54:54 +0000
Subject: [docs] [issue18532] hashlib.HASH objects should officially expose
	the hash	name
In-Reply-To: <1374524940.42.0.582552143445.issue18532@psf.upfronthosting.co.za>
Message-ID: <3c7qV55tLCz7Llw@mail.python.org>


Roundup Robot added the comment:

New changeset 238c37e4c395 by Jason R. Coombs in branch 'default':
Issue 18532: Added tests and documentation to formally specify the .name attribute on hashlib objects.
http://hg.python.org/cpython/rev/238c37e4c395

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

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

From report at bugs.python.org  Mon Aug  5 08:56:07 2013
From: report at bugs.python.org (Jason R. Coombs)
Date: Mon, 05 Aug 2013 06:56:07 +0000
Subject: [docs] [issue18532] hashlib.HASH objects should officially expose
	the hash	name
In-Reply-To: <1374524940.42.0.582552143445.issue18532@psf.upfronthosting.co.za>
Message-ID: <1375685767.71.0.895129166301.issue18532@psf.upfronthosting.co.za>


Jason R. Coombs added the comment:

I've confirmed the tests pass and the updated documentation renders nicely and without warnings. These changes now make the name attribute officially-supported and tested.

----------
resolution:  -> fixed

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

From report at bugs.python.org  Mon Aug  5 11:43:08 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Mon, 05 Aug 2013 09:43:08 +0000
Subject: [docs] [issue18661] Typo in grpmodule.c
Message-ID: <1375695788.15.0.911930238621.issue18661@psf.upfronthosting.co.za>


New submission from Vajrasky Kok:

I guess, there is a typo in Modules/grpmodule.c. See the patch below:

diff -r f4f81ebc3de9 Modules/grpmodule.c
--- a/Modules/grpmodule.c	Sun Aug 04 15:50:08 2013 -0400
+++ b/Modules/grpmodule.c	Mon Aug 05 17:40:33 2013 +0800
@@ -10,7 +10,7 @@
    {"gr_name", "group name"},
    {"gr_passwd", "password"},
    {"gr_gid", "group id"},
-   {"gr_mem", "group memebers"},
+   {"gr_mem", "group members"},
    {0}
 };

I am not sure whether the line after typo should be {0} or {0, 0}.

----------
assignee: docs at python
components: Documentation
messages: 194465
nosy: docs at python, vajrasky
priority: normal
severity: normal
status: open
title: Typo in grpmodule.c
versions: Python 3.4

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

From report at bugs.python.org  Mon Aug  5 11:53:44 2013
From: report at bugs.python.org (Mark Dickinson)
Date: Mon, 05 Aug 2013 09:53:44 +0000
Subject: [docs] [issue18661] Typo in grpmodule.c
In-Reply-To: <1375695788.15.0.911930238621.issue18661@psf.upfronthosting.co.za>
Message-ID: <1375696424.79.0.109270162138.issue18661@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

{0} is fine;  some compilers will warn about it, but I believe it's valid C.

----------
nosy: +mark.dickinson

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

From report at bugs.python.org  Mon Aug  5 18:58:15 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 05 Aug 2013 16:58:15 +0000
Subject: [docs] [issue18661] Typo in grpmodule.c
In-Reply-To: <1375695788.15.0.911930238621.issue18661@psf.upfronthosting.co.za>
Message-ID: <3c84tG4696z7Ln0@mail.python.org>


Roundup Robot added the comment:

New changeset 395ac61ebe1a by Mark Dickinson in branch '2.7':
Issue #18661: typo in grp.struct_group docstring.
http://hg.python.org/cpython/rev/395ac61ebe1a

New changeset 791034a0ae1e by Mark Dickinson in branch '3.3':
Issue #18661: typo in grp.struct_group docstring.  Thanks Vajrasky Kok.
http://hg.python.org/cpython/rev/791034a0ae1e

New changeset f534960c2c02 by Mark Dickinson in branch 'default':
Issue #18661: typo in grp.struct_group docstring (fix merged from 3.3).  Thanks Vajrasky Kok.
http://hg.python.org/cpython/rev/f534960c2c02

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

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

From report at bugs.python.org  Mon Aug  5 18:59:03 2013
From: report at bugs.python.org (Mark Dickinson)
Date: Mon, 05 Aug 2013 16:59:03 +0000
Subject: [docs] [issue18661] Typo in grpmodule.c
In-Reply-To: <1375695788.15.0.911930238621.issue18661@psf.upfronthosting.co.za>
Message-ID: <1375721943.7.0.0258047565807.issue18661@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

Fixed.  Thanks for the report!

----------
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
type:  -> behavior
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Mon Aug  5 19:53:10 2013
From: report at bugs.python.org (py.user)
Date: Mon, 05 Aug 2013 17:53:10 +0000
Subject: [docs] [issue18663] In unittest.TestCase.assertAlmostEqual doc
	specify the	delta description
Message-ID: <1375725190.79.0.442588525807.issue18663@psf.upfronthosting.co.za>


New submission from py.user:

http://docs.python.org/3/library/unittest.html#unittest.TestCase.assertAlmostEqual
"If delta is supplied instead of places then the difference between first and second must be less (or more) than delta."

----------
assignee: docs at python
components: Documentation
files: issue.diff
keywords: patch
messages: 194498
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: In unittest.TestCase.assertAlmostEqual doc specify the delta description
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file31167/issue.diff

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

From report at bugs.python.org  Tue Aug  6 06:53:20 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Tue, 06 Aug 2013 04:53:20 +0000
Subject: [docs] [issue18665] Typos in frame object related code
Message-ID: <1375764800.58.0.482122024787.issue18665@psf.upfronthosting.co.za>


New submission from Vajrasky Kok:

See the patch for details:

diff -r 438cdc97d8ee Include/frameobject.h
--- a/Include/frameobject.h	Mon Aug 05 23:35:43 2013 +0200
+++ b/Include/frameobject.h	Tue Aug 06 12:38:15 2013 +0800
@@ -36,7 +36,7 @@
            non-generator frames. See the save_exc_state and swap_exc_state
            functions in ceval.c for details of their use. */
     PyObject *f_exc_type, *f_exc_value, *f_exc_traceback;
-    /* Borrowed referenced to a generator, or NULL */
+    /* Borrowed reference to a generator, or NULL */
     PyObject *f_gen;
 
     PyThreadState *f_tstate;
diff -r 438cdc97d8ee Lib/test/test_frame.py
--- a/Lib/test/test_frame.py	Mon Aug 05 23:35:43 2013 +0200
+++ b/Lib/test/test_frame.py	Tue Aug 06 12:38:15 2013 +0800
@@ -93,7 +93,7 @@
 
     @support.cpython_only
     def test_clear_refcycles(self):
-        # .clear() doesn't leave any refcycle behin
+        # .clear() doesn't leave any refcycle behind.
         with support.disable_gc():
             class C:
                 pass


About the second comment, I am not sure to put dot or not. In that file, I saw some comments use dot, others don't.

----------
assignee: docs at python
components: Documentation
messages: 194523
nosy: docs at python, pitrou, vajrasky
priority: normal
severity: normal
status: open
title: Typos in frame object related code
versions: Python 3.4

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

From report at bugs.python.org  Tue Aug  6 07:13:02 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 06 Aug 2013 05:13:02 +0000
Subject: [docs] [issue18665] Typos in frame object related code
In-Reply-To: <1375764800.58.0.482122024787.issue18665@psf.upfronthosting.co.za>
Message-ID: <1375765982.05.0.823040455989.issue18665@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Can you attach the patch to the issue?
Full stops for one-sentence comments can be omitted.

----------
nosy: +ezio.melotti
stage:  -> needs patch
type:  -> enhancement
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Tue Aug  6 08:09:19 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Tue, 06 Aug 2013 06:09:19 +0000
Subject: [docs] [issue18665] Typos in frame object related code
In-Reply-To: <1375764800.58.0.482122024787.issue18665@psf.upfronthosting.co.za>
Message-ID: <1375769359.77.0.775522715572.issue18665@psf.upfronthosting.co.za>


Vajrasky Kok added the comment:

Okay, attached the patch to fix the typo.

----------
keywords: +patch
Added file: http://bugs.python.org/file31171/fix_typo_frame_object.patch

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

From ezio.melotti at gmail.com  Tue Aug  6 08:11:56 2013
From: ezio.melotti at gmail.com (ezio.melotti at gmail.com)
Date: Tue, 06 Aug 2013 06:11:56 -0000
Subject: [docs] Regex howto: revision pass (issue 18562)
Message-ID: <20130806061156.7052.78394@psf.upfronthosting.co.za>


http://bugs.python.org/review/18562/diff/8741/Doc/howto/regex.rst
File Doc/howto/regex.rst (right):

http://bugs.python.org/review/18562/diff/8741/Doc/howto/regex.rst#newcode514
Doc/howto/regex.rst:514: starttagopen = re.compile( ... )
It might be worth expanding a bit on this.
Compiling regex at module-level causes an overhead at import time that
might or might not matter.  The re module also has a cache, so even if
the regex are not compiled manually they get cached (unless the cache is
full and they are removed from there).
Deciding what to do is a judgment call, but mentioning these things
might help taking a decision.

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

From report at bugs.python.org  Tue Aug  6 08:12:13 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 06 Aug 2013 06:12:13 +0000
Subject: [docs] [issue18562] Regex howto: revision pass
In-Reply-To: <1374854855.56.0.787824851556.issue18562@psf.upfronthosting.co.za>
Message-ID: <1375769533.06.0.769733944408.issue18562@psf.upfronthosting.co.za>


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


----------
components: +Regular Expressions
nosy: +mrabarnett
type:  -> enhancement

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

From report at bugs.python.org  Tue Aug  6 13:51:34 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 06 Aug 2013 11:51:34 +0000
Subject: [docs] [issue18430] gzip, bz2,
	lzma: peek advances file position of existing file object
In-Reply-To: <1373571241.88.0.314815867736.issue18430@psf.upfronthosting.co.za>
Message-ID: <1375789894.07.0.0553755509787.issue18430@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Aug  6 14:11:33 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 06 Aug 2013 12:11:33 +0000
Subject: [docs] [issue18301] In itertools.chain.from_iterable() there is no
	cls	argument
In-Reply-To: <1372186723.21.0.67533324157.issue18301@psf.upfronthosting.co.za>
Message-ID: <1375791093.74.0.585284037721.issue18301@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

It should be a classmethod.

>>> import itertools
>>> class C(itertools.chain): pass
... 
>>> type(C.from_iterable(['ab', 'cd']))
<class '__main__.C'>

The patch LGTM.

----------
assignee: docs at python -> serhiy.storchaka
stage:  -> commit review

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

From report at bugs.python.org  Tue Aug  6 14:17:06 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 06 Aug 2013 12:17:06 +0000
Subject: [docs] [issue18301] In itertools.chain.from_iterable() there is no
	cls	argument
In-Reply-To: <1372186723.21.0.67533324157.issue18301@psf.upfronthosting.co.za>
Message-ID: <1375791426.61.0.84155150374.issue18301@psf.upfronthosting.co.za>


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


----------
assignee: serhiy.storchaka -> rhettinger

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

From report at bugs.python.org  Tue Aug  6 15:52:44 2013
From: report at bugs.python.org (Christian Heimes)
Date: Tue, 06 Aug 2013 13:52:44 +0000
Subject: [docs] [issue18532] hashlib.HASH objects should officially expose
	the hash	name
In-Reply-To: <1374524940.42.0.582552143445.issue18532@psf.upfronthosting.co.za>
Message-ID: <1375797164.08.0.200307992783.issue18532@psf.upfronthosting.co.za>


Christian Heimes added the comment:

I added some tests in 5fbf23e947d8 and found a bug in the _sha1 module, too.

----------
status: open -> closed

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

From report at bugs.python.org  Tue Aug  6 16:42:50 2013
From: report at bugs.python.org (productivememberofsociety666)
Date: Tue, 06 Aug 2013 14:42:50 +0000
Subject: [docs] [issue18669] curses.chgat() moves cursor,
	documentation says it shouldn't
Message-ID: <1375800170.73.0.20062232661.issue18669@psf.upfronthosting.co.za>


New submission from productivememberofsociety666:

According to docs.python.org/2/library/curses.html#chgat (or any other version), curses.chgat() is not supposed to move the cursor at all.

This is true if you don't give it x,y coordinates, but if you do, the cursor does in fact move to those coordinates, since it then uses C curses's mvchgat() internally and doesn't correct the position afterwards.

See included file for demonstration:

Expected output is:
one
two

Actual output is:
two

Fix the documentation or fix the code :-)

----------
assignee: docs at python
components: Documentation, Extension Modules
files: chgat-bug.py
messages: 194552
nosy: docs at python, productivememberofsociety666
priority: normal
severity: normal
status: open
title: curses.chgat() moves cursor, documentation says it shouldn't
type: behavior
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5
Added file: http://bugs.python.org/file31175/chgat-bug.py

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

From report at bugs.python.org  Tue Aug  6 18:25:45 2013
From: report at bugs.python.org (productivememberofsociety666)
Date: Tue, 06 Aug 2013 16:25:45 +0000
Subject: [docs] [issue18669] curses.chgat() moves cursor,
	documentation says it shouldn't
In-Reply-To: <1375800170.73.0.20062232661.issue18669@psf.upfronthosting.co.za>
Message-ID: <1375806345.46.0.201485664706.issue18669@psf.upfronthosting.co.za>


Changes by productivememberofsociety666 <productivememberofsociety666 at sol.fr.am>:


Removed file: http://bugs.python.org/file31175/chgat-bug.py

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

From report at bugs.python.org  Tue Aug  6 18:26:45 2013
From: report at bugs.python.org (productivememberofsociety666)
Date: Tue, 06 Aug 2013 16:26:45 +0000
Subject: [docs] [issue18669] curses.chgat() moves cursor,
	documentation says it shouldn't
In-Reply-To: <1375800170.73.0.20062232661.issue18669@psf.upfronthosting.co.za>
Message-ID: <1375806405.71.0.444811423436.issue18669@psf.upfronthosting.co.za>


Changes by productivememberofsociety666 <productivememberofsociety666 at sol.fr.am>:


Added file: http://bugs.python.org/file31178/chgat-bug.py

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

From report at bugs.python.org  Tue Aug  6 18:52:37 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 06 Aug 2013 16:52:37 +0000
Subject: [docs] [issue18443] Misc/Readme still documents TextMate
In-Reply-To: <1373775366.01.0.177392157148.issue18443@psf.upfronthosting.co.za>
Message-ID: <3c8hjJ1fjSz7Lm0@mail.python.org>


Roundup Robot added the comment:

New changeset 5c74755e8f04 by Ezio Melotti in branch 'default':
#18443: remove the TextMate entry now that the bundle has been removed and fix ordering.  Patch by F?vry Thibault.
http://hg.python.org/cpython/rev/5c74755e8f04

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

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

From report at bugs.python.org  Tue Aug  6 18:53:04 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 06 Aug 2013 16:53:04 +0000
Subject: [docs] [issue18443] Misc/Readme still documents TextMate
In-Reply-To: <1373775366.01.0.177392157148.issue18443@psf.upfronthosting.co.za>
Message-ID: <1375807984.44.0.67982372644.issue18443@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the report and the patch!

----------
assignee: docs at python -> ezio.melotti
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Tue Aug  6 23:07:08 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 06 Aug 2013 21:07:08 +0000
Subject: [docs] [issue18665] Typos in frame object related code
In-Reply-To: <1375764800.58.0.482122024787.issue18665@psf.upfronthosting.co.za>
Message-ID: <3c8pLz4dJjz7LkN@mail.python.org>


Roundup Robot added the comment:

New changeset 89ce323357db by Antoine Pitrou in branch 'default':
Issue #18665: fix typos.  Patch by Vajrasky Kok.
http://hg.python.org/cpython/rev/89ce323357db

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

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

From report at bugs.python.org  Tue Aug  6 23:07:33 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 06 Aug 2013 21:07:33 +0000
Subject: [docs] [issue18665] Typos in frame object related code
In-Reply-To: <1375764800.58.0.482122024787.issue18665@psf.upfronthosting.co.za>
Message-ID: <1375823253.21.0.0137643855807.issue18665@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Thank you :)

----------
resolution:  -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
versions:  -Python 2.7, Python 3.3

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

From report at bugs.python.org  Wed Aug  7 11:23:16 2013
From: report at bugs.python.org (Thomas Guettler)
Date: Wed, 07 Aug 2013 09:23:16 +0000
Subject: [docs] [issue18675] Daemon Threads can seg fault
Message-ID: <1375867396.76.0.697227657582.issue18675@psf.upfronthosting.co.za>


New submission from Thomas Guettler:

This is a documentation bug: Since #1856  is not solved for Python2, it needs to be documented.

Daemon Threads on Python2 can seg fault.

Work arounds: http://stackoverflow.com/questions/18098475/detect-interpreter-shut-down-in-daemon-thread

----------
assignee: docs at python
components: Documentation
messages: 194601
nosy: docs at python, guettli
priority: normal
severity: normal
status: open
title: Daemon Threads can seg fault
versions: Python 2.6, Python 2.7

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

From report at bugs.python.org  Wed Aug  7 16:11:40 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 07 Aug 2013 14:11:40 +0000
Subject: [docs] [issue18676] Queue: document that zero is accepted as
	timeout value
In-Reply-To: <1375883528.55.0.275850242187.issue18676@psf.upfronthosting.co.za>
Message-ID: <1375884700.35.0.298090985729.issue18676@psf.upfronthosting.co.za>


R. David Murray added the comment:

This is more of a documentation issue than a code issue.  To be mathematically precise, the text and error message should read "a non-negative value".  Alternatively the text and error could be changed to report that timeout may not be negative, which would probably be clearer.  (Note that timeout is a float value, and thus the proposed code change would only break code, it would not change the functionality in any significant way.)

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, r.david.murray
title: Queue: zero should not be accepted as timeout value -> Queue: document that zero is accepted as timeout value
versions: +Python 3.3, Python 3.4

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

From report at bugs.python.org  Wed Aug  7 23:47:28 2013
From: report at bugs.python.org (Zhongyue Luo)
Date: Wed, 07 Aug 2013 21:47:28 +0000
Subject: [docs] [issue18676] Queue: document that zero is accepted as
	timeout value
In-Reply-To: <1375883528.55.0.275850242187.issue18676@psf.upfronthosting.co.za>
Message-ID: <1375912048.13.0.872004246723.issue18676@psf.upfronthosting.co.za>


Zhongyue Luo added the comment:

David,

How about like below?

  elif timeout < sys.float_info.epsilon:
     raise ValueError("'timeout' must be a positive number")

The docstring has been there for quite a while and IMHO it just doesn't make sense passing 0.0 as a timeout value.

----------

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

From report at bugs.python.org  Thu Aug  8 00:06:31 2013
From: report at bugs.python.org (Corey Farwell)
Date: Wed, 07 Aug 2013 22:06:31 +0000
Subject: [docs] [issue18680] JSONDecoder should document that it raises a
	ValueError	for malformed data
Message-ID: <1375913191.45.0.0174536581066.issue18680@psf.upfronthosting.co.za>


New submission from Corey Farwell:

Before someone comes in and tries to correct me, I know Python documentation is different than Javadocs. It is common to test if the JSON is malformed using a try...catch. What if I want to catch something more specific than Exception? The only way a user would know what to catch is to `python -c "import json; json.loads('FAIL')"`. Many other Python modules document which exception is raised on invalid input/parameters.

----------
assignee: docs at python
components: Documentation
messages: 194628
nosy: corey, docs at python
priority: normal
severity: normal
status: open
title: JSONDecoder should document that it raises a ValueError for malformed data
type: enhancement
versions: Python 2.6, 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/issue18680>
_______________________________________

From report at bugs.python.org  Thu Aug  8 00:13:09 2013
From: report at bugs.python.org (Corey Farwell)
Date: Wed, 07 Aug 2013 22:13:09 +0000
Subject: [docs] [issue18680] JSONDecoder should document that it raises a
	ValueError	for malformed data
In-Reply-To: <1375913191.45.0.0174536581066.issue18680@psf.upfronthosting.co.za>
Message-ID: <1375913589.04.0.736260704416.issue18680@psf.upfronthosting.co.za>


Corey Farwell added the comment:

Ideally, this would also be decoumented in json.loads/json.load

----------

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

From report at bugs.python.org  Thu Aug  8 00:13:41 2013
From: report at bugs.python.org (Richard Oudkerk)
Date: Wed, 07 Aug 2013 22:13:41 +0000
Subject: [docs] [issue18676] Queue: document that zero is accepted as
	timeout value
In-Reply-To: <1375883528.55.0.275850242187.issue18676@psf.upfronthosting.co.za>
Message-ID: <1375913621.79.0.342753932092.issue18676@psf.upfronthosting.co.za>


Richard Oudkerk added the comment:

> IMHO it just doesn't make sense passing 0.0 as a timeout value.

I have written lots of code that looks like

    timeout = max(deadline - time.time(), 0)
    some_function(..., timeout=timeout)

This makes perfect sense.  Working code should not be broken -- it is the docsting that should be changed.

I can't think of *any* function taking a timeout which rejects a zero timeout.  See select(), poll(), Condition.wait(), Lock.acquire(), Thread.join().  In each case a zero timeout causes a non-blocking call.

Also, note that the implementation does not contradict the docstring or documentation: they say nothing about what happens it timeout is zero (or negative).

----------
nosy: +sbt

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

From report at bugs.python.org  Thu Aug  8 00:15:33 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 07 Aug 2013 22:15:33 +0000
Subject: [docs] [issue18676] Queue: document that zero is accepted as
	timeout value
In-Reply-To: <1375883528.55.0.275850242187.issue18676@psf.upfronthosting.co.za>
Message-ID: <1375913733.6.0.703561629116.issue18676@psf.upfronthosting.co.za>


R. David Murray added the comment:

Exactly.  0 means "Don't wait, just raise an error immediately if the queue is empty/full".

----------

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

From report at bugs.python.org  Thu Aug  8 03:22:25 2013
From: report at bugs.python.org (Zhongyue Luo)
Date: Thu, 08 Aug 2013 01:22:25 +0000
Subject: [docs] [issue18676] Queue: document that zero is accepted as
	timeout value
In-Reply-To: <1375883528.55.0.275850242187.issue18676@psf.upfronthosting.co.za>
Message-ID: <1375924945.37.0.186707670194.issue18676@psf.upfronthosting.co.za>


Changes by Zhongyue Luo <zhongyue.luo at gmail.com>:


----------
keywords: +patch
Added file: http://bugs.python.org/file31187/queue_timeout_docstring.patch

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

From report at bugs.python.org  Thu Aug  8 03:45:01 2013
From: report at bugs.python.org (Zhongyue Luo)
Date: Thu, 08 Aug 2013 01:45:01 +0000
Subject: [docs] [issue18676] Queue: document that zero is accepted as
	timeout value
In-Reply-To: <1375883528.55.0.275850242187.issue18676@psf.upfronthosting.co.za>
Message-ID: <1375926301.2.0.288631820881.issue18676@psf.upfronthosting.co.za>


Changes by Zhongyue Luo <zhongyue.luo at gmail.com>:


Added file: http://bugs.python.org/file31188/queue_timeout_docstring.patch

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

From report at bugs.python.org  Thu Aug  8 03:48:21 2013
From: report at bugs.python.org (Zhongyue Luo)
Date: Thu, 08 Aug 2013 01:48:21 +0000
Subject: [docs] [issue18676] Queue: document that zero is accepted as
	timeout value
In-Reply-To: <1375883528.55.0.275850242187.issue18676@psf.upfronthosting.co.za>
Message-ID: <1375926501.2.0.741009240682.issue18676@psf.upfronthosting.co.za>


Changes by Zhongyue Luo <zhongyue.luo at gmail.com>:


Added file: http://bugs.python.org/file31189/queue_timeout_docstring.patch

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

From report at bugs.python.org  Thu Aug  8 14:46:27 2013
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 08 Aug 2013 12:46:27 +0000
Subject: [docs] [issue18267] xmlrpc.client documentation multicall
	example	missleading for division behaviour of python3
In-Reply-To: <1371675805.26.0.18697522409.issue18267@psf.upfronthosting.co.za>
Message-ID: <3c9q8L2yJyz7Ljh@mail.python.org>


Roundup Robot added the comment:

New changeset 38d341ef28b3 by Ezio Melotti in branch '3.3':
#18267: make whitespace consistent and fix an operator.
http://hg.python.org/cpython/rev/38d341ef28b3

New changeset 9875410ed390 by Ezio Melotti in branch 'default':
#18267: merge with 3.3.
http://hg.python.org/cpython/rev/9875410ed390

----------

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

From report at bugs.python.org  Thu Aug  8 14:47:03 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 08 Aug 2013 12:47:03 +0000
Subject: [docs] [issue18267] xmlrpc.client documentation multicall
	example	missleading for division behaviour of python3
In-Reply-To: <1371675805.26.0.18697522409.issue18267@psf.upfronthosting.co.za>
Message-ID: <1375966023.18.0.890951179179.issue18267@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the report!

----------
assignee: docs at python -> ezio.melotti
nosy: +ezio.melotti
resolution:  -> fixed
status: open -> closed
type:  -> enhancement
versions:  -Python 3.1, Python 3.2

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

From report at bugs.python.org  Thu Aug  8 14:56:24 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 08 Aug 2013 12:56:24 +0000
Subject: [docs] [issue18301] In itertools.chain.from_iterable() there is no
	cls	argument
In-Reply-To: <1372186723.21.0.67533324157.issue18301@psf.upfronthosting.co.za>
Message-ID: <1375966584.76.0.441778186849.issue18301@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

> I would just remove the decorator.

+1

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

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

From report at bugs.python.org  Thu Aug  8 15:10:24 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 08 Aug 2013 13:10:24 +0000
Subject: [docs] [issue18313] In itertools recipes repeatfunc() defines a
	non-keyword	argument as keyword
In-Reply-To: <1372309261.95.0.7034101172.issue18313@psf.upfronthosting.co.za>
Message-ID: <1375967424.09.0.324102241428.issue18313@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

> it should be: "def repeatfunc(func, times, *args):"
> and None for times described in the docstring

This would require you to provide at least two elements, whereas now it's possible to pass just the function (e.g. repeatfunc(random.random)).

The problem with the current signature is that you are "forced" to specify the "times" (positionally) whenever you want to pass args to the function -- even if you want an endless repetition (i.e. times=None).

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

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

From report at bugs.python.org  Thu Aug  8 15:34:14 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 08 Aug 2013 13:34:14 +0000
Subject: [docs] [issue18572] Remove redundant note about surrogates in
	string escape	doc
In-Reply-To: <1374941533.84.0.352957238503.issue18572@psf.upfronthosting.co.za>
Message-ID: <1375968854.04.0.285720951993.issue18572@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I think it's OK to remove the sentence.

Converting a surrogate pair to a non-BMP char is something that works only while decoding a UTF-16 byte sequence.  Surrogates are invalid in UTF-8/32, and while dealing with Unicode strings, surrogates have no special meaning and are no different from any other codepoint, whether they are lone or paired.

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

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

From report at bugs.python.org  Thu Aug  8 15:37:21 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 08 Aug 2013 13:37:21 +0000
Subject: [docs] [issue18576] Rename and document test.script_helper
	as	test.support.script_helper
In-Reply-To: <1375014764.64.0.152576599022.issue18576@psf.upfronthosting.co.za>
Message-ID: <1375969041.61.0.740008204778.issue18576@psf.upfronthosting.co.za>


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


----------
keywords: +easy
nosy: +ezio.melotti
stage:  -> needs patch

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

From report at bugs.python.org  Thu Aug  8 15:52:51 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 08 Aug 2013 13:52:51 +0000
Subject: [docs] [issue18588] timeit examples should be consistent
In-Reply-To: <1375118438.6.0.867422483387.issue18588@psf.upfronthosting.co.za>
Message-ID: <1375969971.49.0.488270764041.issue18588@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

IIRC those were the actual values I got.  I think I investigated why they were different, but right now I don't remember if I found out why.

----------
assignee: docs at python -> ezio.melotti
nosy: +ezio.melotti
versions:  -Python 2.6, Python 3.1, Python 3.2, Python 3.3

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

From report at bugs.python.org  Thu Aug  8 16:47:49 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 08 Aug 2013 14:47:49 +0000
Subject: [docs] [issue18588] timeit examples should be consistent
In-Reply-To: <1375118438.6.0.867422483387.issue18588@psf.upfronthosting.co.za>
Message-ID: <1375973269.39.0.666247779095.issue18588@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

In command-line invocation the gc is disabled. And timit.repeat() is used instead of timit.timit().

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

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

From report at bugs.python.org  Thu Aug  8 17:41:39 2013
From: report at bugs.python.org (Clay McClure)
Date: Thu, 08 Aug 2013 15:41:39 +0000
Subject: [docs] [issue18588] timeit examples should be consistent
In-Reply-To: <1375118438.6.0.867422483387.issue18588@psf.upfronthosting.co.za>
Message-ID: <1375976499.16.0.522822007683.issue18588@psf.upfronthosting.co.za>


Clay McClure added the comment:

There's a 68% difference in running time between the command-line and programmatic invocations shown in the current documentation, and a 1% difference between the runtimes shown in the patch. I can't speak for why that is the case, but I did find it somewhat confusing when trying to interpret the timeit documentation.

Being a somewhat pedantic and trivial patch, I'm fine if you want to close it wontfix.

----------

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

From report at bugs.python.org  Thu Aug  8 18:45:37 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 08 Aug 2013 16:45:37 +0000
Subject: [docs] [issue18628] Better index entry for encoding declarations
In-Reply-To: <1375418984.87.0.318628832877.issue18628@psf.upfronthosting.co.za>
Message-ID: <1375980337.59.0.201844746105.issue18628@psf.upfronthosting.co.za>


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


----------
keywords: +easy
nosy: +ezio.melotti
type:  -> enhancement

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

From report at bugs.python.org  Thu Aug  8 18:56:48 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 08 Aug 2013 16:56:48 +0000
Subject: [docs] [issue18326] Mention 'keyword only' for list.sort,
	improve  glossary.
In-Reply-To: <1372511136.61.0.278425078947.issue18326@psf.upfronthosting.co.za>
Message-ID: <1375981008.21.0.544011152713.issue18326@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

"keyword-only" is a well-established term, and I think it's better to use it and possibly make it a link to the "parameter" entry of the glossary.

----------
nosy: +ezio.melotti
stage: needs patch -> patch review

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

From report at bugs.python.org  Thu Aug  8 19:19:55 2013
From: report at bugs.python.org (py.user)
Date: Thu, 08 Aug 2013 17:19:55 +0000
Subject: [docs] [issue18313] In itertools recipes repeatfunc() defines a
	non-keyword	argument as keyword
In-Reply-To: <1372309261.95.0.7034101172.issue18313@psf.upfronthosting.co.za>
Message-ID: <1375982395.16.0.456474414957.issue18313@psf.upfronthosting.co.za>


py.user added the comment:

> This would require you to provide at least two elements
I see
how about "def repeatfunc(func, *args, times=None):" ?


>>> from itertools import starmap, repeat
>>> 
>>> def repeatfunc(func, *args, times=None):
...     """Repeat calls to func with specified arguments.
... 
...     Example:  repeatfunc(random.random)
...     """
...     if times is None:
...         return starmap(func, repeat(args))
...     return starmap(func, repeat(args, times))
... 
>>> def f(*args):
...     print(args)
... 
>>> r = repeatfunc(f, 1, 2)
>>> next(r)
(1, 2)
>>> next(r)
(1, 2)
>>> next(r)
(1, 2)
>>> r = repeatfunc(f, 1, 2, times=1)
>>> next(r)
(1, 2)
>>> next(r)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
StopIteration
>>>

----------

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

From report at bugs.python.org  Thu Aug  8 19:25:25 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 08 Aug 2013 17:25:25 +0000
Subject: [docs] [issue18423] Document limitations on -m
In-Reply-To: <1373461112.24.0.280779659137.issue18423@psf.upfronthosting.co.za>
Message-ID: <1375982725.83.0.690316459146.issue18423@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti
type:  -> enhancement
versions: +Python 3.4

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

From report at bugs.python.org  Thu Aug  8 19:44:31 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 08 Aug 2013 17:44:31 +0000
Subject: [docs] [issue18445] Tools/Script/Readme is outdated
In-Reply-To: <1373782620.19.0.347266346086.issue18445@psf.upfronthosting.co.za>
Message-ID: <1375983871.28.0.397362887222.issue18445@psf.upfronthosting.co.za>


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


----------
keywords: +easy
nosy: +ezio.melotti

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

From report at bugs.python.org  Thu Aug  8 19:45:26 2013
From: report at bugs.python.org (py.user)
Date: Thu, 08 Aug 2013 17:45:26 +0000
Subject: [docs] [issue18301] In itertools.chain.from_iterable() there is no
	cls	argument
In-Reply-To: <1372186723.21.0.67533324157.issue18301@psf.upfronthosting.co.za>
Message-ID: <1375983926.78.0.0867551089755.issue18301@psf.upfronthosting.co.za>


py.user added the comment:

>>> import itertools
>>> 
>>> class A(itertools.chain):
...     def from_iter(arg):
...         return A(iter(arg))
... 
>>> class B(A):
...     pass
... 
>>> B('a', 'b')
<__main__.B object at 0x7f40116d7730>
>>> B.from_iter(['a', 'b'])
<__main__.A object at 0x7f40116d7780>
>>>

it should be B

----------

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

From report at bugs.python.org  Thu Aug  8 19:47:56 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 08 Aug 2013 17:47:56 +0000
Subject: [docs] [issue18680] JSONDecoder should document that it raises a
	ValueError	for malformed data
In-Reply-To: <1375913191.45.0.0174536581066.issue18680@psf.upfronthosting.co.za>
Message-ID: <1375984076.8.0.624686852528.issue18680@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


----------
keywords: +easy
stage:  -> needs patch
versions:  -Python 2.6, Python 3.1, Python 3.2, Python 3.5

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

From report at bugs.python.org  Thu Aug  8 19:49:02 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 08 Aug 2013 17:49:02 +0000
Subject: [docs] [issue18456] Documentation for PyDict_Update is incorrect
In-Reply-To: <1373854272.6.0.0142348360978.issue18456@psf.upfronthosting.co.za>
Message-ID: <1375984142.99.0.761125233814.issue18456@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Aug  8 20:05:16 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Thu, 08 Aug 2013 18:05:16 +0000
Subject: [docs] [issue18687] Lib/test/leakers/test_ctypes.py still mentions
	the need	to update Misc/build.sh
Message-ID: <1375985116.56.0.149122259336.issue18687@psf.upfronthosting.co.za>


New submission from F?vry Thibault:

"# When this leak is fixed, remember to remove from Misc/build.sh LEAKY_TESTS." -> Misc/build.sh got removed 19 months ago, this should be updated.

----------
assignee: docs at python
components: Documentation
files: patch.diff
keywords: patch
messages: 194703
nosy: docs at python, iwontbecreative
priority: normal
severity: normal
status: open
title: Lib/test/leakers/test_ctypes.py still mentions the need to update Misc/build.sh
versions: Python 3.4
Added file: http://bugs.python.org/file31200/patch.diff

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

From report at bugs.python.org  Thu Aug  8 21:12:46 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 08 Aug 2013 19:12:46 +0000
Subject: [docs] [issue18688] Document undocumented Unicode object API
Message-ID: <1375989166.23.0.200448183394.issue18688@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Include/unicodeobject.h contains followed names which are declared as public but are not documented in Doc/c-api/unicode.rst.

PyUnicodeIter_Type
Py_UNICODE_REPLACEMENT_CHARACTER
PyUnicode_Resize
PyUnicode_InternImmortal
PyUnicode_CHECK_INTERNED
PyUnicode_FromOrdinal
PyUnicode_GetDefaultEncoding
PyUnicode_AsDecodedObject
PyUnicode_AsDecodedUnicode
PyUnicode_AsEncodedObject
PyUnicode_AsEncodedUnicode
PyUnicode_BuildEncodingMap
PyUnicode_DecodeCodePageStateful
PyUnicode_Append
PyUnicode_AppendAndDel
PyUnicode_Partition
PyUnicode_RPartition
PyUnicode_RSplit
PyUnicode_IsIdentifier
_PyUnicode_FromId
_PyUnicode_ClearStaticStrings

They should be either documented or declared as private.

PyUnicode_AsEncodedObject only mentioned in Doc/whatsnew/3.3.rst as recomended replacement of PyUnicode_Encode.

----------
assignee: docs at python
components: Documentation, Unicode
messages: 194705
nosy: docs at python, ezio.melotti, serhiy.storchaka
priority: normal
severity: normal
stage: needs patch
status: open
title: Document undocumented Unicode object API
type: behavior
versions: Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Aug  9 03:13:57 2013
From: report at bugs.python.org (py.user)
Date: Fri, 09 Aug 2013 01:13:57 +0000
Subject: [docs] [issue18301] In itertools.chain.from_iterable() there is no
	cls	argument
In-Reply-To: <1372186723.21.0.67533324157.issue18301@psf.upfronthosting.co.za>
Message-ID: <1376010837.17.0.322946398209.issue18301@psf.upfronthosting.co.za>


py.user added the comment:

changed iter(arg) to *arg


>>> import itertools
>>> 
>>> class A(itertools.chain):
...     @classmethod
...     def from_iter(cls, arg):
...         return cls(*arg)
... 
>>> class B(A):
...     pass
... 
>>> B('ab', 'cd')
<__main__.B object at 0x7fc280e93cd0>
>>> b = B.from_iter(['ab', 'cd'])
>>> b
<__main__.B object at 0x7fc280e93d20>
>>> next(b)
'a'
>>> next(b)
'b'
>>> next(b)
'c'
>>> next(b)
'd'
>>> next(b)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
StopIteration
>>>

----------

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

From report at bugs.python.org  Fri Aug  9 12:15:21 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 09 Aug 2013 10:15:21 +0000
Subject: [docs] [issue18688] Document undocumented Unicode object API
In-Reply-To: <1375989166.23.0.200448183394.issue18688@psf.upfronthosting.co.za>
Message-ID: <1376043321.91.0.886748065995.issue18688@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


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

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

From report at bugs.python.org  Fri Aug  9 17:58:07 2013
From: report at bugs.python.org (py.user)
Date: Fri, 09 Aug 2013 15:58:07 +0000
Subject: [docs] [issue18696] In unittest.TestCase.longMessage doc remove a
	redundant	sentence
Message-ID: <1376063887.45.0.331340035557.issue18696@psf.upfronthosting.co.za>


New submission from py.user:

http://docs.python.org/3/library/unittest.html#unittest.TestCase.longMessage
"If set to True then any explicit failure message you pass in to the assert methods will be appended to the end of the normal failure message. The normal messages contain useful information about the objects involved, for example the message from assertEqual shows you the repr of the two unequal objects. Setting this attribute to True allows you to have a custom error message in addition to the normal one."

the last sentence duplicates the first one

----------
assignee: docs at python
components: Documentation
files: issue.diff
keywords: patch
messages: 194748
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: In unittest.TestCase.longMessage doc remove a redundant sentence
type: enhancement
versions: Python 3.3, Python 3.4
Added file: http://bugs.python.org/file31208/issue.diff

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

From report at bugs.python.org  Fri Aug  9 18:05:48 2013
From: report at bugs.python.org (R. David Murray)
Date: Fri, 09 Aug 2013 16:05:48 +0000
Subject: [docs] [issue18696] In unittest.TestCase.longMessage doc remove a
	redundant	sentence
In-Reply-To: <1376063887.45.0.331340035557.issue18696@psf.upfronthosting.co.za>
Message-ID: <1376064348.73.0.0952617680905.issue18696@psf.upfronthosting.co.za>


R. David Murray added the comment:

I think the text is OK as it stands.  The first sentence is a technical description of the result of setting the attribute, the last sentence is a conceptual discussion of why you would want to set the attribute.

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

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

From report at bugs.python.org  Fri Aug  9 20:48:46 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 09 Aug 2013 18:48:46 +0000
Subject: [docs] [issue18697] Unify arguments names in Unicode object C
	API	documentation
Message-ID: <1376074126.58.0.40251146149.issue18697@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

In declarations of Unicode object C API functions in Doc/c-api/unicode.rst the first Unicode object argument has different names: "unicode", "str", "u", "s". It will be good to unify these names.

Of course there is no need to change reasonable argument names for such functions as PyUnicode_Concat() or PyUnicode_CopyCharacters().

----------
assignee: docs at python
components: Documentation, Unicode
keywords: easy
messages: 194755
nosy: docs at python, ezio.melotti, haypo, serhiy.storchaka
priority: normal
severity: normal
stage: needs patch
status: open
title: Unify arguments names in Unicode object C API documentation
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Aug  9 20:50:42 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 09 Aug 2013 18:50:42 +0000
Subject: [docs] [issue18688] Document undocumented Unicode object API
In-Reply-To: <1375989166.23.0.200448183394.issue18688@psf.upfronthosting.co.za>
Message-ID: <1376074242.18.0.238073690862.issue18688@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

It will be good first resolve issue18697.

----------

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

From report at bugs.python.org  Fri Aug  9 21:52:21 2013
From: report at bugs.python.org (R. David Murray)
Date: Fri, 09 Aug 2013 19:52:21 +0000
Subject: [docs] [issue18600] email.policy doc example passes 'policy' to
	as_string, but that doesn't work
In-Reply-To: <1375197560.98.0.336881142306.issue18600@psf.upfronthosting.co.za>
Message-ID: <1376077941.88.0.83427598485.issue18600@psf.upfronthosting.co.za>


R. David Murray added the comment:

Turns out even with as_string accepting a policy keyword, the example still failed.  It needs to be generating a bytes object, not a string.  Before I even realized that, though, I decided I wanted to add as_bytes (and __bytes__).  So the attached patch does that: adds policy to as_string, and adds new methods as_bytes and __bytes__ to Message.

This patch is only for 3.4.  The 3.3 patch will just delete that part of the policy example, so I'm not going to bother to upload it.

----------
keywords: +patch
stage: needs patch -> patch review
Added file: http://bugs.python.org/file31209/as_string_policy.patch

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

From report at bugs.python.org  Fri Aug  9 22:17:31 2013
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 09 Aug 2013 20:17:31 +0000
Subject: [docs] [issue18675] Daemon Threads can seg fault
In-Reply-To: <1375867396.76.0.697227657582.issue18675@psf.upfronthosting.co.za>
Message-ID: <1376079451.23.0.272290587913.issue18675@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Aug  9 22:20:27 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 09 Aug 2013 20:20:27 +0000
Subject: [docs] [issue18600] email.policy doc example passes 'policy' to
	as_string, but that doesn't work
In-Reply-To: <1375197560.98.0.336881142306.issue18600@psf.upfronthosting.co.za>
Message-ID: <3cBd9k57r0z7M26@mail.python.org>


Roundup Robot added the comment:

New changeset 53287858e71f by R David Murray in branch 'default':
#18600: add policy to add_string, and as_bytes and __bytes__ methods.
http://hg.python.org/cpython/rev/53287858e71f

New changeset 8fbaf4e649af by R David Murray in branch '3.3':
#18600: In 3.3, as_string does not accept a policy keyword.
http://hg.python.org/cpython/rev/8fbaf4e649af

New changeset b9a5b7e3b32f by R David Murray in branch 'default':
Null merge related to #18600.
http://hg.python.org/cpython/rev/b9a5b7e3b32f

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

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

From report at bugs.python.org  Fri Aug  9 22:22:20 2013
From: report at bugs.python.org (R. David Murray)
Date: Fri, 09 Aug 2013 20:22:20 +0000
Subject: [docs] [issue18600] email.policy doc example passes 'policy' to
	as_string, but that doesn't work
In-Reply-To: <1375197560.98.0.336881142306.issue18600@psf.upfronthosting.co.za>
Message-ID: <1376079740.88.0.688916809772.issue18600@psf.upfronthosting.co.za>


R. David Murray added the comment:

Committed with changes pointed out by Antoine (thank you Antoine).

----------
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Sat Aug 10 17:49:25 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 10 Aug 2013 15:49:25 +0000
Subject: [docs] [issue18516] Typos in Lib/email/generator.py
	and	Lib/email/architecture.rst
In-Reply-To: <1374375453.94.0.44126763837.issue18516@psf.upfronthosting.co.za>
Message-ID: <1376149765.86.0.856781905886.issue18516@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed in 168f6ac90abf (3.3) and 40ef5ce25d08 (default).
Thanks for the report!

----------
assignee: docs at python -> ezio.melotti
nosy: +ezio.melotti
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
type:  -> enhancement
versions: +Python 3.3

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

From report at bugs.python.org  Sat Aug 10 17:51:47 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 10 Aug 2013 15:51:47 +0000
Subject: [docs] [issue18512] sys.stdout.write does not allow bytes in Python
	3.x
In-Reply-To: <1374287481.36.0.643885131326.issue18512@psf.upfronthosting.co.za>
Message-ID: <1376149907.38.0.210654617958.issue18512@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

> You can do
>    sys.stdout.buffer.write(b"hello")

Note that this might not work when sys.stdout has been replaced with something else (e.g. a StringIO).

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

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

From report at bugs.python.org  Sat Aug 10 18:01:48 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 10 Aug 2013 16:01:48 +0000
Subject: [docs] [issue18696] In unittest.TestCase.longMessage doc remove a
	redundant	sentence
In-Reply-To: <1376063887.45.0.331340035557.issue18696@psf.upfronthosting.co.za>
Message-ID: <1376150508.3.0.277946149758.issue18696@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Agreed, closing.

----------
nosy: +ezio.melotti
resolution:  -> invalid
stage:  -> committed/rejected
status: open -> closed

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

From ezio.melotti at gmail.com  Sat Aug 10 19:31:15 2013
From: ezio.melotti at gmail.com (ezio.melotti at gmail.com)
Date: Sat, 10 Aug 2013 17:31:15 -0000
Subject: [docs] Improve tutorial entry on 'Lambda Forms'. (issue 18646)
Message-ID: <20130810173115.32279.15168@psf.upfronthosting.co.za>


http://bugs.python.org/review/18646/diff/8811/Doc/tutorial/controlflow.rst
File Doc/tutorial/controlflow.rst (right):

http://bugs.python.org/review/18646/diff/8811/Doc/tutorial/controlflow.rst#newcode586
Doc/tutorial/controlflow.rst:586: Lambda Forms
"forms" could be changed here as well.

http://bugs.python.org/review/18646/diff/8811/Doc/tutorial/controlflow.rst#newcode589
Doc/tutorial/controlflow.rst:589: Small anonymous functions can be
created with the :keyword:`lambda` keyword.
I prefer "simple", rather than "small".

http://bugs.python.org/review/18646/diff/8811/Doc/tutorial/controlflow.rst#newcode590
Doc/tutorial/controlflow.rst:590: This function returns the sum of its
two arguments: ``lambda a, b: a+b``.
"For example, this function..."?

http://bugs.python.org/review/18646/diff/8811/Doc/tutorial/controlflow.rst#newcode591
Doc/tutorial/controlflow.rst:591: Lambda forms can be used wherever
function objects are required.  They are
I would get rid of "forms" here too.

http://bugs.python.org/review/18646/diff/8811/Doc/tutorial/controlflow.rst#newcode592
Doc/tutorial/controlflow.rst:592: syntactically restricted to a single
expression.  Semantically, they are just
Do we have an explanation of what an "expression" is somewhere?

http://bugs.python.org/review/18646/diff/8811/Doc/tutorial/controlflow.rst#newcode594
Doc/tutorial/controlflow.rst:594: name attribute will always be
'<lambda>'. Like nested function
Is this the only difference?  Maybe you could say:
"... a normal function definition, except that their name attribute will
always be '<lambda>'."
(Also there's a missing space after the period.)

http://bugs.python.org/review/18646/diff/8811/Doc/tutorial/controlflow.rst#newcode612
Doc/tutorial/controlflow.rst:612: [(4, 'four'), (1, 'one'), (3,
'three'), (2, 'two')]
I think this example would make more sense if the elements of the tuples
were swapped.  A normal sort would sort them alphabetically, but with
the lambda you can sort the tuples correctly.
I would also put this example before the make_incrementor one, since
this usage is more common.

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

From report at bugs.python.org  Sat Aug 10 19:31:25 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 10 Aug 2013 17:31:25 +0000
Subject: [docs] [issue18646] Improve tutorial entry on 'Lambda Forms'.
In-Reply-To: <1375562526.59.0.207872880438.issue18646@psf.upfronthosting.co.za>
Message-ID: <1376155885.51.0.773108070857.issue18646@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti
type: behavior -> enhancement

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

From report at bugs.python.org  Sat Aug 10 20:01:16 2013
From: report at bugs.python.org (madan ram)
Date: Sat, 10 Aug 2013 18:01:16 +0000
Subject: [docs] [issue18703] To change the doc of html/faq/gui.html
Message-ID: <1376157675.52.0.120458668025.issue18703@psf.upfronthosting.co.za>


New submission from madan ram:

"Qt 4.5 upwards is licensed under the LGPL license; also, commercial licenses are available from Nokia."

Since new version of Qt 5 is realsed and Licenced under Digia.

So i am fixing this issue .

i am going to write it as 

PyQt5 is licensed on all platforms under a commercial license and the GPL v3. Your PyQt5 license must be compatible with your Qt license.
If you use the GPL version then your own code must also use a compatible license.

Note:-PyQt5, unlike Qt, is not available under the LGPL.

You can purchase a commercial PyQt5 license here.

----------
assignee: docs at python
components: Documentation
files: gui.rst
messages: 194824
nosy: docs at python, madan.ram
priority: normal
severity: normal
status: open
title: To change the doc of html/faq/gui.html
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5
Added file: http://bugs.python.org/file31218/gui.rst

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

From report at bugs.python.org  Sat Aug 10 20:01:27 2013
From: report at bugs.python.org (madan ram)
Date: Sat, 10 Aug 2013 18:01:27 +0000
Subject: [docs] [issue18703] To change the doc of html/faq/gui.html
In-Reply-To: <1376157675.52.0.120458668025.issue18703@psf.upfronthosting.co.za>
Message-ID: <1376157687.45.0.81678312555.issue18703@psf.upfronthosting.co.za>


Changes by madan ram <madan_ram at rocketmail.com>:


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

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

From report at bugs.python.org  Sat Aug 10 20:29:13 2013
From: report at bugs.python.org (madan ram)
Date: Sat, 10 Aug 2013 18:29:13 +0000
Subject: [docs] [issue18703] To change the doc of html/faq/gui.html
In-Reply-To: <1376157675.52.0.120458668025.issue18703@psf.upfronthosting.co.za>
Message-ID: <1376159353.66.0.38450277163.issue18703@psf.upfronthosting.co.za>


Changes by madan ram <madan_ram at rocketmail.com>:


Removed file: http://bugs.python.org/file31218/gui.rst

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

From report at bugs.python.org  Sat Aug 10 20:29:30 2013
From: report at bugs.python.org (madan ram)
Date: Sat, 10 Aug 2013 18:29:30 +0000
Subject: [docs] [issue18703] To change the doc of html/faq/gui.html
In-Reply-To: <1376157675.52.0.120458668025.issue18703@psf.upfronthosting.co.za>
Message-ID: <1376159370.41.0.167886768405.issue18703@psf.upfronthosting.co.za>


Changes by madan ram <madan_ram at rocketmail.com>:


----------
keywords: +patch
Added file: http://bugs.python.org/file31219/mywork.patch

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

From report at bugs.python.org  Sat Aug 10 20:34:09 2013
From: report at bugs.python.org (madan ram)
Date: Sat, 10 Aug 2013 18:34:09 +0000
Subject: [docs] [issue18703] To change the doc of html/faq/gui.html
In-Reply-To: <1376157675.52.0.120458668025.issue18703@psf.upfronthosting.co.za>
Message-ID: <1376159649.09.0.221937184336.issue18703@psf.upfronthosting.co.za>


Changes by madan ram <madan_ram at rocketmail.com>:


----------
nosy: +aleax, eric.araujo, ezio.melotti, georg.brandl

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

From report at bugs.python.org  Sat Aug 10 22:22:37 2013
From: report at bugs.python.org (R. David Murray)
Date: Sat, 10 Aug 2013 20:22:37 +0000
Subject: [docs] [issue18703] To change the doc of html/faq/gui.html
In-Reply-To: <1376157675.52.0.120458668025.issue18703@psf.upfronthosting.co.za>
Message-ID: <1376166157.74.0.506031961229.issue18703@psf.upfronthosting.co.za>


R. David Murray added the comment:

It seems to me (having checked) that the current language is correct.  The fact that PyQt5 is available under the GPL isn't really relevant to the FAQ as it currently exists (it doesn't mention the GPL anywhere else).  Keep in mind that Python's license is non-GPL.  Adding GPL-licensed product information would be a whole different level of change, I think.

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

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

From report at bugs.python.org  Sat Aug 10 23:57:23 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 10 Aug 2013 21:57:23 +0000
Subject: [docs] [issue18676] Queue: document that zero is accepted as
	timeout value
In-Reply-To: <1375883528.55.0.275850242187.issue18676@psf.upfronthosting.co.za>
Message-ID: <1376171843.51.0.849196612458.issue18676@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

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

From report at bugs.python.org  Sun Aug 11 00:40:28 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 10 Aug 2013 22:40:28 +0000
Subject: [docs] [issue18676] Queue: document that zero is accepted as
	timeout value
In-Reply-To: <1375883528.55.0.275850242187.issue18676@psf.upfronthosting.co.za>
Message-ID: <3cCJDr0vdjzQ02@mail.python.org>


Roundup Robot added the comment:

New changeset 737b53ec5d1a by Terry Jan Reedy in branch '2.7':
Issue #18676: Change 'positive' to 'non-negative' in queue.py put and get
http://hg.python.org/cpython/rev/737b53ec5d1a

New changeset 2122d56d6bc5 by Terry Jan Reedy in branch '3.3':
Issue #18676: Change 'positive' to 'non-negative' in queue.py put and get
http://hg.python.org/cpython/rev/2122d56d6bc5

New changeset d9a9fe5e700d by Terry Jan Reedy in branch 'default':
Issue #18676: Merge from 3.3
http://hg.python.org/cpython/rev/d9a9fe5e700d

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

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

From report at bugs.python.org  Sun Aug 11 01:03:53 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 10 Aug 2013 23:03:53 +0000
Subject: [docs] [issue18676] Queue: document that zero is accepted as
	timeout value
In-Reply-To: <1375883528.55.0.275850242187.issue18676@psf.upfronthosting.co.za>
Message-ID: <1376175833.91.0.809136617201.issue18676@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Zhongyue, we merge 3.x patches forward (currently 3.3 to 3.4) so only one patch is usually needed unless the differences are non-trivial. It is easier if different version patches are tagged with the version in the filename.('-27', for instance.

If you think you will ever contribute another patch, especially one less trivial than this one, please go to
http://www.python.org/psf/contrib/ and
http://www.python.org/psf/contrib/contrib-form/
Note that the agreement can now be submitted electronically.

----------
resolution:  -> fixed
stage: commit review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Sun Aug 11 01:45:20 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Sat, 10 Aug 2013 23:45:20 +0000
Subject: [docs] [issue18705] Fix arround 100 typos/spelling mistakes
Message-ID: <1376178317.79.0.772879564661.issue18705@psf.upfronthosting.co.za>


New submission from F?vry Thibault:

In issue 18466 I had said I was planning to write a tool that checks python source code to see if they are spelling mistakes in comments/strings. As it was said there, the big issue was the fact that python has so many non-english words and that docstrings often had variable names in them, so I had to work arround the issue and add a personal word list.

I only applied the tool to Lib/*.py yet, as it takes some time to check false-positives and I didn't want to end with patches too big to be reviewed.

----------
assignee: docs at python
components: Documentation
files: spelling_Lib.diff
keywords: patch
messages: 194850
nosy: docs at python, iwontbecreative
priority: normal
severity: normal
status: open
title: Fix arround 100 typos/spelling mistakes
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file31223/spelling_Lib.diff

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

From report at bugs.python.org  Sun Aug 11 01:48:10 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Sat, 10 Aug 2013 23:48:10 +0000
Subject: [docs] [issue18705] Fix arround 100 typos/spelling mistakes
In-Reply-To: <1376178317.79.0.772879564661.issue18705@psf.upfronthosting.co.za>
Message-ID: <1376178490.13.0.863752745187.issue18705@psf.upfronthosting.co.za>


F?vry Thibault added the comment:

Note that I am not a very good python programmer so the attached script may look ugly to you, but it works.

----------
versions: +Python 3.3
Added file: http://bugs.python.org/file31224/spell.py

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

From report at bugs.python.org  Sun Aug 11 01:48:57 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Sat, 10 Aug 2013 23:48:57 +0000
Subject: [docs] [issue18705] Fix arround 100 typos/spelling mistakes
In-Reply-To: <1376178317.79.0.772879564661.issue18705@psf.upfronthosting.co.za>
Message-ID: <1376178536.93.0.384771582335.issue18705@psf.upfronthosting.co.za>


F?vry Thibault added the comment:

And here is a python_words.txt so you have to press enter less times :)

----------
Added file: http://bugs.python.org/file31225/python_words.txt

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

From report at bugs.python.org  Sun Aug 11 08:37:04 2013
From: report at bugs.python.org (madan ram)
Date: Sun, 11 Aug 2013 06:37:04 +0000
Subject: [docs] [issue18707] the readme should also talk about how to build
	doc.
Message-ID: <1376203024.02.0.197448582438.issue18707@psf.upfronthosting.co.za>


New submission from madan ram:

Since most of and also I faced problem of building Doc initially then later i found out how to build Doc.

So i thought to include details on how to build Doc in README.

----------
assignee: docs at python
components: Build, Devguide, Documentation, Installation
files: README.diff
keywords: patch
messages: 194866
nosy: docs at python, eric.araujo, ezio.melotti, georg.brandl, madan.ram
priority: normal
severity: normal
status: open
title: the readme should also talk about how to build doc.
versions: Python 3.4
Added file: http://bugs.python.org/file31227/README.diff

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

From report at bugs.python.org  Sun Aug 11 09:40:20 2013
From: report at bugs.python.org (sdia)
Date: Sun, 11 Aug 2013 07:40:20 +0000
Subject: [docs] [issue18445] Tools/Script/Readme is outdated
In-Reply-To: <1373782620.19.0.347266346086.issue18445@psf.upfronthosting.co.za>
Message-ID: <1376206820.71.0.316824052789.issue18445@psf.upfronthosting.co.za>


sdia added the comment:

Hello,

I will try to submit a patch for this issue.

----------
nosy: +seydou

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

From report at bugs.python.org  Sun Aug 11 10:47:57 2013
From: report at bugs.python.org (Seydou Dia)
Date: Sun, 11 Aug 2013 08:47:57 +0000
Subject: [docs] [issue18445] Tools/Script/Readme is outdated
In-Reply-To: <1373782620.19.0.347266346086.issue18445@psf.upfronthosting.co.za>
Message-ID: <1376210877.43.0.797516656923.issue18445@psf.upfronthosting.co.za>


Seydou Dia added the comment:

>Several issues :
>- abitype.py, analyze_dxp.py, get-remote-certificate.py, import_diagnostics.py, parse_html5_entities.py are not documented.

Except analyze_dxp.py, all those files have been docummented in README. analyze_dxp.py was already documented so I don't understand what action is needed.
Note that I have also documented find-uname.py.

>- README mentions redemo.py which was moved to Tools/Demo.
Done.

>- README says all python scripts are executables, but some need chmod +x
I can help here.

> - The script list in readme would benefit from being sorted in alphabetical order
Done.

----------
keywords: +patch
Added file: http://bugs.python.org/file31229/issue-18445.diff

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

From report at bugs.python.org  Sun Aug 11 10:50:17 2013
From: report at bugs.python.org (Seydou Dia)
Date: Sun, 11 Aug 2013 08:50:17 +0000
Subject: [docs] [issue18445] Tools/Script/Readme is outdated
In-Reply-To: <1373782620.19.0.347266346086.issue18445@psf.upfronthosting.co.za>
Message-ID: <1376211017.79.0.357127898797.issue18445@psf.upfronthosting.co.za>


Seydou Dia added the comment:

>>- README says all python scripts are executables, but some need chmod +x
>I can help here.

Sorry I meant : "I can't help here". :)

----------

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

From report at bugs.python.org  Sun Aug 11 12:02:47 2013
From: report at bugs.python.org (Mark Dickinson)
Date: Sun, 11 Aug 2013 10:02:47 +0000
Subject: [docs] [issue18705] Fix arround 100 typos/spelling mistakes
In-Reply-To: <1376178317.79.0.772879564661.issue18705@psf.upfronthosting.co.za>
Message-ID: <1376215367.33.0.248319445414.issue18705@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

Thanks for the patch.

I don't think there's a strict policy about using American spellings in the source;  I think spellings like 'behaviour' and 'grey' should be left alone.

----------
nosy: +mark.dickinson

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

From report at bugs.python.org  Sun Aug 11 12:07:04 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 11 Aug 2013 10:07:04 +0000
Subject: [docs] [issue18663] In unittest.TestCase.assertAlmostEqual doc
	specify the	delta description
In-Reply-To: <1375725190.79.0.442588525807.issue18663@psf.upfronthosting.co.za>
Message-ID: <3cCbT35LCdz7Ljj@mail.python.org>


Roundup Robot added the comment:

New changeset e0f86c3b3685 by Ezio Melotti in branch '3.3':
#18663: document that assertAlmostEqual also works when the values are equal and add tests.
http://hg.python.org/cpython/rev/e0f86c3b3685

New changeset eeda59e08c83 by Ezio Melotti in branch 'default':
#18663: merge with 3.3.
http://hg.python.org/cpython/rev/eeda59e08c83

New changeset 9ddc63c039ba by Ezio Melotti in branch '2.7':
#18663: document that assertAlmostEqual also works when the values are equal and add tests.
http://hg.python.org/cpython/rev/9ddc63c039ba

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

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

From report at bugs.python.org  Sun Aug 11 12:07:53 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 11 Aug 2013 10:07:53 +0000
Subject: [docs] [issue18663] In unittest.TestCase.assertAlmostEqual doc
	specify the	delta description
In-Reply-To: <1375725190.79.0.442588525807.issue18663@psf.upfronthosting.co.za>
Message-ID: <1376215673.1.0.934338068343.issue18663@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the report and the patch!

----------
assignee: docs at python -> ezio.melotti
nosy: +ezio.melotti
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Sun Aug 11 12:15:13 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Sun, 11 Aug 2013 10:15:13 +0000
Subject: [docs] [issue18705] Fix arround 100 typos/spelling mistakes
In-Reply-To: <1376178317.79.0.772879564661.issue18705@psf.upfronthosting.co.za>
Message-ID: <1376216113.88.0.282176089216.issue18705@psf.upfronthosting.co.za>


F?vry Thibault added the comment:

> I don't think there's a strict policy about using American spellings in the source;  I think spellings like 'behaviour' and 'grey' should be left alone.

I didn't really know whether to change them or not and did not find an answer in the devguide (Might be worth documenting it ?) so I decided to change it :/.

----------

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

From report at bugs.python.org  Sun Aug 11 12:19:28 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 11 Aug 2013 10:19:28 +0000
Subject: [docs] [issue18705] Fix arround 100 typos/spelling mistakes
In-Reply-To: <1376178317.79.0.772879564661.issue18705@psf.upfronthosting.co.za>
Message-ID: <1376216368.16.0.0904511250454.issue18705@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Both AE and BE are OK, as long as each document is internally consistent.  For new documents I think AE is preferred, but not forced.

----------
nosy: +ezio.melotti
stage:  -> patch review

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

From report at bugs.python.org  Sun Aug 11 14:25:37 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Sun, 11 Aug 2013 12:25:37 +0000
Subject: [docs] [issue18705] Fix arround 100 typos/spelling mistakes
In-Reply-To: <1376178317.79.0.772879564661.issue18705@psf.upfronthosting.co.za>
Message-ID: <1376223935.22.0.0347936115552.issue18705@psf.upfronthosting.co.za>


F?vry Thibault added the comment:

Updated the patch to no longer change BE to AE and fixed two mistakes in my correction.

----------
Added file: http://bugs.python.org/file31231/spelling_Lib.diff

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

From report at bugs.python.org  Sun Aug 11 14:26:48 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Sun, 11 Aug 2013 12:26:48 +0000
Subject: [docs] [issue18705] Fix typos/spelling mistakes in Lib/*.py files
In-Reply-To: <1376178317.79.0.772879564661.issue18705@psf.upfronthosting.co.za>
Message-ID: <1376224008.43.0.731007201333.issue18705@psf.upfronthosting.co.za>


Changes by F?vry Thibault <thibaultfevry at gmail.com>:


----------
title: Fix arround 100 typos/spelling mistakes -> Fix typos/spelling mistakes in Lib/*.py files

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

From report at bugs.python.org  Sun Aug 11 14:31:55 2013
From: report at bugs.python.org (Mark Dickinson)
Date: Sun, 11 Aug 2013 12:31:55 +0000
Subject: [docs] [issue18705] Fix typos/spelling mistakes in Lib/*.py files
In-Reply-To: <1376178317.79.0.772879564661.issue18705@psf.upfronthosting.co.za>
Message-ID: <1376224315.01.0.452021467955.issue18705@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

Thanks for the update.  All the changes in the updated patch look good to me.

----------

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

From ezio.melotti at gmail.com  Sun Aug 11 14:41:58 2013
From: ezio.melotti at gmail.com (ezio.melotti at gmail.com)
Date: Sun, 11 Aug 2013 12:41:58 -0000
Subject: [docs] Document codecs.encode and codecs.decode (issue 17827)
Message-ID: <20130811124158.30788.6465@psf.upfronthosting.co.za>


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

http://bugs.python.org/review/17827/diff/8606/Doc/library/codecs.rst#newcode27
Doc/library/codecs.rst:27: Encodes obj using the codec registered for
encoding. Errors may be given
*encoding*

http://bugs.python.org/review/17827/diff/8606/Doc/library/codecs.rst#newcode28
Doc/library/codecs.rst:28: to set a different error handling scheme.
Default is ``strict`` meaning that
``'strict'``

http://bugs.python.org/review/17827/diff/8606/Doc/library/codecs.rst#newcode30
Doc/library/codecs.rst:30: ``replace`` and ``xmlcharrefreplace`` as well
as any other name registered with
These lines are too long.

http://bugs.python.org/review/17827/diff/8606/Doc/library/codecs.rst#newcode31
Doc/library/codecs.rst:31: ``codecs.register_error`` that can handle
:exc:`ValueError`.
I think there's already a list of valid error handlers somewhere, so you
could just link to that instead of repeating them here.

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

From report at bugs.python.org  Sun Aug 11 21:15:44 2013
From: report at bugs.python.org (Seydou Dia)
Date: Sun, 11 Aug 2013 19:15:44 +0000
Subject: [docs] [issue18576] Rename and document test.script_helper
	as	test.support.script_helper
In-Reply-To: <1375014764.64.0.152576599022.issue18576@psf.upfronthosting.co.za>
Message-ID: <1376248544.45.0.601105354669.issue18576@psf.upfronthosting.co.za>


Seydou Dia added the comment:

Since I am already on bugs.python.org/issue18578 I will tackle this issue, if you don't mind.

----------
nosy: +seydou

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

From report at bugs.python.org  Mon Aug 12 00:44:11 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 11 Aug 2013 22:44:11 +0000
Subject: [docs] [issue12645] test.support. import_fresh_module - incorrect
	doc
In-Reply-To: <1311789815.76.0.639942891335.issue12645@psf.upfronthosting.co.za>
Message-ID: <3cCwGf56PgzSYy@mail.python.org>


Roundup Robot added the comment:

New changeset edaf44136d32 by Eli Bendersky in branch '3.3':
Issue #12645: Clarify and reformat the documentation of import_fresh_module
http://hg.python.org/cpython/rev/edaf44136d32

New changeset d8000009ef0e by Eli Bendersky in branch 'default':
Close #12645: Clarify and reformat the documentation of import_fresh_module
http://hg.python.org/cpython/rev/d8000009ef0e

----------
nosy: +python-dev
resolution:  -> fixed
stage: needs patch -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Mon Aug 12 21:19:11 2013
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 12 Aug 2013 19:19:11 +0000
Subject: [docs] [issue18707] the readme should also talk about how to build
	doc.
In-Reply-To: <1376203024.02.0.197448582438.issue18707@psf.upfronthosting.co.za>
Message-ID: <1376335151.13.0.340350163214.issue18707@psf.upfronthosting.co.za>


?ric Araujo added the comment:

There is a README in the Doc directory.  Wouldn?t it be enough to point to that file from the main README?

----------

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

From report at bugs.python.org  Mon Aug 12 21:51:22 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 12 Aug 2013 19:51:22 +0000
Subject: [docs] [issue17701] Improving strftime documentation
In-Reply-To: <1365725163.24.0.249924950016.issue17701@psf.upfronthosting.co.za>
Message-ID: <3cDSNn3Hs4zSdF@mail.python.org>


Roundup Robot added the comment:

New changeset adbc9789a5e4 by David Wolever in branch '2.7':
Issue #17701: Improving strftime documentation
http://hg.python.org/cpython/rev/adbc9789a5e4

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

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

From report at bugs.python.org  Mon Aug 12 21:51:57 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 12 Aug 2013 19:51:57 +0000
Subject: [docs] [issue18707] the readme should also talk about how to build
	doc.
In-Reply-To: <1376203024.02.0.197448582438.issue18707@psf.upfronthosting.co.za>
Message-ID: <1376337117.37.0.771687784681.issue18707@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

+1

----------
type:  -> enhancement
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Mon Aug 12 23:15:52 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 12 Aug 2013 21:15:52 +0000
Subject: [docs] [issue17701] Improving strftime documentation
In-Reply-To: <1365725163.24.0.249924950016.issue17701@psf.upfronthosting.co.za>
Message-ID: <3cDVGH4HCzzMnM@mail.python.org>


Roundup Robot added the comment:

New changeset 1d4b02d8fa8a by David Wolever in branch '3.3':
Issue #17701: Improving strftime documentation.
http://hg.python.org/cpython/rev/1d4b02d8fa8a

New changeset ab550dac6209 by David Wolever in branch 'default':
Merge issue #17701: Improving strftime documentation.
http://hg.python.org/cpython/rev/ab550dac6209

----------

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

From report at bugs.python.org  Mon Aug 12 23:23:46 2013
From: report at bugs.python.org (David Wolever)
Date: Mon, 12 Aug 2013 21:23:46 +0000
Subject: [docs] [issue17701] Improving strftime documentation
In-Reply-To: <1365725163.24.0.249924950016.issue17701@psf.upfronthosting.co.za>
Message-ID: <1376342626.76.0.537594762375.issue17701@psf.upfronthosting.co.za>


David Wolever added the comment:

Done, pushed to 2.7, 3.3, default.

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

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

From report at bugs.python.org  Mon Aug 12 23:47:05 2013
From: report at bugs.python.org (Felix Crux)
Date: Mon, 12 Aug 2013 21:47:05 +0000
Subject: [docs] [issue18680] JSONDecoder should document that it raises a
	ValueError	for malformed data
In-Reply-To: <1375913191.45.0.0174536581066.issue18680@psf.upfronthosting.co.za>
Message-ID: <1376344024.97.0.67779187711.issue18680@psf.upfronthosting.co.za>


Felix Crux added the comment:

Working with wolever on the process, generated the attached patch.

----------
keywords: +patch
nosy: +felixc, wolever
Added file: http://bugs.python.org/file31263/18680.patch

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

From report at bugs.python.org  Tue Aug 13 00:13:38 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 12 Aug 2013 22:13:38 +0000
Subject: [docs] [issue18680] JSONDecoder should document that it raises a
	ValueError	for malformed data
In-Reply-To: <1375913191.45.0.0174536581066.issue18680@psf.upfronthosting.co.za>
Message-ID: <3cDWXy0G5zzMfc@mail.python.org>


Roundup Robot added the comment:

New changeset f11683963558 by Felix Crux in branch 'default':
Documenting that json.load may raise a ValueError.
http://hg.python.org/cpython/rev/f11683963558

New changeset 905fad4cb40a by Felix Crux in branch 'default':
Documenting that json.load may raise a ValueError.
http://hg.python.org/cpython/rev/905fad4cb40a

New changeset 7ba77d77b499 by Felix Crux in branch 'default':
Documenting that json.load may raise a ValueError.
http://hg.python.org/cpython/rev/7ba77d77b499

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

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

From report at bugs.python.org  Tue Aug 13 00:15:21 2013
From: report at bugs.python.org (David Wolever)
Date: Mon, 12 Aug 2013 22:15:21 +0000
Subject: [docs] [issue18680] JSONDecoder should document that it raises a
	ValueError	for malformed data
In-Reply-To: <1375913191.45.0.0174536581066.issue18680@psf.upfronthosting.co.za>
Message-ID: <1376345721.97.0.938979959419.issue18680@psf.upfronthosting.co.za>


Changes by David Wolever <david at wolever.net>:


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

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

From report at bugs.python.org  Tue Aug 13 00:28:26 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 12 Aug 2013 22:28:26 +0000
Subject: [docs] [issue18680] JSONDecoder should document that it raises a
	ValueError	for malformed data
In-Reply-To: <1375913191.45.0.0174536581066.issue18680@psf.upfronthosting.co.za>
Message-ID: <3cDWt20t6NzRk2@mail.python.org>


Roundup Robot added the comment:

New changeset f8cf0f997dfa by Felix Crux in branch '3.3':
Documenting that json.load may raise a ValueError.
http://hg.python.org/cpython/rev/f8cf0f997dfa

New changeset 524693d62093 by Felix Crux in branch '2.7':
Documenting that json.load may raise a ValueError.
http://hg.python.org/cpython/rev/524693d62093

----------

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

From report at bugs.python.org  Tue Aug 13 01:49:32 2013
From: report at bugs.python.org (Madison May)
Date: Mon, 12 Aug 2013 23:49:32 +0000
Subject: [docs] [issue18707] the readme should also talk about how to build
	doc.
In-Reply-To: <1376203024.02.0.197448582438.issue18707@psf.upfronthosting.co.za>
Message-ID: <1376351372.75.0.884650947879.issue18707@psf.upfronthosting.co.za>


Madison May added the comment:

Here's a patch that adds a short sentence to the README's `Documentation` section that refers readers to the Doc/README.txt file.

----------
nosy: +madison.may
Added file: http://bugs.python.org/file31267/README_v2.diff

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

From report at bugs.python.org  Tue Aug 13 02:31:34 2013
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 13 Aug 2013 00:31:34 +0000
Subject: [docs] [issue18707] the readme should also talk about how to build
	doc.
In-Reply-To: <1376203024.02.0.197448582438.issue18707@psf.upfronthosting.co.za>
Message-ID: <1376353893.84.0.0281378431546.issue18707@psf.upfronthosting.co.za>


?ric Araujo added the comment:

Thanks for the patch!  One thing: Doc/README.txt does not actually mention how to contribute to the doc, does it?  Maybe the main README should link to the devguide instead of or in addition to Doc/README.txt

----------

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

From report at bugs.python.org  Tue Aug 13 03:25:47 2013
From: report at bugs.python.org (Madison May)
Date: Tue, 13 Aug 2013 01:25:47 +0000
Subject: [docs] [issue18707] the readme should also talk about how to build
	doc.
In-Reply-To: <1376203024.02.0.197448582438.issue18707@psf.upfronthosting.co.za>
Message-ID: <1376357147.4.0.495829108723.issue18707@psf.upfronthosting.co.za>


Madison May added the comment:

Good point, ?ric.

It refers readers to the bug tracker, the Sphinx bug tracker, and docs at python.org in the `Contributing` section, but a link to the devguide would probably be more useful.  I've tweaked the patch a bit to reflect this.

----------
Added file: http://bugs.python.org/file31268/README_v3.diff

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

From report at bugs.python.org  Tue Aug 13 03:28:57 2013
From: report at bugs.python.org (Madison May)
Date: Tue, 13 Aug 2013 01:28:57 +0000
Subject: [docs] [issue18707] the readme should also talk about how to build
	doc.
In-Reply-To: <1376203024.02.0.197448582438.issue18707@psf.upfronthosting.co.za>
Message-ID: <1376357337.17.0.894442766358.issue18707@psf.upfronthosting.co.za>


Madison May added the comment:

Or perhaps with an alternate wording: README_v4.diff

----------
Added file: http://bugs.python.org/file31269/README_v4.diff

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

From report at bugs.python.org  Tue Aug 13 09:42:27 2013
From: report at bugs.python.org (Susan Tan)
Date: Tue, 13 Aug 2013 07:42:27 +0000
Subject: [docs] [issue18724] Typo in docs.python.org: smtplib python2.7
Message-ID: <1376379747.75.0.914823707462.issue18724@psf.upfronthosting.co.za>


New submission from Susan Tan:

http://docs.python.org/2.7/library/smtplib.html#smtplib.SMTPException 

"exception smtplib.SMTPException
The base exception class for all the other excpetions provided by this module."

The word "exceptions" is spelled incorrectly in the in "other excpetions".

----------
assignee: docs at python
components: Documentation
messages: 195049
nosy: Susan, docs at python
priority: normal
severity: normal
status: open
title: Typo in docs.python.org: smtplib python2.7
type: enhancement
versions: Python 2.7

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

From report at bugs.python.org  Tue Aug 13 10:16:21 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 13 Aug 2013 08:16:21 +0000
Subject: [docs] [issue18724] Typo in docs.python.org: smtplib python2.7
In-Reply-To: <1376379747.75.0.914823707462.issue18724@psf.upfronthosting.co.za>
Message-ID: <3cDmwP05mbzSKq@mail.python.org>


Roundup Robot added the comment:

New changeset bd030e70cecb by Ned Deily in branch '2.7':
Issue 18724: Fix typo noticed by Susan Tan.
http://hg.python.org/cpython/rev/bd030e70cecb

New changeset 76d71bc949b6 by Ned Deily in branch '3.3':
Issue 18724: Fix typo noticed by Susan Tan.
http://hg.python.org/cpython/rev/76d71bc949b6

New changeset 8dccd3b51711 by Ned Deily in branch 'default':
Issue 18724: Fix typo noticed by Susan Tan.
http://hg.python.org/cpython/rev/8dccd3b51711

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

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

From report at bugs.python.org  Tue Aug 13 10:17:20 2013
From: report at bugs.python.org (Ned Deily)
Date: Tue, 13 Aug 2013 08:17:20 +0000
Subject: [docs] [issue18724] Typo in docs.python.org: smtplib python2.7
In-Reply-To: <1376379747.75.0.914823707462.issue18724@psf.upfronthosting.co.za>
Message-ID: <1376381840.16.0.448509144653.issue18724@psf.upfronthosting.co.za>


Ned Deily added the comment:

Thanks for the report!

----------
nosy: +ned.deily
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
type: enhancement -> 
versions: +Python 3.3, Python 3.4

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

From report at bugs.python.org  Tue Aug 13 11:54:52 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 13 Aug 2013 09:54:52 +0000
Subject: [docs] [issue18687] Lib/test/leakers/test_ctypes.py still mentions
	the need	to update Misc/build.sh
In-Reply-To: <1375985116.56.0.149122259336.issue18687@psf.upfronthosting.co.za>
Message-ID: <3cDq631swqz7LjP@mail.python.org>


Roundup Robot added the comment:

New changeset 49edf4cbc453 by Ezio Melotti in branch '2.7':
#18687: remove obsolete comment.  Patch by F?vry Thibault.
http://hg.python.org/cpython/rev/49edf4cbc453

New changeset 49fa63610c7f by Ezio Melotti in branch '3.3':
#18687: remove obsolete comment.  Patch by F?vry Thibault.
http://hg.python.org/cpython/rev/49fa63610c7f

New changeset 1ea89e5f40cf by Ezio Melotti in branch 'default':
#18687: merge with 3.3.
http://hg.python.org/cpython/rev/1ea89e5f40cf

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

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

From report at bugs.python.org  Tue Aug 13 11:55:50 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 13 Aug 2013 09:55:50 +0000
Subject: [docs] [issue18687] Lib/test/leakers/test_ctypes.py still mentions
	the need	to update Misc/build.sh
In-Reply-To: <1375985116.56.0.149122259336.issue18687@psf.upfronthosting.co.za>
Message-ID: <1376387750.47.0.377889726645.issue18687@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the report and the patch!

----------
assignee: docs at python -> ezio.melotti
nosy: +ezio.melotti
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
type:  -> enhancement
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Tue Aug 13 17:01:42 2013
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 13 Aug 2013 15:01:42 +0000
Subject: [docs] [issue18707] the readme should also talk about how to build
	doc.
In-Reply-To: <1376203024.02.0.197448582438.issue18707@psf.upfronthosting.co.za>
Message-ID: <1376406102.36.0.596722320683.issue18707@psf.upfronthosting.co.za>


?ric Araujo added the comment:

Either one looks good to me.

----------

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

From report at bugs.python.org  Tue Aug 13 17:03:58 2013
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 13 Aug 2013 15:03:58 +0000
Subject: [docs] [issue18703] To change the doc of html/faq/gui.html
In-Reply-To: <1376157675.52.0.120458668025.issue18703@psf.upfronthosting.co.za>
Message-ID: <1376406238.49.0.227473966604.issue18703@psf.upfronthosting.co.za>


?ric Araujo added the comment:

Also, the GPLs allows commercial usage, so using ?LGPL? and ?commercial? to mean two different licensing cases is not quite right.

----------

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

From report at bugs.python.org  Tue Aug 13 20:24:47 2013
From: report at bugs.python.org (py.user)
Date: Tue, 13 Aug 2013 18:24:47 +0000
Subject: [docs] [issue18729] In unittest.TestLoader.discover doc select the
	name of	load_tests function
Message-ID: <1376418287.73.0.835584535115.issue18729@psf.upfronthosting.co.za>


New submission from py.user:

http://docs.python.org/3/library/unittest.html#unittest.TestLoader.discover
"If load_tests exists then discovery does not recurse into the package"

----------
assignee: docs at python
components: Documentation
files: issue.diff
keywords: patch
messages: 195092
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: In unittest.TestLoader.discover doc select the name of load_tests function
type: enhancement
versions: Python 3.3, Python 3.4
Added file: http://bugs.python.org/file31283/issue.diff

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

From report at bugs.python.org  Wed Aug 14 00:19:35 2013
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 13 Aug 2013 22:19:35 +0000
Subject: [docs] [issue1227748] subprocess: inheritance of std descriptors
	inconsistent
Message-ID: <1376432375.71.0.975286723493.issue1227748@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed Aug 14 13:59:06 2013
From: report at bugs.python.org (Basil Peace)
Date: Wed, 14 Aug 2013 11:59:06 +0000
Subject: [docs] [issue18736] Invalid charset in HTML pages inside
	documentation in	CHM format
Message-ID: <1376481546.2.0.725412367622.issue18736@psf.upfronthosting.co.za>


New submission from Basil Peace:

HTML pages inside CHM documentation use the following tag to set applied character set:
    <meta http-equiv="Content-Type" content="text/html; charset=iso8859_1" />

`iso8859_1` is neither valid character set according to IANA registry nor is recognized by most browsers (I've checked IE, Firefox and Opera).

This isn't notable for text in English. But, in `Python Standard Library` in section `4.7.1 String Methods` there is a documentation for str.casefold(). This paragraph contains German letter `?`.
Without defined character set this letter can be displayed wrongly, depending on user's regional settings. In my Russian I see in CHM `?`. Firefox displays it as `?`.

Fix of charset to `ISO-8859-1` could resolve the problem.

P.S. Use of UTF-8 may be more convenient for preventing future errors.

----------
assignee: docs at python
components: Documentation
messages: 195136
nosy: docs at python, grv87
priority: normal
severity: normal
status: open
title: Invalid charset in HTML pages inside documentation in CHM format
versions: Python 3.3

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

From report at bugs.python.org  Wed Aug 14 14:44:02 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 14 Aug 2013 12:44:02 +0000
Subject: [docs] [issue18736] Invalid charset in HTML pages inside
	documentation in	CHM format
In-Reply-To: <1376481546.2.0.725412367622.issue18736@psf.upfronthosting.co.za>
Message-ID: <1376484242.17.0.124544902653.issue18736@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed Aug 14 22:58:38 2013
From: report at bugs.python.org (paul j3)
Date: Wed, 14 Aug 2013 20:58:38 +0000
Subject: [docs] [issue15428] add "Name Collision" section to argparse docs
In-Reply-To: <1343001632.52.0.429837248023.issue15428@psf.upfronthosting.co.za>
Message-ID: <1376513918.59.0.591012956116.issue15428@psf.upfronthosting.co.za>


Changes by paul j3 <ajipanca at gmail.com>:


----------
nosy: +paul.j3

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

From report at bugs.python.org  Wed Aug 14 23:21:25 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Wed, 14 Aug 2013 21:21:25 +0000
Subject: [docs] [issue18741] Fix typos/spelling mistakes in Lib/*/*/.py files
Message-ID: <1376515284.41.0.228001908428.issue18741@psf.upfronthosting.co.za>


New submission from F?vry Thibault:

Using the same tool described in issue 18705, I fixed more typos.

----------
assignee: docs at python
components: Documentation
files: another_typo_patch.diff
keywords: patch
messages: 195216
nosy: docs at python, iwontbecreative
priority: normal
severity: normal
status: open
title: Fix typos/spelling mistakes in Lib/*/*/.py files
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file31294/another_typo_patch.diff

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

From report at bugs.python.org  Thu Aug 15 07:01:51 2013
From: report at bugs.python.org (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Thu, 15 Aug 2013 05:01:51 +0000
Subject: [docs] [issue18743] References to non-existant "StringIO" module
Message-ID: <1376542911.78.0.658455842148.issue18743@psf.upfronthosting.co.za>


New submission from Jes?s Cea Avi?n:

Doing a "grep StringIO Doc/library/*.rst" shows a handful of references to the old StringIO library. Notably:

gzip.rst
mailbox.rst
tempfile.rst
test.rst
unittest.mock.rst
xml.dom.minidom.rst

----------
assignee: docs at python
components: Documentation
messages: 195231
nosy: docs at python, jcea
priority: normal
severity: normal
status: open
title: References to non-existant "StringIO" module
versions: Python 3.3, Python 3.4

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

From report at bugs.python.org  Thu Aug 15 09:32:17 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 15 Aug 2013 07:32:17 +0000
Subject: [docs] [issue18743] References to non-existant "StringIO" module
In-Reply-To: <1376542911.78.0.658455842148.issue18743@psf.upfronthosting.co.za>
Message-ID: <1376551937.88.0.710617039847.issue18743@psf.upfronthosting.co.za>


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


----------
nosy: +serhiy.storchaka
stage:  -> needs patch

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

From report at bugs.python.org  Thu Aug 15 18:33:23 2013
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 15 Aug 2013 16:33:23 +0000
Subject: [docs] [issue18532] hashlib.HASH objects should officially expose
	the hash	name
In-Reply-To: <1374524940.42.0.582552143445.issue18532@psf.upfronthosting.co.za>
Message-ID: <1376584402.96.0.365836383567.issue18532@psf.upfronthosting.co.za>


Christian Heimes added the comment:

The builtin hash algorithms still had upper case names. I fixed it in 
revision http://hg.python.org/cpython/rev/9a4949f5d15c

----------

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

From report at bugs.python.org  Thu Aug 15 18:33:29 2013
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 15 Aug 2013 16:33:29 +0000
Subject: [docs] [issue18532] hashlib.HASH objects should officially expose
	the hash	name
In-Reply-To: <1374524940.42.0.582552143445.issue18532@psf.upfronthosting.co.za>
Message-ID: <1376584409.02.0.486296976923.issue18532@psf.upfronthosting.co.za>


Changes by Christian Heimes <lists at cheimes.de>:


----------
stage: patch review -> committed/rejected

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

From report at bugs.python.org  Thu Aug 15 21:44:51 2013
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 15 Aug 2013 19:44:51 +0000
Subject: [docs] [issue16190] Misleading warning in random module docs
In-Reply-To: <1349885590.41.0.193272073786.issue16190@psf.upfronthosting.co.za>
Message-ID: <1376595890.92.0.10109229276.issue16190@psf.upfronthosting.co.za>


Christian Heimes added the comment:

Thomas H. Ptacek pointed me to a good explanation: http://security.stackexchange.com/a/3939

TL;DR: Just use /dev/urandom and be happy.

----------

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

From report at bugs.python.org  Thu Aug 15 22:21:22 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 15 Aug 2013 20:21:22 +0000
Subject: [docs] [issue16190] Misleading warning in random module docs
In-Reply-To: <1349885590.41.0.193272073786.issue16190@psf.upfronthosting.co.za>
Message-ID: <1376598082.08.0.950137714234.issue16190@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Agreed with a re-wording.

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

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

From report at bugs.python.org  Thu Aug 15 23:08:58 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 15 Aug 2013 21:08:58 +0000
Subject: [docs] [issue18301] In itertools.chain.from_iterable() there is no
	cls	argument
In-Reply-To: <1372186723.21.0.67533324157.issue18301@psf.upfronthosting.co.za>
Message-ID: <1376600938.79.0.959304898545.issue18301@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

My counter proposal #18752 is that chain.from_iterable become a deprecated alias for a new function, chain_iterable.  With '@classmethod' removed, the current Python equivalent would work for chain_iterable.

----------

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

From report at bugs.python.org  Fri Aug 16 08:14:57 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 06:14:57 +0000
Subject: [docs] [issue18743] References to non-existant "StringIO" module
In-Reply-To: <1376542911.78.0.658455842148.issue18743@psf.upfronthosting.co.za>
Message-ID: <1376633697.29.0.90813702854.issue18743@psf.upfronthosting.co.za>


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


----------
assignee: docs at python -> serhiy.storchaka

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

From report at bugs.python.org  Fri Aug 16 08:34:37 2013
From: report at bugs.python.org (Glenn Linderman)
Date: Fri, 16 Aug 2013 06:34:37 +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: <1376634877.49.0.901461797021.issue14191@psf.upfronthosting.co.za>


Glenn Linderman added the comment:

Paul, is this ready to merge, or are you thinking of more refinements?

----------

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

From report at bugs.python.org  Fri Aug 16 17:34:41 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 15:34:41 +0000
Subject: [docs] [issue18743] References to non-existant "StringIO" module
In-Reply-To: <1376542911.78.0.658455842148.issue18743@psf.upfronthosting.co.za>
Message-ID: <1376667281.13.0.495784976605.issue18743@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Here is a patch. Actually this is a small part of larger problem for which I will open several separated issues.

----------
keywords: +patch
stage: needs patch -> patch review
Added file: http://bugs.python.org/file31315/doc_StringIO_refs.patch

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

From report at bugs.python.org  Fri Aug 16 18:02:46 2013
From: report at bugs.python.org (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Fri, 16 Aug 2013 16:02:46 +0000
Subject: [docs] [issue18743] References to non-existant "StringIO" module
In-Reply-To: <1376542911.78.0.658455842148.issue18743@psf.upfronthosting.co.za>
Message-ID: <1376668966.25.0.564105910187.issue18743@psf.upfronthosting.co.za>


Jes?s Cea Avi?n added the comment:

Patch is incomplete. I found this error while reading "unittest.mock", that you are not patching.

----------

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

From report at bugs.python.org  Fri Aug 16 19:17:34 2013
From: report at bugs.python.org (Donald Stufft)
Date: Fri, 16 Aug 2013 17:17:34 +0000
Subject: [docs] [issue16190] Misleading warning in random module docs
In-Reply-To: <1349885590.41.0.193272073786.issue16190@psf.upfronthosting.co.za>
Message-ID: <1376673454.46.0.730136790048.issue16190@psf.upfronthosting.co.za>


Changes by Donald Stufft <donald.stufft at gmail.com>:


----------
nosy: +dstufft

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

From report at bugs.python.org  Fri Aug 16 19:21:35 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 16 Aug 2013 17:21:35 +0000
Subject: [docs] [issue16190] Misleading warning in random module docs
In-Reply-To: <1349885590.41.0.193272073786.issue16190@psf.upfronthosting.co.za>
Message-ID: <3cGrt641G8z7Ljj@mail.python.org>


Roundup Robot added the comment:

New changeset 9df0501fab35 by Antoine Pitrou in branch '3.3':
Issue #16190: fix random module recommendation to use ssl.RAND_bytes().
http://hg.python.org/cpython/rev/9df0501fab35

New changeset 04b50a1eb013 by Antoine Pitrou in branch 'default':
Issue #16190: fix random module recommendation to use ssl.RAND_bytes().
http://hg.python.org/cpython/rev/04b50a1eb013

New changeset 48b618a9ad10 by Antoine Pitrou in branch '2.7':
Issue #16190: fix random module recommendation to use ssl.RAND_bytes().
http://hg.python.org/cpython/rev/48b618a9ad10

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

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

From report at bugs.python.org  Fri Aug 16 19:22:25 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 16 Aug 2013 17:22:25 +0000
Subject: [docs] [issue16190] Misleading warning in random module docs
In-Reply-To: <1349885590.41.0.193272073786.issue16190@psf.upfronthosting.co.za>
Message-ID: <1376673745.51.0.730086974202.issue16190@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Done.

----------
resolution:  -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
versions:  -Python 3.2

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

From report at bugs.python.org  Fri Aug 16 19:43:35 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 17:43:35 +0000
Subject: [docs] [issue18757] Fix internal references for concurrent modules
Message-ID: <1376675015.24.0.101209198038.issue18757@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a patch which fixes internal references in the documentation of concurrent modules: threading, multiprocessing, concurrent.futures, subprocess, queue, and select.

----------
assignee: docs at python
components: Documentation
messages: 195378
nosy: bquinlan, docs at python, jnoller, pitrou, rhettinger, sbt, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Fix internal references for concurrent modules
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Aug 16 19:46:49 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 16 Aug 2013 17:46:49 +0000
Subject: [docs] [issue18757] Fix internal references for concurrent modules
In-Reply-To: <1376675015.24.0.101209198038.issue18757@psf.upfronthosting.co.za>
Message-ID: <1376675209.61.0.306915736914.issue18757@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Serhiy, seems you forgot to attach a patch.

----------
nosy: +ezio.melotti
type:  -> enhancement

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

From report at bugs.python.org  Fri Aug 16 20:17:26 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 18:17:26 +0000
Subject: [docs] [issue18743] References to non-existant "StringIO" module
In-Reply-To: <1376542911.78.0.658455842148.issue18743@psf.upfronthosting.co.za>
Message-ID: <1376677046.02.0.0290662288718.issue18743@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

I don't see StringIO in Doc/library/unittest.mock.rst.

----------

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

From report at bugs.python.org  Fri Aug 16 20:31:53 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 18:31:53 +0000
Subject: [docs] [issue18743] References to non-existant "StringIO" module
In-Reply-To: <1376542911.78.0.658455842148.issue18743@psf.upfronthosting.co.za>
Message-ID: <1376677913.74.0.879800207905.issue18743@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Ah, I missed it. Here is completed patch.

----------
Added file: http://bugs.python.org/file31321/doc_StringIO_refs_2.patch

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

From report at bugs.python.org  Fri Aug 16 20:33:42 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 16 Aug 2013 18:33:42 +0000
Subject: [docs] [issue18707] the readme should also talk about how to build
	doc.
In-Reply-To: <1376203024.02.0.197448582438.issue18707@psf.upfronthosting.co.za>
Message-ID: <3cGtTK6XpNz7LjM@mail.python.org>


Roundup Robot added the comment:

New changeset 6bc88d61f302 by Ezio Melotti in branch '2.7':
#18707: point to Doc/README.txt in the README file.  Patch by Madison May.
http://hg.python.org/cpython/rev/6bc88d61f302

New changeset 477a143bfbfd by Ezio Melotti in branch '3.3':
#18707: point to Doc/README.txt in the README file.  Patch by Madison May.
http://hg.python.org/cpython/rev/477a143bfbfd

New changeset 96c51207e7cd by Ezio Melotti in branch 'default':
#18707: merge with 3.3.
http://hg.python.org/cpython/rev/96c51207e7cd

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

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

From report at bugs.python.org  Fri Aug 16 20:34:27 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 18:34:27 +0000
Subject: [docs] [issue18757] Fix internal references for concurrent modules
In-Reply-To: <1376675015.24.0.101209198038.issue18757@psf.upfronthosting.co.za>
Message-ID: <1376678066.4.0.794939524515.issue18757@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Sorry. It is here.

----------
keywords: +patch
Added file: http://bugs.python.org/file31322/refs.concurrect.diff

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

From report at bugs.python.org  Fri Aug 16 20:34:29 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 16 Aug 2013 18:34:29 +0000
Subject: [docs] [issue18707] the readme should also talk about how to build
	doc.
In-Reply-To: <1376203024.02.0.197448582438.issue18707@psf.upfronthosting.co.za>
Message-ID: <1376678068.95.0.402752793942.issue18707@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the report and the patch!

----------
assignee: docs at python -> ezio.melotti
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Fri Aug 16 20:35:05 2013
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 16 Aug 2013 18:35:05 +0000
Subject: [docs] [issue16190] Misleading warning in random module docs
In-Reply-To: <1349885590.41.0.193272073786.issue16190@psf.upfronthosting.co.za>
Message-ID: <1376678105.06.0.802199109163.issue16190@psf.upfronthosting.co.za>


STINNER Victor added the comment:

Why did you remove reference to ssl.RAND_bytes() on Python 3.3 from the notice?

----------

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

From report at bugs.python.org  Fri Aug 16 20:38:47 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 16 Aug 2013 18:38:47 +0000
Subject: [docs] [issue16190] Misleading warning in random module docs
In-Reply-To: <1349885590.41.0.193272073786.issue16190@psf.upfronthosting.co.za>
Message-ID: <1376678327.61.0.566047884703.issue16190@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

As far as I understand, os.urandom() is fine for the task. There's no point in mentioning ssl.RAND_bytes() just because it exists, IMO.

----------

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

From report at bugs.python.org  Fri Aug 16 20:38:58 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 18:38:58 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
Message-ID: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

This is a meta issue for fixing broken references in the documentation. I will open a child issues for some groups of modules and finally provide a patch for rest files.

----------
assignee: docs at python
components: Documentation
messages: 195392
nosy: docs at python, eric.araujo, ezio.melotti, georg.brandl, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Fix internal references in the documentation
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Aug 16 20:39:56 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 18:39:56 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1376678396.37.0.848924796002.issue18758@psf.upfronthosting.co.za>


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


----------
dependencies: +Fix internal references for concurrent modules, References to non-existant "StringIO" module

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

From report at bugs.python.org  Fri Aug 16 21:22:35 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 19:22:35 +0000
Subject: [docs] [issue18759] Fix internal doc references for logging package
Message-ID: <1376680954.66.0.549191685954.issue18759@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a patch which fixes internal references in the documentation of the logging package.

----------
assignee: docs at python
components: Documentation
files: refs.logging.diff
keywords: patch
messages: 195401
nosy: docs at python, eric.araujo, ezio.melotti, georg.brandl, serhiy.storchaka, vinay.sajip
priority: normal
severity: normal
stage: patch review
status: open
title: Fix internal doc references for logging package
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file31324/refs.logging.diff

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

From ezio.melotti at gmail.com  Fri Aug 16 21:31:56 2013
From: ezio.melotti at gmail.com (ezio.melotti at gmail.com)
Date: Fri, 16 Aug 2013 19:31:56 -0000
Subject: [docs] Fix internal references for concurrent modules (issue 18757)
Message-ID: <20130816193156.9672.73014@psf.upfronthosting.co.za>

LGTM.


http://bugs.python.org/review/18757/diff/8955/Doc/library/multiprocessing.rst
File Doc/library/multiprocessing.rst (right):

http://bugs.python.org/review/18757/diff/8955/Doc/library/multiprocessing.rst#newcode1071
Doc/library/multiprocessing.rst:1071: The :meth:`wait_for
<threading.Condition.wait_for>` method was added.
Isn't this equivalent to :meth:`~threading.Condition.wait_for`? or does
this include "Condition." too?

http://bugs.python.org/review/18757/diff/8955/Doc/library/multiprocessing.rst#newcode1478
Doc/library/multiprocessing.rst:1478: The :meth:`wait_for
<threading.Condition.wait_for>` method was added.
Ditto.

http://bugs.python.org/review/18757/diff/8955/Doc/library/select.rst
File Doc/library/select.rst (right):

http://bugs.python.org/review/18757/diff/8955/Doc/library/select.rst#newcode336
Doc/library/select.rst:336: :meth:`~~io.IOBase.fileno` method that
returns an integer.
Is the double ~ a typo or some syntax that I don't know?

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

From report at bugs.python.org  Fri Aug 16 21:34:45 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 16 Aug 2013 19:34:45 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1376681685.31.0.119940554602.issue18758@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Note that not all the targets should be converted to links.  They should be converted only if the link is useful, and usually redundant links are not necessary (e.g. if the same target is repeated several times in the same paragraph/section).

----------

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

From report at bugs.python.org  Fri Aug 16 21:38:19 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 19:38:19 +0000
Subject: [docs] [issue18760] Fix internal doc references for the xml package
Message-ID: <1376681899.06.0.47911099673.issue18760@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a patch which fixes internal references in the documentation of the xml package.

----------
assignee: docs at python
components: Documentation
messages: 195404
nosy: christian.heimes, docs at python, eli.bendersky, eric.araujo, ezio.melotti, georg.brandl, scoder, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Fix internal doc references for the xml package
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Aug 16 21:39:36 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 19:39:36 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1376681976.33.0.756385366792.issue18758@psf.upfronthosting.co.za>


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


----------
dependencies: +Fix internal doc references for logging package, Fix internal doc references for the xml package

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

From report at bugs.python.org  Fri Aug 16 21:41:02 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 19:41:02 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1376682062.44.0.107758515694.issue18758@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

In such case perhaps links should be explicitly prohibited (with '!' mark).

----------

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

From report at bugs.python.org  Fri Aug 16 21:47:32 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 19:47:32 +0000
Subject: [docs] [issue18761] Fix internal doc references for the email
	package
Message-ID: <1376682451.08.0.523486132403.issue18761@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a preliminary patch (long lines are not wrapped yet) which fixes internal references in the documentation of the email package.

----------
assignee: docs at python
components: Documentation
files: refs.email.diff
keywords: patch
messages: 195406
nosy: barry, docs at python, eric.araujo, ezio.melotti, georg.brandl, r.david.murray, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Fix internal doc references for the email package
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file31326/refs.email.diff

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

From report at bugs.python.org  Fri Aug 16 22:20:59 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 16 Aug 2013 20:20:59 +0000
Subject: [docs] [issue18729] In unittest.TestLoader.discover doc select the
	name of	load_tests function
In-Reply-To: <1376418287.73.0.835584535115.issue18729@psf.upfronthosting.co.za>
Message-ID: <1376684459.94.0.651240217791.issue18729@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti, michael.foord
stage:  -> patch review

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

From report at bugs.python.org  Fri Aug 16 22:29:26 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 16 Aug 2013 20:29:26 +0000
Subject: [docs] [issue18743] References to non-existant "StringIO" module
In-Reply-To: <1376542911.78.0.658455842148.issue18743@psf.upfronthosting.co.za>
Message-ID: <1376684966.82.0.209331927031.issue18743@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

LGTM

----------
nosy: +terry.reedy
stage: patch review -> commit review
type:  -> behavior

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

From report at bugs.python.org  Fri Aug 16 22:39:00 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 16 Aug 2013 20:39:00 +0000
Subject: [docs] [issue18736] Invalid charset in HTML pages inside
	documentation in	CHM format
In-Reply-To: <1376481546.2.0.725412367622.issue18736@psf.upfronthosting.co.za>
Message-ID: <1376685540.19.0.526989563886.issue18736@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

This is a problem with Sphinx and should be reported upstream.
These encondings are defined in the htmlhelp builder and they are recognized by Python, but indeed they shouldn't end up in the meta tag.

----------
assignee: docs at python -> georg.brandl
nosy: +ezio.melotti, georg.brandl
status: open -> pending
type:  -> behavior

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

From report at bugs.python.org  Fri Aug 16 22:46:45 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 16 Aug 2013 20:46:45 +0000
Subject: [docs] [issue18741] Fix typos/spelling mistakes in Lib/*/*/.py files
In-Reply-To: <1376515284.41.0.228001908428.issue18741@psf.upfronthosting.co.za>
Message-ID: <1376686005.95.0.511923194964.issue18741@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti
stage:  -> patch review

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

From report at bugs.python.org  Fri Aug 16 22:47:36 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 16 Aug 2013 20:47:36 +0000
Subject: [docs] [issue18705] Fix typos/spelling mistakes in Lib/*.py files
In-Reply-To: <1376178317.79.0.772879564661.issue18705@psf.upfronthosting.co.za>
Message-ID: <1376686056.26.0.347750869316.issue18705@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

See also #18741.

----------

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

From report at bugs.python.org  Fri Aug 16 23:13:15 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 16 Aug 2013 21:13:15 +0000
Subject: [docs] [issue18743] References to non-existant "StringIO" module
In-Reply-To: <1376542911.78.0.658455842148.issue18743@psf.upfronthosting.co.za>
Message-ID: <3cGy1R1gYzz7LjN@mail.python.org>


Roundup Robot added the comment:

New changeset b23ad357c214 by Serhiy Storchaka in branch '3.3':
Issue #18743: Fix references to non-existant "StringIO" module.
http://hg.python.org/cpython/rev/b23ad357c214

New changeset 3acbd7aca856 by Serhiy Storchaka in branch 'default':
Issue #18743: Fix references to non-existant "StringIO" module.
http://hg.python.org/cpython/rev/3acbd7aca856

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

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

From report at bugs.python.org  Fri Aug 16 23:16:39 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 21:16:39 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1376687799.45.0.478539314581.issue18758@psf.upfronthosting.co.za>


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


----------
dependencies: +Fix internal doc references for the email package

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

From rdmurray at bitdance.com  Fri Aug 16 23:31:43 2013
From: rdmurray at bitdance.com (rdmurray at bitdance.com)
Date: Fri, 16 Aug 2013 21:31:43 -0000
Subject: [docs] Fix internal doc references for the email package (issue
	18761)
Message-ID: <20130816213143.25104.32384@psf.upfronthosting.co.za>


http://bugs.python.org/review/18761/diff/8959/Doc/library/email.errors.rst
File Doc/library/email.errors.rst (left):

http://bugs.python.org/review/18761/diff/8959/Doc/library/email.errors.rst#oldcode50
Doc/library/email.errors.rst:50: :meth:`add_payload`, but the payload is
already a scalar and the message's
add_payload no longer exists.

http://bugs.python.org/review/18761/diff/8959/Doc/library/email.headerregistry.rst
File Doc/library/email.headerregistry.rst (left):

http://bugs.python.org/review/18761/diff/8959/Doc/library/email.headerregistry.rst#oldcode59
Doc/library/email.headerregistry.rst:59: is exactly the value passed in
the :attr:`~EmailPolicy.header_factory`
Hmm.  I would have though that this would work, being in the same rst
file.  Oh well.

http://bugs.python.org/review/18761/diff/8959/Doc/library/email.message.rst
File Doc/library/email.message.rst (right):

http://bugs.python.org/review/18761/diff/8959/Doc/library/email.message.rst#newcode316
Doc/library/email.message.rst:316: :meth:`~object.__getitem__` except
that optional *failobj* is returned if the
This change is incorrect.  The original construct correctly links to
Message's __getitem__.

http://bugs.python.org/review/18761/diff/8959/Doc/library/email.message.rst#newcode331
Doc/library/email.message.rst:331: Extended header setting.  This method
is similar to :meth:`~object.__setitem__`
This change is also incorrect.

http://bugs.python.org/review/18761/diff/8959/Doc/library/email.policy.rst
File Doc/library/email.policy.rst (right):

http://bugs.python.org/review/18761/diff/8959/Doc/library/email.policy.rst#newcode318
Doc/library/email.policy.rst:318: :mod:`email.policy` module also
defines an instance of this class,
missing ~.

http://bugs.python.org/review/18761/diff/8959/Doc/library/email.rst
File Doc/library/email.rst (right):

http://bugs.python.org/review/18761/diff/8959/Doc/library/email.rst#newcode174
Doc/library/email.rst:174: :class:`~email.mime.text.MIMEText`
constructor, the :meth:`Message.add_payload` method, the
Don't we need ~email.message here as well?

http://bugs.python.org/review/18761/diff/8959/Doc/library/email.rst#newcode205
Doc/library/email.rst:205: false, :meth:`get_payload` was not a list
object, but a single :class:`~email.message.Message`
Don't we need ~email.message.Message here?

http://bugs.python.org/review/18761/diff/8959/Doc/library/email.rst#newcode217
Doc/library/email.rst:217: doesn't do a :meth:`set_payload` with a
:class:`~email.message.Message` instance on a container
~email.message.Message.set_payload?

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

From ezio.melotti at gmail.com  Fri Aug 16 23:38:47 2013
From: ezio.melotti at gmail.com (ezio.melotti at gmail.com)
Date: Fri, 16 Aug 2013 21:38:47 -0000
Subject: [docs] Fix internal doc references for the email package (issue
	18761)
Message-ID: <20130816213847.25104.77702@psf.upfronthosting.co.za>


http://bugs.python.org/review/18761/diff/8959/Doc/library/email.rst
File Doc/library/email.rst (right):

http://bugs.python.org/review/18761/diff/8959/Doc/library/email.rst#newcode300
Doc/library/email.rst:300: * The method :meth:`setboundary` was renamed
to :meth:`~email.message.Message.set_boundary`.
Is there any way to either set a shortcut somewhere for
email.message.Message or set is as current class/module?

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

From rdmurray at bitdance.com  Fri Aug 16 23:40:49 2013
From: rdmurray at bitdance.com (rdmurray at bitdance.com)
Date: Fri, 16 Aug 2013 21:40:49 -0000
Subject: [docs] Fix internal doc references for the email package (issue
	18761)
Message-ID: <20130816214049.25104.1426@psf.upfronthosting.co.za>

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

From report at bugs.python.org  Fri Aug 16 23:55:44 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 21:55:44 +0000
Subject: [docs] [issue18744] pathological performance using tarfile
In-Reply-To: <1376544025.63.0.959353089302.issue18744@psf.upfronthosting.co.za>
Message-ID: <1376690144.69.0.313597234283.issue18744@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

I think in most cases peoples extracts archives in natural order and don't have a failure.

But adding a warning looks reasonable.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python
stage:  -> needs patch
versions: +Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Aug 16 23:57:40 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 16 Aug 2013 21:57:40 +0000
Subject: [docs] [issue18741] Fix typos/spelling mistakes in Lib/*/*/.py files
In-Reply-To: <1376515284.41.0.228001908428.issue18741@psf.upfronthosting.co.za>
Message-ID: <1376690260.52.0.277023063246.issue18741@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


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

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

From report at bugs.python.org  Fri Aug 16 23:57:50 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 16 Aug 2013 21:57:50 +0000
Subject: [docs] [issue18705] Fix typos/spelling mistakes in Lib/*.py files
In-Reply-To: <1376178317.79.0.772879564661.issue18705@psf.upfronthosting.co.za>
Message-ID: <1376690270.14.0.972050959928.issue18705@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


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

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

From report at bugs.python.org  Sat Aug 17 00:04:48 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 22:04:48 +0000
Subject: [docs] [issue18757] Fix internal references for concurrent modules
In-Reply-To: <1376675015.24.0.101209198038.issue18757@psf.upfronthosting.co.za>
Message-ID: <1376690687.57.0.338470775907.issue18757@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Here is updated patch. Thank Ezio for found errors.

----------
Added file: http://bugs.python.org/file31328/refs.concurrect.diff

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

From report at bugs.python.org  Sat Aug 17 00:07:56 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 16 Aug 2013 22:07:56 +0000
Subject: [docs] [issue18705] Fix typos/spelling mistakes in Lib/*.py files
In-Reply-To: <1376178317.79.0.772879564661.issue18705@psf.upfronthosting.co.za>
Message-ID: <1376690876.37.0.447850262721.issue18705@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

I'm not spelling expert Antoine. :-)

----------

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

From report at bugs.python.org  Sat Aug 17 01:00:26 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 16 Aug 2013 23:00:26 +0000
Subject: [docs] [issue18760] Fix internal doc references for the xml package
In-Reply-To: <1376681899.06.0.47911099673.issue18760@psf.upfronthosting.co.za>
Message-ID: <1376694026.11.0.870056383327.issue18760@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Aug 17 01:05:23 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 16 Aug 2013 23:05:23 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1376694323.91.0.207622183004.issue18758@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

That's probably not worth it.

----------

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

From report at bugs.python.org  Sat Aug 17 01:34:51 2013
From: report at bugs.python.org (Vinay Sajip)
Date: Fri, 16 Aug 2013 23:34:51 +0000
Subject: [docs] [issue18759] Fix internal doc references for logging package
In-Reply-To: <1376680954.66.0.549191685954.issue18759@psf.upfronthosting.co.za>
Message-ID: <1376696091.78.0.0545693950957.issue18759@psf.upfronthosting.co.za>


Changes by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
assignee: docs at python -> vinay.sajip

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

From report at bugs.python.org  Sat Aug 17 01:40:56 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 16 Aug 2013 23:40:56 +0000
Subject: [docs] [issue18759] Fix internal doc references for logging package
In-Reply-To: <1376680954.66.0.549191685954.issue18759@psf.upfronthosting.co.za>
Message-ID: <3cH1Hr10ktzRTR@mail.python.org>


Roundup Robot added the comment:

New changeset aea67c35e3ce by Vinay Sajip in branch '2.7':
Issue #18759: Improved cross-references in logging documentation.
http://hg.python.org/cpython/rev/aea67c35e3ce

New changeset 80c475617608 by Vinay Sajip in branch '3.3':
Issue #18759: Improved cross-references in logging documentation.
http://hg.python.org/cpython/rev/80c475617608

New changeset 9580f237139f by Vinay Sajip in branch 'default':
Issue #18759: Merged updates from 3.3.
http://hg.python.org/cpython/rev/9580f237139f

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

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

From report at bugs.python.org  Sat Aug 17 04:24:13 2013
From: report at bugs.python.org (Brian McLaughlin)
Date: Sat, 17 Aug 2013 02:24:13 +0000
Subject: [docs] [issue18767] csv documentation does not note default quote
	constant
Message-ID: <1376706253.43.0.482794872786.issue18767@psf.upfronthosting.co.za>


New submission from Brian McLaughlin:

Documentation should note default quoting behavior of the csv module is csv.QUOTE_MINIMAL

http://hg.python.org/cpython/file/tip/Modules/_csv.c#l420

----------
assignee: docs at python
components: Documentation
files: doc.patch
keywords: patch
messages: 195448
nosy: bemclaugh, docs at python
priority: normal
severity: normal
status: open
title: csv documentation does not note default quote constant
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5
Added file: http://bugs.python.org/file31333/doc.patch

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

From report at bugs.python.org  Sat Aug 17 10:04:20 2013
From: report at bugs.python.org (R. David Murray)
Date: Sat, 17 Aug 2013 08:04:20 +0000
Subject: [docs] [issue18767] csv documentation does not note default quote
	constant
In-Reply-To: <1376706253.43.0.482794872786.issue18767@psf.upfronthosting.co.za>
Message-ID: <1376726660.2.0.220192868034.issue18767@psf.upfronthosting.co.za>


R. David Murray added the comment:

Well, it does say that QUOTE_MINIMAL is the default for the dialect 'quoting' attribute.  What it doesn't say is that the default dialect (excel) is exactly the documented default values for all the dialect parameters.  (Although having said that, I'm not 100% sure it is true, I didn't fully check the correspondence).

----------
nosy: +r.david.murray
versions:  -Python 2.6, Python 3.1, Python 3.2, Python 3.5

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

From report at bugs.python.org  Sat Aug 17 14:54:29 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 17 Aug 2013 12:54:29 +0000
Subject: [docs] [issue18705] Fix typos/spelling mistakes in Lib/*.py files
In-Reply-To: <1376178317.79.0.772879564661.issue18705@psf.upfronthosting.co.za>
Message-ID: <3cHLvS6pB7z7LjP@mail.python.org>


Roundup Robot added the comment:

New changeset d234dd21374a by Ezio Melotti in branch '2.7':
#18705: fix a number of typos.  Patch by F?vry Thibault.
http://hg.python.org/cpython/rev/d234dd21374a

New changeset e07f104133d5 by Ezio Melotti in branch '3.3':
#18705: fix a number of typos.  Patch by F?vry Thibault.
http://hg.python.org/cpython/rev/e07f104133d5

New changeset a9ee869cae40 by Ezio Melotti in branch 'default':
#18705: merge with 3.3.
http://hg.python.org/cpython/rev/a9ee869cae40

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

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

From report at bugs.python.org  Sat Aug 17 14:56:22 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 17 Aug 2013 12:56:22 +0000
Subject: [docs] [issue18705] Fix typos/spelling mistakes in Lib/*.py files
In-Reply-To: <1376178317.79.0.772879564661.issue18705@psf.upfronthosting.co.za>
Message-ID: <1376744182.3.0.358430856146.issue18705@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the report and the patch!

----------
assignee: docs at python -> ezio.melotti
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed
versions: +Python 2.7

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

From report at bugs.python.org  Sat Aug 17 15:14:24 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 17 Aug 2013 13:14:24 +0000
Subject: [docs] [issue18741] Fix typos/spelling mistakes in Lib/*/*/.py files
In-Reply-To: <1376515284.41.0.228001908428.issue18741@psf.upfronthosting.co.za>
Message-ID: <3cHMLS0MXkz7LjP@mail.python.org>


Roundup Robot added the comment:

New changeset 5295ed192ffd by Ezio Melotti in branch '2.7':
#18741: fix more typos.  Patch by F?vry Thibault.
http://hg.python.org/cpython/rev/5295ed192ffd

New changeset 9e4685d703d4 by Ezio Melotti in branch '3.3':
#18741: fix more typos.  Patch by F?vry Thibault.
http://hg.python.org/cpython/rev/9e4685d703d4

New changeset b3236989f869 by Ezio Melotti in branch 'default':
#18741: merge with 3.3.
http://hg.python.org/cpython/rev/b3236989f869

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

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

From report at bugs.python.org  Sat Aug 17 15:15:15 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 17 Aug 2013 13:15:15 +0000
Subject: [docs] [issue18741] Fix typos/spelling mistakes in Lib/*/*/.py files
In-Reply-To: <1376515284.41.0.228001908428.issue18741@psf.upfronthosting.co.za>
Message-ID: <1376745315.45.0.959097837756.issue18741@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the patch!

----------
assignee: docs at python -> ezio.melotti
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Sat Aug 17 15:24:47 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 17 Aug 2013 13:24:47 +0000
Subject: [docs] [issue18759] Fix internal doc references for logging package
In-Reply-To: <1376680954.66.0.549191685954.issue18759@psf.upfronthosting.co.za>
Message-ID: <1376745887.81.0.0322801696883.issue18759@psf.upfronthosting.co.za>


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


----------
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed
type:  -> enhancement

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

From report at bugs.python.org  Sat Aug 17 16:13:13 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 17 Aug 2013 14:13:13 +0000
Subject: [docs] [issue15248] Better explain "TypeError: 'tuple' object is
	not	callable"
In-Reply-To: <1341379722.78.0.0866285571225.issue15248@psf.upfronthosting.co.za>
Message-ID: <1376748793.02.0.302937655843.issue15248@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
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Sat Aug 17 16:14:23 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 17 Aug 2013 14:14:23 +0000
Subject: [docs] [issue6916] Remove deprecated items from asynchat
In-Reply-To: <1252994156.96.0.167712988312.issue6916@psf.upfronthosting.co.za>
Message-ID: <1376748863.45.0.600388234822.issue6916@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

What's the status of this?

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

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

From report at bugs.python.org  Sat Aug 17 16:30:38 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 17 Aug 2013 14:30:38 +0000
Subject: [docs] [issue17232] Improve -O docs
In-Reply-To: <1361255101.21.0.948205073894.issue17232@psf.upfronthosting.co.za>
Message-ID: <1376749838.49.0.473443027545.issue17232@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Terry, do you want to update your patch?

----------
versions:  -Python 3.2

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

From report at bugs.python.org  Sat Aug 17 17:02:21 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 17 Aug 2013 15:02:21 +0000
Subject: [docs] [issue18553] os.isatty() is not Unix only
In-Reply-To: <1374752779.81.0.230915084667.issue18553@psf.upfronthosting.co.za>
Message-ID: <1376751740.97.0.112719975125.issue18553@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Are there tests for this?

----------
components: +Tests
keywords: +easy
nosy: +ezio.melotti

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

From report at bugs.python.org  Sat Aug 17 17:15:39 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Sat, 17 Aug 2013 15:15:39 +0000
Subject: [docs] [issue18768] Wrong documentation of RAND_egd function in ssl
	module
Message-ID: <1376752539.41.0.731008742763.issue18768@psf.upfronthosting.co.za>


New submission from Vajrasky Kok:

>>> import ssl
>>> ssl.RAND_egd.__doc__
"RAND_egd(path) -> bytes\n\nQueries the entropy gather daemon (EGD) on the socket named by 'path'.\nReturns number of bytes read.  Raises SSLError if connection to EGD\nfails or if it does provide enough data to seed PRNG."

Compare it to documentation about RAND_egd() function from openssl website (https://www.openssl.org/docs/crypto/RAND_egd.html):

RAND_egd() and RAND_egd_bytes() return the number of bytes read from the daemon on success, and -1 if the connection failed or the daemon did not return enough data to fully seed the PRNG. 

Attached the patch to fix the documentation. I am not sure whether we should put the word "fully" or not.

On the side note:
In line 813 in Modules/_ssl.c (the same file where my patch fixed the documentation about RAND_egd function):

gntype = name-> type;

The space between "->" and "type" irritates my eyes. Maybe we can fix this while we fix the documentation? Anyway, this is not really important. I just want to expose it to public and think this does not deserve a dedicated ticket.

----------
assignee: docs at python
components: Documentation
files: fix_documentation_on_rand_egd_function.patch
keywords: patch
messages: 195482
nosy: christian.heimes, docs at python, vajrasky
priority: normal
severity: normal
status: open
title: Wrong documentation of RAND_egd function in ssl module
versions: Python 3.3, Python 3.4
Added file: http://bugs.python.org/file31338/fix_documentation_on_rand_egd_function.patch

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

From report at bugs.python.org  Sat Aug 17 17:16:00 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 17 Aug 2013 15:16:00 +0000
Subject: [docs] [issue15939] make *.rst files in Doc/ parseable by doctest
In-Reply-To: <1347543698.43.0.179468389771.issue15939@psf.upfronthosting.co.za>
Message-ID: <1376752559.84.0.747235558081.issue15939@psf.upfronthosting.co.za>


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


----------
type:  -> enhancement
versions:  -Python 3.2
Added file: http://bugs.python.org/file31339/issue15939-ctypes-2.diff

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

From report at bugs.python.org  Sat Aug 17 17:19:54 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 17 Aug 2013 15:19:54 +0000
Subject: [docs] [issue18768] Wrong documentation of RAND_egd function in ssl
	module
In-Reply-To: <1376752539.41.0.731008742763.issue18768@psf.upfronthosting.co.za>
Message-ID: <3cHQ7F1tJdz7Lk7@mail.python.org>


Roundup Robot added the comment:

New changeset b352a5cb60b6 by Christian Heimes in branch '3.3':
Issue #18768: coding style nitpick. Thanks to Vajrasky Kok
http://hg.python.org/cpython/rev/b352a5cb60b6

New changeset fe444f324756 by Christian Heimes in branch 'default':
Issue #18768: coding style nitpick. Thanks to Vajrasky Kok
http://hg.python.org/cpython/rev/fe444f324756

New changeset a8787a6fa107 by Christian Heimes in branch '2.7':
Issue #18768: coding style nitpick. Thanks to Vajrasky Kok
http://hg.python.org/cpython/rev/a8787a6fa107

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

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

From report at bugs.python.org  Sat Aug 17 17:20:58 2013
From: report at bugs.python.org (Christian Heimes)
Date: Sat, 17 Aug 2013 15:20:58 +0000
Subject: [docs] [issue18768] Wrong documentation of RAND_egd function in ssl
	module
In-Reply-To: <1376752539.41.0.731008742763.issue18768@psf.upfronthosting.co.za>
Message-ID: <1376752858.88.0.282009683953.issue18768@psf.upfronthosting.co.za>


Christian Heimes added the comment:

Thanks, I have removed the extra space in gntype = name-> type;

----------

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

From report at bugs.python.org  Sat Aug 17 17:26:16 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 17 Aug 2013 15:26:16 +0000
Subject: [docs] [issue18768] Wrong documentation of RAND_egd function in ssl
	module
In-Reply-To: <1376752539.41.0.731008742763.issue18768@psf.upfronthosting.co.za>
Message-ID: <3cHQGc1rR8zT2B@mail.python.org>


Roundup Robot added the comment:

New changeset ae91252943bf by Christian Heimes in branch '3.3':
Issue 18768: Correct doc string of RAND_edg(). Patch by Vajrasky Kok.
http://hg.python.org/cpython/rev/ae91252943bf

New changeset 5c091acc799f by Christian Heimes in branch 'default':
Issue 18768: Correct doc string of RAND_edg(). Patch by Vajrasky Kok.
http://hg.python.org/cpython/rev/5c091acc799f

New changeset 31389495cdbf by Christian Heimes in branch '2.7':
Issue 18768: Correct doc string of RAND_edg(). Patch by Vajrasky Kok.
http://hg.python.org/cpython/rev/31389495cdbf

----------

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

From report at bugs.python.org  Sat Aug 17 17:27:17 2013
From: report at bugs.python.org (Christian Heimes)
Date: Sat, 17 Aug 2013 15:27:17 +0000
Subject: [docs] [issue18768] Wrong documentation of RAND_egd function in ssl
	module
In-Reply-To: <1376752539.41.0.731008742763.issue18768@psf.upfronthosting.co.za>
Message-ID: <1376753237.81.0.287540821809.issue18768@psf.upfronthosting.co.za>


Christian Heimes added the comment:

Thanks :)

----------
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Sun Aug 18 02:34:20 2013
From: report at bugs.python.org (A.M. Kuchling)
Date: Sun, 18 Aug 2013 00:34:20 +0000
Subject: [docs] [issue18562] Regex howto: revision pass
In-Reply-To: <1374854855.56.0.787824851556.issue18562@psf.upfronthosting.co.za>
Message-ID: <1376786059.51.0.537951236723.issue18562@psf.upfronthosting.co.za>


A.M. Kuchling added the comment:

Slightly revised version that modifies the discussion of when to pre-compile a regex and when to not bother.  I don't think this is a very important issue, so I don't think it needs a long discussion.

----------
Added file: http://bugs.python.org/file31348/regex.diff

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

From report at bugs.python.org  Sun Aug 18 02:44:15 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sun, 18 Aug 2013 00:44:15 +0000
Subject: [docs] [issue18562] Regex howto: revision pass
In-Reply-To: <1374854855.56.0.787824851556.issue18562@psf.upfronthosting.co.za>
Message-ID: <1376786655.29.0.853291513116.issue18562@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Well, this is already too long IMO. Two sentences should suffice. If you are calling a regex very often in a loop, then it makes sense to compile it. Otherwise, don't bother.

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

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

From report at bugs.python.org  Sun Aug 18 17:27:32 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 18 Aug 2013 15:27:32 +0000
Subject: [docs] [issue18562] Regex howto: revision pass
In-Reply-To: <1374854855.56.0.787824851556.issue18562@psf.upfronthosting.co.za>
Message-ID: <1376839652.86.0.192392030366.issue18562@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

#17441 also has a discussion about regex caching that might be relevant.

----------

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

From bart.aelterman at gmail.com  Fri Aug  2 12:06:49 2013
From: bart.aelterman at gmail.com (Bart Aelterman)
Date: Fri, 02 Aug 2013 10:06:49 -0000
Subject: [docs] possible bug in regular expression documentation
Message-ID: <CAP+wG8OTZwahuzz44FA_7jWhH+KL28rseX0t_9fgXgepqC9hBw@mail.gmail.com>

Dear,

While reading the python documentation, chapter 7.2 "Regular expression
operations", I noticed a sentence that could be experienced as confusing:

"
\d
When the UNICODE flag is not specified, matches any decimal digit; this is
equivalent to the set [0-9]. With UNICODE, it will match whatever is
classified as a decimal digit in the Unicode character properties database.
"

I have a problem with "decimal digit". These patterns match only one
character. Therefore, one character can never be decimal, as that would
imply the presence of at least one digit and a decimal character (dot). I
would propose to delete the word "decimal". \d matches a digit.
Unless you want to say that \d+ matches a decimal digit, for instance
"2.2". But when I try that in ipython, \d+ only matches "2".

I hope my comment was helpful!

Thanks for all the great efforts!

Bart
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130802/c6ed7181/attachment.html>

From bendwarn at gmail.com  Mon Aug 12 20:31:44 2013
From: bendwarn at gmail.com (=?Big5?B?uK3aervK?=)
Date: Tue, 13 Aug 2013 02:31:44 +0800
Subject: [docs] Template files in documentation sources
Message-ID: <CALmm8Uot07Uhaa8mmRLzH60CrcV0Q2vH3=PMifdH31Q+_8_xXw@mail.gmail.com>

Hello,

I am Eric from Taiwan. I would like to translate the documentation to
Chinese (not simplified) and host it on readthedocs. Of course, I use
sphinx and complete the setup so that I can make html with the files
downloaded from docs.python.org, but I find that the generated index.html
looks not the same as the official website. After studying for a while, I
know I can create other htmls with template through conf.py, and I cannot
find the template used by the documentation anywhere, even in the offcial
mirror or similar projects on readthedocs.

Could I ask those files not provided at the download page? Thank you.

Best regards,
Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130813/ea8a850a/attachment.html>

From bendwarn at gmail.com  Tue Aug 13 04:21:05 2013
From: bendwarn at gmail.com (=?Big5?B?uK3aervK?=)
Date: Tue, 13 Aug 2013 10:21:05 +0800
Subject: [docs] Template files in documentation sources
In-Reply-To: <CALmm8Uot07Uhaa8mmRLzH60CrcV0Q2vH3=PMifdH31Q+_8_xXw@mail.gmail.com>
References: <CALmm8Uot07Uhaa8mmRLzH60CrcV0Q2vH3=PMifdH31Q+_8_xXw@mail.gmail.com>
Message-ID: <CALmm8Upg+RJsTyYe147tnReZQfCw7WYDUhSjeViDF5X6gn2-fA@mail.gmail.com>

Hello,

Sorry, I finally find that in cpython mirror, sorry for annoying you.

Best regards,
Eric


2013/8/13 ??? <bendwarn at gmail.com>

> Hello,
>
> I am Eric from Taiwan. I would like to translate the documentation to
> Chinese (not simplified) and host it on readthedocs. Of course, I use
> sphinx and complete the setup so that I can make html with the files
> downloaded from docs.python.org, but I find that the generated index.html
> looks not the same as the official website. After studying for a while, I
> know I can create other htmls with template through conf.py, and I cannot
> find the template used by the documentation anywhere, even in the offcial
> mirror or similar projects on readthedocs.
>
> Could I ask those files not provided at the download page? Thank you.
>
> Best regards,
> Eric
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130813/2a507b78/attachment.html>

From erichiggins at gmail.com  Mon Aug  5 23:13:36 2013
From: erichiggins at gmail.com (Eric Higgins)
Date: Mon, 5 Aug 2013 14:13:36 -0700
Subject: [docs] Minor mistake on HTMLParser docs
Message-ID: <CAHfxMJ6CZ5cPySYMVXbdMf7WOROGoxJo2gOHOyhCosv5XtgUkQ@mail.gmail.com>

Greetings,

There's a minor mistake on the doc page for the HTMLParser
module<http://docs.python.org/2/library/htmlparser.html>
.

The last snippet labeled: "*Parsing invalid HTML (e.g. unquoted attributes)
also works:*" is mistaken in assuming that unquoted attributes are invalid.

  >>> parser.feed('<p><a class=link href=#main>tag soup</p ></a>')
  ...

According to the
HTML4<http://www.w3.org/TR/REC-html40/intro/sgmltut.html#h-3.2.2>and
HTML5 <http://dev.w3.org/html5/markup/syntax.html#syntax-attr-unquoted>attribute
syntax spec, the example you provide are actually perfectly valid
attribute definitions. You could add a space or other breaking/invalid
character to the attribute value to correct it.

Thanks!
-Eric Higgins
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130805/9fda78bc/attachment.html>

From zhangpeipei812 at outlook.com  Thu Aug  8 14:48:58 2013
From: zhangpeipei812 at outlook.com (=?gb2312?B?1cXF5cXl?=)
Date: Thu, 8 Aug 2013 20:48:58 +0800
Subject: [docs] There is a spelling mistakes in Python source code
Message-ID: <BLU402-EAS1031633E217291364CBAFFF9D5F0@phx.gbl>

Hello:
	I found there is a spelling mistakes in Python source code comment.
In file:
	Python\lib\_pyio.py
Line 413:
	        """closed: bool.  True iff the file has been closed.
Best regards!
peipei

From drazen.lucanin at gmail.com  Fri Aug  9 19:21:37 2013
From: drazen.lucanin at gmail.com (=?ISO-8859-2?Q?Dra=BEen_Lu=E8anin?=)
Date: Fri, 9 Aug 2013 19:21:37 +0200
Subject: [docs] Confusing default redirects
Message-ID: <CADg_278+dmzttUKo+esTQMh+tCZDr0jG1-9_FXzXw3Ln-dMmaA@mail.gmail.com>

Dear Sir/Madam,

When I open http://docs.python.org/ it redirects me to http://docs.python.org/3/

When I open http://docs.python.org/library/ it redirects me to
http://docs.python.org/2/library/

Expected - all "versionless" URLs should redirect to the same (current
stable and recommended) version of Python.

Regards,
Dra?en Lu?anin

From report at bugs.python.org  Sun Aug 18 19:52:00 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 18 Aug 2013 17:52:00 +0000
Subject: [docs] [issue18743] References to non-existant "StringIO" module
In-Reply-To: <1376542911.78.0.658455842148.issue18743@psf.upfronthosting.co.za>
Message-ID: <1376848320.57.0.572399781902.issue18743@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Here is a patch which fixes references to StringIO in docstrings and comments and removes redundant code.

----------
Added file: http://bugs.python.org/file31362/src_StringIO_refs.patch

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

From issaria at gmail.com  Fri Aug  2 16:01:59 2013
From: issaria at gmail.com (Issaria Peng)
Date: Fri, 02 Aug 2013 14:01:59 -0000
Subject: [docs] Possible document issue.
Message-ID: <CAFxYmVoHjn35=U4RFsq2YW+syFCw3mujxF2YO=2wa-mY-zbrpA@mail.gmail.com>

Hi,

http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst

509<http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l509>
/*
Time to call the callback */
 510<http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l510>
arglist
= Py_BuildValue("(i)", arg);
 511<http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l511>
result
= PyObject_CallObject(my_callback, arglist);
 512<http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l512>
Py_DECREF(arglist);
 513<http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l513>
 514<http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l514>
:c:func:`PyObject_CallObject`
returns a Python object pointer: this is the return
 515<http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l515>value
of the Python function.
:c:func:`PyObject_CallObject` is
 516<http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l516>"reference-count-neutral"
with respect to its arguments. In the example a
new
 517<http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l517>tuple
was created to serve as the argument list, which is
:c:func:`Py_DECREF`\
 518<http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l518>-ed
immediately after the call.

According to the explain directly after the code, line 512 should be:

Py_DECREF(result);

Regards,
Isaiah Peng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130802/f0aadff5/attachment-0001.html>

From hariharanrangasamy at gmail.com  Mon Aug  5 07:30:23 2013
From: hariharanrangasamy at gmail.com (Hariharan Rangasamy)
Date: Mon, 5 Aug 2013 11:00:23 +0530
Subject: [docs] 5-Minutes with Python [video not found bug]
Message-ID: <CAGkYVKmWQO732_MhmFs0ZupSePUu465tgxfPnAoiQF5_vF8DeA@mail.gmail.com>

Can't watch any of the videos in "5 Minutes with Python: A Video
Series" (http://www.python.org/doc/av/5minutes/), when i play the
video, it shows "video not found error".

But these videos exists in the original website showmedo.com. I can
actually watch these videos in the showmedo.com.

From madan_ram at rocketmail.com  Sat Aug 10 20:04:44 2013
From: madan_ram at rocketmail.com (Madan Ram)
Date: Sat, 10 Aug 2013 11:04:44 -0700 (PDT)
Subject: [docs] Enhancement of faq/gui.html
Message-ID: <1376157884.45775.YahooMailNeo@web121902.mail.ne1.yahoo.com>

"Qt 4.5 upwards is licensed under the LGPL license; also, commercial licenses are available from Nokia." Since new version of Qt 5 is realsed and Licenced under Digia. So i am fixing this issue . i am going to write it as  PyQt5 is licensed on all platforms under a commercial license and the GPL v3. Your PyQt5 license must be compatible with your Qt license.
If you use the GPL version then your own code must also use a compatible license. Note:-PyQt5, unlike Qt, is not available under the LGPL. You can purchase a commercial PyQt5 license here.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130810/190c8c90/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gui.rst
Type: application/octet-stream
Size: 7450 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130810/190c8c90/attachment-0001.obj>

From jeanoliveiralopes at gmail.com  Sun Aug 11 17:22:40 2013
From: jeanoliveiralopes at gmail.com (jean Lopes)
Date: Sun, 11 Aug 2013 12:22:40 -0300
Subject: [docs] I want to report a error on python tutorial
Message-ID: <CAEh6n9px3CpnuW7Ms-c4dEzgQrSP3xRKSFmeCE_z61KwnTtwNw@mail.gmail.com>

Hello manager of python documentation,

I want to report a little error on tutorial. Follows the links:

http://docs.python.org/2/tutorial/datastructures.html#using-lists-as-stacks
http://docs.python.org/2/tutorial/datastructures.html#using-lists-as-queues

Just there is a small exchange in the explain of stacks and queues.

I hope to have helped.

-- 
-- 
Att,

*Jean Lopes*
Desenvolvedor .NET
@ www.RedeHost.com.br <http://www.redehost.com.br/>
Telefone: (51) 8149.8684
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130811/41278b67/attachment.html>

From georgegadvani at hsbc.com.hk  Thu Aug 15 05:08:53 2013
From: georgegadvani at hsbc.com.hk (georgegadvani at hsbc.com.hk)
Date: Thu, 15 Aug 2013 11:08:53 +0800
Subject: [docs] Defining new keyword (extension of default keywords) in
	Python 3.3.2
Message-ID: <OF6719A499.C60B1433-ON48257BC8.000F88E7-48257BC8.00116AA2@hsbc.asia>

Hi team,

Actually this is not a bug but a question.  I started using Python 
recently on building prototype analytics. 
FYI, my Python version is 3.3.2 &  I used  IPython/WinPython in 
development.
 


Basic packages are all installed, e.g.
numpy version is 1.7.1



scipy version is 0.12.0


Path & PythonPath settings as below:-



My question is related to this thread somebody posts on adding new 
keywords in Python.
http://stackoverflow.com/questions/214881/can-you-add-new-statements-to-pythons-syntax

Looking at the suggestions, there are couple of ways to achieve this and I 
prefer this way since it sounds easiest:-



However, I cannot simply use these statements owing to the following 
reasons:-

(i)  the new package is replaced by Types package;
(ii) In the Types Package (checking on documentation), there is nothing 
like types.module(  ....). How to re-write the statements ?





(iii) When I execute this line 
    exec data in mod.__dict__

I got  message like syntax error   highlighting  the word "data" 


My understanding is that this support group is runned on voluntary basis. 
Grateful if somebody may help and revert with valid examples that
can run on Python 3.3.2.

Thx & Rgds,

George Advani


-----------------------------------------
*******************************************************************
This e-mail is confidential. It may also be legally privileged.
If you are not the addressee you may not copy, forward, disclose
or use any part of it. If you have received this message in error,
please delete it and all copies from your system and notify the
sender immediately by return e-mail.

Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
*******************************************************************
"SAVE PAPER - THINK BEFORE YOU PRINT!" 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/85d51eb7/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 12546 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/85d51eb7/attachment-0007.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 10399 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/85d51eb7/attachment-0008.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 10512 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/85d51eb7/attachment-0009.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 13790 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/85d51eb7/attachment-0010.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 16600 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/85d51eb7/attachment-0011.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 5861 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/85d51eb7/attachment-0012.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 9130 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/85d51eb7/attachment-0013.gif>

From georgegadvani at hsbc.com.hk  Thu Aug 15 06:23:30 2013
From: georgegadvani at hsbc.com.hk (georgegadvani at hsbc.com.hk)
Date: Thu, 15 Aug 2013 12:23:30 +0800
Subject: [docs] Defining new keyword (extension of default keywords) in
	Python 3.3.2
In-Reply-To: <OF6719A499.C60B1433-ON48257BC8.000F88E7-48257BC8.00116AA2@LocalDomain>
References: <OF6719A499.C60B1433-ON48257BC8.000F88E7-48257BC8.00116AA2@LocalDomain>
Message-ID: <OFB4A2B038.B726986F-ON48257BC8.001803D1-48257BC8.00183FC6@hsbc.asia>

I did some research and found this article maybe of use, 

http://stackoverflow.com/questions/2315044/how-to-generate-a-module-object-from-a-code-object-in-python
Thus, I followed the example but not successful. The screen-dumps below 
illustrate the problem (iii)  in my last message.




Can you advice what's the right syntax for exec in this case ?



From:
George G ADVANI/HBAP/HSBC
To:
docs at python.org
Date:
08/15/2013 11:08 AM
Subject:
Defining new keyword (extension of default keywords) in Python 3.3.2


Hi team,

Actually this is not a bug but a question.  I started using Python 
recently on building prototype analytics. 
FYI, my Python version is 3.3.2 &  I used  IPython/WinPython in 
development.
 


Basic packages are all installed, e.g.
numpy version is 1.7.1



scipy version is 0.12.0


Path & PythonPath settings as below:-



My question is related to this thread somebody posts on adding new 
keywords in Python.
http://stackoverflow.com/questions/214881/can-you-add-new-statements-to-pythons-syntax

Looking at the suggestions, there are couple of ways to achieve this and I 
prefer this way since it sounds easiest:-



However, I cannot simply use these statements owing to the following 
reasons:-

(i)  the new package is replaced by Types package;
(ii) In the Types Package (checking on documentation), there is nothing 
like types.module(  ....). How to re-write the statements ?





(iii) When I execute this line 
    exec data in mod.__dict__

I got  message like syntax error   highlighting  the word "data" 


My understanding is that this support group is runned on voluntary basis. 
Grateful if somebody may help and revert with valid examples that
can run on Python 3.3.2.

Thx & Rgds,

George Advani




-----------------------------------------
*******************************************************************
This e-mail is confidential. It may also be legally privileged.
If you are not the addressee you may not copy, forward, disclose
or use any part of it. If you have received this message in error,
please delete it and all copies from your system and notify the
sender immediately by return e-mail.

Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
*******************************************************************
"SAVE PAPER - THINK BEFORE YOU PRINT!" 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/2ed55434/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 18418 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/2ed55434/attachment-0008.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 12546 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/2ed55434/attachment-0009.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 10399 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/2ed55434/attachment-0010.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 10512 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/2ed55434/attachment-0011.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 13790 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/2ed55434/attachment-0012.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 16600 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/2ed55434/attachment-0013.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 5861 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/2ed55434/attachment-0014.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 9130 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20130815/2ed55434/attachment-0015.gif>

From report at bugs.python.org  Sun Aug 18 21:46:10 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 18 Aug 2013 19:46:10 +0000
Subject: [docs] [issue18761] Fix internal doc references for the email
	package
In-Reply-To: <1376682451.08.0.523486132403.issue18761@psf.upfronthosting.co.za>
Message-ID: <1376855168.6.0.472121952916.issue18761@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Here is updated patch which addresses comments from David. Long lines are wrapped now.

----------
Added file: http://bugs.python.org/file31363/refs.email_2.patch

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

From storchaka at gmail.com  Sun Aug 18 22:06:50 2013
From: storchaka at gmail.com (storchaka at gmail.com)
Date: Sun, 18 Aug 2013 20:06:50 -0000
Subject: [docs] Fix internal doc references for the email package (issue
	18761)
Message-ID: <20130818200650.18559.65671@psf.upfronthosting.co.za>


http://bugs.python.org/review/18761/diff/8959/Doc/library/email.rst
File Doc/library/email.rst (right):

http://bugs.python.org/review/18761/diff/8959/Doc/library/email.rst#newcode300
Doc/library/email.rst:300: * The method :meth:`setboundary` was renamed
to :meth:`~email.message.Message.set_boundary`.
On 2013/08/16 23:38:47, ezio.melotti wrote:
> Is there any way to either set a shortcut somewhere for
email.message.Message or
> set is as current class/module?

Yes, we can change current module and class. But then we should change
them back when we want refers to entities in other modules/classes. And
we should always remember which module and class are current (it can be
declared several pages above). I think explicitness is better here.

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

From report at bugs.python.org  Mon Aug 19 00:08:42 2013
From: report at bugs.python.org (R. David Murray)
Date: Sun, 18 Aug 2013 22:08:42 +0000
Subject: [docs] [issue18761] Fix internal doc references for the email
	package
In-Reply-To: <1376682451.08.0.523486132403.issue18761@psf.upfronthosting.co.za>
Message-ID: <1376863722.08.0.567539217713.issue18761@psf.upfronthosting.co.za>


R. David Murray added the comment:

Based on your response to the review (I haven't looked at the new patch) I say go ahead and apply it.

----------

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

From report at bugs.python.org  Mon Aug 19 00:57:33 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 18 Aug 2013 22:57:33 +0000
Subject: [docs] [issue18562] Regex howto: revision pass
In-Reply-To: <1374854855.56.0.787824851556.issue18562@psf.upfronthosting.co.za>
Message-ID: <3cJDDr3Mqxz7LjM@mail.python.org>


Roundup Robot added the comment:

New changeset 366ca21600c9 by Andrew Kuchling in branch '3.3':
#18562: various revisions to the regex howto for 3.x
http://hg.python.org/cpython/rev/366ca21600c9

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

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

From report at bugs.python.org  Mon Aug 19 01:01:22 2013
From: report at bugs.python.org (A.M. Kuchling)
Date: Sun, 18 Aug 2013 23:01:22 +0000
Subject: [docs] [issue18562] Regex howto: revision pass
In-Reply-To: <1374854855.56.0.787824851556.issue18562@psf.upfronthosting.co.za>
Message-ID: <1376866882.81.0.930246660415.issue18562@psf.upfronthosting.co.za>


Changes by A.M. Kuchling <lists at amk.ca>:


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

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

From report at bugs.python.org  Mon Aug 19 01:01:32 2013
From: report at bugs.python.org (A.M. Kuchling)
Date: Sun, 18 Aug 2013 23:01:32 +0000
Subject: [docs] [issue18562] Regex howto: revision pass
In-Reply-To: <1374854855.56.0.787824851556.issue18562@psf.upfronthosting.co.za>
Message-ID: <1376866892.38.0.826007644583.issue18562@psf.upfronthosting.co.za>


Changes by A.M. Kuchling <lists at amk.ca>:


----------
stage: patch review -> committed/rejected

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

From report at bugs.python.org  Mon Aug 19 01:56:16 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 18 Aug 2013 23:56:16 +0000
Subject: [docs] [issue18445] Tools/Script/Readme is outdated
In-Reply-To: <1373782620.19.0.347266346086.issue18445@psf.upfronthosting.co.za>
Message-ID: <3cJFXb1RQ4z7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset 9d5468a7a381 by Andrew Kuchling in branch 'default':
#18445: change permissions on some scripts to executable
http://hg.python.org/cpython/rev/9d5468a7a381

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

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

From report at bugs.python.org  Mon Aug 19 02:07:19 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 19 Aug 2013 00:07:19 +0000
Subject: [docs] [issue18445] Tools/Script/Readme is outdated
In-Reply-To: <1373782620.19.0.347266346086.issue18445@psf.upfronthosting.co.za>
Message-ID: <3cJFnL3Lqqz7LjZ@mail.python.org>


Roundup Robot added the comment:

New changeset 16fad6c48016 by Andrew Kuchling in branch 'default':
#18445: update Tools/scripts/README.
http://hg.python.org/cpython/rev/16fad6c48016

----------

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

From report at bugs.python.org  Mon Aug 19 02:08:13 2013
From: report at bugs.python.org (A.M. Kuchling)
Date: Mon, 19 Aug 2013 00:08:13 +0000
Subject: [docs] [issue18445] Tools/Script/Readme is outdated
In-Reply-To: <1373782620.19.0.347266346086.issue18445@psf.upfronthosting.co.za>
Message-ID: <1376870893.51.0.868455185049.issue18445@psf.upfronthosting.co.za>


A.M. Kuchling added the comment:

Seydou: thanks for the patch!  I've applied it to 3.4.

----------
nosy: +akuchling
resolution:  -> fixed
stage: needs patch -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Mon Aug 19 03:54:34 2013
From: report at bugs.python.org (=?utf-8?q?Juan_Luis_Boya_Garc=C3=ADa?=)
Date: Mon, 19 Aug 2013 01:54:34 +0000
Subject: [docs] [issue18512] sys.stdout.write does not allow bytes in Python
	3.x
In-Reply-To: <1374287481.36.0.643885131326.issue18512@psf.upfronthosting.co.za>
Message-ID: <1376877274.74.0.259887377232.issue18512@psf.upfronthosting.co.za>


Juan Luis Boya Garc?a added the comment:

Sorry for the late response, GMail's SPAM filter ate the replies.

The main issue is sys.stdout being opened as text instead of binary. This fact is stated in the docs. http://docs.python.org/3/library/sys.html#sys.stdout

In any case, there are some caveats worth noting:

> You can do
>    sys.stdout.buffer.write(b"hello")
This is problematic if both buffer and IOTextWrapper are used. For example:

  print("Hello", end=""); sys.stdout.buffer.write(b"World")

That line may write `WorldHello` instead of `HelloWorld` (and it does indeed, at least in Linux implementation).

Yes, an application should not do this in Python3, but using print() and writing to stdout were OK in Python2, which makes porting programs harder.

A workaround is to perform sys.stdout.flush() before sys.stdout.buffer.write().

> (from the docs)
> Using io.TextIOBase.detach(), streams can be made binary by default.
> sys.stdout = sys.stdout.detach()

This should help in cases where most output is binary, but it's worth noting that interactive shells (such as the builtin python or IPython) and debuggers (both pdb and ipdb) stop working when this is used. Also, it will probably break every function there that relies on sys.stdout being Unicode or binary depending on only the Python version.

----------

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

From report at bugs.python.org  Mon Aug 19 09:05:08 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 19 Aug 2013 07:05:08 +0000
Subject: [docs] [issue18761] Fix internal doc references for the email
	package
In-Reply-To: <1376682451.08.0.523486132403.issue18761@psf.upfronthosting.co.za>
Message-ID: <3cJR3S12WFz7LjS@mail.python.org>


Roundup Robot added the comment:

New changeset 7a1534dba050 by Serhiy Storchaka in branch '3.3':
Issue #18761: Improved cross-references in email documentation.
http://hg.python.org/cpython/rev/7a1534dba050

New changeset 464eed5ddb2e by Serhiy Storchaka in branch 'default':
Issue #18761: Improved cross-references in email documentation.
http://hg.python.org/cpython/rev/464eed5ddb2e

New changeset 062533327ad2 by Serhiy Storchaka in branch '2.7':
Issue #18761: Improved cross-references in email documentation.
http://hg.python.org/cpython/rev/062533327ad2

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

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

From report at bugs.python.org  Mon Aug 19 09:22:21 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 19 Aug 2013 07:22:21 +0000
Subject: [docs] [issue18761] Fix internal doc references for the email
	package
In-Reply-To: <1376682451.08.0.523486132403.issue18761@psf.upfronthosting.co.za>
Message-ID: <1376896941.43.0.892296872792.issue18761@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you for the review.

----------
assignee: docs at python -> serhiy.storchaka
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Mon Aug 19 09:45:16 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Mon, 19 Aug 2013 07:45:16 +0000
Subject: [docs] [issue18779] Misleading documentations and comments in
	regular	expression about alphanumerics and underscore
Message-ID: <1376898316.85.0.0813282739116.issue18779@psf.upfronthosting.co.za>


New submission from Vajrasky Kok:

According to:

http://oald8.oxfordlearnersdictionaries.com/dictionary/alphanumeric
http://en.wikipedia.org/wiki/Alphanumeric

Alphanumeric is defined as [A-Za-z0-9]. Underscore (_) is not one of them. One of the documentation in Python (Doc/tutorial/stdlib2.rst) differentiates them very clearly:

"The format uses placeholder names formed by ``$`` with valid Python identifiers
(alphanumeric characters and underscores).  Surrounding the placeholder with
braces allows it to be followed by more alphanumeric letters with no intervening
spaces.  Writing ``$$`` creates a single escaped ``$``::"

Yet, in documentations as well as comments in regex, we implicitely assumes underscore belongs to alphanumeric.

Explicit is better than implicit!

Attached the patch to differentiate alphanumeric and underscore in documentations and comments in regex.

This is important in case someone is confused with this code:
>>> import re
>>> re.split('\W', 'haha$hihi*huhu_hehe hoho')
['haha', 'hihi', 'huhu_hehe', 'hoho']

On the side note:
In Python code base, sometimes we write "alphanumerics" and "underscores", yet sometimes we write "alphanumeric characters" and "underscore characters". Which one again is the true way?

----------
assignee: docs at python
components: Documentation
files: fix_alphanumeric_and_underscore_doc_in_regex.patch
keywords: patch
messages: 195611
nosy: akuchling, docs at python, vajrasky
priority: normal
severity: normal
status: open
title: Misleading documentations and comments in regular expression about alphanumerics and underscore
versions: Python 3.3, Python 3.4
Added file: http://bugs.python.org/file31371/fix_alphanumeric_and_underscore_doc_in_regex.patch

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

From report at bugs.python.org  Mon Aug 19 11:15:36 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 19 Aug 2013 09:15:36 +0000
Subject: [docs] [issue18438] Obsolete url in comment inside decimal module
In-Reply-To: <1373686911.48.0.750703855786.issue18438@psf.upfronthosting.co.za>
Message-ID: <1376903736.24.0.345191683584.issue18438@psf.upfronthosting.co.za>


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


----------
nosy: +facundobatista, skrah

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

From report at bugs.python.org  Mon Aug 19 11:31:47 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 19 Aug 2013 09:31:47 +0000
Subject: [docs] [issue18779] Misleading documentations and comments in
	regular	expression about alphanumerics and underscore
In-Reply-To: <1376898316.85.0.0813282739116.issue18779@psf.upfronthosting.co.za>
Message-ID: <1376904707.33.0.189836808205.issue18779@psf.upfronthosting.co.za>


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


----------
components: +Regular Expressions
nosy: +ezio.melotti, mrabarnett, pitrou
stage:  -> patch review

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

From report at bugs.python.org  Mon Aug 19 11:37:36 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 19 Aug 2013 09:37:36 +0000
Subject: [docs] [issue18779] Misleading documentations and comments in
	regular	expression HOWTO
In-Reply-To: <1376898316.85.0.0813282739116.issue18779@psf.upfronthosting.co.za>
Message-ID: <1376905056.34.0.97935452053.issue18779@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

I was wondering which doc you were alluding it, before I noticed your patch is against the regex HOWTO.
The HOWTO seems quite outdated wrt. Python 3. For example "\w" is not equivalent to "[a-zA-Z0-9_]", anymore, except with the ASCII flag.

----------
title: Misleading documentations and comments in regular expression about alphanumerics and underscore -> Misleading documentations and comments in regular expression HOWTO

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

From report at bugs.python.org  Mon Aug 19 12:19:36 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Mon, 19 Aug 2013 10:19:36 +0000
Subject: [docs] [issue18779] Misleading documentations and comments in
	regular	expression HOWTO
In-Reply-To: <1376898316.85.0.0813282739116.issue18779@psf.upfronthosting.co.za>
Message-ID: <1376907576.3.0.437350024386.issue18779@psf.upfronthosting.co.za>


Vajrasky Kok added the comment:

In Lib/re.py, starting from line 77 (Python 3.4):

    \w       Matches any alphanumeric character; equivalent to [a-zA-Z0-9_]
             in bytes patterns or string patterns with the ASCII flag.
             In string patterns without the ASCII flag, it will match the
             range of Unicode alphanumeric characters (letters plus digits
             plus underscore).
             With LOCALE, it will match the set [0-9_] plus characters defined
             as letters for the current locale.

The prelude is "Matches any alphanumeric character;".

Yet, in any case (bytes, string patterns with ascii flag, string patterns without the ascii flag, strings with locale), the underscore is always included.

Then why don't we change the prelude to "Matches any alphanumeric character and underscore character;"? In the description we explain the alphanumeric depending on it's unicode or not can be [A-Za-z0-9] or wider than that.

The description is already okay but the prelude is misleading readers.

----------

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

From report at bugs.python.org  Mon Aug 19 14:39:58 2013
From: report at bugs.python.org (R. David Murray)
Date: Mon, 19 Aug 2013 12:39:58 +0000
Subject: [docs] [issue18779] Misleading documentations and comments in
	regular	expression HOWTO
In-Reply-To: <1376898316.85.0.0813282739116.issue18779@psf.upfronthosting.co.za>
Message-ID: <1376915998.68.0.437880445223.issue18779@psf.upfronthosting.co.za>


R. David Murray added the comment:

The answer to the question about "alphanumerics" versus "alphanumeric characters" is that is is mostly likely context-dependent, so I'd have to see particular examples to say which I though read better.  So, there is no One True Answer for this question, I think.

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

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

From report at bugs.python.org  Tue Aug 20 16:22:54 2013
From: report at bugs.python.org (Joe Tennies)
Date: Tue, 20 Aug 2013 14:22:54 +0000
Subject: [docs] [issue18789] XML Vunerability Table Unclear
Message-ID: <1377008574.91.0.12100936862.issue18789@psf.upfronthosting.co.za>


New submission from Joe Tennies:

EASY

This is an issue with the 2.x and 3.x documentation.

http://docs.python.org/3.2/library/xml.html#xml-vulnerabilities
http://docs.python.org/dev/library/xml.html#xml-vulnerabilities
http://docs.python.org/2/library/xml.html#xml-vulnerabilities

This section has a table with a bunch of Trues and Falses. This is a bit confusing, especially for something that is trying to describe security concerns. After looking at the table, I'm pretty sure that True means vunerable (only due to the (1), (2), & (3) comments), but it's not clear. All that is needed is a heading stating "Vunerable", or change the "True" to "Vunerable" and "False" to "Not Vunerable" (probably V and NV w/ a legend).

----------
assignee: docs at python
components: Documentation
messages: 195691
nosy: docs at python, joe-tennies
priority: normal
severity: normal
status: open
title: XML Vunerability Table Unclear
type: security
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5

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

From report at bugs.python.org  Tue Aug 20 16:23:55 2013
From: report at bugs.python.org (Christian Heimes)
Date: Tue, 20 Aug 2013 14:23:55 +0000
Subject: [docs] [issue18789] XML Vunerability Table Unclear
In-Reply-To: <1377008574.91.0.12100936862.issue18789@psf.upfronthosting.co.za>
Message-ID: <1377008635.45.0.608596054248.issue18789@psf.upfronthosting.co.za>


Changes by Christian Heimes <lists at cheimes.de>:


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

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

From report at bugs.python.org  Tue Aug 20 16:37:58 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 20 Aug 2013 14:37:58 +0000
Subject: [docs] [issue18789] XML Vunerability Table Unclear
In-Reply-To: <1377008574.91.0.12100936862.issue18789@psf.upfronthosting.co.za>
Message-ID: <1377009478.22.0.45083873451.issue18789@psf.upfronthosting.co.za>


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


----------
components: +XML
versions:  -Python 3.2, Python 3.5

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

From report at bugs.python.org  Tue Aug 20 16:47:05 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 20 Aug 2013 14:47:05 +0000
Subject: [docs] [issue17576] PyNumber_Index() is not int-subclass friendly
	(or	operator.index() docos lie)
In-Reply-To: <1364595911.19.0.826873230127.issue17576@psf.upfronthosting.co.za>
Message-ID: <1377010025.8.0.669009326465.issue17576@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Aug 20 17:21:26 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 20 Aug 2013 15:21:26 +0000
Subject: [docs] [issue18512] sys.stdout.write does not allow bytes in Python
	3.x
In-Reply-To: <1374287481.36.0.643885131326.issue18512@psf.upfronthosting.co.za>
Message-ID: <1377012086.6.0.238175178614.issue18512@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

> A workaround is to perform sys.stdout.flush() before 
> sys.stdout.buffer.write().

FWIW you can just use print(..., flush=True) from 3.3+.

----------

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

From report at bugs.python.org  Tue Aug 20 18:19:27 2013
From: report at bugs.python.org (Zachary Ware)
Date: Tue, 20 Aug 2013 16:19:27 +0000
Subject: [docs] [issue18326] Mention 'keyword only' for list.sort,
	improve  glossary.
In-Reply-To: <1372511136.61.0.278425078947.issue18326@psf.upfronthosting.co.za>
Message-ID: <1377015567.51.0.328048990139.issue18326@psf.upfronthosting.co.za>


Zachary Ware added the comment:

How about this?

----------
Added file: http://bugs.python.org/file31385/issue18326.v2.diff

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

From report at bugs.python.org  Tue Aug 20 20:58:24 2013
From: report at bugs.python.org (purplezephyr)
Date: Tue, 20 Aug 2013 18:58:24 +0000
Subject: [docs] [issue18790] incorrect text in argparse add_help example
Message-ID: <1377025104.92.0.641943823333.issue18790@psf.upfronthosting.co.za>


New submission from purplezephyr:

The last example under add_help in the documentation for the argparse module has incorrect text.  It is supposed to demonstrate what happens when prefix_chars doesn't include '-', and add_help is True, but the example has the following:

  usage: PROG [-h]

  optional arguments:
    -h, --help  show this help message and exit

instead of:

  usage: PROG [+h]

  optional arguments:
    +h, ++help  show this help message and exit

----------
assignee: docs at python
components: Documentation
messages: 195710
nosy: docs at python, purplezephyr
priority: normal
severity: normal
status: open
title: incorrect text in argparse add_help example
versions: Python 2.7, Python 3.3

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

From report at bugs.python.org  Tue Aug 20 21:52:35 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 20 Aug 2013 19:52:35 +0000
Subject: [docs] [issue17576] PyNumber_Index() is not int-subclass friendly
	(or	operator.index() docos lie)
In-Reply-To: <1364595911.19.0.826873230127.issue17576@psf.upfronthosting.co.za>
Message-ID: <1377028355.32.0.68001079553.issue17576@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Shouldn't it be PendingDeprecationWarning?

----------

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

From report at bugs.python.org  Tue Aug 20 22:17:01 2013
From: report at bugs.python.org (Claudiu.Popa)
Date: Tue, 20 Aug 2013 20:17:01 +0000
Subject: [docs] [issue14971] (unittest) loadTestsFromName does not work on
	method	with a decorator
In-Reply-To: <1338490939.51.0.536223048687.issue14971@psf.upfronthosting.co.za>
Message-ID: <1377029821.22.0.867647373482.issue14971@psf.upfronthosting.co.za>


Claudiu.Popa added the comment:

The patch for Python 2.7 is pretty similar with the one provided for Python 3.

----------
nosy: +Claudiu.Popa
Added file: http://bugs.python.org/file31386/unittest_method_name_difference_27.patch

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

From report at bugs.python.org  Wed Aug 21 01:28:01 2013
From: report at bugs.python.org (paul j3)
Date: Tue, 20 Aug 2013 23:28:01 +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: <1377041281.08.0.0981477196317.issue14191@psf.upfronthosting.co.za>


paul j3 added the comment:

It's everything I intend to add.  Now I'm just waiting for a committer to act, either with suggested changes, or a merge.  I'm watching more than a dozen argparse patches.

----------

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

From report at bugs.python.org  Wed Aug 21 03:29:23 2013
From: report at bugs.python.org (Glenn Linderman)
Date: Wed, 21 Aug 2013 01:29:23 +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: <1377048563.85.0.529994384462.issue14191@psf.upfronthosting.co.za>


Glenn Linderman added the comment:

So I read over your code again, and even read the documentation this time, and it all looks good, and I know it works good because I've been using the code. I tried to send a notice through Reitveld, and maybe did, but I don't know where it went, so I'll say this much here, too.

----------

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

From report at bugs.python.org  Wed Aug 21 04:56:59 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Wed, 21 Aug 2013 02:56:59 +0000
Subject: [docs] [issue18796] Wrong documentation of show_code function from
	dis module
Message-ID: <1377053819.02.0.986969704551.issue18796@psf.upfronthosting.co.za>


New submission from Vajrasky Kok:

$ ./python
Python 3.4.0a1+ (default:afb1b4797419, Aug 21 2013, 09:54:46) 
[GCC 4.7.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import dis
>>> import sys
>>> def spam(x):
...   return x * 2
... 
>>> dis.show_code(spam, file=sys.stderr)
Name:              spam
Filename:          <stdin>
Argument count:    1
Kw-only arguments: 0
Number of locals:  1
Stack size:        2
Flags:             OPTIMIZED, NEWLOCALS, NOFREE
Constants:
   0: None
   1: 2
Variable names:
   0: x
>>> output = open('/tmp/output.txt', 'w')
>>> dis.show_code(spam, file=output)
>>> output.close()
>>> dis.show_code.__doc__
'Print details of methods, functions, or code to stdout.'

Attached the patch to fix the documentation.

----------
assignee: docs at python
components: Documentation
files: fix_doc_show_code.patch
keywords: patch
messages: 195742
nosy: docs at python, vajrasky
priority: normal
severity: normal
status: open
title: Wrong documentation of show_code function from dis module
versions: Python 3.4
Added file: http://bugs.python.org/file31392/fix_doc_show_code.patch

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

From report at bugs.python.org  Wed Aug 21 07:47:34 2013
From: report at bugs.python.org (Mark Dickinson)
Date: Wed, 21 Aug 2013 05:47:34 +0000
Subject: [docs] [issue17576] PyNumber_Index() is not int-subclass friendly
	(or	operator.index() docos lie)
In-Reply-To: <1364595911.19.0.826873230127.issue17576@psf.upfronthosting.co.za>
Message-ID: <1377064054.88.0.645596281376.issue17576@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

> Shouldn't it be PendingDeprecationWarning?

Hmm.  Possibly.  I'm not sure what the policy is any more regarding DeprecationWarning versus PendingDeprecationWarning.  Nick?

----------

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

From report at bugs.python.org  Wed Aug 21 08:29:34 2013
From: report at bugs.python.org (Michael Bikovitsky)
Date: Wed, 21 Aug 2013 06:29:34 +0000
Subject: [docs] [issue18790] incorrect text in argparse add_help example
In-Reply-To: <1377025104.92.0.641943823333.issue18790@psf.upfronthosting.co.za>
Message-ID: <1377066574.72.0.260748059333.issue18790@psf.upfronthosting.co.za>


Changes by Michael Bikovitsky <moshe.biko at gmail.com>:


----------
keywords: +patch
Added file: http://bugs.python.org/file31393/doc_fix.patch

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

From report at bugs.python.org  Wed Aug 21 08:33:12 2013
From: report at bugs.python.org (Michael Bikovitsky)
Date: Wed, 21 Aug 2013 06:33:12 +0000
Subject: [docs] [issue18790] incorrect text in argparse add_help example
In-Reply-To: <1377025104.92.0.641943823333.issue18790@psf.upfronthosting.co.za>
Message-ID: <1377066792.45.0.10414085617.issue18790@psf.upfronthosting.co.za>


Changes by Michael Bikovitsky <moshe.biko at gmail.com>:


----------
nosy: +Michael.Bikovitsky

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

From report at bugs.python.org  Wed Aug 21 11:31:54 2013
From: report at bugs.python.org (Michael Foord)
Date: Wed, 21 Aug 2013 09:31:54 +0000
Subject: [docs] [issue14971] (unittest) loadTestsFromName does not work on
	method	with a decorator
In-Reply-To: <1338490939.51.0.536223048687.issue14971@psf.upfronthosting.co.za>
Message-ID: <1377077514.6.0.978674494998.issue14971@psf.upfronthosting.co.za>


Michael Foord added the comment:

Cool, thanks!

----------
assignee:  -> michael.foord

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

From report at bugs.python.org  Wed Aug 21 11:33:16 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 21 Aug 2013 09:33:16 +0000
Subject: [docs] [issue17576] PyNumber_Index() is not int-subclass friendly
	(or	operator.index() docos lie)
In-Reply-To: <1364595911.19.0.826873230127.issue17576@psf.upfronthosting.co.za>
Message-ID: <1377077596.58.0.317556542548.issue17576@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Yet some nitpicks.

Currently the code of _PyLong_FromNbInt() is inlined and the do_decref flag is used to prevent needless change refcounts of int objects (see also issue18797). In proposed patch common code is extracted into the _PyLong_FromNbInt() function and int objects increfed and decrefed. Doesn't it affect a performance? PyLong_As* functions used in arguments parsing in a lot of builtins and their .performance is important.

If the patch slowdowns PyLong_As* functions we perhaps should check PyLong_CheckExact() before calling _PyLong_FromNbInt() and use the do_decref flag.

In general the idea and the patch LGTM.

----------

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

From report at bugs.python.org  Wed Aug 21 12:22:18 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 21 Aug 2013 10:22:18 +0000
Subject: [docs] [issue17576] PyNumber_Index() is not int-subclass friendly
	(or	operator.index() docos lie)
In-Reply-To: <1364595911.19.0.826873230127.issue17576@psf.upfronthosting.co.za>
Message-ID: <1377080538.25.0.0551283820478.issue17576@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

On PyPy 1.8.0 operator.index(True) returns 1.

----------

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

From report at bugs.python.org  Wed Aug 21 13:32:36 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 21 Aug 2013 11:32:36 +0000
Subject: [docs] [issue17576] PyNumber_Index() is not int-subclass friendly
	(or	operator.index() docos lie)
In-Reply-To: <1364595911.19.0.826873230127.issue17576@psf.upfronthosting.co.za>
Message-ID: <1377084756.17.0.93479943928.issue17576@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

And yet one nitpick. For int subclasses which doesn't overload the __int__ method the patch calls default int.__int__ which creates a copy of int object. This is redundant in PyLong_As* functions because they only extract C int value and drop Python int object. So we can use int subclass object itself as good as int object.

----------

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

From report at bugs.python.org  Wed Aug 21 13:45:28 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 21 Aug 2013 11:45:28 +0000
Subject: [docs] [issue18743] References to non-existant "StringIO" module
In-Reply-To: <1376542911.78.0.658455842148.issue18743@psf.upfronthosting.co.za>
Message-ID: <1377085528.87.0.240571463904.issue18743@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed Aug 21 18:27:53 2013
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 21 Aug 2013 16:27:53 +0000
Subject: [docs] [issue15233] atexit: guarantee order of execution of
	registered	functions?
In-Reply-To: <1341129521.95.0.805489135584.issue15233@psf.upfronthosting.co.za>
Message-ID: <3cKvRr2NQsz7LjV@mail.python.org>


Roundup Robot added the comment:

New changeset 84d74eb7a341 by Charles-Fran?ois Natali in branch '2.7':
Issue #15233: Python now guarantees that callables registered with the atexit
http://hg.python.org/cpython/rev/84d74eb7a341

----------

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

From report at bugs.python.org  Wed Aug 21 18:47:44 2013
From: report at bugs.python.org (=?utf-8?q?Charles-Fran=C3=A7ois_Natali?=)
Date: Wed, 21 Aug 2013 16:47:44 +0000
Subject: [docs] [issue15233] atexit: guarantee order of execution of
	registered	functions?
In-Reply-To: <1341129521.95.0.805489135584.issue15233@psf.upfronthosting.co.za>
Message-ID: <1377103664.14.0.756293823332.issue15233@psf.upfronthosting.co.za>


Charles-Fran?ois Natali added the comment:

Backported to 2.7.

----------
resolution:  -> fixed
stage: commit review -> committed/rejected
status: open -> closed
versions:  -Python 3.2

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

From report at bugs.python.org  Wed Aug 21 19:05:46 2013
From: report at bugs.python.org (icedream91)
Date: Wed, 21 Aug 2013 17:05:46 +0000
Subject: [docs] [issue18800] Document Fraction's numerator and denominator
	properties
Message-ID: <1377104746.66.0.571132107535.issue18800@psf.upfronthosting.co.za>


New submission from icedream91:

The document (http://docs.python.org/3/library/fractions.html) doesn't mention Fraction's numerator and denominator properties, I knew these properties from dir().

Since sometimes these two properties are very useful, for example: http://projecteuler.net/problem=33 and http://projecteuler.net/problem=57 , I think document should mention them. 

Thanks.

----------
assignee: docs at python
components: Documentation
messages: 195808
nosy: docs at python, icedream91
priority: normal
severity: normal
status: open
title: Document Fraction's numerator and denominator properties
type: enhancement
versions: Python 3.3

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

From report at bugs.python.org  Wed Aug 21 21:30:44 2013
From: report at bugs.python.org (Eric Snow)
Date: Wed, 21 Aug 2013 19:30:44 +0000
Subject: [docs] [issue17972] inspect module docs omits many functions
In-Reply-To: <1368501068.91.0.677640111487.issue17972@psf.upfronthosting.co.za>
Message-ID: <1377113444.19.0.929890350934.issue17972@psf.upfronthosting.co.za>


Changes by Eric Snow <ericsnowcurrently at gmail.com>:


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

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

From owen at existence.com  Tue Aug  6 08:48:35 2013
From: owen at existence.com (Owen Johnson)
Date: Tue, 06 Aug 2013 06:48:35 -0000
Subject: [docs] Documention bug
Message-ID: <CADcxe66UsUNqtBjQP-f=RsBE_VO9q_W5zKbo_ehb3t6eYR0exQ@mail.gmail.com>

On page:

http://docs.python.org/3.0/library/csv.html

Under Examples:

----
The simplest example of reading a CSV file:

import csv
reader = csv.reader(open("some.csv", "rb"))
for row in reader:
    print(row)
----

Code works in python 2, but in python 3, it throws error:

----
Traceback (most recent call last):
  File "WeeklyDepletionParser.py", line 3, in <module>
    for row in reader:
_csv.Error: iterator should return strings, not bytes (did you open
the file in text mode?)
----

Fix was straightforward to change parameter "rb" to "rt".

I am running:

Python 3.3.2 (v3.3.2:d047928ae3f6, May 13 2013, 13:52:24)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin

Owen

From csimmons at google.com  Fri Aug  9 21:36:17 2013
From: csimmons at google.com (Chuck Simmons)
Date: Fri, 9 Aug 2013 12:36:17 -0700
Subject: [docs] printing unicode strings
Message-ID: <CALzwb8LSH8RMowkCBT7Fyiic3mY=vK3__xwTF_n6WC9xuaEAnQ@mail.gmail.com>

Context:  I'm getting

UnicodeEncodeError: 'ascii' codec can't encode character u'\u2019' in
position 7: ordinal not in range(128)

from the code

print '%s%s%s' % (prefix, value, suffix),

[Here, 'value' contains unicode characters, while prefix and suffix contain
7-bit characters.]


So I went to
http://docs.python.org/2/howto/unicode.html#reading-and-writing-unicode-data
to determine what I should do to fix my bug.  I saw the section "Reading
and Writing Unicode
Data<http://docs.python.org/2/howto/unicode.html#reading-and-writing-unicode-data>",
which seemed relevant. That section doesn't seem to discuss printing to
stdout.


No doubt I got confused and didn't read carefully enough, but it might be
the case that if the Reading and Writing section had an example of printing
a unicode string to stdout that it would have helped me find a solution
faster.

g'luck, Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130809/11e2eb75/attachment-0001.html>

From pitrou at free.fr  Fri Aug  9 22:02:25 2013
From: pitrou at free.fr (pitrou at free.fr)
Date: Fri, 09 Aug 2013 20:02:25 -0000
Subject: [docs] email.policy doc example passes 'policy' to as_string,
 but that doesn't work (issue 18600)
Message-ID: <20130809200225.7052.87866@psf.upfronthosting.co.za>


http://bugs.python.org/review/18600/diff/8864/Doc/library/email.message.rst
File Doc/library/email.message.rst (right):

http://bugs.python.org/review/18600/diff/8864/Doc/library/email.message.rst#newcode43
Doc/library/email.message.rst:43: .. method:: as_string(unixfrom=False,
maxheaderlen=0, policy=None)
You need a versionchanged tag for the new parameter.

http://bugs.python.org/review/18600/diff/8864/Doc/library/email.message.rst#newcode85
Doc/library/email.message.rst:85: .. method:: as_bytes(unixfrom=False,
policy=None)
versionadded required.

http://bugs.python.org/review/18600/diff/8864/Doc/library/email.message.rst#newcode114
Doc/library/email.message.rst:114: .. method:: __bytes__()
versionadded required.

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

From roger at erens-krekels.net  Sat Aug 10 00:32:41 2013
From: roger at erens-krekels.net (Roger Erens)
Date: Sat, 10 Aug 2013 00:32:41 +0200
Subject: [docs] MS Windows inconsistent advice in
	http://docs.python.org/2/install/index.html
Message-ID: <CAMTMGpoBRYCsN7Cbdc2Xak=L_qqZ+GCa555M_OyWEbM3o6p-NA@mail.gmail.com>

In the line right above the section
http://docs.python.org/2/install/index.html#splitting-the-job-up
it is stated that on windows one should use

python setup.py install

whereas in the earlier section
http://docs.python.org/2/install/index.html#the-new-standard-distutils
it was stated that for windows this command should be

setup.py install

Thanks for the great docs on python.org!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130810/81309ab2/attachment-0001.html>

From roy.nard at gmail.com  Wed Aug 14 12:47:25 2013
From: roy.nard at gmail.com (Roy Nard)
Date: Wed, 14 Aug 2013 12:47:25 +0200
Subject: [docs] Minor fix, docpage
Message-ID: <CAMJKnh=D_xxPL_OYCtdSVFOAOXtnqrjg8B5JGoBt3SrsEGtSEQ@mail.gmail.com>

http://docs.python.org/2/library/os.html
os.walk(*top*, *topdown=True*, *onerror=None*, *followlinks=False*) :::

"Generate the file names in a directory tree by walking the tree either
top-down or bottom-up. For each directory in the tree rooted at directory *
top* (including *top* itself), it yields a 3-tuple (dirpath, dirnames, *
filenames*).
*dirpath* is a string, the path to the directory. *dirnames* is a list of
the names of the subdirectories in *dirpath* (excluding '.' and '..'). *
filenames* is a list of the names of the non-directory files in *dirpath*.
Note that the names in the lists contain no path components. To get a full
path (which begins with *top*) to a file or directory in *dirpath*, do
os.path.join(dirpath, *name*)"

Small revision: Variables does not match.

//Roy Nard
Chalmers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130814/ad68c2b7/attachment.html>

From aseembansal at ymail.com  Tue Aug 20 20:08:57 2013
From: aseembansal at ymail.com (aseem bansal)
Date: Tue, 20 Aug 2013 11:08:57 -0700 (PDT)
Subject: [docs] Suggestion for improving 4.7.5 Lambda Forms in Python
	tutorial
Message-ID: <1377022137.71051.YahooMailNeo@web142704.mail.bf1.yahoo.com>

The tutorial about Lambda forms(Documentation->The Python Tutorial->4.7.5 Lambda Forms) currently assumes a prior knowledge of functional? programming paradigm. I wanted to propose a change to that. It can be made better by adding some common sense things to the explanation so the simple examples given don't overwhelm the first-time reader due to unfamiliarity with functional programming. The following could take care of the problem.
------------------
By popular demand, a few features commonly found in functional programming
languages like Lisp have been added to Python.  With the lambda keyword, small anonymous functions can be created. 

Here?s a function that
returns the sum of its two arguments: lambda a, b: a+b. Here the comma separated variables between the lambda and the colon are the function's arguments and the part after the colon is the return type of the anonymous function.

Lambda forms can be
used wherever function objects are required.  They are syntactically restricted
to a single expression.  Semantically, they are just syntactic sugar for a
normal function definition.  Like nested function definitions, lambda forms can
reference variables from the containing scope:

//The Code will be here.
------------------
Additionally adding the link to functional programming HowTO? in the first sentence "commonly found in functional programming
languages" can help the first-time reader and those unfamiliar with functional paradigm to get acquainted with functional programming in Python's context.

If someone reads it can someone send a reply to this about where this mailing list can be browsed. I sent a previous one also but wasn't able to follow through because I didn't know where to browse this mailing list.

?
Aseem Bansal
(aseembansal? at? ymail)
(asmbansal2 at gmail)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130820/e5a9099d/attachment-0001.html>

From tristan.naumann at gmail.com  Fri Aug  9 19:24:34 2013
From: tristan.naumann at gmail.com (Tristan Naumann)
Date: Fri, 9 Aug 2013 10:24:34 -0700
Subject: [docs] Error in heapq documentation
Message-ID: <CAGBdhLdw+k2z7bcj-uuY3LNd6Gin07K5LbYjQCvC+Quh2+ncHw@mail.gmail.com>

The current heapq documentation states that:

- heapq.nlargest(n, iterable[, key]) is "Equivalent to: sorted(iterable,
key=key, reverse=True)[:n]"

- heapq.nsmallest(n, iterable[, key]) is "Equivalent to: sorted(iterable,
key=key)[:n]"

However, this does not hold true when n = None. Specifically, heapq throws
an exception while slicing appears to produce a shallow copy of the sorted
list.

Thanks!
--Tristan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130809/78fd3c23/attachment-0001.html>

From tama at tama.co.nz  Sat Aug 10 23:47:32 2013
From: tama at tama.co.nz (Tama Pugsley)
Date: Sun, 11 Aug 2013 09:47:32 +1200
Subject: [docs] Pedantic word change
	(http://docs.python.org/2/tutorial/classes.html#generators)
Message-ID: <5206B4F4.1000801@tama.co.nz>

Hi there,

I'm just getting started with Python (escaping PHP madness), thanks for 
writing such awesome documentation.

Quick tense change here:
http://docs.python.org/2/tutorial/classes.html
9.10. Generators

"Another key feature is that the local variables and execution state are 
automatically saved between calls. This >>>made<<< the function easier 
to write and much more clear than an approach using instance variables 
like self.index and self.data."

Should the second sentence start "This MAKES"?

Cheers,
Tama

From v+python at g.nevcal.com  Wed Aug 21 02:45:57 2013
From: v+python at g.nevcal.com (v+python at g.nevcal.com)
Date: Wed, 21 Aug 2013 00:45:57 -0000
Subject: [docs] argparse: nargs='*' doesn't get out-of-order positional
 parameters (issue 14191)
Message-ID: <20130821004557.415.48252@psf.upfronthosting.co.za>

Reviewers: ,

Message:
This looks good to me, and definitely solves the problem I reported in
the bug. Wish I'd had time learn the code and to do a nice thorough job
of fixing the bug as paul.j3 did. In reviewing his changes, and
integrating them in to my working version (where they are running fine),
I did wind up learning a bit more than I had figured out on my own.



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

Affected files:
  Doc/library/argparse.rst
  Lib/argparse.py
  Lib/test/test_argparse.py



From report at bugs.python.org  Wed Aug 21 23:16:05 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Wed, 21 Aug 2013 21:16:05 +0000
Subject: [docs] [issue18803] Fix more typos in .py files
Message-ID: <1377119764.79.0.128935070292.issue18803@psf.upfronthosting.co.za>


New submission from F?vry Thibault:

Just like issue 18741 and 18705.

It also fixes one typo in a C file.

----------
assignee: docs at python
components: Documentation
files: more_typos.diff
keywords: patch
messages: 195823
nosy: docs at python, iwontbecreative
priority: normal
severity: normal
status: open
title: Fix more typos in .py files
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file31411/more_typos.diff

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

From report at bugs.python.org  Wed Aug 21 23:32:15 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 21 Aug 2013 21:32:15 +0000
Subject: [docs] [issue17576] PyNumber_Index() is not int-subclass friendly
	(or	operator.index() docos lie)
In-Reply-To: <1377064054.88.0.645596281376.issue17576@psf.upfronthosting.co.za>
Message-ID: <CADiSq7dHVRrLSJT_LRhhksHgG8W9dJbKvRn9BNchzashHnGkMQ@mail.gmail.com>


Nick Coghlan added the comment:

On 21 Aug 2013 15:47, "Mark Dickinson" <report at bugs.python.org> wrote:
>
>
> Mark Dickinson added the comment:
>
> > Shouldn't it be PendingDeprecationWarning?
>
> Hmm.  Possibly.  I'm not sure what the policy is any more regarding
DeprecationWarning versus PendingDeprecationWarning.  Nick?

Not sure if this is written down anywhere, but I use
PendingDeprecationWarning for "definitely still around next release, may
not have a set date for removal" and DeprecationWarning for "may be removed
next release".

----------

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

From report at bugs.python.org  Thu Aug 22 01:59:04 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 21 Aug 2013 23:59:04 +0000
Subject: [docs] [issue18326] Mention 'keyword only' for list.sort,
	improve  glossary.
In-Reply-To: <1372511136.61.0.278425078947.issue18326@psf.upfronthosting.co.za>
Message-ID: <1377129544.52.0.491454186038.issue18326@psf.upfronthosting.co.za>


R. David Murray added the comment:

In this expository context, I prefer the issue18326.that.diff version, but the index link to the keyword-only_parameter ref should still be added to it (on "only be passed by keyword").

----------

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

From report at bugs.python.org  Thu Aug 22 09:27:09 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 22 Aug 2013 07:27:09 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <1377156428.89.0.995046878618.issue15204@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Here is an updated patch. I think we can combine 1 and 2 stages (change the documentation and add warnings).

----------
Added file: http://bugs.python.org/file31416/deprecate-U-mode.patch

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

From report at bugs.python.org  Thu Aug 22 11:08:49 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 22 Aug 2013 09:08:49 +0000
Subject: [docs] [issue16700] Document that bytes OS API can returns unusable
	results	on Windows
In-Reply-To: <1355677117.39.0.191453655217.issue16700@psf.upfronthosting.co.za>
Message-ID: <1377162529.19.0.13194005148.issue16700@psf.upfronthosting.co.za>


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


----------
versions:  -Python 3.2

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

From report at bugs.python.org  Thu Aug 22 11:50:50 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Thu, 22 Aug 2013 09:50:50 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <1377165050.16.0.979426380806.issue15204@psf.upfronthosting.co.za>


Vajrasky Kok added the comment:

http://bugs.python.org/review/15204/diff/9032/Tools/iobench/iobench.py

Line 10 in New:
import io

But io module is never used.

----------
nosy: +vajrasky

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

From report at bugs.python.org  Thu Aug 22 15:40:54 2013
From: report at bugs.python.org (Alexander Belopolsky)
Date: Thu, 22 Aug 2013 13:40:54 +0000
Subject: [docs] [issue18800] Document Fraction's numerator and denominator
	properties
In-Reply-To: <1377104746.66.0.571132107535.issue18800@psf.upfronthosting.co.za>
Message-ID: <1377178854.04.0.796504903617.issue18800@psf.upfronthosting.co.za>


Changes by Alexander Belopolsky <alexander.belopolsky at gmail.com>:


----------
nosy: +belopolsky

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

From report at bugs.python.org  Thu Aug 22 16:04:14 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 22 Aug 2013 14:04:14 +0000
Subject: [docs] [issue18800] Document Fraction's numerator and denominator
	properties
In-Reply-To: <1377104746.66.0.571132107535.issue18800@psf.upfronthosting.co.za>
Message-ID: <1377180254.41.0.773521475701.issue18800@psf.upfronthosting.co.za>


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


----------
keywords: +easy
nosy: +mark.dickinson, rhettinger
stage:  -> needs patch
versions: +Python 2.7, Python 3.4

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

From report at bugs.python.org  Fri Aug 23 06:08:19 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 23 Aug 2013 04:08:19 +0000
Subject: [docs] [issue18713] Clearly document the use of PYTHONIOENCODING to
	set	surrogateescape
In-Reply-To: <1376320774.07.0.703505392881.issue18713@psf.upfronthosting.co.za>
Message-ID: <1377230898.79.0.357977419834.issue18713@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Note: I created issue 18814 to cover some additional tools for working with surrogate escaped strings.

For this issue, we currently have http://docs.python.org/3/howto/unicode.html, which aims to be a more comprehensive guide to understanding Unicode issues.

I'm thinking we may want a "Debugging Unicode Errors" document, which defers to the existing howto guide for those that really want to understand Unicode, and instead focuses on quick fixes for resolving various problems that may present themselves.

Application developers will likely want to read the longer guide, while the debugging document would be aimed at getting script writers past their immediate hurdle, without necessarily gaining a full understanding of Unicode.

The would be for this page to become the top hit for "python surrogates not allowed", rather than the current top hit, which is a rejected bug report about it (http://bugs.python.org/issue13717).

For example:

================================
What is the meaning of "UnicodeEncodeError: surrogates not allowed"?
--------------------------------------------------------------------

Operating system metadata on POSIX based systems like Linux and Mac OS X may include improperly encoded text values. To cope with this, Python uses the "surrogateescape" error handler to store those arbitrary bytes inside a Unicode object. When converted back to bytes using the same encoding and error handler, the original byte sequence is reproduced exactly. This allows operations like opening a file based on a directory listing to work correctly, even when the metadata is not properly encoded according to the system settings.

The "surrogates not allowed" error appears when a string from one of these operating system interfaces contains an embedded arbitrary byte sequence, but an attempt is made to encode it using the default "strict" error handler rather than the "surrogateescape" handler. This commonly occurs when printing improperly encoded operating system data to the console, or writing it to a file, database or other serialised interface.

The ``PYTHONIOENCODING`` environment variable can be used to ensure operating system metadata can always be read via sys.stdin and written via sys.stdout. The following command will display the encoding Python will use by default to interact with the operating system::

    $ python3 -c "import sys; print(sys.getfilesystemencoding())"
    utf-8

This can then be used to specify an appropriate setting for ``PYTHONIOENCODING``:: 


    $ export PYTHONIOENCODING=utf-8:surrogateescape

For other interfaces, there is no such general solution. If allowing the invalid byte sequence to propagate further is acceptable, then enabling the surrogateescape handler may be appropriate. Alternatively, it may be better to track these corrupted strings back to their point of origin, and either fix the underlying metadata, or else filter them out early on.
================================

If issue 18814 is implemented, then it could point to those tools. Similarly, issue 15216 could be referenced if that is implemented.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
title: Enable surrogateescape on stdin and stdout when appropriate -> Clearly document the use of PYTHONIOENCODING to set surrogateescape

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

From report at bugs.python.org  Fri Aug 23 06:20:01 2013
From: report at bugs.python.org (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Fri, 23 Aug 2013 04:20:01 +0000
Subject: [docs] [issue18815] DOCUMENTATION: "mmap .close()" doesn't close
	the	underlying file
Message-ID: <1377231601.59.0.456805422296.issue18815@psf.upfronthosting.co.za>


New submission from Jes?s Cea Avi?n:

In documentation http://docs.python.org/3.3/library/mmap.html#mmap.close you can read: "Close the file". I could interpret that it is going to close the file vinculated to the MMAP. But it doesn't. It only close the MMAP object (as it should).

Please, update doc to clear possible misunderstandings. Thanks.

----------
assignee: docs at python
keywords: easy
messages: 195939
nosy: docs at python, jcea
priority: normal
severity: normal
status: open
title: DOCUMENTATION: "mmap .close()" doesn't close the underlying file

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

From report at bugs.python.org  Fri Aug 23 08:46:35 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 23 Aug 2013 06:46:35 +0000
Subject: [docs] [issue18713] Clearly document the use of PYTHONIOENCODING to
	set	surrogateescape
In-Reply-To: <1376320774.07.0.703505392881.issue18713@psf.upfronthosting.co.za>
Message-ID: <1377240395.62.0.546052423026.issue18713@psf.upfronthosting.co.za>


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


----------
dependencies: +Empty PYTHONIOENCODING is not the same as nonexistent

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

From report at bugs.python.org  Fri Aug 23 12:30:30 2013
From: report at bugs.python.org (July Tikhonov)
Date: Fri, 23 Aug 2013 10:30:30 +0000
Subject: [docs] [issue18820] json.dump() ignores its 'default' option
	when	serializing dictionary keys
Message-ID: <1377253830.03.0.463497944995.issue18820@psf.upfronthosting.co.za>


New submission from July Tikhonov:

According to documentation of json.dump(), concerning its 'default' option:

default(obj) is a function that should return a serializable version of obj or raise TypeError. The default simply raises TypeError.

But this function is actually never applied to serialized dictionary keys:

>>> def default(obj):
...  if isinstance(obj, bytes):
...   return obj.decode('ascii')
...  raise ValueError
... 
>>> json.dumps(b'asdf')
Traceback (most recent call last):
...
TypeError: b'asdf' is not JSON serializable
>>> json.dumps(b'asdf', default=default)
'"asdf"'
>>> json.dumps({b'asdf' : 1}, default=default)
Traceback (most recent call last):
...
TypeError: keys must be a string
>>> json.dumps({1 : b'asdf'}, default=default)
'{"1": "asdf"}'

(bytes are used purely for the purpose of example)
Such behavior should be either documented or corrected.
Patch correcting python implementation of json attached.

----------
assignee: docs at python
components: Documentation, Library (Lib)
files: json-default-dict-keys.diff
keywords: patch
messages: 195957
nosy: docs at python, july
priority: normal
severity: normal
status: open
title: json.dump() ignores its 'default' option when serializing dictionary keys
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file31436/json-default-dict-keys.diff

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

From report at bugs.python.org  Fri Aug 23 12:58:37 2013
From: report at bugs.python.org (July Tikhonov)
Date: Fri, 23 Aug 2013 10:58:37 +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: <1377255517.71.0.983663189845.issue18820@psf.upfronthosting.co.za>


July Tikhonov added the comment:

Oops, my patch disables 'skipkeys' argument of dump. Another version attached.

----------
Added file: http://bugs.python.org/file31437/json-default-dict-keys.diff

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

From report at bugs.python.org  Fri Aug 23 12:59:26 2013
From: report at bugs.python.org (July Tikhonov)
Date: Fri, 23 Aug 2013 10:59:26 +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: <1377255566.88.0.283490620423.issue18820@psf.upfronthosting.co.za>


Changes by July Tikhonov <july.tikh at gmail.com>:


Removed file: http://bugs.python.org/file31436/json-default-dict-keys.diff

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

From report at bugs.python.org  Fri Aug 23 14:52:26 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 23 Aug 2013 12:52:26 +0000
Subject: [docs] [issue18713] Clearly document the use of PYTHONIOENCODING to
	set	surrogateescape
In-Reply-To: <1376320774.07.0.703505392881.issue18713@psf.upfronthosting.co.za>
Message-ID: <1377262346.43.0.646810991672.issue18713@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

With new subject this issue looks as a duplicate of (or tightly related to) issue12832.

----------

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

From report at bugs.python.org  Fri Aug 23 16:40:28 2013
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 23 Aug 2013 14:40:28 +0000
Subject: [docs] [issue18326] Mention 'keyword only' for list.sort,
	improve  glossary.
In-Reply-To: <1372511136.61.0.278425078947.issue18326@psf.upfronthosting.co.za>
Message-ID: <1377268828.19.0.593036145121.issue18326@psf.upfronthosting.co.za>


Zachary Ware added the comment:

How about a combination of the two?  It's still short, but gets the point across without assuming the reader knows exactly what 'keyword-only argument' or requiring further reading, while introducing the term and providing the link for deeper understanding.

(Here's the relevant change in this patch, the rest is the same:)

+      :meth:`sort` accepts two arguments that must be passed by keyword
+      (:ref:`keyword-only arguments <keyword-only_parameter>`):

----------
Added file: http://bugs.python.org/file31440/issue18326.v3.diff

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

From report at bugs.python.org  Fri Aug 23 17:15:46 2013
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 23 Aug 2013 15:15:46 +0000
Subject: [docs] [issue17326] Windows build docs still referring to VS 2008
	in 3.3
In-Reply-To: <1362142705.89.0.367756520949.issue17326@psf.upfronthosting.co.za>
Message-ID: <1377270946.35.0.37472206454.issue17326@psf.upfronthosting.co.za>


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


----------
versions: +Python 3.4

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

From report at bugs.python.org  Fri Aug 23 18:41:32 2013
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Fri, 23 Aug 2013 16:41:32 +0000
Subject: [docs] [issue18767] csv documentation does not note default quote
	constant
In-Reply-To: <1376706253.43.0.482794872786.issue18767@psf.upfronthosting.co.za>
Message-ID: <1377276092.33.0.515110057321.issue18767@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/issue18767>
_______________________________________

From report at bugs.python.org  Fri Aug 23 18:56:15 2013
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Fri, 23 Aug 2013 16:56:15 +0000
Subject: [docs] [issue18760] Fix internal doc references for the xml package
In-Reply-To: <1376681899.06.0.47911099673.issue18760@psf.upfronthosting.co.za>
Message-ID: <1377276975.25.0.438590525997.issue18760@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/issue18760>
_______________________________________

From report at bugs.python.org  Fri Aug 23 21:00:15 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 23 Aug 2013 19:00:15 +0000
Subject: [docs] [issue18760] Fix internal doc references for the xml package
In-Reply-To: <1376681899.06.0.47911099673.issue18760@psf.upfronthosting.co.za>
Message-ID: <1377284415.18.0.855559154071.issue18760@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Serhiy, you forgot to attach the patch.

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

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

From report at bugs.python.org  Fri Aug 23 21:18:06 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 23 Aug 2013 19:18:06 +0000
Subject: [docs] [issue18760] Fix internal doc references for the xml package
In-Reply-To: <1376681899.06.0.47911099673.issue18760@psf.upfronthosting.co.za>
Message-ID: <1377285486.8.0.0149682398272.issue18760@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Sorry. Can't believe I done it again.

----------
keywords: +patch
Added file: http://bugs.python.org/file31448/refs.xml.diff

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

From report at bugs.python.org  Fri Aug 23 21:21:52 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 23 Aug 2013 19:21:52 +0000
Subject: [docs] [issue18757] Fix internal references for concurrent modules
In-Reply-To: <1376675015.24.0.101209198038.issue18757@psf.upfronthosting.co.za>
Message-ID: <1377285711.93.0.844123234667.issue18757@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

LGTM.

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

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

From report at bugs.python.org  Fri Aug 23 21:41:58 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 23 Aug 2013 19:41:58 +0000
Subject: [docs] [issue18796] Wrong documentation of show_code function from
	dis module
In-Reply-To: <1377053819.02.0.986969704551.issue18796@psf.upfronthosting.co.za>
Message-ID: <3cMCfs3YRBz7Ll9@mail.python.org>


Roundup Robot added the comment:

New changeset 64678369c4d0 by Ezio Melotti in branch 'default':
#18796: improve documentation of the file argument of dis.show_code.  Initial patch by Vajrasky Kok.
http://hg.python.org/cpython/rev/64678369c4d0

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

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

From report at bugs.python.org  Fri Aug 23 21:43:18 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 23 Aug 2013 19:43:18 +0000
Subject: [docs] [issue18796] Wrong documentation of show_code function from
	dis module
In-Reply-To: <1377053819.02.0.986969704551.issue18796@psf.upfronthosting.co.za>
Message-ID: <1377286998.65.0.431946492194.issue18796@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the report and the patch!

----------
assignee: docs at python -> ezio.melotti
nosy: +ezio.melotti
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
type:  -> enhancement

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

From report at bugs.python.org  Fri Aug 23 22:13:29 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 23 Aug 2013 20:13:29 +0000
Subject: [docs] [issue18800] Document Fraction's numerator and denominator
	properties
In-Reply-To: <1377104746.66.0.571132107535.issue18800@psf.upfronthosting.co.za>
Message-ID: <1377288809.55.0.679822901343.issue18800@psf.upfronthosting.co.za>


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


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

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

From ezio.melotti at gmail.com  Fri Aug 23 22:27:55 2013
From: ezio.melotti at gmail.com (ezio.melotti at gmail.com)
Date: Fri, 23 Aug 2013 20:27:55 -0000
Subject: [docs] Fix more typos in .py files (issue 18803)
Message-ID: <20130823202755.18559.65959@psf.upfronthosting.co.za>


http://bugs.python.org/review/18803/diff/9027/Lib/inspect.py
File Lib/inspect.py (right):

http://bugs.python.org/review/18803/diff/9027/Lib/inspect.py#newcode50
Lib/inspect.py:50: # back to hard-coding so the dependency is optional
Apparently the "hardcoding" spelling is accepted too (and I prefer it).

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

From report at bugs.python.org  Fri Aug 23 22:28:02 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 23 Aug 2013 20:28:02 +0000
Subject: [docs] [issue18803] Fix more typos in .py files
In-Reply-To: <1377119764.79.0.128935070292.issue18803@psf.upfronthosting.co.za>
Message-ID: <1377289682.5.0.0554781866962.issue18803@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti
stage:  -> patch review

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

From report at bugs.python.org  Fri Aug 23 22:32:50 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 23 Aug 2013 20:32:50 +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: <1377289970.04.0.288016870567.issue18820@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Are there already tests that cover the changes in your patch?  If not, could you add them?

----------
nosy: +ezio.melotti, pitrou, rhettinger
stage:  -> test needed

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

From report at bugs.python.org  Fri Aug 23 23:37:12 2013
From: report at bugs.python.org (July Tikhonov)
Date: Fri, 23 Aug 2013 21:37:12 +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: <1377293832.73.0.174419115773.issue18820@psf.upfronthosting.co.za>


July Tikhonov added the comment:

Proposed tests attached.

----------
Added file: http://bugs.python.org/file31450/json-default-tests.diff

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

From report at bugs.python.org  Fri Aug 23 23:39:08 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 23 Aug 2013 21:39:08 +0000
Subject: [docs] [issue18803] Fix more typos in .py files
In-Reply-To: <1377119764.79.0.128935070292.issue18803@psf.upfronthosting.co.za>
Message-ID: <1377293948.29.0.0552522337387.issue18803@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Incorrect fixes.
accidentaly -> accidentally
occurence -> occurrence

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

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

From report at bugs.python.org  Fri Aug 23 23:45:22 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 23 Aug 2013 21:45:22 +0000
Subject: [docs] [issue18757] Fix internal references for concurrent modules
In-Reply-To: <1376675015.24.0.101209198038.issue18757@psf.upfronthosting.co.za>
Message-ID: <3cMGPF6fBDz7Ljs@mail.python.org>


Roundup Robot added the comment:

New changeset 6575074aae1c by Serhiy Storchaka in branch '3.3':
Issue #18757: Improved cross-references in the concurrent package.
http://hg.python.org/cpython/rev/6575074aae1c

New changeset 383d85249997 by Serhiy Storchaka in branch 'default':
Issue #18757: Improved cross-references in the concurrent package.
http://hg.python.org/cpython/rev/383d85249997

New changeset c24941251473 by Serhiy Storchaka in branch '2.7':
Issue #18757: Improved cross-references in the concurrent package.
http://hg.python.org/cpython/rev/c24941251473

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

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

From report at bugs.python.org  Fri Aug 23 23:49:02 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 23 Aug 2013 21:49:02 +0000
Subject: [docs] [issue18757] Fix internal references for concurrent modules
In-Reply-To: <1376675015.24.0.101209198038.issue18757@psf.upfronthosting.co.za>
Message-ID: <1377294542.24.0.0326577156035.issue18757@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you for the review Ezio.

----------
resolution:  -> fixed
stage: commit review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Sat Aug 24 08:10:38 2013
From: report at bugs.python.org (Martin Panter)
Date: Sat, 24 Aug 2013 06:10:38 +0000
Subject: [docs] [issue15125] argparse: positional arguments containing - in
	name not	handled well
In-Reply-To: <1340292847.64.0.123942573403.issue15125@psf.upfronthosting.co.za>
Message-ID: <1377324638.98.0.758283441674.issue15125@psf.upfronthosting.co.za>


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


----------
nosy: +vadmium

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

From report at bugs.python.org  Sat Aug 24 09:16:06 2013
From: report at bugs.python.org (Martin Panter)
Date: Sat, 24 Aug 2013 07:16:06 +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: <1377328566.28.0.0925079648541.issue14191@psf.upfronthosting.co.za>


Martin Panter added the comment:

It sounds like this bug might cover Issue 15112, which is only concerned with options between different positional parameters.

----------
nosy: +vadmium

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

From report at bugs.python.org  Sat Aug 24 18:13:12 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Sat, 24 Aug 2013 16:13:12 +0000
Subject: [docs] [issue18803] Fix more typos in .py files
In-Reply-To: <1377119764.79.0.128935070292.issue18803@psf.upfronthosting.co.za>
Message-ID: <1377360791.94.0.0762654293764.issue18803@psf.upfronthosting.co.za>


F?vry Thibault added the comment:

Ezio : Yes, I was just following Reddy's advice from another bug report (issue 18466) 

Terry : Yes, looks like I was tired while doing that...

 Should be fixed in the updated patch

----------
Added file: http://bugs.python.org/file31454/more_typos.diff

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

From report at bugs.python.org  Sun Aug 25 00:05:21 2013
From: report at bugs.python.org (Alexander Schier)
Date: Sat, 24 Aug 2013 22:05:21 +0000
Subject: [docs] [issue18827] mistake in the timedelta.total_seconds docstring
Message-ID: <1377381921.16.0.995171026465.issue18827@psf.upfronthosting.co.za>


New submission from Alexander Schier:

> Return the total number of seconds contained in the duration. Equivalent to (td.microseconds + (td.seconds + td.days * 24 * 3600) * 10**6) / 10**6 computed with true division enabled.

Should be
> Return the total number of seconds contained in the duration. Equivalent to (td.microseconds / 10**6 + (td.seconds + td.days * 24 * 3600) * 10**6) computed with true division enabled.

At least i hope, the bug is only in the docs and not in the function ;).

----------
assignee: docs at python
components: Documentation
messages: 196100
nosy: allo, docs at python
priority: normal
severity: normal
status: open
title: mistake in the timedelta.total_seconds docstring
type: behavior
versions: Python 2.7

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

From report at bugs.python.org  Sun Aug 25 00:14:29 2013
From: report at bugs.python.org (Tim Peters)
Date: Sat, 24 Aug 2013 22:14:29 +0000
Subject: [docs] [issue18827] mistake in the timedelta.total_seconds docstring
In-Reply-To: <1377381921.16.0.995171026465.issue18827@psf.upfronthosting.co.za>
Message-ID: <1377382469.42.0.295230732266.issue18827@psf.upfronthosting.co.za>


Tim Peters added the comment:

The docs look correct to me.  For example,

>>> from datetime import *
>>> td = datetime.now() - datetime(1,1,1)
>>> td
datetime.timedelta(735103, 61756, 484000)
>>> td.total_seconds()
63512960956.484
                                                                ^
What the docs say match that output:

>>> (td.microseconds + (td.seconds + td.days * 24 * 3600) * 10**6) / 1e6
63512960956.484

Your suggestion's output:

>>> (td.microseconds / 1e6 + (td.seconds + td.days * 24 * 3600) * 10**6)
6.3512960956e+16

You're multiplying the number seconds by a million - not a good idea ;-)

----------
nosy: +tim.peters

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

From report at bugs.python.org  Sun Aug 25 00:31:43 2013
From: report at bugs.python.org (Alexander Schier)
Date: Sat, 24 Aug 2013 22:31:43 +0000
Subject: [docs] [issue18827] mistake in the timedelta.total_seconds docstring
In-Reply-To: <1377381921.16.0.995171026465.issue18827@psf.upfronthosting.co.za>
Message-ID: <1377383503.0.0.362723496873.issue18827@psf.upfronthosting.co.za>


Alexander Schier added the comment:

Err, sorry my fault. Too late in the evening ;).

I saw the division by one million, but not the multiplation by one million before. Additionally i was confused, because i expected that seconds are added to each other in the parenthesis.

closing.

----------
resolution:  -> invalid
status: open -> closed

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

From report at bugs.python.org  Sun Aug 25 04:01:09 2013
From: report at bugs.python.org (paul j3)
Date: Sun, 25 Aug 2013 02:01:09 +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: <1377396068.92.0.880123129049.issue14191@psf.upfronthosting.co.za>


paul j3 added the comment:

Above in
http://bugs.python.org/issue14191#msg187051
I proposed a patch that is quite close to bethard's patch in http://bugs.python.org/issue15112#msg166173

Both modify the same place, doing the same (pop items off arg_counts).  The logic is a little different.  I'd have to look at them more carefully to see whether one is more robust.  Thanks for linking that issue.

The main issue here is different, allowing for complete intermixing of optionals and positionals.  Over at 15112 the issue is intermixing of optionals and 'whole' positionals.  My 187051 patch belongs over there.

----------

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

From report at bugs.python.org  Sun Aug 25 04:02:22 2013
From: report at bugs.python.org (paul j3)
Date: Sun, 25 Aug 2013 02:02:22 +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: <1377396142.33.0.797560015548.issue14191@psf.upfronthosting.co.za>


Changes by paul j3 <ajipanca at gmail.com>:


Added file: http://bugs.python.org/file29880/mixed.patch

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

From report at bugs.python.org  Sun Aug 25 04:13:03 2013
From: report at bugs.python.org (paul j3)
Date: Sun, 25 Aug 2013 02:13:03 +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: <1377396783.27.0.612116384427.issue14191@psf.upfronthosting.co.za>


Changes by paul j3 <ajipanca at gmail.com>:


Removed file: http://bugs.python.org/file29880/mixed.patch

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

From report at bugs.python.org  Mon Aug 26 00:34:02 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 25 Aug 2013 22:34:02 +0000
Subject: [docs] [issue18803] Fix more typos in .py files
In-Reply-To: <1377119764.79.0.128935070292.issue18803@psf.upfronthosting.co.za>
Message-ID: <3cNWNT4Gl6z7Ljh@mail.python.org>


Roundup Robot added the comment:

New changeset 33b156e118c0 by Ezio Melotti in branch '2.7':
#18803: fix more typos.  Patch by F?vry Thibault.
http://hg.python.org/cpython/rev/33b156e118c0

New changeset c57d99a8fc42 by Ezio Melotti in branch '3.3':
#18803: fix more typos.  Patch by F?vry Thibault.
http://hg.python.org/cpython/rev/c57d99a8fc42

New changeset 6b28bfff9204 by Ezio Melotti in branch 'default':
#18803: merge with 3.3.
http://hg.python.org/cpython/rev/6b28bfff9204

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

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

From report at bugs.python.org  Mon Aug 26 00:35:06 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 25 Aug 2013 22:35:06 +0000
Subject: [docs] [issue18803] Fix more typos in .py files
In-Reply-To: <1377119764.79.0.128935070292.issue18803@psf.upfronthosting.co.za>
Message-ID: <1377470106.04.0.570735144885.issue18803@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the report and the patch!

----------
assignee: docs at python -> ezio.melotti
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Mon Aug 26 08:56:10 2013
From: report at bugs.python.org (=?utf-8?q?Tomi_Pievil=C3=A4inen?=)
Date: Mon, 26 Aug 2013 06:56:10 +0000
Subject: [docs] [issue18837] multiprocessing.reduction is undocumented
Message-ID: <1377500170.46.0.281746133519.issue18837@psf.upfronthosting.co.za>


New submission from Tomi Pievil?inen:

In older versions (2.x, 3.2, 3.3) multiprocessing.reduction was only mentioned in a one example, with a one comment after it. In the 3.4dev documentation even this was dropped.

----------
assignee: docs at python
components: Documentation
messages: 196184
nosy: docs at python, tpievila
priority: normal
severity: normal
status: open
title: multiprocessing.reduction is undocumented
versions: Python 3.4

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

From report at bugs.python.org  Mon Aug 26 08:58:14 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 26 Aug 2013 06:58:14 +0000
Subject: [docs] [issue18837] multiprocessing.reduction is undocumented
In-Reply-To: <1377500170.46.0.281746133519.issue18837@psf.upfronthosting.co.za>
Message-ID: <1377500294.89.0.0097040510521.issue18837@psf.upfronthosting.co.za>


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


----------
nosy: +jnoller, sbt

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

From report at bugs.python.org  Mon Aug 26 12:51:32 2013
From: report at bugs.python.org (Marco Buttu)
Date: Mon, 26 Aug 2013 10:51:32 +0000
Subject: [docs] [issue18839] Wrong sentence in sys.exit.__doc__
Message-ID: <1377514292.79.0.0321965724475.issue18839@psf.upfronthosting.co.za>


New submission from Marco Buttu:

Python 3.3::

    >>> import sys
    >>> print(sys.exit.__doc__)
    exit([status])

    Exit the interpreter by raising SystemExit(status).
    If the status is omitted or None, it defaults to zero (i.e., success).
    If the status is numeric, it will be used as the system exit status.
    If it is another kind of object, it will be printed and the system
    exit status will be one (i.e., failure).

The sentence "If the status is numeric, it will be used as the system exit status."
is wrong::

    >>> sys.exit(3.33)
    3.33
    $ echo $?
    1


It should be "If the status is an *integer*, it will be used as the system exit status.",
as specified in the SystemExit `doc`.

.. doc: http://docs.python.org/3/library/exceptions.html#SystemExit

----------
assignee: docs at python
components: Documentation
messages: 196195
nosy: docs at python, marco.buttu
priority: normal
severity: normal
status: open
title: Wrong sentence in sys.exit.__doc__
type: behavior

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

From report at bugs.python.org  Mon Aug 26 13:01:57 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 26 Aug 2013 11:01:57 +0000
Subject: [docs] [issue18839] Wrong sentence in sys.exit.__doc__
In-Reply-To: <1377514292.79.0.0321965724475.issue18839@psf.upfronthosting.co.za>
Message-ID: <3cNqzS3yvtz7LjM@mail.python.org>


Roundup Robot added the comment:

New changeset 187a678c6033 by Ezio Melotti in branch '2.7':
#18839: document that sys.exit() will not accept a non-integer numeric value as exit status.
http://hg.python.org/cpython/rev/187a678c6033

New changeset 694e50a79638 by Ezio Melotti in branch '3.3':
#18839: document that sys.exit() will not accept a non-integer numeric value as exit status.
http://hg.python.org/cpython/rev/694e50a79638

New changeset 6cb3ae431bef by Ezio Melotti in branch 'default':
#18839: merge with 3.3.
http://hg.python.org/cpython/rev/6cb3ae431bef

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

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

From report at bugs.python.org  Mon Aug 26 13:02:31 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 26 Aug 2013 11:02:31 +0000
Subject: [docs] [issue18839] Wrong sentence in sys.exit.__doc__
In-Reply-To: <1377514292.79.0.0321965724475.issue18839@psf.upfronthosting.co.za>
Message-ID: <1377514951.34.0.312296005278.issue18839@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the report!

----------
assignee: docs at python -> ezio.melotti
nosy: +ezio.melotti
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
type: behavior -> enhancement
versions: +Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon Aug 26 14:37:59 2013
From: report at bugs.python.org (Donald Stufft)
Date: Mon, 26 Aug 2013 12:37:59 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
Message-ID: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>


New submission from Donald Stufft:

The Python tutorial tells, and even recommends, new users that they can use the pickle module to serialize arbitrary objects. However it does not provide any warning about the insecurity of unpickling arbtirary data. The text even goes so far as to mention sending pickled data over a network connection to other machines.

I believe this section should be replaced with using the json module instead of pickle. It is more standard and doesn't present the same security concerns with untrusted data as pickle does. However if it continues to recommend pickle to new users it should at least warn them of the dangers of using pickle.

The section in question is located at http://docs.python.org/3/tutorial/inputoutput.html#the-pickle-module

----------
assignee: docs at python
components: Documentation
messages: 196203
nosy: docs at python, dstufft
priority: normal
severity: normal
status: open
title: Tutorial recommends pickle module without any warning of insecurity

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

From report at bugs.python.org  Mon Aug 26 14:51:40 2013
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Mon, 26 Aug 2013 12:51:40 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>
Message-ID: <1377521500.42.0.134653894567.issue18840@psf.upfronthosting.co.za>


Fred L. Drake, Jr. added the comment:

Advising the reader to be aware of the security warnings in the API documentation seems sufficient.

JSON isn't intended to support arbitrary data, and that's what this section is discussing.  Another section about data interchange with other applications (regardless of language), may be a reasonable addition, or a good candidate for a separate How-To document that can be referenced.

----------
nosy: +fdrake

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

From report at bugs.python.org  Mon Aug 26 14:57:25 2013
From: report at bugs.python.org (Donald Stufft)
Date: Mon, 26 Aug 2013 12:57:25 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>
Message-ID: <1377521845.76.0.485486519886.issue18840@psf.upfronthosting.co.za>


Donald Stufft added the comment:

The section to me just seems to be about how to handle more than just strings, it mentions numbers, lists, dictionaries, and class instances. Of those it mentions, only the class instances are not able to handled out of the box by JSON.

However like I said even if it remains pickle this particular area of the documentation should still warn users even though there's already a warning in the API documentation for pickle. As it is if a new user reads this and doesn't click through to the API documentation they've received recommendation from the Python documentation that they can send pickle strings over the network. This is dangerous behavior and the documentation shouldn't be advising new users to do dangerous things by default.

----------

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

From report at bugs.python.org  Mon Aug 26 14:59:38 2013
From: report at bugs.python.org (Donald Stufft)
Date: Mon, 26 Aug 2013 12:59:38 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>
Message-ID: <1377521978.91.0.716599581247.issue18840@psf.upfronthosting.co.za>


Donald Stufft added the comment:

Further more the tutorial claims it's the standard way of persisting data which in my experience it's far from that due to the security concerns. I've seen very little actual use of pickle in the wild (and when it was used it was often used by people who didn't understand the security implications).

----------

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

From report at bugs.python.org  Mon Aug 26 16:16:22 2013
From: report at bugs.python.org (Martin Panter)
Date: Mon, 26 Aug 2013 14:16:22 +0000
Subject: [docs] [issue1944] Documentation for PyUnicode_AsString (et al.)
	missing.
In-Reply-To: <1201415203.65.0.272410099804.issue1944@psf.upfronthosting.co.za>
Message-ID: <1377526582.45.0.543056410649.issue1944@psf.upfronthosting.co.za>


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


----------
nosy: +vadmium

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

From report at bugs.python.org  Mon Aug 26 17:02:03 2013
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Mon, 26 Aug 2013 15:02:03 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>
Message-ID: <1377529323.79.0.488028735319.issue18840@psf.upfronthosting.co.za>


Fred L. Drake, Jr. added the comment:

When I read "... that can take almost any Python object  ...", I don't think the recommendation is about just a few types.

The Zope and ZODB communities certainly use pickle extensively, we're aware of the security implications, and we send pickled data over the network all the time.

----------

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

From report at bugs.python.org  Mon Aug 26 17:13:49 2013
From: report at bugs.python.org (Donald Stufft)
Date: Mon, 26 Aug 2013 15:13:49 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>
Message-ID: <1377530029.44.0.512094533134.issue18840@psf.upfronthosting.co.za>


Donald Stufft added the comment:

A description of the pickle module itself does not equate to the purpose of the section. Given that this is a tutorial and previous section taught how to read and write from files I would suggest that the purpose of the section was to give them the next step to persisting data which could be pickle or it could be JSON (or it could be another format all together). 

I don't see what Zope/ZODB's awareness of the security implications has to do with anything unless you're trying to state that the developers and users of ZODB are newcomers to Python whose knowledge of pickle stems from what they read in the tutorial. However I am glad that those communities are aware of the implications if they are using that module, but the point is the reader of the tutorial is *not* likely to be aware of them and should *not* be using pickle without being aware of them especially if they are sending that data over the network.

I'm really not sure what your problem is here. What is there to lose by annotating this section of the tutorial with a similar warning as exists in the pickle documentation that they should not unpickle data from an untrusted or unauthenticated sources? I can see how someone could state that the problem with switching to JSON is that it's harder to construct a serialization for arbitrary objects. That's not something I think it all that important to teach someone brand new to Python however I can understand if switching this section to using a "safe" serialization format doesn't sit well with people which is why I suggested at least adding a warning.

So what exactly is your problem with at a minimum adding a warning?

----------

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

From report at bugs.python.org  Mon Aug 26 17:38:40 2013
From: report at bugs.python.org (Steven D'Aprano)
Date: Mon, 26 Aug 2013 15:38:40 +0000
Subject: [docs] [issue18841] math.isfinite fails with Decimal sNAN
Message-ID: <1377531520.63.0.106544243675.issue18841@psf.upfronthosting.co.za>


New submission from Steven D'Aprano:

math.isfinite currently raises ValueError when given a Decimal sNAN (signalling NAN).

I've run into a situation where I'm calling isfinite() on a numeric value which may be a Decimal sNAN, and it would be nice if it returned False.

On the other hand, see the discussion on issue 15544, which possibly leads to the conclusion that raising ValueError is the right thing to do.

http://bugs.python.org/issue15544

Either way, behaviour should be documented.

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 196213
nosy: docs at python, stevenjd
priority: normal
severity: normal
status: open
title: math.isfinite fails with Decimal sNAN
type: behavior
versions: Python 3.4

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

From report at bugs.python.org  Mon Aug 26 17:42:33 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 26 Aug 2013 15:42:33 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>
Message-ID: <1377531753.87.0.0579855193146.issue18840@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

I would be ok with changing that part of the tutorial to use json. Since json is much better known outside of the Python programming circles, and since its output is human-readable, it's probably a better fit for the tutorial. pickle can be mentioned as a more powerful and more dangerous alternative.

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

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

From report at bugs.python.org  Mon Aug 26 17:52:11 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 26 Aug 2013 15:52:11 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>
Message-ID: <1377532331.57.0.772877249691.issue18840@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

By the way, there is one difference between json and pickle in this context: json will output a text serialization, pickle a binary one. If serializing to a binary file, users must do the (utf-8, most likely) encoding themselves.

----------

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

From report at bugs.python.org  Mon Aug 26 19:04:15 2013
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Mon, 26 Aug 2013 17:04:15 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>
Message-ID: <1377536655.92.0.888524290703.issue18840@psf.upfronthosting.co.za>


Changes by Fred L. Drake, Jr. <fdrake at gmail.com>:


----------
nosy:  -fdrake

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

From report at bugs.python.org  Mon Aug 26 19:45:48 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 26 Aug 2013 17:45:48 +0000
Subject: [docs] [issue18841] math.isfinite fails with Decimal sNAN
In-Reply-To: <1377531520.63.0.106544243675.issue18841@psf.upfronthosting.co.za>
Message-ID: <1377539148.18.0.657378127766.issue18841@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Aug 27 03:21:37 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Tue, 27 Aug 2013 01:21:37 +0000
Subject: [docs] [issue17902] Document that _elementtree C API cannot use
	custom	TreeBuilder for iterparse or IncrementalParser
In-Reply-To: <1367614578.64.0.34953241054.issue17902@psf.upfronthosting.co.za>
Message-ID: <1377566496.87.0.3638890359.issue17902@psf.upfronthosting.co.za>


Eli Bendersky added the comment:

Aaron - could you describe your use case of passing a custom parser into iterparse? We're currently considering deprecating the feature of passing a parser into iterparse in a future release (this is being discussed in issue 17741).

----------

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

From report at bugs.python.org  Tue Aug 27 04:11:20 2013
From: report at bugs.python.org (Aaron Oakley)
Date: Tue, 27 Aug 2013 02:11:20 +0000
Subject: [docs] [issue17902] Document that _elementtree C API cannot use
	custom	TreeBuilder for iterparse or IncrementalParser
In-Reply-To: <1367614578.64.0.34953241054.issue17902@psf.upfronthosting.co.za>
Message-ID: <1377569480.34.0.0904623844155.issue17902@psf.upfronthosting.co.za>


Aaron Oakley added the comment:

>From memory, the use case at the time was using a custom TreeBuilder sub-class fed into a builtin XMLParser object. The code would construct a builder separately and keep a reference to it around. The builder would delegate calls to start(), data(), end(), and close() to super and save the completed tree when its close() was called.

    my_builder = CustomTreeBuilder()
    et_parser = ET.XMLParser(target=my_builder)

    for (evt, elem) in ET.iterparse("...", events, parser=et_parser):
        pass  # Do first processing

    tree = my_builder.root  # Saved tree

It was done like this initially so that some data (I can't recall exactly what) from the XML input could be processed first very conveniently using the parse events from iterparse while allowing the whole tree to be retrieved afterwards.

That said, the project later moved to using lxml for various features not contained in xml.etree.ElementTree, and I don't think the process I described is still being used.

----------

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

From report at bugs.python.org  Tue Aug 27 04:57:46 2013
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Tue, 27 Aug 2013 02:57:46 +0000
Subject: [docs] [issue18177] Incorect quote marks in code section-headers in
	PDF	version of docs
In-Reply-To: <1370829780.84.0.0627044566719.issue18177@psf.upfronthosting.co.za>
Message-ID: <1377572266.45.0.322779538072.issue18177@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/issue18177>
_______________________________________

From report at bugs.python.org  Tue Aug 27 05:41:41 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Tue, 27 Aug 2013 03:41:41 +0000
Subject: [docs] [issue17902] Document that _elementtree C API cannot use
	custom	TreeBuilder for iterparse or IncrementalParser
In-Reply-To: <1377569480.34.0.0904623844155.issue17902@psf.upfronthosting.co.za>
Message-ID: <CAF-Rda9A8JPzWGrpFr_YTFSxwmUtFQcSE8xvs_voftQdwou3_w@mail.gmail.com>


Eli Bendersky added the comment:

On Mon, Aug 26, 2013 at 7:11 PM, Aaron Oakley <report at bugs.python.org>wrote:

>
> Aaron Oakley added the comment:
>
> >From memory, the use case at the time was using a custom TreeBuilder
> sub-class fed into a builtin XMLParser object. The code would construct a
> builder separately and keep a reference to it around. The builder would
> delegate calls to start(), data(), end(), and close() to super and save the
> completed tree when its close() was called.
>
>     my_builder = CustomTreeBuilder()
>     et_parser = ET.XMLParser(target=my_builder)
>
>     for (evt, elem) in ET.iterparse("...", events, parser=et_parser):
>         pass  # Do first processing
>
>     tree = my_builder.root  # Saved tree
>
> It was done like this initially so that some data (I can't recall exactly
> what) from the XML input could be processed first very conveniently using
> the parse events from iterparse while allowing the whole tree to be
> retrieved afterwards.
>
> That said, the project later moved to using lxml for various features not
> contained in xml.etree.ElementTree, and I don't think the process I
> described is still being used.
>

Thanks for the information, Aaron; much appreciated.

----------

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

From report at bugs.python.org  Tue Aug 27 14:23:59 2013
From: report at bugs.python.org (Madison May)
Date: Tue, 27 Aug 2013 12:23:59 +0000
Subject: [docs] [issue18800] Document Fraction's numerator and denominator
	properties
In-Reply-To: <1377104746.66.0.571132107535.issue18800@psf.upfronthosting.co.za>
Message-ID: <1377606239.36.0.741749610607.issue18800@psf.upfronthosting.co.za>


Madison May added the comment:

The docs page does mention, however, that Fraction inherits from numbers.Rational, and links to that page (http://docs.python.org/2/library/numbers.html#numbers.Rational). There the properties 'numerator' and 'denominator' are clearly documented.  Perhaps its still worth it to mention those properties on the Fraction docs page though, or to include them in one of the examples.

----------
nosy: +madison.may

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

From report at bugs.python.org  Tue Aug 27 17:16:10 2013
From: report at bugs.python.org (Madison May)
Date: Tue, 27 Aug 2013 15:16:10 +0000
Subject: [docs] [issue18855] Inconsistent README filenames
Message-ID: <1377616570.1.0.108273179071.issue18855@psf.upfronthosting.co.za>


New submission from Madison May:

Is there any reason (other than backwards compatibility) that the names of README files are inconsistent?

README: 3 instances - root, /Mac, /Misc, /Tools
readme.txt: 2 instances - /PC, /PCbuild
README.txt: 1 instance - /Doc

----------
assignee: docs at python
components: Documentation
messages: 196299
nosy: docs at python, madison.may
priority: normal
severity: normal
status: open
title: Inconsistent README filenames

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

From report at bugs.python.org  Tue Aug 27 22:09:29 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 27 Aug 2013 20:09:29 +0000
Subject: [docs] [issue18855] Inconsistent README filenames
In-Reply-To: <1377616570.1.0.108273179071.issue18855@psf.upfronthosting.co.za>
Message-ID: <1377634169.52.0.12617826552.issue18855@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

No reason really. We could standardize all of them on README.txt, perhaps.

----------
nosy: +pitrou
priority: normal -> low
versions: +Python 3.4

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

From report at bugs.python.org  Tue Aug 27 22:42:52 2013
From: report at bugs.python.org (Madison May)
Date: Tue, 27 Aug 2013 20:42:52 +0000
Subject: [docs] [issue18855] Inconsistent README filenames
In-Reply-To: <1377616570.1.0.108273179071.issue18855@psf.upfronthosting.co.za>
Message-ID: <1377636172.37.0.57987647947.issue18855@psf.upfronthosting.co.za>


Madison May added the comment:

It's obviously low priority, just thought I would mention it.  I found it a bit odd that "README" is used, though, since that means users will likely have to select the program they want to use to open the file (in Windows, at least).  

It might also be nice to follow the standard distutils idiom. From ?ric Araujo on issue11913, 

"In packaging/distutils2, the recommended idiom looks like this (in setup.cfg):

    [metadata]
    description-file = README.whatever"

In other words, README.txt would work nicely.

----------

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

From report at bugs.python.org  Wed Aug 28 12:32:48 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 28 Aug 2013 10:32:48 +0000
Subject: [docs] [issue18855] Inconsistent README filenames
In-Reply-To: <1377616570.1.0.108273179071.issue18855@psf.upfronthosting.co.za>
Message-ID: <1377685968.14.0.0535402417637.issue18855@psf.upfronthosting.co.za>


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


----------
nosy: +eric.araujo, ezio.melotti, tim.peters
type:  -> enhancement

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

From report at bugs.python.org  Wed Aug 28 21:32:58 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 28 Aug 2013 19:32:58 +0000
Subject: [docs] [issue18871] Be more stringent about the test suite
Message-ID: <1377718378.43.0.460982109409.issue18871@psf.upfronthosting.co.za>


New submission from Antoine Pitrou:

Here is a proposal to make the devguide more precise and explicit about needing to run the entire test suite before committing a change.

----------
assignee: docs at python
components: Devguide, Documentation
files: test_suite.patch
keywords: patch
messages: 196405
nosy: asvetlov, docs at python, eric.araujo, ezio.melotti, ncoghlan, pitrou, r.david.murray
priority: normal
severity: normal
status: open
title: Be more stringent about the test suite
type: enhancement
versions: 3rd party
Added file: http://bugs.python.org/file31500/test_suite.patch

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

From report at bugs.python.org  Wed Aug 28 21:45:07 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 28 Aug 2013 19:45:07 +0000
Subject: [docs] [issue18870] eval() uses latin-1 to decode str
In-Reply-To: <1377713902.12.0.966249722349.issue18870@psf.upfronthosting.co.za>
Message-ID: <1377719107.42.0.212952835006.issue18870@psf.upfronthosting.co.za>


R. David Murray added the comment:

I don't think it is even "won't fix".  Your "workarounds" are just the way you need to feed non-latin1 text into Python2.  Since the default source encoding in python2 is latin-1, and that is documented, I'm not sure what additional documentation you want?

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, r.david.murray

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

From report at bugs.python.org  Wed Aug 28 21:51:10 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 28 Aug 2013 19:51:10 +0000
Subject: [docs] [issue18871] Be more stringent about the test suite
In-Reply-To: <1377718378.43.0.460982109409.issue18871@psf.upfronthosting.co.za>
Message-ID: <1377719470.38.0.10949767816.issue18871@psf.upfronthosting.co.za>


R. David Murray added the comment:

Looks OK to me.  Do we want to also recommend more explicitly that the tests be run with -uall?

----------

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

From report at bugs.python.org  Wed Aug 28 22:16:18 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 28 Aug 2013 20:16:18 +0000
Subject: [docs] [issue18871] Be more stringent about the test suite
In-Reply-To: <1377718378.43.0.460982109409.issue18871@psf.upfronthosting.co.za>
Message-ID: <1377720978.63.0.846673837679.issue18871@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

I don't know. I wouldn't insist too much on -uall, because generally it won't find anything more (except for network tests, perhaps).

----------

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

From report at bugs.python.org  Wed Aug 28 22:20:31 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 28 Aug 2013 20:20:31 +0000
Subject: [docs] [issue18870] eval() uses latin-1 to decode str
In-Reply-To: <1377713902.12.0.966249722349.issue18870@psf.upfronthosting.co.za>
Message-ID: <1377721231.63.0.0300050247602.issue18870@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

> Since the default source encoding in python2 is latin-1

Mmh, really? According to PEP 263:

    Python will default to ASCII as standard encoding if no other
    encoding hints are given.

And indeed when trying Merlijn's code in a .py file rather than an eval() call, I get:

SyntaxError: Non-ASCII character '\xc3' in file tcc.py on line 1, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details

----------
components: +Interpreter Core -Documentation
nosy: +benjamin.peterson, pitrou
type:  -> behavior

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

From report at bugs.python.org  Wed Aug 28 22:23:29 2013
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 28 Aug 2013 20:23:29 +0000
Subject: [docs] [issue18870] eval() uses latin-1 to decode str
In-Reply-To: <1377713902.12.0.966249722349.issue18870@psf.upfronthosting.co.za>
Message-ID: <1377721409.91.0.751261467486.issue18870@psf.upfronthosting.co.za>


STINNER Victor added the comment:

Where / how do you type the eval() instruction? In IDLE, in the interactive prompt (>>>) or in a script (test.py)? What is your OS and what is your locale encoding?

Example:

$ python -m platform
Linux-3.9.4-200.fc18.x86_64-x86_64-with-fedora-18-Spherical_Cow
$ python -c 'import locale; print(locale.getpreferredencoding())'
UTF-8

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

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

From report at bugs.python.org  Wed Aug 28 22:24:39 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 28 Aug 2013 20:24:39 +0000
Subject: [docs] [issue18870] eval() uses latin-1 to decode str
In-Reply-To: <1377713902.12.0.966249722349.issue18870@psf.upfronthosting.co.za>
Message-ID: <1377721479.81.0.637994950538.issue18870@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

$ python
Python 2.7.4 (default, Apr 19 2013, 18:28:01) 
[GCC 4.7.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> eval("u'?'")
u'\xc3\xa4'
>>> import locale
>>> locale.getpreferredencoding()
'UTF-8'

----------

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

From report at bugs.python.org  Wed Aug 28 23:36:30 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 28 Aug 2013 21:36:30 +0000
Subject: [docs] [issue18871] Be more stringent about the test suite
In-Reply-To: <1377720978.63.0.846673837679.issue18871@psf.upfronthosting.co.za>
Message-ID: <CADiSq7ccAHQkcyZOTmO-ADZpwMRc3Q9-SzwjNSRM=8Fd98MsWQ@mail.gmail.com>


Nick Coghlan added the comment:

Looks good to me. I think it's OK to leave the optional resources in the
set of things covered by the buildbots rather than expecting them to always
be run in pre-commit testing.

----------

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

From report at bugs.python.org  Wed Aug 28 23:51:47 2013
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 28 Aug 2013 21:51:47 +0000
Subject: [docs] [issue18871] Be more stringent about the test suite
In-Reply-To: <1377718378.43.0.460982109409.issue18871@psf.upfronthosting.co.za>
Message-ID: <3cQLJL5XlmzNHd@mail.python.org>


Roundup Robot added the comment:

New changeset a62bb0481ac9 by Antoine Pitrou in branch 'default':
Issue #18871: make it more explicit that the test suite should be run before committing
http://hg.python.org/devguide/rev/a62bb0481ac9

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

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

From report at bugs.python.org  Wed Aug 28 23:52:40 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 28 Aug 2013 21:52:40 +0000
Subject: [docs] [issue18871] Be more stringent about the test suite
In-Reply-To: <1377718378.43.0.460982109409.issue18871@psf.upfronthosting.co.za>
Message-ID: <1377726760.44.0.463273787281.issue18871@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Thanks for allowing me to be lazy, Nick :-)

----------
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Wed Aug 28 23:53:22 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 28 Aug 2013 21:53:22 +0000
Subject: [docs] [issue18870] eval() uses latin-1 to decode str
In-Reply-To: <1377713902.12.0.966249722349.issue18870@psf.upfronthosting.co.za>
Message-ID: <1377726802.3.0.972836709525.issue18870@psf.upfronthosting.co.za>


R. David Murray added the comment:

Heh.  Obviously I've forgotten some things about python2.  I could have sworn the default was latin-1, but perhaps that was just the stdlib standard for coding cookies?  I don't use python2 much any more...

----------

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

From report at bugs.python.org  Thu Aug 29 00:12:23 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 28 Aug 2013 22:12:23 +0000
Subject: [docs] [issue18871] Be more stringent about the test suite
In-Reply-To: <1377726760.44.0.463273787281.issue18871@psf.upfronthosting.co.za>
Message-ID: <CADiSq7coRj4YFV9j5WB-7ysBoo89f1CNyPxaHPrnshpBSe7mVg@mail.gmail.com>


Nick Coghlan added the comment:

The fact I don't run the tests with - uall before committing had nothing to
do with it whatsoever. Nope. Nothing at all ;)

----------

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

From report at bugs.python.org  Thu Aug 29 00:46:30 2013
From: report at bugs.python.org (Benjamin Peterson)
Date: Wed, 28 Aug 2013 22:46:30 +0000
Subject: [docs] [issue18870] eval() uses latin-1 to decode str
In-Reply-To: <1377713902.12.0.966249722349.issue18870@psf.upfronthosting.co.za>
Message-ID: <1377729990.72.0.807115924764.issue18870@psf.upfronthosting.co.za>


Benjamin Peterson added the comment:

Yeah, this is an obnoxious bug. Too late to fix in Python 3, though. I would take a doc patch.

----------
components: +Documentation -Interpreter Core

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

From report at bugs.python.org  Thu Aug 29 06:19:08 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Thu, 29 Aug 2013 04:19:08 +0000
Subject: [docs] [issue18760] Fix internal doc references for the xml package
In-Reply-To: <1376681899.06.0.47911099673.issue18760@psf.upfronthosting.co.za>
Message-ID: <1377749948.36.0.433653086961.issue18760@psf.upfronthosting.co.za>


Eli Bendersky added the comment:

lgtm

----------

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

From report at bugs.python.org  Thu Aug 29 09:36:12 2013
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 29 Aug 2013 07:36:12 +0000
Subject: [docs] [issue18760] Fix internal doc references for the xml package
In-Reply-To: <1376681899.06.0.47911099673.issue18760@psf.upfronthosting.co.za>
Message-ID: <3cQbGg20SCz7LjS@mail.python.org>


Roundup Robot added the comment:

New changeset a426e5c03d6e by Serhiy Storchaka in branch '3.3':
Issue #18760: Improved cross-references in the xml package.
http://hg.python.org/cpython/rev/a426e5c03d6e

New changeset 32b59d122989 by Serhiy Storchaka in branch 'default':
Issue #18760: Improved cross-references in the xml package.
http://hg.python.org/cpython/rev/32b59d122989

New changeset 9c66b9cb886b by Serhiy Storchaka in branch '2.7':
Issue #18760: Improved cross-references in the xml package.
http://hg.python.org/cpython/rev/9c66b9cb886b

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

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

From report at bugs.python.org  Thu Aug 29 09:54:59 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 29 Aug 2013 07:54:59 +0000
Subject: [docs] [issue18760] Fix internal doc references for the xml package
In-Reply-To: <1376681899.06.0.47911099673.issue18760@psf.upfronthosting.co.za>
Message-ID: <1377762899.54.0.852982993741.issue18760@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you for your review.

----------
resolution:  -> fixed
stage: needs patch -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Thu Aug 29 10:46:57 2013
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 29 Aug 2013 08:46:57 +0000
Subject: [docs] [issue18743] References to non-existant "StringIO" module
In-Reply-To: <1376542911.78.0.658455842148.issue18743@psf.upfronthosting.co.za>
Message-ID: <3cQcrJ3GR3z7Lk0@mail.python.org>


Roundup Robot added the comment:

New changeset 6c0f5af2f5a5 by Serhiy Storchaka in branch '3.3':
Issue #18743: Fix references to non-existant "StringIO" module
http://hg.python.org/cpython/rev/6c0f5af2f5a5

New changeset 676bbd5b0254 by Serhiy Storchaka in branch 'default':
Issue #18743: Fix references to non-existant "StringIO" module
http://hg.python.org/cpython/rev/676bbd5b0254

New changeset 8c768bbacd92 by Serhiy Storchaka in branch '2.7':
Issue #18743: Improved cross-references to the StringIO class.
http://hg.python.org/cpython/rev/8c768bbacd92

----------

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

From report at bugs.python.org  Thu Aug 29 10:48:46 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 29 Aug 2013 08:48:46 +0000
Subject: [docs] [issue18743] References to non-existant "StringIO" module
In-Reply-To: <1376542911.78.0.658455842148.issue18743@psf.upfronthosting.co.za>
Message-ID: <1377766126.88.0.213408584825.issue18743@psf.upfronthosting.co.za>


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


----------
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Thu Aug 29 10:50:02 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 29 Aug 2013 08:50:02 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1377766202.75.0.528962785282.issue18758@psf.upfronthosting.co.za>


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


----------
assignee: docs at python -> serhiy.storchaka

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

From report at bugs.python.org  Thu Aug 29 20:29:33 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 29 Aug 2013 18:29:33 +0000
Subject: [docs] =?utf-8?q?=5Bissue17003=5D_Unification_of_read=28=29=C2=A0?=
 =?utf-8?q?and_readline=28=29_argument_names?=
In-Reply-To: <1358698394.54.0.180835263252.issue17003@psf.upfronthosting.co.za>
Message-ID: <1377800973.11.0.937672810315.issue17003@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Are there any objections to the patch?

----------
assignee: docs at python -> serhiy.storchaka
versions: +Python 3.4

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

From report at bugs.python.org  Thu Aug 29 22:25:53 2013
From: report at bugs.python.org (Merlijn van Deen)
Date: Thu, 29 Aug 2013 20:25:53 +0000
Subject: [docs] [issue18870] eval() uses latin-1 to decode str
In-Reply-To: <1377713902.12.0.966249722349.issue18870@psf.upfronthosting.co.za>
Message-ID: <1377807953.52.0.536183205972.issue18870@psf.upfronthosting.co.za>


Merlijn van Deen added the comment:

On the lowest level, this affects exec, eval(), compile() and input() (!). On a higher level, more modules are affected:

modules ast, codeop, compiler, cProfile, dis, distutils (not sure), doctest, idlelib, ihooks, pdb, pkgutil, plat-mac, py_compile, rexec, runpy and timeit all call compile()

modules dbd, compiler, gettext, idlelib, lib2to3, lib-tk.turtle, logging, mhlib, pdb, plat-irix5, plat-mac, rexec, rlcompleter and warnings all call eval()

and modules Bastion, bdb, code, collections, cProfile, distutils, doctest, idlelib, ihooks, imputil, pdb, plat-irix5, plat-irix6, plat-mac, profile, rexec, site, timeit and trace all call exec.

Not all of them necessarily take user-supplied code - I haven't checked that.


After checking tests/test_pep263.py, it seems the behavior is a bit more complicated than I initially thought: a str parameter is considered latin-1 unless either
 a) an utf-8 bom is present, in which case it is considered utf-8
 b) an # encoding: XXX  line is present, in which case it is considered
    to be in that encoding

In any case, I have attached a doc patch for exec, eval(), compile(), and ast.literal_eval(), because I think these are the most widely used. I think input() does not need a doc change because it explicitly refers to eval().

I ignored the subtleties noted above for the doc patch, simplifying to 'pass either a Unicode or a latin-1 encoded string'.

----------
keywords: +patch
Added file: http://bugs.python.org/file31513/doc_18870.patch

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

From report at bugs.python.org  Thu Aug 29 23:06:07 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 29 Aug 2013 21:06:07 +0000
Subject: [docs] [issue18870] eval() uses latin-1 to decode str
In-Reply-To: <1377713902.12.0.966249722349.issue18870@psf.upfronthosting.co.za>
Message-ID: <1377810367.31.0.218585226449.issue18870@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

See also issue15809.

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

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

From report at bugs.python.org  Fri Aug 30 08:35:30 2013
From: report at bugs.python.org (=?utf-8?q?Westley_Mart=C3=ADnez?=)
Date: Fri, 30 Aug 2013 06:35:30 +0000
Subject: [docs] [issue13951] Document that Seg Fault in .so called by ctypes
	causes	the interpreter to Seg Fault
In-Reply-To: <1328535030.63.0.73417525944.issue13951@psf.upfronthosting.co.za>
Message-ID: <1377844530.41.0.72651589715.issue13951@psf.upfronthosting.co.za>


Westley Mart?nez added the comment:

Can we have this committed?

----------

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

From report at bugs.python.org  Fri Aug 30 14:03:09 2013
From: report at bugs.python.org (Stefan Krah)
Date: Fri, 30 Aug 2013 12:03:09 +0000
Subject: [docs] [issue17145] memoryview(array.array)
In-Reply-To: <1360170754.31.0.614797074916.issue17145@psf.upfronthosting.co.za>
Message-ID: <1377864189.03.0.203750363951.issue17145@psf.upfronthosting.co.za>


Stefan Krah added the comment:

The request is certainly valid, but the patch is tricky to review.

----------

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

From report at bugs.python.org  Fri Aug 30 18:57:54 2013
From: report at bugs.python.org (Stefan Krah)
Date: Fri, 30 Aug 2013 16:57:54 +0000
Subject: [docs] [issue18438] Obsolete url in comment inside decimal module
In-Reply-To: <1373686911.48.0.750703855786.issue18438@psf.upfronthosting.co.za>
Message-ID: <1377881873.99.0.0450593393628.issue18438@psf.upfronthosting.co.za>


Stefan Krah added the comment:

Wikipedia sounds good. Let's avoid linking directly to "free" versions. :)

----------

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

From report at bugs.python.org  Fri Aug 30 23:14:54 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 30 Aug 2013 21:14:54 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>
Message-ID: <1377897294.76.0.771571778444.issue18840@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

For the tutorial, I agree with presenting json rather than pickle for all the reasons given, with pickle mentioned in a paragraph at the end (more powerful, more dangerous, see warning in manual before using).

----------
nosy: +terry.reedy
stage:  -> needs patch

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

From report at bugs.python.org  Fri Aug 30 23:34:28 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 30 Aug 2013 21:34:28 +0000
Subject: [docs] [issue18855] Inconsistent README filenames
In-Reply-To: <1377616570.1.0.108273179071.issue18855@psf.upfronthosting.co.za>
Message-ID: <1377898468.3.0.228623187288.issue18855@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

README.txt is also used in lib/idlelib and lib/idlelib/idle_test. In the latter case, I was told to use this.

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

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

From report at bugs.python.org  Sat Aug 31 00:25:00 2013
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Fri, 30 Aug 2013 22:25:00 +0000
Subject: [docs] [issue18855] Inconsistent README filenames
In-Reply-To: <1377616570.1.0.108273179071.issue18855@psf.upfronthosting.co.za>
Message-ID: <1377901500.31.0.00500514393884.issue18855@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/issue18855>
_______________________________________

From report at bugs.python.org  Sat Aug 31 01:07:27 2013
From: report at bugs.python.org (=?utf-8?q?Westley_Mart=C3=ADnez?=)
Date: Fri, 30 Aug 2013 23:07:27 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>
Message-ID: <1377904047.08.0.366787760561.issue18840@psf.upfronthosting.co.za>


Westley Mart?nez added the comment:

How about we simply add the warning from http://docs.python.org/3/library/pickle.html#module-pickle to the beginning (or end) of the section?  The Official Python Tutorial has always assumed a certain programmer's competence.  It's up to them if they want to use the module or not.

----------
nosy: +anikom15

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

From report at bugs.python.org  Sat Aug 31 01:27:03 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 30 Aug 2013 23:27:03 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377904047.08.0.366787760561.issue18840@psf.upfronthosting.co.za>
Message-ID: <52212A2C.9090104@udel.edu>


Terry J. Reedy added the comment:

> How about we simply add the warning from http://docs.python.org/3/library/pickle.html#module-pickle to the beginning (or end) of the section?

That is one possibility.

> The Official Python Tutorial has always assumed a certain programmer's competence.

Such a person is much more likely to know about and find use for 
language independent json than Python-specific pickle. The tutorial was 
written before json existed, but if it were written today, json would 
seem to me to be the better choice for first exposure to serialization. 
If someone cares enough to write a patch, I think it should be considered.

----------

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

From report at bugs.python.org  Sat Aug 31 01:36:57 2013
From: report at bugs.python.org (=?utf-8?q?Westley_Mart=C3=ADnez?=)
Date: Fri, 30 Aug 2013 23:36:57 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>
Message-ID: <1377905817.79.0.0471258928625.issue18840@psf.upfronthosting.co.za>


Westley Mart?nez added the comment:

I won't question the usefulness of JSON.  I'm not a web programmer and have never used it.  From my interpretation of the tutorial, it seems that the section's purpose is for storing python objects.  If pickle is going to stay in the tutorial, I think a warning is imperative.  Either way, I think a section on JSON would be a welcome addition to the tutorial.

+1 adding a warning
+0 keeping pickle in the tutorial

----------

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

From report at bugs.python.org  Sat Aug 31 02:01:14 2013
From: report at bugs.python.org (=?utf-8?q?Westley_Mart=C3=ADnez?=)
Date: Sat, 31 Aug 2013 00:01:14 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>
Message-ID: <1377907274.04.0.721598518724.issue18840@psf.upfronthosting.co.za>


Westley Mart?nez added the comment:

Here's a patch that adds the warning, if we so choose to keep pickle in the tutorial.  It's taken verbatim from the pickle module's documentation.

----------
keywords: +patch
Added file: http://bugs.python.org/file31524/pickle-add-warning_18840.diff

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

From report at bugs.python.org  Sat Aug 31 02:12:41 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 31 Aug 2013 00:12:41 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>
Message-ID: <1377907961.03.0.18774194079.issue18840@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

The very fact that we would add a warning makes pickle unfit for the tutorial, IMHO. The tutorial should stick to simple enough stuff that doesn't need any warnings.

----------

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

From report at bugs.python.org  Sat Aug 31 18:22:54 2013
From: report at bugs.python.org (py.user)
Date: Sat, 31 Aug 2013 16:22:54 +0000
Subject: [docs] [issue18894] In unittest.TestResult.failures remove
	deprecated fail*	methods
Message-ID: <1377966174.08.0.355322542495.issue18894@psf.upfronthosting.co.za>


New submission from py.user:

http://docs.python.org/3/library/unittest.html#unittest.TestResult.failures

----------
assignee: docs at python
components: Documentation
files: issue.diff
keywords: patch
messages: 196644
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: In unittest.TestResult.failures remove deprecated fail* methods
type: enhancement
versions: Python 3.3, Python 3.4
Added file: http://bugs.python.org/file31534/issue.diff

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

From report at bugs.python.org  Sat Aug 31 18:26:06 2013
From: report at bugs.python.org (py.user)
Date: Sat, 31 Aug 2013 16:26:06 +0000
Subject: [docs] [issue18895] In unittest.TestResult.addError split the
	sentence
Message-ID: <1377966366.86.0.69110585984.issue18895@psf.upfronthosting.co.za>


New submission from py.user:

http://docs.python.org/3/library/unittest.html#unittest.TestResult.addError

----------
assignee: docs at python
components: Documentation
files: issue.diff
keywords: patch
messages: 196645
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: In unittest.TestResult.addError split the sentence
type: enhancement
versions: Python 3.3, Python 3.4
Added file: http://bugs.python.org/file31535/issue.diff

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

From khous11 at gmail.com  Sat Aug 24 06:58:40 2013
From: khous11 at gmail.com (Ken Housley)
Date: Fri, 23 Aug 2013 22:58:40 -0600
Subject: [docs] Typo error 21.10.ossaudiodev Python 2.7 documentation
Message-ID: <CAPYtohK9zK0o63VxnVqJQ=5nmX7VUTx2Zi7FTQYVyHBZCeHu=w@mail.gmail.com>

In 21.10.1 Audio Device Objects near the end of the section there is
an example of how to use the setparameters() method.
The example is said to be equivalent to three separate statements.
The last of the three statements is:

rate = dsp.rate(channels)

I think the statement should be

rate = dsp.rate(rate)

It is a minor correction, but we would want to fix the small errors as
well as the big ones, right?  The error appears on the web at

http://docs.python.org/2/library/ossaudiodev.html

and in the pdf file library.pdf in the python 2.7 documentation.


Thanks,

Ken Housley

From drekin at gmail.com  Sat Aug 24 16:54:47 2013
From: drekin at gmail.com (Draic Kin)
Date: Sat, 24 Aug 2013 16:54:47 +0200
Subject: [docs] =?utf-8?q?Wrong_link_in_Python_3=2E3_documentation_index_?=
	=?utf-8?b?4oCTIGV4ZWM=?=
Message-ID: <CACvLUa=FHuq2o94AmFFrER2awA-+s49GDu2O4eDw3DbCkY2+DA@mail.gmail.com>

In Python 3.3 documentation index, the link on exec leads to
http://docs.python.org/3/reference/simple_stmts.html#index-42 which is
incorrect.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130824/e80fc8ec/attachment-0001.html>

From skelly at passportcapital.com  Mon Aug 26 23:59:54 2013
From: skelly at passportcapital.com (Scot Kelly)
Date: Mon, 26 Aug 2013 21:59:54 +0000
Subject: [docs] backslash ending raw string literals.
Message-ID: <C450F7046A908F498A5A88FE4A3612E00B80A428@VNMSGPPCSFO24.passportcapital.com>

>From the doc: http://docs.python.org/2/reference/lexical_analysis.html
  r"\" is not a valid string literal (even a raw string cannot end in an odd number of backslashes). Specifically, a raw string cannot end in a single backslash (since the backslash would escape the following quote character).

If it's a raw string, then the backslash will not escape the following quote character.  Ergo r"\" should be allowed.

Regards,
Scot Kelly

"Be excellent to each other."



PASSPORT CAPITAL
One Market Street
Steuart Tower, Suite 2200
San Francisco, CA 94105
www.passportcapital.com<http://www.passportcapital.com/>

Scot Kelly
Tel 415-525-8910
Fax 415-321-4620
skelly at passportcapital.com




CONFIDENTIALITY: The information transmitted is intended only for the addressee and may contain confidential or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by anyone other than the intended recipient is prohibited. If you received this message in error, please contact the sender and delete the material from all computers. 

E-mail transmissions cannot be guaranteed to be secure or error-free and we accept no liability for any errors or omissions. We screen for viruses on a routine basis, however, we make no representation or warranty as to the absence of viruses in this e-mail or any attachments.  Please note that for regulatory and compliance reasons we may monitor and read e-mails sent to and from our servers. 

Passport Capital, LLC and its affiliated investment vehicles are actively engaged in investment management and evaluation activities in global markets and do not wish to be exposed to any nonpublic information regarding any company(s) or security(s) that could be deemed material and restrict their ability to trade securities without their express prior consent.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130826/31fe81f8/attachment-0001.html>

From luca.sbardella at gmail.com  Fri Aug 30 22:52:20 2013
From: luca.sbardella at gmail.com (Luca Sbardella)
Date: Fri, 30 Aug 2013 21:52:20 +0100
Subject: [docs] defaults redirects bit confusing
Message-ID: <CAF94-jboFPdNjPndyoBqC0EWtPzjzVW-uwnVNqQicZH3A3m1Dw@mail.gmail.com>

Hi,
just noticed that
http://docs.python.org/
redirect to
http://docs.python.org/3/
good
but
http://docs.python.org/library/
redirect to
http://docs.python.org/2/library/
not good if not confusing

am I missing something?

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130830/93dfc3c3/attachment-0001.html>

From simeon.simeonov.s at gmail.com  Mon Aug 12 17:42:25 2013
From: simeon.simeonov.s at gmail.com (Simeon S)
Date: Mon, 12 Aug 2013 15:42:25 -0000
Subject: [docs] socket.sethostname() error type mistake
Message-ID: <CAGwyPpFM5TNgbO26vdxhkj+baDx3T7MvjAXb=V6oUe+KbyW6iw@mail.gmail.com>

Hi,

I believe there is a mistake in the type of error raised by
socket.sethostname(). The documentation says the error returned is
OSError. Here is what I get (3.3.2):

[16:39:sys]
 % python3
Python 3.3.2 (default, Aug  5 2013, 11:52:10)
[GCC 4.5.3] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import socket as s
>>> s.sethostname('bla')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
PermissionError: [Errno 1] Operation not permitted

Simeon

From braden.wentworth at gmail.com  Mon Aug 19 02:09:57 2013
From: braden.wentworth at gmail.com (Braden)
Date: Mon, 19 Aug 2013 00:09:57 -0000
Subject: [docs] Py_SetProgramName error
Message-ID: <CAEFsHE2BD6fuFnTwJ6K=ZXHer87baVQ+Hb-kQXZvDJ8yZvtkXQ@mail.gmail.com>

The Python3.3 embedding example says to use:
[
http://docs.python.org/3.3/extending/embedding.html#very-high-level-embedding
 ]

    Py_SetProgramName(argv[0]);

Which throws:

    error C2664: 'Py_SetProgramName' : cannot convert parameter 1 from
'char *' to 'wchar_t *'

To fix this someone suggested the following code
[ http://stackoverflow.com/a/18248800<http://stackoverflow.com/questions/18248343/c-python-3-binding>
 ]

    wchar_t progname[FILENAME_MAX + 1];
    mbstowcs(progname, argv[0], strlen(argv[0]) + 1);
    Py_SetProgramName(progname);

Regards,
-- 
Braden Wentworth
[ online director / code monkey ]
[ www.labvc.com.au ]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130819/db6d0f76/attachment.html>

From bigfunlx at gmail.com  Sat Aug 31 02:17:48 2013
From: bigfunlx at gmail.com (=?UTF-8?Q?Karol_St=C4=99pniewski?=)
Date: Sat, 31 Aug 2013 02:17:48 +0200
Subject: [docs] Possible bug in shutil docs for move() function
Message-ID: <CAMHTaYYi1qrWjFD6uTJKamNuMCquHB_PUTYpF_7qEa313EKs8Q@mail.gmail.com>

Hi,

On page http://docs.python.org/2/library/shutil.html The fragment
below move(src,dst) function says:

> The destination directory must not already exist


However, the behavior of this function is that if the dst does not
exist (and is provided as directory, with os separator at the end) it
will raise an exception. IMHO it should be:

> The destination directory must already exist.


Best Regards,
Karol