From mike at saguaroscuba.com  Sat Oct  1 02:23:15 2011
From: mike at saguaroscuba.com (Mike)
Date: Fri, 30 Sep 2011 17:23:15 -0700
Subject: [docs] [issue13075] PEP-0001 contains dead links
In-Reply-To: <1317374485.54.0.239839552518.issue13075@psf.upfronthosting.co.za>
References: <1317374485.54.0.239839552518.issue13075@psf.upfronthosting.co.za>
Message-ID: <4E865D73.9070904@saguaroscuba.com>


> The links in section "Resources" of PEP-0001 are all dead. They point to www.python.org/dev/<whatever>  and all return a 404. Most of them can still be found via google archive.org, but that's not really how it should be. Maybe some of them are already superseded, but even then I think they have at least historical value and should be kept on python.org.
>
> ----------
> assignee: docs at python
> components: Documentation
> messages: 144680
> nosy: docs at python, ezander
> priority: normal
> severity: normal
> status: open
> title: PEP-0001 contains dead links
>
> _______________________________________
> Python tracker<report at bugs.python.org>
> <http://bugs.python.org/issue13075>
> _______________________________________
Where can I find the PEPs? I would be willing to track down the links 
and submit a patch. I looked around in cpython/Doc. Can't find it.

From report at bugs.python.org  Sat Oct  1 03:18:00 2011
From: report at bugs.python.org (Mike Hoy)
Date: Sat, 01 Oct 2011 01:18:00 +0000
Subject: [docs] [issue13075] PEP-0001 contains dead links
In-Reply-To: <1317374485.54.0.239839552518.issue13075@psf.upfronthosting.co.za>
Message-ID: <1317431879.92.0.681828900965.issue13075@psf.upfronthosting.co.za>


Mike Hoy <mhoy09 at gmail.com> added the comment:

I'm working on making a patch for this. I just want to confirm that the information I found is correct:

Article Name
OLD URL
ARCHIVED URL

How Python is Developed 
OLD: http://www.python.org/dev/intro/
ARCHIVE: http://www.etsimo.uniovi.es/python/dev/intro/

Python's Development Process
http://www.python.org/dev/process/
http://www.etsimo.uniovi.es/python/dev/process/

Why Develop Python?
http://www.python.org/dev/why/
http://www.etsimo.uniovi.es/python/dev/why/

Development Tools
http://www.python.org/dev/tools/
http://www.etsimo.uniovi.es/python/dev/tools/

Frequently Asked Questions for Developers
http://www.python.org/dev/faq/
http://www.etsimo.uniovi.es/python/dev/faq/

----------
nosy: +mikehoy

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

From report at bugs.python.org  Sat Oct  1 03:19:08 2011
From: report at bugs.python.org (Mike Hoy)
Date: Sat, 01 Oct 2011 01:19:08 +0000
Subject: [docs] [issue13075] PEP-0001 contains dead links
In-Reply-To: <1317374485.54.0.239839552518.issue13075@psf.upfronthosting.co.za>
Message-ID: <1317431947.96.0.55975689313.issue13075@psf.upfronthosting.co.za>


Mike Hoy <mhoy09 at gmail.com> added the comment:

Of course I would be creating new articles based on the archived pages.

----------

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

From report at bugs.python.org  Sat Oct  1 03:52:00 2011
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 01 Oct 2011 01:52:00 +0000
Subject: [docs] [issue13075] PEP-0001 contains dead links
In-Reply-To: <1317374485.54.0.239839552518.issue13075@psf.upfronthosting.co.za>
Message-ID: <1317433920.76.0.141121490091.issue13075@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

These pages are all still on python.org - the links just need to be updated to point to the devguide equivalents (under http://docs.python.org/devguide)

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

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

From report at bugs.python.org  Sat Oct  1 15:43:59 2011
From: report at bugs.python.org (etuardu)
Date: Sat, 01 Oct 2011 13:43:59 +0000
Subject: [docs] [issue13077] Unclear behavior of daemon threads on main
	thread exit
In-Reply-To: <1317396642.03.0.535538271179.issue13077@psf.upfronthosting.co.za>
Message-ID: <1317476639.29.0.288812849627.issue13077@psf.upfronthosting.co.za>


etuardu <edonan at gmail.com> added the comment:

Let me put it this way: the definition of daemon thread describes the behaviour of the Python program running it (its exit condition in particular) instead of going straight to the point describing the behaviour of the daemon thread itself first, and finally add other considerations.

Specifically, I think a situation like the following is not quite clear from the given definition:
- I have a main thread and a secondary thread, both printing to stdout.
- At some point, I press Ctrl+c raising an unhandled KeyboardInterrupt exception in the main thread, which kills it.

This is what I get using a daemon thread:

etuardu at subranu:~/Desktop$ python foo.py # other = daemon
other thread
main thread
other thread
main thread
^C
Traceback [...]
KeyboardInterrupt
etuardu at subranu:~/Desktop$ # process terminates

This is what I get using a non-daemon thread:

etuardu at subranu:~/Desktop$ python foo.py # other = non-daemon
other thread
main thread
other thread
main thread
^C
Traceback [...]
KeyboardInterrupt
other thread
other thread
other thread
... (process still running)

So, to explain the significance of the "daemon" flag, I'd say something like:

A daemon thread is shut down when the main thread and all others non-daemon threads end.
This means a Python program runs as long as non-daemon threads, such as the main thread, are running.
When only daemon threads are left, the Python program exits.

Of course this can be understood from the current definition (?the entire Python program exits when only daemon threads are left?), still it looks a bit sybilline to me.

----------
Added file: http://bugs.python.org/file23283/foo.py

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

From report at bugs.python.org  Sun Oct  2 05:29:04 2011
From: report at bugs.python.org (Mike Hoy)
Date: Sun, 02 Oct 2011 03:29:04 +0000
Subject: [docs] [issue13075] PEP-0001 contains dead links
In-Reply-To: <1317374485.54.0.239839552518.issue13075@psf.upfronthosting.co.za>
Message-ID: <1317526144.22.0.878821995463.issue13075@psf.upfronthosting.co.za>


Mike Hoy <mhoy09 at gmail.com> added the comment:

Added links under Resources to the new Dev Guide. Added a link to the Guide itself and a link to the faq.

----------
keywords: +patch
Added file: http://bugs.python.org/file23289/pep-0001-broken-links.diff

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

From report at bugs.python.org  Sun Oct  2 09:32:21 2011
From: report at bugs.python.org (Ben Hayden)
Date: Sun, 02 Oct 2011 07:32:21 +0000
Subject: [docs] [issue13073] message_body argument of
	HTTPConnection.endheaders is	undocumented
In-Reply-To: <1317370143.22.0.297306447289.issue13073@psf.upfronthosting.co.za>
Message-ID: <1317540741.36.0.628580760096.issue13073@psf.upfronthosting.co.za>


Ben Hayden <hayden767 at gmail.com> added the comment:

I added in docs for the method from the actual method docstring from the http.client module.

----------
keywords: +patch
nosy: +beardedp
Added file: http://bugs.python.org/file23290/issue13073.patch

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

From report at bugs.python.org  Sun Oct  2 10:18:23 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 02 Oct 2011 08:18:23 +0000
Subject: [docs] [issue13076] Bad links to 'time' in datetime documentation
In-Reply-To: <1317390308.93.0.874341309843.issue13076@psf.upfronthosting.co.za>
Message-ID: <1317543503.59.0.981181094898.issue13076@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

The broken links seem to be only in the "time objects" section, and only in the body of attribute/method directives.

The attached patch fixes the issue by using :class:`~datetime.time` explicitly where the links are broken.

Georg, is this a bug in Sphinx?

----------
assignee: docs at python -> ezio.melotti
keywords: +patch
nosy: +ezio.melotti, georg.brandl
stage: needs patch -> patch review
Added file: http://bugs.python.org/file23292/issue13076.diff

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

From report at bugs.python.org  Sun Oct  2 10:23:18 2011
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 02 Oct 2011 08:23:18 +0000
Subject: [docs] [issue13076] Bad links to 'time' in datetime documentation
In-Reply-To: <1317390308.93.0.874341309843.issue13076@psf.upfronthosting.co.za>
Message-ID: <1317543798.27.0.509906321551.issue13076@psf.upfronthosting.co.za>


Georg Brandl <georg at python.org> added the comment:

No, it's not, it's how Sphinx works. Use :class:`.time` to refer to the datetime class.

----------

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

From report at bugs.python.org  Sun Oct  2 11:47:25 2011
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 02 Oct 2011 09:47:25 +0000
Subject: [docs] [issue13076] Bad links to 'time' in datetime documentation
In-Reply-To: <1317390308.93.0.874341309843.issue13076@psf.upfronthosting.co.za>
Message-ID: <E1RAIdn-0008TM-Dn@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 854e31d80151 by Ezio Melotti in branch '2.7':
#13076: fix links to datetime.time.
http://hg.python.org/cpython/rev/854e31d80151

New changeset 95689ed69097 by Ezio Melotti in branch '3.2':
#13076: fix links to datetime.time and datetime.datetime.
http://hg.python.org/cpython/rev/95689ed69097

New changeset 175cd2a51ea9 by Ezio Melotti in branch 'default':
#13076: merge with 3.2.
http://hg.python.org/cpython/rev/175cd2a51ea9

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

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

From report at bugs.python.org  Sun Oct  2 11:49:51 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 02 Oct 2011 09:49:51 +0000
Subject: [docs] [issue13076] Bad links to 'time' in datetime documentation
In-Reply-To: <1317390308.93.0.874341309843.issue13076@psf.upfronthosting.co.za>
Message-ID: <1317548991.65.0.778030714562.issue13076@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

This should be fixed now, thanks for the report.
FTR with Sphinx 1.0 all the links to :class:`time` and also :class:`datetime` needed to be fixed because they were pointing to the modules, with 0.6 only the :class:`time` in the body of attribute/method directives were broken.

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

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

From report at bugs.python.org  Mon Oct  3 01:39:31 2011
From: report at bugs.python.org (Senthil Kumaran)
Date: Sun, 02 Oct 2011 23:39:31 +0000
Subject: [docs] [issue13073] message_body argument of
	HTTPConnection.endheaders is	undocumented
In-Reply-To: <1317370143.22.0.297306447289.issue13073@psf.upfronthosting.co.za>
Message-ID: <1317598771.59.0.292415701319.issue13073@psf.upfronthosting.co.za>


Senthil Kumaran <senthil at uthcode.com> added the comment:

This is fixed the following changesets.

changeset a3f2dba93743
changeset 1ed413b52af3
changeset 277688052c5a

Thanks for the patch, Ben Hayden.

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

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

From report at bugs.python.org  Mon Oct  3 04:09:09 2011
From: report at bugs.python.org (Meador Inge)
Date: Mon, 03 Oct 2011 02:09:09 +0000
Subject: [docs] [issue12943] tokenize: add python -m tokenize support back
In-Reply-To: <1315537867.15.0.614423357455.issue12943@psf.upfronthosting.co.za>
Message-ID: <1317607749.78.0.985477200064.issue12943@psf.upfronthosting.co.za>


Meador Inge <meadori at gmail.com> added the comment:

Fixed a few more nits pointed out in review.

----------
Added file: http://bugs.python.org/file23304/issue12943-6.patch

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

From report at bugs.python.org  Mon Oct  3 16:45:28 2011
From: report at bugs.python.org (R. David Murray)
Date: Mon, 03 Oct 2011 14:45:28 +0000
Subject: [docs] [issue13094] setattr misbehaves when used with lambdas
	inside for loop
In-Reply-To: <1317652797.3.0.357677492942.issue13094@psf.upfronthosting.co.za>
Message-ID: <1317653128.63.0.875115518309.issue13094@psf.upfronthosting.co.za>


R. David Murray <rdmurray at bitdance.com> added the comment:

Sorry.  It is intended behavior.  The lambda 'each' is bound to the local 'each', and by the time the lambda's execute, the value of 'each' is 'baz'.

I'm going to turn this into a doc bug, because while I'm pretty sure this is documented *somewhere*, I don't see it in the programming FAQ, and it should be there.

----------
assignee:  -> docs at python
components: +Documentation -None
nosy: +docs at python, r.david.murray
stage:  -> needs patch
type:  -> behavior
versions: +Python 3.2, Python 3.3

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

From report at bugs.python.org  Mon Oct  3 16:46:35 2011
From: report at bugs.python.org (R. David Murray)
Date: Mon, 03 Oct 2011 14:46:35 +0000
Subject: [docs] [issue13094] Need Programming FAQ entry for the behavior of
	closures
In-Reply-To: <1317652797.3.0.357677492942.issue13094@psf.upfronthosting.co.za>
Message-ID: <1317653195.51.0.773057163828.issue13094@psf.upfronthosting.co.za>


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


----------
title: setattr misbehaves when used with lambdas inside for loop -> Need Programming FAQ entry for the behavior of closures

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

From report at bugs.python.org  Mon Oct  3 17:03:19 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 03 Oct 2011 15:03:19 +0000
Subject: [docs] [issue13094] Need Programming FAQ entry for the behavior of
	closures
In-Reply-To: <1317652797.3.0.357677492942.issue13094@psf.upfronthosting.co.za>
Message-ID: <1317654199.49.0.0212202123252.issue13094@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

To understand better what's going on, try to change the value of 'each' after the 3 prints and then call again the 3 methods: you will see that they now return the new value of each.  This is because the lambdas refer to global 'each' (that at the end of the loop is set to 'baz').
If you do setattr(x, each, lambda each=each: each), the each will be local to the lambda, and it will then work as expected.

An entry in the FAQ would be useful, I thought it was there already but apparently it's not (I'm pretty sure I saw this already somewhere in the doc, but I can't seem to find where).

----------
assignee: docs at python -> 
components: +None -Documentation
nosy: +ezio.melotti
stage: needs patch -> 
type: behavior -> 
versions:  -Python 3.2, Python 3.3

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

From report at bugs.python.org  Mon Oct  3 17:13:34 2011
From: report at bugs.python.org (=?utf-8?b?VG9tw6HFoSBEdm/FmcOhaw==?=)
Date: Mon, 03 Oct 2011 15:13:34 +0000
Subject: [docs] [issue13094] Need Programming FAQ entry for the behavior of
	closures
In-Reply-To: <1317652797.3.0.357677492942.issue13094@psf.upfronthosting.co.za>
Message-ID: <1317654813.95.0.772062209318.issue13094@psf.upfronthosting.co.za>


Tom?? Dvo??k <dvtomas at gmail.com> added the comment:

Thank you all very much for the super-quick responses. I'm used to smalltalk, so the python variable binding behaviour is unnatural to me, but I guess there must have been some reasons for making it behave this way. 

Ezio, the 
"lambda each=each: each" 
trick works nicely, thanks a lot. But - what does it mean? :) I just don't know how to parse and understand it :-)

Best regards,
  Tom?? Dvo??k

----------

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

From report at bugs.python.org  Mon Oct  3 17:22:44 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 03 Oct 2011 15:22:44 +0000
Subject: [docs] [issue13094] Need Programming FAQ entry for the behavior of
	closures
In-Reply-To: <1317652797.3.0.357677492942.issue13094@psf.upfronthosting.co.za>
Message-ID: <1317655364.34.0.784602471719.issue13094@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Maybe with a different name is less confusing: lambda return_value=each: return_value
This copies the value of 'each' in a variable called 'return_value' that is local to the lambda.  Since the copy happens when the lambdas are defined, 'return_value' has then the right value.

----------

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

From paulkoning at comcast.net  Mon Oct  3 18:39:17 2011
From: paulkoning at comcast.net (Paul Koning)
Date: Mon, 3 Oct 2011 12:39:17 -0400
Subject: [docs] "sane" tzinfo subclasses
In-Reply-To: <20110928234921.GG4665@mathmagic>
References: <A1665AE4-1865-4536-9278-F27FC4CD7F88@comcast.net>
	<20110928234921.GG4665@mathmagic>
Message-ID: <B820C66B-8884-4781-B375-94D2D6F43C26@comcast.net>


On Sep 28, 2011, at 7:49 PM, Senthil Kumaran wrote:

> On Sun, Sep 18, 2011 at 09:04:16PM -0400, Paul Koning wrote:
>> Gentlepeople,
>> 
>> Section 8.1.6 of the library manual talks about
>> utcoffset(dt)-dst(dt) as the "standard offset" and says that this
>> should not depend on the date or time but only on the location.
> 
> What would be good note to add to explain that? IIRC, someone at the
> top when dealing with datetime and timezones Python docs already
> mentions that it cannot be relied up completely, because timezone
> rules changes sometimes due to politics of the land.

I think the documentation is wrong here.  I did a simple test (using the pytz module which implements the Olson timezone database), using datetime.astimezone() to change from US Eastern time to Venezuela time.  Venezuela changed its standard offset from -4:00 to -4:30 in 2007.

The answer is that it works correctly -- you can see this by doing the experiment once with a date in 2006, and once with a date in a later year (like 2011).

So I think what's needed is to delete this entire block of text from the description of the tzinfo.dst method:

--------
An instance tz of a tzinfo subclass that models both standard and daylight times must be consistent in this sense:
tz.utcoffset(dt) - tz.dst(dt)
mustreturnthesameresultforeverydatetimedtwithdt.tzinfo == tzForsanetzinfosubclasses, this expression yields the time zone?s ?standard offset?, which should not depend on the date or the time, but only on geographic location. The implementation of datetime.astimezone() relies on this, but cannot detect violations; it?s the programmer?s responsibility to ensure it. If a tzinfo subclass cannot guarantee this, it may be able to override the default implementation of tzinfo.fromutc() to work correctly with astimezone() regardless.
---------

because it is not true -- astimezone() works right.

It might also be useful to add to the description of the tzinfo.utcoffset() method to point out that the examples given are simplified and apply only if the base offset is indeed constant, which is true for some timezones (like US Eastern) but not others (like Venezuela).  

	paul


From matrixhasu at gmail.com  Mon Oct  3 21:20:15 2011
From: matrixhasu at gmail.com (Sandro Tosi)
Date: Mon, 3 Oct 2011 21:20:15 +0200
Subject: [docs] Epub and A5
In-Reply-To: <CAPRBuQ=Cdss4YBe=DwMNjZgQhjDzx5ABTchJ8pu3XqZ43CUE4Q@mail.gmail.com>
References: <CAPRBuQ=Cdss4YBe=DwMNjZgQhjDzx5ABTchJ8pu3XqZ43CUE4Q@mail.gmail.com>
Message-ID: <CAPdtAj2a9ng_ANjhktdSoLgEDJUXOgmNXFRz8ny8E0GOPGrF4Q@mail.gmail.com>

Hello akatsuki,

On Thu, Sep 29, 2011 at 06:12, akatsuki deidara <deidaramail at gmail.com> wrote:
> Hi. Is it possible to have an epub version or an A5 version of the
> documentations?

We are providing an EPUB version of the documentation for Python 3.x:
http://docs.python.org/py3k/download.html

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Tue Oct  4 06:21:34 2011
From: report at bugs.python.org (Meador Inge)
Date: Tue, 04 Oct 2011 04:21:34 +0000
Subject: [docs] [issue12880] ctypes: clearly document how structure bit
	fields are	allocated
In-Reply-To: <1317403151.53.0.993055557363.issue12880@psf.upfronthosting.co.za>
Message-ID: <CAK1Qoor_ZD-9sdVJVBb-wN=xshbZCD_ri4t8cH7nME3=GbT4DA@mail.gmail.com>


Meador Inge <meadori at gmail.com> added the comment:

On Fri, Sep 30, 2011 at 12:19 PM, Vlad Riscutia <report at bugs.python.org> wrote:

> I believe this is the better thing to do rather than detailing how GCC and MSVC allocated their bitfields because that would just
> encourage people to use this feature incorrectly.

So clearly documenting how a feature works will cause people to use
the feature incorrectly?  I think not.  In any case, I agree that
documenting the low-level specifics of each compiler's algorithm is too much.

> Most bugs opened on bit fields are because people are toying with the underlying buffer and get other results than what they expect.

The issues that I have looked at (issue6069, issue11920, and
issue11920) all involve fundamental misunderstandings of *how* the
structure layout is determined.  I don't know if I would generalize
these misunderstanding as "toying with the underlying buffer".  Some
times people need to know the exact layout for proper C interop.  In
some of the bugs reported folks are casting buffers in an attempt
to discover the structure layout since it is not clearly documented.

The general content of your patch seems reasonable.  I will provide
more specific comments shortly.

----------

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

From report at bugs.python.org  Tue Oct  4 06:49:47 2011
From: report at bugs.python.org (Meador Inge)
Date: Tue, 04 Oct 2011 04:49:47 +0000
Subject: [docs] [issue12880] ctypes: clearly document how structure bit
	fields are	allocated
In-Reply-To: <1314930851.91.0.112444630543.issue12880@psf.upfronthosting.co.za>
Message-ID: <1317703787.61.0.662563806056.issue12880@psf.upfronthosting.co.za>


Meador Inge <meadori at gmail.com> added the comment:

Added some comments in rietveld.  P.S. watch out for trailing whitespace
when writing patches.  Use 'make patchcheck' to help find bad whitespace
formatting.

----------

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

From report at bugs.python.org  Tue Oct  4 17:21:46 2011
From: report at bugs.python.org (Vlad Riscutia)
Date: Tue, 04 Oct 2011 15:21:46 +0000
Subject: [docs] [issue12880] ctypes: clearly document how structure bit
	fields are	allocated
In-Reply-To: <1314930851.91.0.112444630543.issue12880@psf.upfronthosting.co.za>
Message-ID: <1317741706.31.0.492233657134.issue12880@psf.upfronthosting.co.za>


Vlad Riscutia <riscutiavlad at gmail.com> added the comment:

Thanks for the "make patchcheck" tip, I didn't know about that. I will update the patch soon.

In the mean time, I want to point out a couple of things:
First, I'm saying "toying with the underlying buffer" because none of the bugs are actual issues of the form "I created this bitfield structure with Python, passed it to C function but C structure was different". That would be a bitfield bug. All of these bugs are people setting raw memory to some bytes, then looking at bitfield members and not seeing what they expect. 

Since this is platform dependent, they shouldn't worry about the raw memory as long as C interop works fine. Bitfield layout is complex as it involves both allocation algorithm and structure packing and same Python code will work differently on Windows and Unix.

My point is that documenting all this low-level stuff will encourage people to work with the raw memory which will open the door for other issues. I believe it would be better to encourage users to stick to declaring members and accessing them by name as raw memory WILL be different for the same code on different OSes.

Second, one of your review comments is: "GCC is used for most Unix systems and Microsoft VC++ is used on Windows.". This is not how ctypes works. Ctypes implements the bitfield allocation algorithm itself, it doesn't use the compiler with which it is built. Basically it says #ifdef WIN32 - allocate like VC++ - #else - allocate like GCC. So it doesn't really matter with which compiler you are building Python. It will still do GCC style allocation on Solaris.

----------

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

From report at bugs.python.org  Tue Oct  4 19:44:30 2011
From: report at bugs.python.org (Meador Inge)
Date: Tue, 04 Oct 2011 17:44:30 +0000
Subject: [docs] [issue12880] ctypes: clearly document how structure bit
	fields are	allocated
In-Reply-To: <1317741706.31.0.492233657134.issue12880@psf.upfronthosting.co.za>
Message-ID: <CAK1QoopLaZrkokwQwM91Cei9PNryOaFdJ3dEV_077rVdO00mew@mail.gmail.com>


Meador Inge <meadori at gmail.com> added the comment:

On Tue, Oct 4, 2011 at 10:21 AM, Vlad Riscutia <report at bugs.python.org> wrote:

> First, I'm saying "toying with the underlying buffer" because none of the bugs are actual issues of the form "I created this bitfield
> structure with Python, passed it to C function but C structure was different". That would be a bitfield bug. All of these bugs are people
> setting raw memory to some bytes, then looking at bitfield members and not seeing what they expect.

Please qualify "all" instead of generalizing.  I can point to two
issues (issue11990 "I'm generating python code from real c code.",
issue12945 "We have raw data packages from some tools. These packages
contains bitfields, arrays, simple data and so on.") where C
code or raw data was, in fact, involved and the reporters just don't
understand what layout algorithm is being used.  They may not need
to know the specifics of the algorithm, but they *do* need to know if
it matches the compiler they are using to do interop or the one
that generated the raw data.

The reason that we are seeing folks cast raw memory into a cyptes
bitfield structure is because they do not understand how the structure
layout algorithm works and are trying to figure it out via these
examples.

> Second, one of your review comments is: "GCC is used for most Unix systems and Microsoft VC++ is used on Windows.". This is not
> how ctypes works. Ctypes implements the bitfield allocation algorithm itself, it doesn't use the compiler with which it is built. Basically
> it says #ifdef WIN32 - allocate like VC++ - #else - allocate like GCC. So it doesn't really matter with which compiler you are building
> Python. It will still do GCC style allocation on Solaris.

I understand how it works.  This quote is taken somewhat out of
context as the preceding sentence is important.  Perhaps saying GCC-
style and VC++-style would have been more clear.  The reason that I
mentioned the compiler used to build Python is that it is an easy
reference point and more times than not the bitfield allocation and
layout *do* match that of the compiler used to build the interpreter.
Anyway, I am fine with dropping the "used to build the Python
interpreter" and going with something similar to what you originally
had.

Also, in general, the compiler used to build the ctypes extension
*does* matter.  Look in 'cfield.c' where all of the native alignments
are
computed at compile time.  These alignments affect the structure
layout and are defined by the compiler building the ctypes extension.

----------

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

From report at bugs.python.org  Tue Oct  4 19:46:36 2011
From: report at bugs.python.org (Meador Inge)
Date: Tue, 04 Oct 2011 17:46:36 +0000
Subject: [docs] [issue12880] ctypes: clearly document how structure bit
	fields are	allocated
In-Reply-To: <1314930851.91.0.112444630543.issue12880@psf.upfronthosting.co.za>
Message-ID: <1317750396.47.0.0335003197932.issue12880@psf.upfronthosting.co.za>


Meador Inge <meadori at gmail.com> added the comment:

> Look in 'cfield.c' where all of the native alignments

Well, not *all* the native alignments, but many of them.

----------

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

From report at bugs.python.org  Tue Oct  4 20:36:49 2011
From: report at bugs.python.org (Brian Curtin)
Date: Tue, 04 Oct 2011 18:36:49 +0000
Subject: [docs] [issue13101] Module Doc viewer closes when browser window
	closes on	Windows 8
Message-ID: <1317753409.09.0.358970019617.issue13101@psf.upfronthosting.co.za>


New submission from Brian Curtin <brian at python.org>:

Reported by Ryan Wells (v-rywel at microsoft.com) of Microsoft, in reference to a problem with the Module Doc viewer on Windows 8 when using Internet Explorer 10. This was reported on 3.2.2, but it's likely the same on 2.7.


Reference #: 70652
Description of the Problem: The application Python Module Doc is automatically closed when Internet Explorer 10 is closed.
Steps to Reproduce:
1.       Install Windows Developer Preview
2.       Install Python 3.2.2
3.       Launch Module Doc.  Start Menu -> All Program -> Python -> Manual Docs
4.       Click on the button open browser
5.       It should open the site http://localhost:7464/ In Internet Explorer 10 and the contents should be displayed
6.       Should be able to view list of Modules, Scripts, DLLs, and Libraries etc.
7.       Close Internet Explorer

Expected Result: Internet Explorer 10 should only get closed and we should be able to work with the application Module Doc.
Actual Result: The application Module Doc is closed with Internet Explorer 10.
 
Developer Notes: There is likely a difference in return values between IE8 and IE9/10 when launched from the app.

----------
assignee: docs at python
components: Documentation, Windows
messages: 144918
nosy: brian.curtin, docs at python
priority: normal
severity: normal
status: open
title: Module Doc viewer closes when browser window closes on Windows 8
type: behavior
versions: Python 3.3

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

From report at bugs.python.org  Tue Oct  4 20:39:27 2011
From: report at bugs.python.org (Vlad Riscutia)
Date: Tue, 04 Oct 2011 18:39:27 +0000
Subject: [docs] [issue12880] ctypes: clearly document how structure bit
	fields are	allocated
In-Reply-To: <1314930851.91.0.112444630543.issue12880@psf.upfronthosting.co.za>
Message-ID: <1317753567.25.0.786594630469.issue12880@psf.upfronthosting.co.za>


Vlad Riscutia <riscutiavlad at gmail.com> added the comment:

I agree compiler matters for alignment but if you look at PyCField_FromDesc, you will see the layout is pretty much #ifdef MS_WIN32 - #else.

Sorry for generalizing, "all" indeed is not the right word. My point is that we should set expectation correctly - VC++-style on Windows, GCC-style everywhere else and encourage users to access structure members by name, not raw memory. Issues opened for bitfields *usually* are of the form I mentioned - setting raw memory to some bytes then seeing members are not what user expected, even if ctypes algorithm works correctly.

As I said, I will revise the patch and maybe make it more clear that users should look up how bitfield allocation works for their compiler instead of trying to understand this via structure raw memory.

----------

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

From report at bugs.python.org  Tue Oct  4 20:56:19 2011
From: report at bugs.python.org (Nick Coghlan)
Date: Tue, 04 Oct 2011 18:56:19 +0000
Subject: [docs] [issue13101] Module Doc viewer closes when browser window
	closes on	Windows 8
In-Reply-To: <1317753409.09.0.358970019617.issue13101@psf.upfronthosting.co.za>
Message-ID: <1317754578.99.0.926548764728.issue13101@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

If that's the app I think it is (pydoc -g), we're probably going to kill it off in 3.3 in favour of the -b option.

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

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

From report at bugs.python.org  Tue Oct  4 21:01:26 2011
From: report at bugs.python.org (Nick Coghlan)
Date: Tue, 04 Oct 2011 19:01:26 +0000
Subject: [docs] [issue13101] Module Doc viewer closes when browser window
	closes on	Windows 8
In-Reply-To: <1317753409.09.0.358970019617.issue13101@psf.upfronthosting.co.za>
Message-ID: <1317754886.65.0.967783598215.issue13101@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Slight correction, pydoc.gui() is already gone in current hg tip.

However, this error may be indicative of an underlying problem with webbrowser.open(url) throwing an exception.

----------

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

From report at bugs.python.org  Tue Oct  4 21:04:08 2011
From: report at bugs.python.org (Brian Curtin)
Date: Tue, 04 Oct 2011 19:04:08 +0000
Subject: [docs] [issue13101] Module Doc viewer closes when browser window
	closes on	Windows 8
In-Reply-To: <1317753409.09.0.358970019617.issue13101@psf.upfronthosting.co.za>
Message-ID: <1317755048.33.0.0500806581238.issue13101@psf.upfronthosting.co.za>


Brian Curtin <brian at python.org> added the comment:

The menu shortcut opens up the following: "C:\Python32\pythonw.exe" "C:\Python32\Tools\scripts\pydocgui.pyw", which is just pydoc.gui()

----------

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

From report at bugs.python.org  Wed Oct  5 01:51:15 2011
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 04 Oct 2011 23:51:15 +0000
Subject: [docs] [issue12880] ctypes: clearly document how structure bit
	fields are	allocated
In-Reply-To: <1314930851.91.0.112444630543.issue12880@psf.upfronthosting.co.za>
Message-ID: <1317772275.78.0.121151886567.issue12880@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

If I understand correctly, this doc patch would apply to 2.7 and 3.2 also. I have two style comments. I believe

"It is important to note that bit field allocation and layout in memory is not defined as a standard, rather its implementation is compiler-specific." 

could be shortened to

"Bit field allocation and memory layout is compiler-specific."

To me, this leads nicely into the proposed sentence that follows.

"it is recommended that no assumptions are made about the structure size and layout."

I do not like 'it is recommended'. Let us state the fact.

"any assumptions about the structure size and layout may be wrong."

----------
versions:  -Python 3.4

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

From report at bugs.python.org  Wed Oct  5 02:50:24 2011
From: report at bugs.python.org (Mark Hammond)
Date: Wed, 05 Oct 2011 00:50:24 +0000
Subject: [docs] [issue13101] Module Doc viewer closes when browser window
	closes on	Windows 8
In-Reply-To: <1317753409.09.0.358970019617.issue13101@psf.upfronthosting.co.za>
Message-ID: <1317775824.63.0.290294797485.issue13101@psf.upfronthosting.co.za>


Mark Hammond <skippy.hammond at gmail.com> added the comment:

For some reason, IE is struggling to even display the page - it just seems to sit there loading the page without displaying anything, but hitting "stop" then "refresh" usually brings it up.  But if you kill IE (which best I can tell can only be done via the task manager - it has no other Windows controls) the doc server process does also terminate.

If you run the doc server using python.exe, you will notice tracebacks in the console due to the socket connection being reset (which is probably related to the above problems - the socket should have been fully read by the time you manage to kill IE) - but using python.exe the process stays alive serving requests.  I *guess* that the problem is pythonw.exe is hitting an error when it attempts to print to the invalid stderr handle.  It might be possible that somehow under Windows 8, stderr isn't buffered (or has as large of a buffer) as other Windows versions, so dies when a small amount of data is written to stderr - but I suspect the same problem could be provoked on other Windows versions by arranging for > 8k of "connection reset by peer" tracebacks to be written, at which point the buffer is attempted to be flushed and fails.

Here endeth my speculation for the day ;)

----------
nosy: +mhammond

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

From report at bugs.python.org  Wed Oct  5 12:30:42 2011
From: report at bugs.python.org (Petri Lehtinen)
Date: Wed, 05 Oct 2011 10:30:42 +0000
Subject: [docs] [issue13073] message_body argument of
	HTTPConnection.endheaders is	undocumented
In-Reply-To: <1317370143.22.0.297306447289.issue13073@psf.upfronthosting.co.za>
Message-ID: <1317810642.73.0.210514641552.issue13073@psf.upfronthosting.co.za>


Petri Lehtinen <petri at digip.org> added the comment:

The 2.7 documentation should mention the version in which the argument was added. I believe it was 2.7.

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

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

From report at bugs.python.org  Wed Oct  5 12:32:29 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 05 Oct 2011 10:32:29 +0000
Subject: [docs] [issue13073] message_body argument of
	HTTPConnection.endheaders is	undocumented
In-Reply-To: <1317370143.22.0.297306447289.issue13073@psf.upfronthosting.co.za>
Message-ID: <1317810749.55.0.422552656027.issue13073@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

I also left some comments on the review page that should be addressed.

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

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

From ewan_higgs at yahoo.co.uk  Wed Oct  5 17:04:50 2011
From: ewan_higgs at yahoo.co.uk (Ewan Higgs)
Date: Wed, 5 Oct 2011 16:04:50 +0100 (BST)
Subject: [docs] Documentation bug in glob examples
Message-ID: <1317827090.45411.YahooMailNeo@web24614.mail.ird.yahoo.com>

Sir/Madame,
I believe there is a bug in the documentation for the glob module accessed through the following url on 2011/10/05:
http://docs.python.org/library/glob.html


Currently the example demonstrates the output of a series of globbing patterns in a directory with files 1.gif, 2.gif, and card.gif. The results returned are incorrect. They read:


>>> import glob?
>>> glob.glob('./[0-9].*')?
['./1.gif', './2.txt']?
>>> glob.glob('*.gif')?
['1.gif', 'card.gif']?
>>> glob.glob('?.gif')?
['1.gif']


However, the results should be as follows:

$python
Python 2.6.5 (r265:79063, Apr 26 2010, 12:52:32)?
[GCC 4.4.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import glob
>>> glob.glob('./[0-9].gif')
['./1.gif', './2.gif']
>>> glob.glob('*.gif')
['1.gif', 'card.gif', '2.gif']
>>> glob.glob('?.gif')
['1.gif', '2.gif']
>>>?

Yours,
Ewan Higgs

NB: This email was written based on advice found here:
http://docs.python.org/bugs.html


From report at bugs.python.org  Wed Oct  5 17:27:53 2011
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 05 Oct 2011 15:27:53 +0000
Subject: [docs] [issue13073] message_body argument of
	HTTPConnection.endheaders is	undocumented
In-Reply-To: <1317370143.22.0.297306447289.issue13073@psf.upfronthosting.co.za>
Message-ID: <E1RBTNv-0004Ur-B5@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset befa7b926aad by Senthil Kumaran in branch '3.2':
Issue  #13073 - Address the review comments made by Ezio.
http://hg.python.org/cpython/rev/befa7b926aad

New changeset a7b7ba225de7 by Senthil Kumaran in branch 'default':
merge from 3.2. Issue  #13073 - Address the review comments made by Ezio.
http://hg.python.org/cpython/rev/a7b7ba225de7

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

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

From report at bugs.python.org  Wed Oct  5 17:53:12 2011
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 05 Oct 2011 15:53:12 +0000
Subject: [docs] [issue13073] message_body argument of
	HTTPConnection.endheaders is	undocumented
In-Reply-To: <1317370143.22.0.297306447289.issue13073@psf.upfronthosting.co.za>
Message-ID: <E1RBTmR-00073Y-4H@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 64fae6f7b64c by Senthil Kumaran in branch '2.7':
Issue13073 - Address review comments and add versionchanged information in the docs.
http://hg.python.org/cpython/rev/64fae6f7b64c

----------

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

From report at bugs.python.org  Wed Oct  5 17:54:13 2011
From: report at bugs.python.org (Senthil Kumaran)
Date: Wed, 05 Oct 2011 15:54:13 +0000
Subject: [docs] [issue13073] message_body argument of
	HTTPConnection.endheaders is	undocumented
In-Reply-To: <1317370143.22.0.297306447289.issue13073@psf.upfronthosting.co.za>
Message-ID: <1317830052.93.0.129183242088.issue13073@psf.upfronthosting.co.za>


Senthil Kumaran <senthil at uthcode.com> added the comment:

I believe, I have addressed all the comments. Closing this report.

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

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

From georg at python.org  Wed Oct  5 17:57:49 2011
From: georg at python.org (Georg Brandl)
Date: Wed, 05 Oct 2011 17:57:49 +0200
Subject: [docs] Documentation bug in glob examples
In-Reply-To: <1317827090.45411.YahooMailNeo@web24614.mail.ird.yahoo.com>
References: <1317827090.45411.YahooMailNeo@web24614.mail.ird.yahoo.com>
Message-ID: <4E8C7E7D.3080704@python.org>

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

On 10/05/11 17:04, Ewan Higgs wrote:
> Sir/Madame, I believe there is a bug in the documentation for the glob
> module accessed through the following url on 2011/10/05: 
> http://docs.python.org/library/glob.html
> 
> 
> Currently the example demonstrates the output of a series of globbing
> patterns in a directory with files 1.gif, 2.gif, and card.gif. The results
> returned are incorrect. They read:
> 
> 
>>>> import glob glob.glob('./[0-9].*')
> ['./1.gif', './2.txt']
>>>> glob.glob('*.gif')
> ['1.gif', 'card.gif']
>>>> glob.glob('?.gif')
> ['1.gif']
> 
> 
> However, the results should be as follows:
> 
> $python Python 2.6.5 (r265:79063, Apr 26 2010, 12:52:32) [GCC 4.4.3] on
> linux2 Type "help", "copyright", "credits" or "license" for more
> information.
>>>> import glob glob.glob('./[0-9].gif')
> ['./1.gif', './2.gif']
>>>> glob.glob('*.gif')
> ['1.gif', 'card.gif', '2.gif']
>>>> glob.glob('?.gif')
> ['1.gif', '2.gif']
>>>> 

Hi Ewan,

it seems to me that the example is correct: note that the second file is
called "2.txt", not "2.gif".

cheers,
Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEARECAAYFAk6Mfn0ACgkQN9GcIYhpnLCyCACfc3BcT6AoXqv5EcbgOIedalQX
0rAAn2zYsYpSSf3mCEbM7bBUARL8DL8D
=eN8J
-----END PGP SIGNATURE-----

From ewan_higgs at yahoo.co.uk  Wed Oct  5 18:06:46 2011
From: ewan_higgs at yahoo.co.uk (Ewan Higgs)
Date: Wed, 5 Oct 2011 17:06:46 +0100 (BST)
Subject: [docs] Documentation bug in glob examples
In-Reply-To: <4E8C7E7D.3080704@python.org>
References: <1317827090.45411.YahooMailNeo@web24614.mail.ird.yahoo.com>
	<4E8C7E7D.3080704@python.org>
Message-ID: <1317830806.53437.YahooMailNeo@web24603.mail.ird.yahoo.com>

How embarassing!

Sorry to have wasted your time.

Yours,
Ewan


________________________________
From: Georg Brandl <georg at python.org>
To: Ewan Higgs <ewan_higgs at yahoo.co.uk>
Cc: "docs at python.org" <docs at python.org>
Sent: Wednesday, 5 October 2011, 16:57
Subject: Re: [docs] Documentation bug in glob examples

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

On 10/05/11 17:04, Ewan Higgs wrote:
> Sir/Madame, I believe there is a bug in the documentation for the glob
> module accessed through the following url on 2011/10/05: 
> http://docs.python.org/library/glob.html
> 
> 
> Currently the example demonstrates the output of a series of globbing
> patterns in a directory with files 1.gif, 2.gif, and card.gif. The results
> returned are incorrect. They read:
> 
> 
>>>> import glob glob.glob('./[0-9].*')
> ['./1.gif', './2.txt']
>>>> glob.glob('*.gif')
> ['1.gif', 'card.gif']
>>>> glob.glob('?.gif')
> ['1.gif']
> 
> 
> However, the results should be as follows:
> 
> $python Python 2.6.5 (r265:79063, Apr 26 2010, 12:52:32) [GCC 4.4.3] on
> linux2 Type "help", "copyright", "credits" or "license" for more
> information.
>>>> import glob glob.glob('./[0-9].gif')
> ['./1.gif', './2.gif']
>>>> glob.glob('*.gif')
> ['1.gif', 'card.gif', '2.gif']
>>>> glob.glob('?.gif')
> ['1.gif', '2.gif']
>>>> 

Hi Ewan,

it seems to me that the example is correct: note that the second file is
called "2.txt", not "2.gif".

cheers,
Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEARECAAYFAk6Mfn0ACgkQN9GcIYhpnLCyCACfc3BcT6AoXqv5EcbgOIedalQX
0rAAn2zYsYpSSf3mCEbM7bBUARL8DL8D
=eN8J
-----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111005/d2fbc791/attachment-0001.html>

From report at bugs.python.org  Thu Oct  6 13:19:45 2011
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 06 Oct 2011 11:19:45 +0000
Subject: [docs] [issue9442] Update sys.version doc
In-Reply-To: <1280605593.44.0.301230771819.issue9442@psf.upfronthosting.co.za>
Message-ID: <E1RBlzL-0000af-QY@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 9f6704da4abb by ?ric Araujo in branch '2.7':
Fix markup used in the documentation of sys.prefix and sys.exec_prefix.
http://hg.python.org/cpython/rev/9f6704da4abb

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

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

From report at bugs.python.org  Thu Oct  6 13:24:05 2011
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 06 Oct 2011 11:24:05 +0000
Subject: [docs] [issue9442] Update sys.version doc
In-Reply-To: <1280605593.44.0.301230771819.issue9442@psf.upfronthosting.co.za>
Message-ID: <E1RBm3X-0000ym-MA@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 6ea47522f466 by ?ric Araujo in branch '3.2':
Fix markup used in the documentation of sys.prefix and sys.exec_prefix.
http://hg.python.org/cpython/rev/6ea47522f466

----------

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

From report at bugs.python.org  Thu Oct  6 13:38:12 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 06 Oct 2011 11:38:12 +0000
Subject: [docs] [issue13073] message_body argument of
	HTTPConnection.endheaders is	undocumented
In-Reply-To: <1317370143.22.0.297306447289.issue13073@psf.upfronthosting.co.za>
Message-ID: <1317901092.1.0.246854308757.issue13073@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

It is IMO a source of confusion that the doc talk about a string instead of ?a bytes object? (3.x) or ?a string (str)? (2.x, unless unicode is supported too).

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

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

From report at bugs.python.org  Thu Oct  6 14:44:44 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 06 Oct 2011 12:44:44 +0000
Subject: [docs] [issue12943] tokenize: add python -m tokenize support back
In-Reply-To: <1315537867.15.0.614423357455.issue12943@psf.upfronthosting.co.za>
Message-ID: <1317905084.47.0.61944677483.issue12943@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

I made a few last remarks on Rietveld; feel free to address or ignore them and commit right away.

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

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

From report at bugs.python.org  Thu Oct  6 17:03:04 2011
From: report at bugs.python.org (Senthil Kumaran)
Date: Thu, 06 Oct 2011 15:03:04 +0000
Subject: [docs] [issue13073] message_body argument of
	HTTPConnection.endheaders is	undocumented
In-Reply-To: <1317901092.1.0.246854308757.issue13073@psf.upfronthosting.co.za>
Message-ID: <20111006150255.GE1946@mathmagic>


Senthil Kumaran <senthil at uthcode.com> added the comment:

Yes, I agree. I think, it can be clarified at that point too. Because.
in 2.7 the string is being checked and in 3.3 the message_body is
checked if it's instance of bytes.  But, I think, it should be
carefully worded (aligned with how other socket message args are
mentioned).

----------

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

From report at bugs.python.org  Thu Oct  6 20:35:25 2011
From: report at bugs.python.org (=?utf-8?q?F=C3=A9lix-Antoine_Fortin?=)
Date: Thu, 06 Oct 2011 18:35:25 +0000
Subject: [docs] [issue13118] Py_BuildValue format f incorrect description.
Message-ID: <1317926125.15.0.437576148609.issue13118@psf.upfronthosting.co.za>


New submission from F?lix-Antoine Fortin <felixantoinefortin+python at gmail.com>:

Python/C API Reference Manual, section Utilities, Parsing arguments and building values, function Py_BuildValue.

The description for the format unit "f" is incorrect. It reads "Same as d.", as it should be "Convert a C float to a Python floating point number." since "f" is not the same as "d" when converting double to Python float. 

This was corrected in the documentation of Python 3, from which the proposed description comes.

----------
assignee: docs at python
components: Documentation
messages: 145031
nosy: docs at python, felixantoinefortin
priority: normal
severity: normal
status: open
title: Py_BuildValue format f incorrect description.
versions: Python 2.6, Python 2.7

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

From report at bugs.python.org  Fri Oct  7 00:59:50 2011
From: report at bugs.python.org (Mike Hoy)
Date: Thu, 06 Oct 2011 22:59:50 +0000
Subject: [docs] [issue12436] Missing items in installation/setup instructions
In-Reply-To: <1309305395.29.0.101516779086.issue12436@psf.upfronthosting.co.za>
Message-ID: <1317941990.78.0.378605947804.issue12436@psf.upfronthosting.co.za>


Mike Hoy <mhoy09 at gmail.com> added the comment:

> - How to prepare a text editor
See: http://docs.python.org/dev/using/unix.html#editors

> - How to run Python code from a file (if the tutorial or using docs don?t already have it).

See: http://docs.python.org/dev/using/unix.html#miscellaneous

----------
nosy: +mikehoy

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

From report at bugs.python.org  Fri Oct  7 01:12:35 2011
From: report at bugs.python.org (Amaury Forgeot d'Arc)
Date: Thu, 06 Oct 2011 23:12:35 +0000
Subject: [docs] [issue13118] Py_BuildValue format f incorrect description.
In-Reply-To: <1317926125.15.0.437576148609.issue13118@psf.upfronthosting.co.za>
Message-ID: <1317942755.22.0.884446222941.issue13118@psf.upfronthosting.co.za>


Amaury Forgeot d'Arc <amauryfa at gmail.com> added the comment:

I've checked in the code: 'f' and 'd' are really the same (Python/modsupport.c).

And in http://en.wikipedia.org/wiki/Stdarg.h, you can read: """A float will automatically be promoted to a double."""

----------
nosy: +amaury.forgeotdarc

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

From report at bugs.python.org  Fri Oct  7 01:31:38 2011
From: report at bugs.python.org (Mike Hoy)
Date: Thu, 06 Oct 2011 23:31:38 +0000
Subject: [docs] [issue12823] Broken link in "SSL wrapper for socket objects"
	document
In-Reply-To: <1314086720.91.0.705244554246.issue12823@psf.upfronthosting.co.za>
Message-ID: <1317943898.08.0.537958291243.issue12823@psf.upfronthosting.co.za>


Mike Hoy <mhoy09 at gmail.com> added the comment:

Patch to remove broken link.

----------
keywords: +patch
nosy: +mikehoy
Added file: http://bugs.python.org/file23334/SSL-broken-link.diff

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

From report at bugs.python.org  Fri Oct  7 06:34:10 2011
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 07 Oct 2011 04:34:10 +0000
Subject: [docs] [issue12602] Missing using docs cross-references
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1317962050.09.0.148104173773.issue12602@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

This is all a puzzle to me. "<script>" ??

Links from docs to tracker issue??

There is at least one other issue about bad links (from builtin functions entries).

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

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

From report at bugs.python.org  Fri Oct  7 07:51:55 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 07 Oct 2011 05:51:55 +0000
Subject: [docs] [issue12602] Missing using docs cross-references
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1317966715.7.0.663176267282.issue12602@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/issue12602>
_______________________________________

From report at bugs.python.org  Fri Oct  7 15:51:56 2011
From: report at bugs.python.org (Meador Inge)
Date: Fri, 07 Oct 2011 13:51:56 +0000
Subject: [docs] [issue12943] tokenize: add python -m tokenize support back
In-Reply-To: <1315537867.15.0.614423357455.issue12943@psf.upfronthosting.co.za>
Message-ID: <1317995516.69.0.745379490275.issue12943@psf.upfronthosting.co.za>


Meador Inge <meadori at gmail.com> added the comment:

?ric, thanks.  I fixed most of your points.  And thanks to everyone that reviewed this.  Much appreciated.

----------

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

From report at bugs.python.org  Fri Oct  7 15:55:04 2011
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 07 Oct 2011 13:55:04 +0000
Subject: [docs] [issue12943] tokenize: add python -m tokenize support back
In-Reply-To: <1315537867.15.0.614423357455.issue12943@psf.upfronthosting.co.za>
Message-ID: <E1RCAtD-00027B-6k@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 85254bb6c1c6 by Meador Inge in branch 'default':
Issue #12943: python -m tokenize support has been added to tokenize.
http://hg.python.org/cpython/rev/85254bb6c1c6

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

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

From report at bugs.python.org  Fri Oct  7 15:56:53 2011
From: report at bugs.python.org (Meador Inge)
Date: Fri, 07 Oct 2011 13:56:53 +0000
Subject: [docs] [issue12943] tokenize: add python -m tokenize support back
In-Reply-To: <1315537867.15.0.614423357455.issue12943@psf.upfronthosting.co.za>
Message-ID: <1317995813.97.0.270184955841.issue12943@psf.upfronthosting.co.za>


Changes by Meador Inge <meadori at gmail.com>:


----------
assignee: docs at python -> meador.inge
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Fri Oct  7 16:04:57 2011
From: report at bugs.python.org (Mike Hoy)
Date: Fri, 07 Oct 2011 14:04:57 +0000
Subject: [docs] [issue12602] Missing using docs cross-references
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1317996297.68.0.628753882555.issue12602@psf.upfronthosting.co.za>


Changes by Mike Hoy <mhoy09 at gmail.com>:


----------
nosy: +mikehoy

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

From report at bugs.python.org  Fri Oct  7 16:06:15 2011
From: report at bugs.python.org (Mike Hoy)
Date: Fri, 07 Oct 2011 14:06:15 +0000
Subject: [docs] [issue12192] Doc that collection mutation methods return
	item or None
In-Reply-To: <1306445590.95.0.898960015708.issue12192@psf.upfronthosting.co.za>
Message-ID: <1317996375.08.0.643084274251.issue12192@psf.upfronthosting.co.za>


Changes by Mike Hoy <mhoy09 at gmail.com>:


----------
nosy: +mikehoy

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

From report at bugs.python.org  Fri Oct  7 16:20:00 2011
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 07 Oct 2011 14:20:00 +0000
Subject: [docs] [issue12602] Missing using docs cross-references
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1317997200.42.0.414757522772.issue12602@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

The 'using docs' are, oddly enough, the part of the docs called 'using' :)

In particular, the part about the command line components (including the '<script>' argument):
http://docs.python.org/using/cmdline.html

----------

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

From report at bugs.python.org  Fri Oct  7 16:57:20 2011
From: report at bugs.python.org (=?utf-8?q?F=C3=A9lix-Antoine_Fortin?=)
Date: Fri, 07 Oct 2011 14:57:20 +0000
Subject: [docs] [issue13118] Py_BuildValue format f incorrect description.
In-Reply-To: <1317926125.15.0.437576148609.issue13118@psf.upfronthosting.co.za>
Message-ID: <1317999440.38.0.226046727071.issue13118@psf.upfronthosting.co.za>


F?lix-Antoine Fortin <felixantoinefortin+python at gmail.com> added the comment:

I stand corrected.

----------
resolution:  -> rejected
status: open -> closed

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

From report at bugs.python.org  Fri Oct  7 17:02:20 2011
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 07 Oct 2011 15:02:20 +0000
Subject: [docs] [issue12823] Broken link in "SSL wrapper for socket objects"
	document
In-Reply-To: <1314086720.91.0.705244554246.issue12823@psf.upfronthosting.co.za>
Message-ID: <E1RCBwI-0000dE-NX@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 459f5e10cd4f by Antoine Pitrou in branch '3.2':
Issue #12823: remove broken link and replace it with another resource.
http://hg.python.org/cpython/rev/459f5e10cd4f

New changeset e80121fd12ba by Antoine Pitrou in branch 'default':
Issue #12823: remove broken link and replace it with another resource.
http://hg.python.org/cpython/rev/e80121fd12ba

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

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

From report at bugs.python.org  Fri Oct  7 17:02:20 2011
From: report at bugs.python.org (Sven Marnach)
Date: Fri, 07 Oct 2011 15:02:20 +0000
Subject: [docs] [issue13122] Out of date links in the sidebar of the
	documentation	index of versions 3.1 and 3.2
Message-ID: <1317999740.46.0.922190010194.issue13122@psf.upfronthosting.co.za>


New submission from Sven Marnach <sven at marnach.net>:

The sidebar on http://docs.python.org/release/3.1.3/ names 3.2 as the development version of Python, while the link points to 3.3.  The sidebar on http://docs.python.org/py3k/ links to 3.1 as the "stable version" -- obviously a relict from the time when 3.2 was in development.  (This could be fixed in Doc/tools/sphinxext/indexsidebar.html of the respective branches.)

----------
assignee: docs at python
components: Documentation
messages: 145084
nosy: docs at python, smarnach
priority: normal
severity: normal
status: open
title: Out of date links in the sidebar of the documentation index of versions 3.1 and 3.2
versions: Python 3.1, Python 3.2

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

From report at bugs.python.org  Fri Oct  7 17:08:26 2011
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 07 Oct 2011 15:08:26 +0000
Subject: [docs] [issue12823] Broken link in "SSL wrapper for socket objects"
	document
In-Reply-To: <1314086720.91.0.705244554246.issue12823@psf.upfronthosting.co.za>
Message-ID: <E1RCC2C-0001K1-VW@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 666e7e325795 by Antoine Pitrou in branch '2.7':
Issue #12823: remove broken link and replace it with another resource.
http://hg.python.org/cpython/rev/666e7e325795

----------

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

From report at bugs.python.org  Fri Oct  7 17:09:34 2011
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 07 Oct 2011 15:09:34 +0000
Subject: [docs] [issue12823] Broken link in "SSL wrapper for socket objects"
	document
In-Reply-To: <1314086720.91.0.705244554246.issue12823@psf.upfronthosting.co.za>
Message-ID: <1318000174.85.0.714711684939.issue12823@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

Fixed now. Hopefully the replacement resource is good enough.

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

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

From report at bugs.python.org  Fri Oct  7 18:13:45 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 07 Oct 2011 16:13:45 +0000
Subject: [docs] [issue12436] Missing items in installation/setup instructions
In-Reply-To: <1309305395.29.0.101516779086.issue12436@psf.upfronthosting.co.za>
Message-ID: <1318004025.15.0.877100771173.issue12436@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Thanks Mike!  So the first item is covered (at least for UNIX, can you check the Windows docs too?), but not the second.  The item you linked to explains how to modify a script so that it?s possible to run ./script on Unix, but does not give an actual example of running it, nor does it explain ?python script? or ?python script.py? or ?python -m module?.

----------

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

From report at bugs.python.org  Fri Oct  7 18:16:17 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 07 Oct 2011 16:16:17 +0000
Subject: [docs] [issue12602] Missing cross-references in Doc/using
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1318004177.81.0.444589989915.issue12602@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Terry, might that other issue be #12298?

----------
title: Missing using docs cross-references -> Missing cross-references in Doc/using

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

From report at bugs.python.org  Fri Oct  7 19:10:19 2011
From: report at bugs.python.org (Mike Hoy)
Date: Fri, 07 Oct 2011 17:10:19 +0000
Subject: [docs] [issue12436] Missing items in installation/setup instructions
In-Reply-To: <1309305395.29.0.101516779086.issue12436@psf.upfronthosting.co.za>
Message-ID: <1318007419.76.0.0380576944804.issue12436@psf.upfronthosting.co.za>


Mike Hoy <mhoy09 at gmail.com> added the comment:

> Thanks Mike!  So the first item is covered (at least for UNIX, can you 
> check the Windows docs too?), but not the second.  

http://docs.python.org/dev/using/windows.html Makes no reference to preparing a text editor. This I could help with but...

> The item you linked 
> to explains how to modify a script so that it?s possible to run 
> ./script on Unix, but does not give an actual example of running it, 
> nor does it explain ?python script? or ?python script.py? or ?python -m 
> module?.

Some one else would have to write this part unless you can give me some info about how it should be worded.

----------

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

From report at bugs.python.org  Fri Oct  7 19:38:24 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 07 Oct 2011 17:38:24 +0000
Subject: [docs] [issue12436] Missing items in installation/setup instructions
In-Reply-To: <1309305395.29.0.101516779086.issue12436@psf.upfronthosting.co.za>
Message-ID: <1318009104.26.0.680721561885.issue12436@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

> http://docs.python.org/dev/using/windows.html Makes no reference to
> preparing a text editor. This I could help with but...
Cool, please follow the guidelines in the devguide to make a patch for 3.2.  It should be something short, like the unix docs, mostly to recommend Notepad++ I think.

For Windows users, added a section about how to use a terminal and possibly a link to PowerShell would be another good addition IMO.

> Some one else would have to write this part unless you can give me
> some info about how it should be worded.
I?ll propose a patch.

----------

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

From report at bugs.python.org  Fri Oct  7 20:18:38 2011
From: report at bugs.python.org (Eric Snow)
Date: Fri, 07 Oct 2011 18:18:38 +0000
Subject: [docs] [issue13124] Add "Running a Build Slave" page to the devguide
Message-ID: <1318011517.56.0.343886781977.issue13124@psf.upfronthosting.co.za>


New submission from Eric Snow <ericsnowcurrently at gmail.com>:

Here's a patch to add a page to the devguide on running a build slave.  I copied pretty liberally from the wiki (http://wiki.python.org/moin/BuildBot).  That page may or may not be up to date (I don't know), so the bulk of this new page may also be out of date...

The current devguide buildbots page is oriented toward the use of buildbots in the dev process.  In contrast, this new page is all about running one.  I figured it is yet another easy way that people can contribute to Python.

I didn't stick in the windows-specific buildbot info (http://wiki.python.org/moin/BuildbotOnWindows), but did link to the wiki page.

I did include the info, as far as I understood it, from a recent python-dev thread (http://mail.python.org/pipermail/python-dev/2011-October/113935.html).

I added a link to the devguide index page, but it may need to be shifted to the right spot (maybe right after "Running & Writing Tests").  I also renamed buildbots.rst to continuous_integration.rst (and updated reference accordingly).

I want to be sure attribution is appropriate, regarding the text pulled from the wiki page and from the python-dev thread.  Is linking to the thread sufficient?

This is a rough stab (especially with the inclusion of the still-ongoing python-dev thread); but hopefully this gets a ball rolling and doesn't take much work to polish.  :)

----------
assignee: docs at python
components: Devguide, Documentation
files: buildslaves.diff
keywords: patch
messages: 145120
nosy: brett.cannon, docs at python, eric.snow
priority: normal
severity: normal
status: open
title: Add "Running a Build Slave" page to the devguide
type: feature request
versions: Python 3.3
Added file: http://bugs.python.org/file23338/buildslaves.diff

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

From report at bugs.python.org  Fri Oct  7 20:30:03 2011
From: report at bugs.python.org (Mike Hoy)
Date: Fri, 07 Oct 2011 18:30:03 +0000
Subject: [docs] [issue12436] Missing items in installation/setup instructions
In-Reply-To: <1309305395.29.0.101516779086.issue12436@psf.upfronthosting.co.za>
Message-ID: <1318012203.84.0.114627612943.issue12436@psf.upfronthosting.co.za>


Mike Hoy <mhoy09 at gmail.com> added the comment:

> mostly to recommend Notepad++ I think.

In addition to Notepad++ do you think it would be a good idea to at least mention Vim and Emacs with a disclaimer about the learning curve?

> For Windows users, added a section about how to use a terminal and 

Do you think it would be a good idea to add instructions on how to add Python to the Path in Windows? It could be 'borrowed' from the Boston Python Workshop Page I would think. It's pretty long but useful considering how much trouble I have had having to do this myself under Windows.

----------

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

From report at bugs.python.org  Fri Oct  7 21:10:12 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 07 Oct 2011 19:10:12 +0000
Subject: [docs] [issue13124] Add "Running a Build Slave" page to the devguide
In-Reply-To: <1318011517.56.0.343886781977.issue13124@psf.upfronthosting.co.za>
Message-ID: <1318014612.04.0.148264127407.issue13124@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

A few comments:
  * are you following some convention about the spelling of buildbot/Buildbot/BuildBot?
  * "+3. the standard development toolchain."
    Which is? I think a compiler is the only missing bit.
  * "(in which case you'll have to install Python and Twisted first)."
    I would say "you'll need" and not assume that they are not installed.
  * "a couple of third-party libraries (such as zlib and OpenSSL)."
    Actually these are not required, and it might even be good to have some buildbot without e.g. zlib.
  * "+   % su - buildbot"
    I think we use $ elsewhere in the doc.  You can also set the highlightlang to sh (iirc).
  * "/usr/local/bin", these should get some markup: either ``..`` or :file:`...` (is :file: ok for dirs too?).
  * "You'll need to get someone to create the slavename/slavepasswd on dinsdale.python.org before doing this."
    So maybe put it before?
  * "monitor the build results and solve any setup issues causing test failures"
    If running a buildbot implies some responsibilities, maybe they should be mentioned earlier.
  * "executing arbitrarily horrible and/or malicious code"
    This sounds bad and misleading.  At worst the test can use resources extensively and/or cause crashes, but that doesn't mean that the code is arbitrary, horrible, or malicious.
  * "for cutting of the builder"
    s/of/off/
  * "Therefore builders should be set up in both configurations"
    This might lead build masters to think they have to set up both.
  * "Some tests, as the start of `this thread "
    You already have a link to this at the end of the section
  * "+Running a build slave requires some network access."
    Isn't 9020 the only *required* one?  If the others are not available, test will (should) be skipped.

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

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

From report at bugs.python.org  Fri Oct  7 21:25:27 2011
From: report at bugs.python.org (Ned Deily)
Date: Fri, 07 Oct 2011 19:25:27 +0000
Subject: [docs] [issue13122] Out of date links in the sidebar of the
	documentation	index of versions 3.1 and 3.2
In-Reply-To: <1317999740.46.0.922190010194.issue13122@psf.upfronthosting.co.za>
Message-ID: <1318015527.58.0.181067701303.issue13122@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Oct  7 21:26:57 2011
From: report at bugs.python.org (Eric Snow)
Date: Fri, 07 Oct 2011 19:26:57 +0000
Subject: [docs] [issue13124] Add "Running a Build Slave" page to the devguide
In-Reply-To: <1318011517.56.0.343886781977.issue13124@psf.upfronthosting.co.za>
Message-ID: <1318015617.49.0.046358771642.issue13124@psf.upfronthosting.co.za>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:

Great feedback!  Keep in mind that nearly all the content in my patch is pulled unedited from either the wiki page and the python-dev thread I mentioned.

I'll work on cleaning it up when I get a chance (probably after Wednesday's PyCon CFP closes :).  If anyone wants to do it before I get a chance, they are welcome to it.  Either way I think such a page will be helpful to have in the devguide.

----------

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

From report at bugs.python.org  Fri Oct  7 21:30:32 2011
From: report at bugs.python.org (Stefan Krah)
Date: Fri, 07 Oct 2011 19:30:32 +0000
Subject: [docs] [issue13124] Add "Running a Build Slave" page to the devguide
In-Reply-To: <1318011517.56.0.343886781977.issue13124@psf.upfronthosting.co.za>
Message-ID: <1318015832.26.0.319720984919.issue13124@psf.upfronthosting.co.za>


Stefan Krah <stefan-usenet at bytereef.org> added the comment:

I think the whole security paragraph should be deleted. The
discussion on python-dev has overstated the risks.

Anyone who is *that* security conscious and in effect does
not trust the Python committers should also audit the thousands
of lines of ./configure and any code that is executed by
`make install`, to name a few "security risks".


What I would like to see in the devguide is a cookbook shell
script with minimal comments that interested persons can
simply run.


The easiest way for me (I'm running two bots) was to install
Python-2.7 from source, then pip, then `pip install buildslave`.
(Yes, as root :). That automatically gets everything right and
you don't depend on stale packages from the distro.

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

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

From report at bugs.python.org  Fri Oct  7 21:30:55 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 07 Oct 2011 19:30:55 +0000
Subject: [docs] [issue12436] Missing items in installation/setup instructions
In-Reply-To: <1309305395.29.0.101516779086.issue12436@psf.upfronthosting.co.za>
Message-ID: <1318015855.2.0.291871518352.issue12436@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

> In addition to Notepad++ do you think it would be a good idea to at
> least mention Vim and Emacs with a disclaimer about the learning curve?

I'm not sure how many windows user use Vim/Emacs.  Maybe PyScripter could be mentioned too, but I'm not sure how popular it is and if there are better alternatives.

> Do you think it would be a good idea to add instructions on how to add
> Python to the Path in Windows? 

Yes, but isn't there a script somewhere that does that already?

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

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

From report at bugs.python.org  Fri Oct  7 21:37:29 2011
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 07 Oct 2011 19:37:29 +0000
Subject: [docs] [issue12436] Missing items in installation/setup instructions
In-Reply-To: <1309305395.29.0.101516779086.issue12436@psf.upfronthosting.co.za>
Message-ID: <1318016249.49.0.753702364253.issue12436@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

> In addition to Notepad++ do you think it would be a good idea to at
> least mention Vim and Emacs with a disclaimer about the learning curve?

I'm a bit surprised. I would think the devguide is aimed are people who are *already* programmers, and have chosen their tools. Therefore I don't know how such material is useful, and the devguide is already hefty enough.

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

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

From report at bugs.python.org  Fri Oct  7 21:38:48 2011
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 07 Oct 2011 19:38:48 +0000
Subject: [docs] [issue12436] Missing items in installation/setup instructions
In-Reply-To: <1309305395.29.0.101516779086.issue12436@psf.upfronthosting.co.za>
Message-ID: <1318016328.47.0.350082174698.issue12436@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

Oops. I just noticed this issue is not talking about the devguide, but the general docs. Please ignore the message above.

----------

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

From report at bugs.python.org  Fri Oct  7 23:59:35 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 07 Oct 2011 21:59:35 +0000
Subject: [docs] [issue13122] Out of date links in the sidebar of the
	documentation	index of versions 3.1 and 3.2
In-Reply-To: <1317999740.46.0.922190010194.issue13122@psf.upfronthosting.co.za>
Message-ID: <1318024775.25.0.593347511707.issue13122@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

AFAIK the doc for 3.1 is not rebuilt anymore, so even if it's fixed, the change won't have any visible effect -- unless someone manually triggers a rebuild.
Regarding the 3.1 link on the py3k page: I think 'stable' still applies, even if it only receives security fixes.

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

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

From report at bugs.python.org  Sat Oct  8 00:16:13 2011
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 07 Oct 2011 22:16:13 +0000
Subject: [docs] [issue12602] Missing cross-references in Doc/using
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1318025773.71.0.242689641188.issue12602@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

As of 2.7/3.2, the doc is named "Python Setup and Usage" at
http://docs.python.org/index.html
http://docs.python.org/using/cmdline.html (and other chapters)
and in the contents list of the Windows help version.
For new doc editors, it would be nicer if the filename (directory name, actually) had been changed to 'py_setup' or even 'py_usage'.

Looking in the first chapter, which you finally referenced, I do see an entry for '<script>', with the brackets, that can be both a target and container of links. That usage, with a generic argument name in angle brackets, may be unique in the docs. (I looked at trace, profile, pydoc, timeit, test, and doctest docs.) So don't be so surprised that others are not familiar with it. 

Now that is cleared up:
+1 on the links suggested in the original message.

-1 on a link to the tracker issue. That is not a coherent document and cannot be edited and improved. If more doc is needed, there should have been and could be a PEP, addition to the <script> entry, or a new chapter section 1.3 Zipfiles.

---
>Terry, might that other issue be #12298?

Yes. I see you have applied a fix.

----------

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

From report at bugs.python.org  Sat Oct  8 04:04:38 2011
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 08 Oct 2011 02:04:38 +0000
Subject: [docs] [issue13122] Out of date links in the sidebar of the
	documentation	index of versions 3.1 and 3.2
In-Reply-To: <1317999740.46.0.922190010194.issue13122@psf.upfronthosting.co.za>
Message-ID: <1318039477.99.0.523585618964.issue13122@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

I disagree about 3.2 not being 'stable'. With more bugs fixes, it should be more stable. People should be encouraged to download 3.2. 2.7 came out 8 months before, and that should be updated (and again when 3.3 comes out).

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

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

From report at bugs.python.org  Sat Oct  8 06:18:12 2011
From: report at bugs.python.org (Dillon Amburgey)
Date: Sat, 08 Oct 2011 04:18:12 +0000
Subject: [docs] [issue13127] xml.dom.Attr.name is not labeled as read-only
Message-ID: <1318047492.07.0.217686953928.issue13127@psf.upfronthosting.co.za>


New submission from Dillon Amburgey <dillona at dillona.com>:

http://docs.python.org/library/xml.dom.html#dom-attr-objects does not label the name attribute as read-only (like localName) even though it is.

----------
assignee: docs at python
components: Documentation
messages: 145155
nosy: dillona, docs at python
priority: normal
severity: normal
status: open
title: xml.dom.Attr.name is not labeled as read-only

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

From report at bugs.python.org  Sat Oct  8 06:19:35 2011
From: report at bugs.python.org (Dillon Amburgey)
Date: Sat, 08 Oct 2011 04:19:35 +0000
Subject: [docs] [issue13127] xml.dom.Attr.name is not labeled as read-only
In-Reply-To: <1318047492.07.0.217686953928.issue13127@psf.upfronthosting.co.za>
Message-ID: <1318047575.12.0.0784977708118.issue13127@psf.upfronthosting.co.za>


Dillon Amburgey <dillona at dillona.com> added the comment:

The behavior can be verified as follows. Notice that despite changing the value, the output XML does not change

>>> from xml.dom import minidom, Node
>>> a = minidom.parseString("<a href=\"http://asd.com\">asd</a>")
>>> a
<xml.dom.minidom.Document instance at 0x22d7c68>
>>> a.childNodes
[<DOM Element: a at 0x22d7d88>]
>>> a.childNodes[0]
<DOM Element: a at 0x22d7d88>
>>> a.childNodes[0].attributes
<xml.dom.minidom.NamedNodeMap object at 0x21caa70>
>>> a.childNodes[0].attributes.item(0)
<xml.dom.minidom.Attr instance at 0x22d7f38>
>>> a.childNodes[0].attributes.item(0).name
u'href'
>>> attr = a.childNodes[0].attributes.item(0)
>>> attr.name = "ad"
>>> a.toxml()
u'<?xml version="1.0" ?><a href="http://asd.com">asd</a>'
>>> attr.value = "asd"
>>> a.toxml()
u'<?xml version="1.0" ?><a href="asd">asd</a>'

----------

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

From report at bugs.python.org  Sat Oct  8 09:38:07 2011
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 08 Oct 2011 07:38:07 +0000
Subject: [docs] [issue13122] Out of date links in the sidebar of the
	documentation	index of versions 3.1 and 3.2
In-Reply-To: <1317999740.46.0.922190010194.issue13122@psf.upfronthosting.co.za>
Message-ID: <1318059487.37.0.434394623243.issue13122@psf.upfronthosting.co.za>


Georg Brandl <georg at python.org> added the comment:

Nobody said 3.2 was not stable...

----------

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

From report at bugs.python.org  Sat Oct  8 18:02:36 2011
From: report at bugs.python.org (Mike Hoy)
Date: Sat, 08 Oct 2011 16:02:36 +0000
Subject: [docs] [issue12192] Doc that collection mutation methods return
	item or None
In-Reply-To: <1306445590.95.0.898960015708.issue12192@psf.upfronthosting.co.za>
Message-ID: <1318089756.82.0.469510243259.issue12192@psf.upfronthosting.co.za>


Mike Hoy <mhoy09 at gmail.com> added the comment:

Created a patch based on suggestions here.

----------
keywords: +patch
Added file: http://bugs.python.org/file23346/return-none.diff

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

From report at bugs.python.org  Sat Oct  8 18:31:05 2011
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 08 Oct 2011 16:31:05 +0000
Subject: [docs] [issue12192] Doc that collection mutation methods return
	item or None
In-Reply-To: <1306445590.95.0.898960015708.issue12192@psf.upfronthosting.co.za>
Message-ID: <E1RCZnj-0005ri-Kq@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 352d075839f7 by Georg Brandl in branch 'default':
Closes #12192: Document that mutating list methods do not return the instance (original patch by Mike Hoy).
http://hg.python.org/cpython/rev/352d075839f7

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

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

From report at bugs.python.org  Sun Oct  9 02:49:33 2011
From: report at bugs.python.org (=?utf-8?q?Andreas_St=C3=BChrk?=)
Date: Sun, 09 Oct 2011 00:49:33 +0000
Subject: [docs] [issue13138] ElementTree's Element.iter() lacks versionadded
Message-ID: <1318121372.98.0.459756814836.issue13138@psf.upfronthosting.co.za>


New submission from Andreas St?hrk <andy-python at hammerhartes.de>:

See http://docs.python.org/whatsnew/2.7.html#updated-module-elementtree-1-3

----------
assignee: docs at python
components: Documentation
files: Element_iter_versionadded.patch
keywords: patch
messages: 145199
nosy: Trundle, docs at python
priority: normal
severity: normal
status: open
title: ElementTree's Element.iter() lacks versionadded
versions: Python 2.7
Added file: http://bugs.python.org/file23352/Element_iter_versionadded.patch

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

From report at bugs.python.org  Sun Oct  9 05:19:53 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 09 Oct 2011 03:19:53 +0000
Subject: [docs] [issue12436] Missing items in installation/setup instructions
In-Reply-To: <1309305395.29.0.101516779086.issue12436@psf.upfronthosting.co.za>
Message-ID: <1318130392.99.0.0037175845756.issue12436@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

> In addition to Notepad++ do you think it would be a good idea to at
> least mention Vim and Emacs with a disclaimer about the learning
> curve?
No.  If someone is looking at this page and doesn?t already have a text editor they?re familiar with, I think Notepad++ is the right tool to suggest.

> Do you think it would be a good idea to add instructions on how to add Python
> to the Path in Windows?
The doc already has that somewhere, unless I misremember.

> Yes, but isn't there a script somewhere that does that already?
One or more in Tools/scripts and maybe in PC or PCbuild too.

----------

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

From report at bugs.python.org  Sun Oct  9 08:59:47 2011
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 09 Oct 2011 06:59:47 +0000
Subject: [docs] [issue10526] Minor typo in What's New in Python 2.7
In-Reply-To: <1290681942.88.0.460201126168.issue10526@psf.upfronthosting.co.za>
Message-ID: <E1RCnMQ-0001rR-1V@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset c52bac35b498 by ?ric Araujo in branch 'default':
Merge fixes for #10526, #10359, #11254, #9100 and the bug without number
http://hg.python.org/cpython/rev/c52bac35b498

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

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

From report at bugs.python.org  Sun Oct  9 08:59:49 2011
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 09 Oct 2011 06:59:49 +0000
Subject: [docs] [issue10536] Enhancements to gettext docs
In-Reply-To: <1290730924.88.0.289473332428.issue10536@psf.upfronthosting.co.za>
Message-ID: <E1RCnMQ-0001rR-1z@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset e48e6e9bdef6 by ?ric Araujo in branch '3.2':
Fix a typo and a broken link (part of #10536).
http://hg.python.org/cpython/rev/e48e6e9bdef6

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

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

From report at bugs.python.org  Sun Oct  9 09:00:17 2011
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 09 Oct 2011 07:00:17 +0000
Subject: [docs] [issue10536] Enhancements to gettext docs
In-Reply-To: <1290730924.88.0.289473332428.issue10536@psf.upfronthosting.co.za>
Message-ID: <E1RCnMo-00024d-JU@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 1e48a2b484a3 by ?ric Araujo in branch '2.7':
Fix a typo and a broken link (part of #10536).
http://hg.python.org/cpython/rev/1e48a2b484a3

----------

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

From report at bugs.python.org  Sun Oct  9 11:04:29 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 09 Oct 2011 09:04:29 +0000
Subject: [docs] [issue13074] Improve documentation of locale encoding
	functions
In-Reply-To: <1317370534.21.0.426762958064.issue13074@psf.upfronthosting.co.za>
Message-ID: <1318151069.28.0.166619265031.issue13074@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
nosy: +eric.araujo, haypo, lemburg

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

From report at bugs.python.org  Sun Oct  9 11:14:26 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 09 Oct 2011 09:14:26 +0000
Subject: [docs] [issue13030] Be more generic when identifying the Windows
	main dir in	installation doc
In-Reply-To: <1316727111.41.0.373563358156.issue13030@psf.upfronthosting.co.za>
Message-ID: <1318151666.67.0.438185621626.issue13030@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

> The table headings 'Standard installation location' (of what?)
Of software projects using distutils.

> and 'Default value' (for what program?)
For a CPython without changes to the default build configuration.

> both seem a bit ambiguous, or rather they seem reversed to me. I
> would label the columns 'Default module directory' and 'Standard
> Python location'.
Well, no: the first column does not contain real paths, but templates with placeholders like prefix and X.Y.  The second column gives the path with the placeholders replaced by their default value.

> That said, I hope that the actual default module installation
> directory for install is the actual site-packages directory on
> my machine, based on where I actually put python,
Yes.

> and not the non-existent standard location, which I did not use
> but which is what the text seems to say (but which would be a
> behavior design bug to me).
?Default? means ?if you haven?t made any change to the build/install configuration of Python?.

Do these replies make sense?  If so, I can rephrase them as a doc patch.

----------

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

From report at bugs.python.org  Sun Oct  9 11:16:13 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 09 Oct 2011 09:16:13 +0000
Subject: [docs] [issue13094] Need Programming FAQ entry for the behavior of
	closures
In-Reply-To: <1317652797.3.0.357677492942.issue13094@psf.upfronthosting.co.za>
Message-ID: <1318151773.52.0.798907570703.issue13094@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
assignee:  -> docs at python
components: +Documentation -None
nosy: +eric.araujo
versions: +Python 3.2, Python 3.3

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

From report at bugs.python.org  Sun Oct  9 13:25:14 2011
From: report at bugs.python.org (Paul Moore)
Date: Sun, 09 Oct 2011 11:25:14 +0000
Subject: [docs] [issue12779] Update packaging documentation
In-Reply-To: <1313686169.0.0.406072932055.issue12779@psf.upfronthosting.co.za>
Message-ID: <1318159514.81.0.671316768994.issue12779@psf.upfronthosting.co.za>


Changes by Paul Moore <p.f.moore at gmail.com>:


----------
nosy: +pmoore

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

From report at bugs.python.org  Sun Oct  9 17:05:15 2011
From: report at bugs.python.org (Brian Brazil)
Date: Sun, 09 Oct 2011 15:05:15 +0000
Subject: [docs] [issue13050] RLock support the context manager protocol but
	this is	not documented
Message-ID: <1318172715.77.0.360303466185.issue13050@psf.upfronthosting.co.za>


New submission from Brian Brazil <brian.brazil at gmail.com>:

This is already documented:

http://docs.python.org/library/threading.html#using-locks-conditions-and-semaphores-in-the-with-statement

----------
nosy: +bbrazil

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

From report at bugs.python.org  Sun Oct  9 17:43:51 2011
From: report at bugs.python.org (Mike Hoy)
Date: Sun, 09 Oct 2011 15:43:51 +0000
Subject: [docs] [issue12436] Missing items in installation/setup instructions
In-Reply-To: <1309305395.29.0.101516779086.issue12436@psf.upfronthosting.co.za>
Message-ID: <1318175031.49.0.986539218473.issue12436@psf.upfronthosting.co.za>


Mike Hoy <mhoy09 at gmail.com> added the comment:

Here is what I have so far:

> For Windows users, added a section about how to use a terminal

How to use a terminal

Open a command prompt:

* On Windows Vista or Windows 7: click on the Start menu (the Windows logo in the lower left of the screen), type cmd into the Search field directly above the Start menu button, and click on "cmd" in the search results above the Search field.

* On Windows XP: click on the Start menu (the Windows logo in the lower left of the screen), click on "Run...", type cmd into the text box, and hit enter.

Commands used in terminal

* cd C:\ - Puts you in the root directory of the C drive.
* cd Python32 - Puts you in the directory where Python 3.2 is installed.
* dir - This command lists the contents of the Python32 directory.
* python - This command will invoke python.exe and bring up the interpreter.

> a link to PowerShell 

Windows PowerShell

Windows PowerShell is a task-based command-line shell and scripting language designed for system administration. It can be obtained here: http://technet.microsoft.com/en-us/library/bb978526.aspx.

----------

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

From report at bugs.python.org  Sun Oct  9 17:51:45 2011
From: report at bugs.python.org (R. David Murray)
Date: Sun, 09 Oct 2011 15:51:45 +0000
Subject: [docs] [issue13050] RLock support the context manager protocol but
	this is	not documented
In-Reply-To: <1318172715.77.0.360303466185.issue13050@psf.upfronthosting.co.za>
Message-ID: <1318175505.58.0.000355739442967.issue13050@psf.upfronthosting.co.za>


R. David Murray <rdmurray at bitdance.com> added the comment:

Hmm.  But what I did was look up the RLock section of the manual to answer the question "does this support the context manager protocol", and the answer appeared to be no.  In a reference manual I would expect all the important features of an object to be described in that object's documentation, or linked to therefrom.

----------

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

From report at bugs.python.org  Sun Oct  9 22:37:07 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Sun, 09 Oct 2011 20:37:07 +0000
Subject: [docs] [issue13141] get rid of old threading API in the examples
Message-ID: <1318192627.46.0.311858462486.issue13141@psf.upfronthosting.co.za>


New submission from Florent Xicluna <florent.xicluna at gmail.com>:

http://docs.python.org/dev/library/socketserver.html#asynchronous-mixins

Still there's getName or setDaemon in some example.

----------
assignee: docs at python
components: Documentation
messages: 145274
nosy: docs at python, flox
priority: low
severity: normal
stage: needs patch
status: open
title: get rid of old threading API in the examples
type: behavior
versions: Python 2.7, Python 3.3

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

From report at bugs.python.org  Sun Oct  9 22:57:17 2011
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 09 Oct 2011 20:57:17 +0000
Subject: [docs] [issue13138] ElementTree's Element.iter() lacks versionadded
In-Reply-To: <1318121372.98.0.459756814836.issue13138@psf.upfronthosting.co.za>
Message-ID: <E1RD0Qu-00062C-5j@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 0f0a5d1c7a93 by Ezio Melotti in branch '2.7':
#13138: add missing versionadded.  Patch by Andreas St?hrk.
http://hg.python.org/cpython/rev/0f0a5d1c7a93

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

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

From report at bugs.python.org  Sun Oct  9 23:03:40 2011
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 09 Oct 2011 21:03:40 +0000
Subject: [docs] [issue13138] ElementTree's Element.iter() lacks versionadded
In-Reply-To: <1318121372.98.0.459756814836.issue13138@psf.upfronthosting.co.za>
Message-ID: <E1RD0X5-0006Pe-Gq@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 66d01b252b9a by Ezio Melotti in branch '3.2':
#13138: add missing versionadded.
http://hg.python.org/cpython/rev/66d01b252b9a

New changeset 2580e642e2ee by Ezio Melotti in branch 'default':
#13138: merge with 3.2.
http://hg.python.org/cpython/rev/2580e642e2ee

----------

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

From report at bugs.python.org  Sun Oct  9 23:04:47 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 09 Oct 2011 21:04:47 +0000
Subject: [docs] [issue13138] ElementTree's Element.iter() lacks versionadded
In-Reply-To: <1318121372.98.0.459756814836.issue13138@psf.upfronthosting.co.za>
Message-ID: <1318194287.41.0.15604214313.issue13138@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> 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

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

From report at bugs.python.org  Sun Oct  9 23:48:42 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 09 Oct 2011 21:48:42 +0000
Subject: [docs] [issue13127] xml.dom.Attr.name is not labeled as read-only
In-Reply-To: <1318047492.07.0.217686953928.issue13127@psf.upfronthosting.co.za>
Message-ID: <1318196922.06.0.722736384691.issue13127@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

localName is defined with defproperty() in Lib/xml/dom/minidom.py:464 and looking at the definition of defproperty() in  Lib/xml/dom/minicompat.py:97 I think this is supposed to raise an xml.dom.NoModificationAllowedErr exception when someone tries to write on the attribute.  This doesn't seem to happen though.
OTOH 'name' doesn't use defproperty(), so technically it's writable, expect that writing on it has no effect.
This should still be documented, and it would also be good to figure out what's going on with defproperty().

----------
components: +Library (Lib)
keywords: +easy
nosy: +ezio.melotti
stage:  -> test needed
versions: +Python 2.7

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

From report at bugs.python.org  Mon Oct 10 00:58:00 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 09 Oct 2011 22:58:00 +0000
Subject: [docs] [issue12436] Missing items in installation/setup instructions
In-Reply-To: <1309305395.29.0.101516779086.issue12436@psf.upfronthosting.co.za>
Message-ID: <1318201079.97.0.217028074088.issue12436@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

> Open a command prompt:
Another alternative is win+r -> type 'cmd' -> hit enter.  This should work on all the Windows versions.

> * cd C:\ - Puts you in the root directory of the C drive.
> * cd Python32 - Puts you in the directory where Python 3.2 is installed.

What if it's not installed there?  Maybe it's better to say something like "use the 'cd' command to move to the directory where Python is installed" possibly mentioning the default installation directory and  'cd ..'.

> * dir - This command lists the contents of the Python32 directory.
> * python - This command will invoke python.exe and bring up the 
interpreter.

If the dir is already added to the PATH 'python' will work already without having to navigate to the installation dir.
Also if the user installed Python there should be a "Python (command line)" entry in the start menu that brings up the interpreter.

----------

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

From report at bugs.python.org  Mon Oct 10 01:15:26 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 09 Oct 2011 23:15:26 +0000
Subject: [docs] [issue13075] PEP-0001 contains dead links
In-Reply-To: <1317374485.54.0.239839552518.issue13075@psf.upfronthosting.co.za>
Message-ID: <1318202126.06.0.423350899348.issue13075@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

This has been fixed in http://hg.python.org/peps/rev/398596beeee3
Thanks for the report and the patch!

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

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

From report at bugs.python.org  Mon Oct 10 01:59:57 2011
From: report at bugs.python.org (Mike Hoy)
Date: Sun, 09 Oct 2011 23:59:57 +0000
Subject: [docs] [issue12602] Missing cross-references in Doc/using
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1318204797.6.0.477186322816.issue12602@psf.upfronthosting.co.za>


Changes by Mike Hoy <mhoy09 at gmail.com>:


----------
nosy:  -mikehoy

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

From report at bugs.python.org  Mon Oct 10 12:00:23 2011
From: report at bugs.python.org (Guandalino)
Date: Mon, 10 Oct 2011 10:00:23 +0000
Subject: [docs] [issue11776] types.MethodType() params and usage is not
	documented
In-Reply-To: <1302036805.33.0.506634428921.issue11776@psf.upfronthosting.co.za>
Message-ID: <1318240823.23.0.820082060299.issue11776@psf.upfronthosting.co.za>


Changes by Guandalino <guandalino at gmail.com>:


----------
nosy: +guandalino

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

From report at bugs.python.org  Mon Oct 10 14:16:08 2011
From: report at bugs.python.org (Graeme Glass)
Date: Mon, 10 Oct 2011 12:16:08 +0000
Subject: [docs] [issue13144] Global Module Index link in the offline
	documentation is	incorrect
Message-ID: <1318248968.6.0.0439422849007.issue13144@psf.upfronthosting.co.za>


New submission from Graeme Glass <graemeglass at gmail.com>:

On my machine (Ubuntu 11.04) the link to "Python Module Index" from the index page is incorrect in the "Indices and tables" section (it links to    
modindex.html instead of py-modindex.html).
It links to the correct place in the navigation bar at the top right of the page.

Navigation (Correct): 
<li class="right" >
    <a href="py-modindex.html" title="Python Module Index">modules</a> 
|</li>

In the body (Incorrect):
 <p><strong>Indices and tables:</strong></p>
  ...
  <p class="biglink"><a class="biglink" href="modindex.html">Global Module Index</a><br/
  ...

This seems to affect python2.6 and python2.7 documentation.

(Indices and tables) link for these files:
file:///usr/share/doc/python2.6/html/index.html
file:///usr/share/doc/python2.6-doc/html/index.html

Link to: 
file:///usr/share/doc/python2.6/html/modindex.html
file:///usr/share/doc/python2.6-doc/html/modindex.html

When they should link to:
file:///usr/share/doc/python2.6/html/py-modindex.html
file:///usr/share/doc/python2.6-doc/html/py-modindex.html

Likewise:
file:///usr/share/doc/python2.7/html/index.html
file:///usr/share/doc/python2.7-doc/html/index.html

Link to:
file:///usr/share/doc/python2.7/html/modindex.html
file:///usr/share/doc/python2.7-doc/html/modindex.html

When they should link to:
file:///usr/share/doc/python2.7/html/py-modindex.html
file:///usr/share/doc/python2.7-doc/html/py-modindex.html

I searched the python bug tracker for a similar issue and could not find one.
I do not know if this affects python3.x Documentation also as I do not have it installed so have not checked. 
I am not sure if this is an Ubuntu issue or Python Docs Issue.

----------
assignee: docs at python
components: Documentation
messages: 145295
nosy: docs at python, graemeglass
priority: normal
severity: normal
status: open
title: Global Module Index link in the offline documentation is incorrect
versions: Python 2.6, Python 2.7

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

From report at bugs.python.org  Mon Oct 10 15:26:15 2011
From: report at bugs.python.org (Sven Marnach)
Date: Mon, 10 Oct 2011 13:26:15 +0000
Subject: [docs] [issue13145] Documentation of PyNumber_ToBase() wrong
Message-ID: <1318253175.42.0.981988907278.issue13145@psf.upfronthosting.co.za>


New submission from Sven Marnach <sven at marnach.net>:

The documentation of PyNumber_ToBase() [1] states

    When base is not 2, 8, 10, or 16, the format is 'x#num'
    where x is the base.

In reality, the function does not accept any bases different
from 2, 8, 10, or 16, as can be seen in the source code of 
_PyLong_Form() [2], which is called from PyNumber_ToBase() to
do the actual conversion.

The patch fixes the documentation.

[1]: http://docs.python.org/c-api/number.html#PyNumber_ToBase
[2]: http://hg.python.org/cpython/file/f924e0f62bcb/Objects/longobject.c#l1663

----------
assignee: docs at python
components: Documentation
files: pynumber-tobase-doc.patch
keywords: patch
messages: 145297
nosy: docs at python, smarnach
priority: normal
severity: normal
status: open
title: Documentation of PyNumber_ToBase() wrong
Added file: http://bugs.python.org/file23367/pynumber-tobase-doc.patch

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

From report at bugs.python.org  Mon Oct 10 17:31:56 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 10 Oct 2011 15:31:56 +0000
Subject: [docs] [issue11776] types.MethodType() params and usage is not
	documented
In-Reply-To: <1302036805.33.0.506634428921.issue11776@psf.upfronthosting.co.za>
Message-ID: <1318260716.51.0.0115257744428.issue11776@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
keywords: +easy
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Mon Oct 10 17:42:58 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 10 Oct 2011 15:42:58 +0000
Subject: [docs] [issue12436] Missing items in installation/setup instructions
In-Reply-To: <1309305395.29.0.101516779086.issue12436@psf.upfronthosting.co.za>
Message-ID: <1318261378.2.0.28991135849.issue12436@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Thanks, I will take all contributions and suggestions and propose one patch.

----------
assignee: docs at python -> eric.araujo

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

From report at bugs.python.org  Mon Oct 10 17:50:03 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 10 Oct 2011 15:50:03 +0000
Subject: [docs] [issue12602] Missing cross-references in Doc/using
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1318261803.38.0.558368564129.issue12602@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

> For new doc editors, it would be nicer if the filename (directory name, actually)
> had been changed to 'py_setup' or even 'py_usage'.
py_setup would conflict with pysetup, the installer part of distutils2/packaging.  py_ seems redundant to me, we are in the Python docs.

> Looking in the first chapter, which you finally referenced, I do see an entry for
> '<script>', with the brackets, that can be both a target and container of links. That
> usage, with a generic argument name in angle brackets, may be unique in the docs. (I
> looked at trace, profile, pydoc, timeit, test, and doctest docs.) So don't be so
> surprised that others are not familiar with it. 
I however am familiar with the use of <brackets>, $SHELL-LIKE-DOLLAR, OPTPARSE-LIKE-ALLCAPS or even {str-format-like-braces} to mark up metavariables.  ?Use python -m <module> or python -c "YOUR CODE HERE" or python path/to/script? is no problem; maybe it is because other documentation (man pages?) I?m familiar with use it.  (I even see them in email, like in ?$deity knows etc.?)

> +1 on the links suggested in the original message.
I?ll put up a patch for review.

> -1 on a link to the tracker issue.
I?ll see if I can add a few lines with the gist of the bug report, then.

----------
assignee:  -> eric.araujo

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

From report at bugs.python.org  Mon Oct 10 21:13:37 2011
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 10 Oct 2011 19:13:37 +0000
Subject: [docs] [issue12602] Missing cross-references in Doc/using
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1318274017.29.0.0809827571081.issue12602@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

I was not necessary suggesting that the filename actually be changed, just that the mapping between docs and filenames is not always obvious. I will somedays look at the dev docs doc page and see if I have any further suggestions to help.

Add 'in the Python doc context' after 'not familiar with it'. I *am* familiar with <text> in monofont ascii text and use it, for instance, in newsgroup posts. But unlike man pages, the Python docs are not so restricted and, except in this instance, use italics for parameter names. I suggest that it do so in this instance also, using *script* (in bold-faced italic) as the entry title.

----------

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

From report at bugs.python.org  Tue Oct 11 01:37:50 2011
From: report at bugs.python.org (Jakub Gedeon)
Date: Mon, 10 Oct 2011 23:37:50 +0000
Subject: [docs] [issue13147] Multiprocessing Pool.map_async() does not have
	an	error_callback parameter
Message-ID: <1318289870.89.0.681252830912.issue13147@psf.upfronthosting.co.za>


New submission from Jakub Gedeon <kazagistar at gmail.com>:

Multiprocessing Pool.map_async() does not have an error_callback paramter as described here http://docs.python.org/library/multiprocessing.html#multiprocessing.pool.multiprocessing.Pool.map_async

I assume this is an old configuration that no longer works... I tried to call that parameter by name and I got a Type Error, plus the actual documentation does not mention it at all (and it is missing from similar functions). Recommend it be removed from the documentation, or else better described and implemented.

----------
assignee: docs at python
components: Documentation
messages: 145316
nosy: Jakub.Gedeon, docs at python
priority: normal
severity: normal
status: open
title: Multiprocessing Pool.map_async() does not have an error_callback parameter
versions: Python 2.7

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

From report at bugs.python.org  Tue Oct 11 02:45:36 2011
From: report at bugs.python.org (Nick Coghlan)
Date: Tue, 11 Oct 2011 00:45:36 +0000
Subject: [docs] [issue12602] Missing cross-references in Doc/using
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1318293936.12.0.82328975529.issue12602@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Don't feel bad about not recognising the context - this stuff wasn't documented at all for a long time, and it wasn't until Georg pointed me to the usage docs that I realised adding it there would be the right place. I should have remembered that and been less cryptic when creating this issue.

It may suggest a meta-issue though - perhaps 'Documenting Python' should grow a devguide-style description of the Docs layout in source control, with a pointer from the devguide's directory layout description [1]?

[1] http://docs.python.org/devguide/setup.html#directory-structure

----------

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

From report at bugs.python.org  Tue Oct 11 06:11:55 2011
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 11 Oct 2011 04:11:55 +0000
Subject: [docs] [issue12602] Missing cross-references in Doc/using
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1318306315.66.0.203566685451.issue12602@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

That was the page I said I would look at. My suggest is that one or more of the directory entries could have either a bit more information about the directory or a "More info" link to a separate page. As a remember, files for modules were named after the module and easy to find. Those could be disposed of in one sentence. But files for the manuals were less so and could use more info.

My memory of Objects is that most files were obvious but, again, a few were/are not.

----------

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

From report at bugs.python.org  Tue Oct 11 15:44:48 2011
From: report at bugs.python.org (Barry A. Warsaw)
Date: Tue, 11 Oct 2011 13:44:48 +0000
Subject: [docs] [issue10976] json.loads() throws TypeError on bytes object
In-Reply-To: <1295636509.41.0.0138366952356.issue10976@psf.upfronthosting.co.za>
Message-ID: <1318340688.53.0.778980394001.issue10976@psf.upfronthosting.co.za>


Barry A. Warsaw <barry at python.org> added the comment:

I'll just mention that the elimination of bytes handling is a bit unfortunate, since this idiom which works in Python 2 no longer works:

fp = urlopen(url)
json_data = json.load(fp)

/me sad

----------
nosy: +barry

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

From report at bugs.python.org  Tue Oct 11 15:51:37 2011
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 11 Oct 2011 13:51:37 +0000
Subject: [docs] [issue10976] json.loads() throws TypeError on bytes object
In-Reply-To: <1318340688.53.0.778980394001.issue10976@psf.upfronthosting.co.za>
Message-ID: <1318340873.3277.4.camel@localhost.localdomain>


Antoine Pitrou <pitrou at free.fr> added the comment:

> I'll just mention that the elimination of bytes handling is a bit
> unfortunate, since this idiom which works in Python 2 no longer works:
> 
> fp = urlopen(url)
> json_data = json.load(fp)

What if the returned JSON uses a charset other than utf-8 ?

----------

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

From report at bugs.python.org  Tue Oct 11 19:06:49 2011
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 11 Oct 2011 17:06:49 +0000
Subject: [docs] [issue13145] Documentation of PyNumber_ToBase() wrong
In-Reply-To: <1318253175.42.0.981988907278.issue13145@psf.upfronthosting.co.za>
Message-ID: <E1RDfmy-00077K-Ef@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 61eb59516b55 by Mark Dickinson in branch '3.2':
Issue #13145. Fix incorrect documentation for PyNumber_ToBase.  Thanks Sven Marnach.
http://hg.python.org/cpython/rev/61eb59516b55

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

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

From report at bugs.python.org  Tue Oct 11 19:07:29 2011
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 11 Oct 2011 17:07:29 +0000
Subject: [docs] [issue13145] Documentation of PyNumber_ToBase() wrong
In-Reply-To: <1318253175.42.0.981988907278.issue13145@psf.upfronthosting.co.za>
Message-ID: <E1RDfnc-0007Af-0A@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset a644e2c43c4b by Mark Dickinson in branch 'default':
Merge issue #13145 fix.
http://hg.python.org/cpython/rev/a644e2c43c4b

----------

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

From report at bugs.python.org  Tue Oct 11 19:12:23 2011
From: report at bugs.python.org (Mark Dickinson)
Date: Tue, 11 Oct 2011 17:12:23 +0000
Subject: [docs] [issue13145] Documentation of PyNumber_ToBase() wrong
In-Reply-To: <1318253175.42.0.981988907278.issue13145@psf.upfronthosting.co.za>
Message-ID: <1318353143.88.0.953401301481.issue13145@psf.upfronthosting.co.za>


Mark Dickinson <dickinsm at gmail.com> added the comment:

Fixed.  Thanks for the report!

----------
nosy: +mark.dickinson
resolution:  -> fixed
status: open -> closed
versions: +Python 3.2, Python 3.3

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

From report at bugs.python.org  Tue Oct 11 19:12:39 2011
From: report at bugs.python.org (Mark Dickinson)
Date: Tue, 11 Oct 2011 17:12:39 +0000
Subject: [docs] [issue13145] Documentation of PyNumber_ToBase() wrong
In-Reply-To: <1318253175.42.0.981988907278.issue13145@psf.upfronthosting.co.za>
Message-ID: <1318353159.03.0.0641572208225.issue13145@psf.upfronthosting.co.za>


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


----------
assignee: docs at python -> mark.dickinson

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

From report at bugs.python.org  Tue Oct 11 23:55:08 2011
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 11 Oct 2011 21:55:08 +0000
Subject: [docs] [issue13154] pep-0000.txt doesn't build anymore
Message-ID: <1318370108.79.0.613915208631.issue13154@psf.upfronthosting.co.za>


New submission from Antoine Pitrou <pitrou at free.fr>:

$ make
make: D?pendance circulaire pep-0000.txt <- pep-0000.txt abandonn?e.
python genpepindex.py .
Traceback (most recent call last):
  File "genpepindex.py", line 67, in <module>
    main(sys.argv)
  File "genpepindex.py", line 64, in main
    write_pep0(peps, pep0_file)
  File "/home/antoine/cpython/peps/pep0/output.py", line 195, in write_pep0
    authors_dict = verify_email_addresses(peps)
  File "/home/antoine/cpython/peps/pep0/output.py", line 104, in verify_email_addresses
    "listed:\n" + '\n'.join(err_output))
ValueError: some authors have more than one email address listed:
    Gregory Ewing: [u'greg at cosc.canterbury.ac.nz', u'greg.ewing at canterbury.ac.nz']
make: *** [pep-0000.txt] Erreur 1

----------
assignee: docs at python
components: Documentation
messages: 145370
nosy: docs at python, pitrou
priority: normal
severity: normal
status: open
title: pep-0000.txt doesn't build anymore
type: compile error

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

From astrojohn at hotmail.co.uk  Sun Oct  9 17:41:21 2011
From: astrojohn at hotmail.co.uk (John Rowland)
Date: Sun, 9 Oct 2011 15:41:21 +0000
Subject: [docs] Hard Copy Documentation
Message-ID: <SNT110-W1F86E5C2221FA3913A481EAFC0@phx.gbl>


Hi Guys,
 
>From where can I obtain hard copy documentation - preferably in the form of proper books - on all aspects of Python?
 
I have already bought the book Natural Language Processing with Python, and whilst this is useful, it is not a reference manual. What I need is a book with all the commands, statements, expressions etc. listed (ideally alphabetically) along with their syntax.
 
I'm the sort of guy that starting from and given the ">>>" prompt, want to know what my options are in response to this. I also need more explanation on all sorts of things. As an example, "Import". What does this actually do? What does import really mean? Where is the imported item stored? What happens if I import when I've already imported? That sort of thing.
 
Sorry if I'm an awkward so_and_so but this is just how my mind works.
 
Hope to hear back from you soon.
 
Kind regards,
 
John Rowland
York, United Kingdom 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111009/d87ea61a/attachment-0001.html>

From bluefca at gmail.com  Wed Oct 12 08:27:25 2011
From: bluefca at gmail.com (Ray Wang)
Date: Wed, 12 Oct 2011 14:27:25 +0800
Subject: [docs] I found a question in the documentation.
Message-ID: <CA+P=fnyrUhqdKFfpo_jtZeJVgCrXa3K0MyW54xmsKcMoWa=GMQ@mail.gmail.com>

In the chapter of "3.1.2 String", the example:

>>> '"Isn\'t," she said.'
'"Isn\'t," she said.'

Should the printed result be
'"Isn't," she said.'
?

From joao.flavio at gmail.com  Mon Oct 10 16:10:36 2011
From: joao.flavio at gmail.com (Joao Carneiro)
Date: Mon, 10 Oct 2011 16:10:36 +0200
Subject: [docs] Mistake in the Python 3.2.2rc1 "help(set)"
Message-ID: <CAOcxvsMwSSOjtpTpx3=BbxPPw+mFhtPoyrNQ1ixd+MVh3NWduw@mail.gmail.com>

Hello,

I would like to report that I found a mistake in the document of
"help(set)".

In the document all the __i*__ methods are described exactly like the same
methods without i before the name.

Copied from the document:
__ixor__(...)

x.__ixor__(y) <==> x^y


__xor__(...)

x.__xor__(y) <==> x^y


I suppose that the __ixor__ would mean x^=y and not x^y like the __xor__ method
right?

This problem also occurs for:
__iand__
__ior__
__isub__

Best regards,
Joao Carneiro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111010/75a7da49/attachment.html>

From jonathan.blakes at gmail.com  Tue Oct 11 23:07:53 2011
From: jonathan.blakes at gmail.com (Jonathan Blakes)
Date: Tue, 11 Oct 2011 22:07:53 +0100
Subject: [docs] reverse/backwards quotes now displaying correctly
Message-ID: <CAEFwTqAbU5j3PjnLhrawQ92-AsOm9g0Th55URtyY97KLr1wGHQ@mail.gmail.com>

Hello,

I think that the "reverse (a.k.a) backwards quotes" in
http://docs.python.org/reference/expressions.html#string-conversions are not
displaying correctly.

My browser is Google Chrome 16.0.899.0 dev on Ubuntu Natty 64-bit.

Cheers,

Jon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111011/a687a16d/attachment.html>

From thudfoo at gmail.com  Tue Oct 11 18:19:51 2011
From: thudfoo at gmail.com (xDog Walker)
Date: Tue, 11 Oct 2011 09:19:51 -0700
Subject: [docs] windows help file (.chm) for Python 2.7
Message-ID: <201110110919.51634.thudfoo@gmail.com>

The file I downloaded yesterday (2011 October 10) is messed up: The index 
section is abnormal; it appears to be displaying the "target" rather than 
the "key". Anyway, that function of the chm file is worthless here. (I have 
many other chm files that do not exhibit this behavior and no others that 
do.)

-- 
I have seen the future and I am not in it.


From sandro.tosi at gmail.com  Wed Oct 12 09:05:35 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Wed, 12 Oct 2011 09:05:35 +0200
Subject: [docs] Hard Copy Documentation
In-Reply-To: <SNT110-W1F86E5C2221FA3913A481EAFC0@phx.gbl>
References: <SNT110-W1F86E5C2221FA3913A481EAFC0@phx.gbl>
Message-ID: <CAPdtAj0NWaQ-_S-4MYf2riOV8Hvz-vXnm2cJdXt9kKP6vSOW_w@mail.gmail.com>

Hello John,
this mailing list is to fix bugs/propose enhancement to the python
documentation, but your question is not so off-topic :)

On Sun, Oct 9, 2011 at 17:41, John Rowland <astrojohn at hotmail.co.uk> wrote:
> Hi Guys,
>
> >From where can I obtain hard copy documentation - preferably in the form of
> proper books - on all aspects of Python?
>
> I have already bought the book Natural Language Processing with Python, and
> whilst this is useful, it is not a reference manual. What I need is a book
> with all the commands, statements, expressions etc. listed (ideally
> alphabetically) along with their syntax.
>
> I'm the sort of guy that starting from and given the ">>>" prompt, want to
> know what my options are in response to this. I also need more explanation
> on all sorts of things. As an example, "Import". What does this actually do?
> What does import really mean? Where is the imported item stored? What
> happens if I import when I've already imported? That sort of thing.

I looked quickly on the python.org website and end-up on this wiki
page: http://wiki.python.org/moin/PythonBooks . It seems like a good
starting point, hope  you'll find what you're looking for.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From eliben at gmail.com  Wed Oct 12 16:12:17 2011
From: eliben at gmail.com (Eli Bendersky)
Date: Wed, 12 Oct 2011 16:12:17 +0200
Subject: [docs] I found a question in the documentation.
In-Reply-To: <CA+P=fnyrUhqdKFfpo_jtZeJVgCrXa3K0MyW54xmsKcMoWa=GMQ@mail.gmail.com>
References: <CA+P=fnyrUhqdKFfpo_jtZeJVgCrXa3K0MyW54xmsKcMoWa=GMQ@mail.gmail.com>
Message-ID: <CAF-Rda-gC5KNS5WU9aQ8oayr3e2q6Etxs+uXDiK3tJ7SQhzabg@mail.gmail.com>

On Wed, Oct 12, 2011 at 08:27, Ray Wang <bluefca at gmail.com> wrote:
> In the chapter of "3.1.2 String", the example:
>
>>>> '"Isn\'t," she said.'
> '"Isn\'t," she said.'
>
> Should the printed result be
> '"Isn't," she said.'
> ?

No, because it shows what the interactive session displays, which is
the "repr" of the string. Had you actually printed it, you would get
the result you expect.

Eli

From report at bugs.python.org  Wed Oct 12 18:21:41 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 12 Oct 2011 16:21:41 +0000
Subject: [docs] [issue12602] Missing cross-references in Doc/using
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1318436500.9.0.724476267112.issue12602@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

> I suggest that it do so in this instance also, using *script* (in
> bold-faced italic) as the entry title.

What do you think about :file:`{script}`?  file+{} is what Sphinx uses for filenames with replaceable parts, which map to the HTML var element, which the stylesheets display as italics.

----------

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

From report at bugs.python.org  Wed Oct 12 18:22:23 2011
From: report at bugs.python.org (Eli Bendersky)
Date: Wed, 12 Oct 2011 16:22:23 +0000
Subject: [docs] [issue13161] problems with help() documentation of __i*__
	operators
Message-ID: <1318436543.45.0.46958950416.issue13161@psf.upfronthosting.co.za>


New submission from Eli Bendersky <eliben at gmail.com>:

Report from Joao Carneiro in the docs@ maillist:

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

I would like to report that I found a mistake in the document of "help(set)".

In the document all the __i*__ methods are described exactly like the same methods without i before the name.

Copied from the document:
__ixor__(...)

    x.__ixor__(y) <==> x^y


__xor__(...)

    x.__xor__(y) <==> x^y


I suppose that the __ixor__ would mean x^=y and not x^y like the __xor__ method right?

This problem also occurs for:
__iand__
__ior__
__isub__

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

The report is on Python 3.2, but the problem also exists in 2.7

It appears that the problem's source is in Objects/typeobject.c, where the __i*__ operators are defined with the IBSLOT macro. The documentation string is the operator, passed to IBSLOT - for __ixor__ it's "^", while it should probably be "^="

----------
assignee: docs at python
components: Documentation
messages: 145411
nosy: docs at python, eli.bendersky
priority: normal
severity: normal
status: open
title: problems with help() documentation of __i*__ operators
versions: Python 2.7, Python 3.2, Python 3.3

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

From eliben at gmail.com  Wed Oct 12 18:23:02 2011
From: eliben at gmail.com (Eli Bendersky)
Date: Wed, 12 Oct 2011 18:23:02 +0200
Subject: [docs] Mistake in the Python 3.2.2rc1 "help(set)"
In-Reply-To: <CAOcxvsMwSSOjtpTpx3=BbxPPw+mFhtPoyrNQ1ixd+MVh3NWduw@mail.gmail.com>
References: <CAOcxvsMwSSOjtpTpx3=BbxPPw+mFhtPoyrNQ1ixd+MVh3NWduw@mail.gmail.com>
Message-ID: <CAF-Rda_-RvPog85qFrEOkWdLjVd7a6zX5R=iQA4fMktd5_c_Uw@mail.gmail.com>

Joao,

Thanks for the report. I have opened issue
http://bugs.python.org/issue13161 to track this problem, with some
initial analysis.

Eli


On Mon, Oct 10, 2011 at 16:10, Joao Carneiro <joao.flavio at gmail.com> wrote:
> Hello,
> I would like to report that I found a mistake in the document of
> "help(set)".
> In the document all the __i*__ methods are described exactly like the same
> methods without i before the name.
> Copied from the document:
> __ixor__(...)
>
> x.__ixor__(y) <==> x^y
>
> __xor__(...)
>
> x.__xor__(y) <==> x^y
>
> I suppose that the __ixor__ would mean x^=y and not x^y like the __xor__
> method right?
> This problem also occurs for:
> __iand__
> __ior__
> __isub__
> Best regards,
> Joao Carneiro
> _______________________________________________
> docs mailing list
> docs at python.org
> http://mail.python.org/mailman/listinfo/docs
>
>

From report at bugs.python.org  Wed Oct 12 18:44:38 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 12 Oct 2011 16:44:38 +0000
Subject: [docs] [issue12602] Missing cross-references in Doc/using
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1318437878.33.0.064881556399.issue12602@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

The italics parts are easier to recognize when they are within regular text (e.g. :file:`path/with/python{XY}/file`).  If the whole text is in italic people might not notice the difference.

----------

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

From joseph.2011 at reagle.org  Wed Oct 12 20:37:06 2011
From: joseph.2011 at reagle.org (Joseph Reagle)
Date: Wed, 12 Oct 2011 14:37:06 -0400
Subject: [docs] typo in argparse docs
Message-ID: <201110121437.07146.joseph.2011@reagle.org>


"So, a single positional argument with dest='bar' will that argument will be referred to as bar."

"So, a single positional argument with dest='bar' WITH that argument will be referred to as bar."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111012/60b4dc55/attachment.html>

From report at bugs.python.org  Wed Oct 12 22:18:21 2011
From: report at bugs.python.org (Terry J. Reedy)
Date: Wed, 12 Oct 2011 20:18:21 +0000
Subject: [docs] [issue12602] Missing cross-references in Doc/using
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1318450701.28.0.294207113227.issue12602@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

Since *script* is a file -- that is all variable -- that seems appropriate. 

Bold italic tends to be more notably different from bold italic than the normal pair. In any case, italic is the doc standard for function parameter names. It seems more sensible than introducing a unique occurrence of angle brackets. An alternative is to simply delete the angle brackets. 

If we consistently applied the "italicize non-literal symbolic parameter names" rule to command line examples, we would italicize 'command', 'module-name', 'script', and 'args' in

python [-BdEiOQsStuUvVWxX3?] [-c command | -m module-name | script | - ] [args]

just like in function signatures. I actually would like that as it would similarly diffentiate them from the literal constants meant to be entered as written. Has that ever been discussed by the doc group?

----------

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

From report at bugs.python.org  Wed Oct 12 22:42:20 2011
From: report at bugs.python.org (Mike Hoy)
Date: Wed, 12 Oct 2011 20:42:20 +0000
Subject: [docs] [issue13154] pep-0000.txt doesn't build anymore
In-Reply-To: <1318370108.79.0.613915208631.issue13154@psf.upfronthosting.co.za>
Message-ID: <1318452140.43.0.682989646914.issue13154@psf.upfronthosting.co.za>


Changes by Mike Hoy <mhoy09 at gmail.com>:


----------
nosy: +mikehoy

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

From eliben at gmail.com  Wed Oct 12 22:58:26 2011
From: eliben at gmail.com (Eli Bendersky)
Date: Wed, 12 Oct 2011 22:58:26 +0200
Subject: [docs] typo in argparse docs
In-Reply-To: <201110121437.07146.joseph.2011@reagle.org>
References: <201110121437.07146.joseph.2011@reagle.org>
Message-ID: <CAF-Rda8jtZ7vbXPdDU4EKHhaco+8+=YL8HFPv8tP2sHa7zWYHA@mail.gmail.com>

On Wed, Oct 12, 2011 at 20:37, Joseph Reagle <joseph.2011 at reagle.org> wrote:
>
>
> "So, a single positional argument with dest='bar' will that argument will be
> referred to as bar."
>
>
>
> "So, a single positional argument with dest='bar' WITH that argument will be
> referred to as bar."
>

I agree the original sentence makes little sense. But I'm not sure
your correction fully fixes it either - "a single positional argument
... with that argument" doesn't sound right.

Perhaps it should just say:

"So, a single positional argument with dest='bar' will be referred to as bar" ?

Eli

From report at bugs.python.org  Wed Oct 12 23:10:17 2011
From: report at bugs.python.org (Mike Hoy)
Date: Wed, 12 Oct 2011 21:10:17 +0000
Subject: [docs] [issue13154] pep-0000.txt doesn't build anymore
In-Reply-To: <1318370108.79.0.613915208631.issue13154@psf.upfronthosting.co.za>
Message-ID: <1318453817.1.0.183738267313.issue13154@psf.upfronthosting.co.za>


Mike Hoy <mhoy09 at gmail.com> added the comment:

:~/peps$ find . -name "*.txt" | xargs grep "canterbury"
./pep-3152.txt:Author: Gregory Ewing <greg.ewing at canterbury.ac.nz>
./pep-0380.txt:Author: Gregory Ewing <greg.ewing at canterbury.ac.nz>
./pep-0284.txt:    Greg Ewing <greg.ewing at canterbury.ac.nz>
./pep-0335.txt:Author: Gregory Ewing <greg at cosc.canterbury.ac.nz>

Looks like pep-0335.txt has a "Gregory Ewing" with a different email address (greg at cosc.canterbury.ac.nz) that is normally associated with "Gregory Ewing" (greg.ewing at canterbury.ac.nz).

Which is an error according to:

pep0/output.py:

    if too_many_emails:
        err_output = []
        for author, emails in too_many_emails:
            err_output.append("    %s: %r" % (author, emails))
        raise ValueError("some authors have more than one email address "
                         "listed:\n" + '\n'.join(err_output))

----------

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

From report at bugs.python.org  Thu Oct 13 02:03:04 2011
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 13 Oct 2011 00:03:04 +0000
Subject: [docs] [issue13154] pep-0000.txt doesn't build anymore
In-Reply-To: <1318370108.79.0.613915208631.issue13154@psf.upfronthosting.co.za>
Message-ID: <1318464184.15.0.441483444502.issue13154@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Oct 13 02:04:15 2011
From: report at bugs.python.org (Senthil Kumaran)
Date: Thu, 13 Oct 2011 00:04:15 +0000
Subject: [docs] [issue13154] pep-0000.txt doesn't build anymore
In-Reply-To: <1318370108.79.0.613915208631.issue13154@psf.upfronthosting.co.za>
Message-ID: <1318464255.34.0.253110920165.issue13154@psf.upfronthosting.co.za>


Senthil Kumaran <senthil at uthcode.com> added the comment:

Fixed in 25ff1adf5f30

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

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

From mike at saguaroscuba.com  Thu Oct 13 20:33:19 2011
From: mike at saguaroscuba.com (Mike Hoy)
Date: Thu, 13 Oct 2011 11:33:19 -0700
Subject: [docs] typo in argparse docs
In-Reply-To: <CAF-Rda8jtZ7vbXPdDU4EKHhaco+8+=YL8HFPv8tP2sHa7zWYHA@mail.gmail.com>
References: <201110121437.07146.joseph.2011@reagle.org>
	<CAF-Rda8jtZ7vbXPdDU4EKHhaco+8+=YL8HFPv8tP2sHa7zWYHA@mail.gmail.com>
Message-ID: <4E972EEF.4070603@saguaroscuba.com>

On 10/12/2011 01:58 PM, Eli Bendersky wrote:
>> "So, a single positional argument with dest='bar' will that argument will be
>> >  referred to as bar."
>> >
>> >
>> >
>> >  "So, a single positional argument with dest='bar' WITH that argument will be
>> >  referred to as bar."
>> >
> I agree the original sentence makes little sense. But I'm not sure
> your correction fully fixes it either - "a single positional argument
> ... with that argument" doesn't sound right.
>
> Perhaps it should just say:
>
> "So, a single positional argument with dest='bar' will be referred to as bar" ?
>
> Eli
I didn't see this on the tracker. I open a bug report if no one is going 
to do it.

From report at bugs.python.org  Fri Oct 14 10:05:08 2011
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 14 Oct 2011 08:05:08 +0000
Subject: [docs] [issue13176] Broken link in bugs.rst
Message-ID: <1318579508.22.0.235286137503.issue13176@psf.upfronthosting.co.za>


New submission from Berker Peksag <berker.peksag at gmail.com>:

http://www.python.org/dev/workflow/ is missing in 3.2 documentation.

See: http://docs.python.org/py3k/bugs.html

It works with latest version of the documentation: http://docs.python.org/dev/bugs.html

----------
assignee: docs at python
components: Documentation
files: broken_link_v1.patch
keywords: patch
messages: 145499
nosy: berkerpeksag, docs at python
priority: normal
severity: normal
status: open
title: Broken link in bugs.rst
versions: Python 3.2
Added file: http://bugs.python.org/file23402/broken_link_v1.patch

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

From report at bugs.python.org  Fri Oct 14 16:26:05 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 14 Oct 2011 14:26:05 +0000
Subject: [docs] [issue12602] Missing cross-references in Doc/using
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1318602365.19.0.708182429039.issue12602@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Attached path adds these links:
> Missing incoming:
> - from "Invoking the Interpreter" in the tutorial
> - direct link from runpy.run_module to -m switch

> Missing outgoing:
> - direct link from <script> to runpy.run_path

I couldn?t add this one:
> - direct link from runpy.run_path to <script>
I tried adding a standard reST link target (.. _using-on-script:) but that didn?t seem to work with the describe item.  I added a link to the nearest heading instead, but maybe it is after all redundant: the seealso section of library/runpy already points to using/cmdline.

----------
keywords: +patch
Added file: http://bugs.python.org/file23405/using-links.diff

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

From report at bugs.python.org  Fri Oct 14 16:30:08 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 14 Oct 2011 14:30:08 +0000
Subject: [docs] [issue12602] Missing cross-references in Doc/using
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1318602608.07.0.262513463295.issue12602@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

[Terry]
> It may suggest a meta-issue though - perhaps 'Documenting Python'
> should grow a devguide-style description of the Docs layout in source
> control

I would just describe the layout of the Doc subtree in the same devguide page.  Care to open another bug for that?

> If we consistently applied the "italicize non-literal symbolic parameter names"
> rule to command line examples, we would italicize 'command', 'module-name',
> 'script', and 'args' in
> 
> python [-BdEiOQsStuUvVWxX3?] [-c command | -m module-name | script | - ] [args]
> 
> just like in function signatures. I actually would like that as it would
> similarly diffentiate them from the literal constants meant to be entered as
> written. Has that ever been discussed by the doc group?

Not that I recall.  Currently the ?python [-Bd etc.]? line is currently a code block, and as such cannot gain inline markup (:file:), but this is not insurmountable.

----------

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

From report at bugs.python.org  Fri Oct 14 16:52:55 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 14 Oct 2011 14:52:55 +0000
Subject: [docs] [issue12602] Missing cross-references in Doc/using
In-Reply-To: <1311249393.53.0.190511112739.issue12602@psf.upfronthosting.co.za>
Message-ID: <1318603975.08.0.876694820064.issue12602@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

BTW, I?ve done nothing about #1739468 because I don?t see why you wanted to add a link.

----------

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

From report at bugs.python.org  Fri Oct 14 17:33:40 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 14 Oct 2011 15:33:40 +0000
Subject: [docs] [issue13176] Broken link in bugs.rst
In-Reply-To: <1318579508.22.0.235286137503.issue13176@psf.upfronthosting.co.za>
Message-ID: <1318606420.63.0.369797778555.issue13176@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
assignee: docs at python -> eric.araujo
nosy: +eric.araujo

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

From report at bugs.python.org  Fri Oct 14 17:38:50 2011
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 14 Oct 2011 15:38:50 +0000
Subject: [docs] [issue13176] Broken link in bugs.rst
In-Reply-To: <1318579508.22.0.235286137503.issue13176@psf.upfronthosting.co.za>
Message-ID: <E1REjqS-0003d4-GS@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 9ef20fbd340f by ?ric Araujo in branch '3.2':
Update dead references from py.org/dev/faq to the devguide (#13176)
http://hg.python.org/cpython/rev/9ef20fbd340f

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

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

From report at bugs.python.org  Fri Oct 14 17:47:57 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 14 Oct 2011 15:47:57 +0000
Subject: [docs] [issue13176] Broken link in bugs.rst
In-Reply-To: <1318579508.22.0.235286137503.issue13176@psf.upfronthosting.co.za>
Message-ID: <1318607276.95.0.724025303042.issue13176@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Thanks for the report!

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

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

From report at bugs.python.org  Fri Oct 14 18:06:07 2011
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 14 Oct 2011 16:06:07 +0000
Subject: [docs] [issue13176] Broken link in bugs.rst
In-Reply-To: <1318579508.22.0.235286137503.issue13176@psf.upfronthosting.co.za>
Message-ID: <E1REkGr-00069f-Hy@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset ebf3f2a4c61a by ?ric Araujo in branch '2.7':
Update dead references from py.org/dev/faq to the devguide (#13176)
http://hg.python.org/cpython/rev/ebf3f2a4c61a

----------

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

From lhorn003 at woh.rr.com  Thu Oct 13 01:15:59 2011
From: lhorn003 at woh.rr.com (Larry Horn)
Date: Wed, 12 Oct 2011 19:15:59 -0400
Subject: [docs] Subprocess Starup Error
Message-ID: <8F693A3A31F74FB1AAFF6E781A1C4E1F@PC127417878215>

I am running 2.7.2 on a Windows XP machine. Python worked fine for a week, but then developed this problem. When ever I start python a get the error message:   --IDLE's subprocess didn't make connection. Either IDLE can't start a subprocess or firewall software is blocking the connection. There must be some fix for this problem. Please let me know.

Thanks,
    Larry Horn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111012/296c07eb/attachment-0001.html>

From josh at servercobra.com  Thu Oct 13 22:50:22 2011
From: josh at servercobra.com (Josh Gachnang)
Date: Thu, 13 Oct 2011 15:50:22 -0500
Subject: [docs] Dead Link in Documentation
Message-ID: <CAOrc4CzTYjPU+K+atuGKuMvKG_VQpO85MERKDJ0=2+c4TQm=gQ@mail.gmail.com>

The link to DiveIntoPython.org in
http://docs.python.org/using/windows.html (and
probably a few other pages) is permanently down. Mark Pilgrim took down all
his sites recently, so a bunch of people have mirrored his sites. I set up a
mirror at www.DiveIntoPython.net. It doesn't have all the translations yet,
but neither do any of the other mirrors I'm seeing. I'm working to scrape
those from the Google cache and the WayBack machine and get them up ASAP.

Thanks!
---
Josh Gachnang

Tech Blog: ServerCobra.com, @ServerCobra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111013/0050f9cf/attachment.html>

From report at bugs.python.org  Sat Oct 15 00:27:25 2011
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 14 Oct 2011 22:27:25 +0000
Subject: [docs] [issue13127] xml.dom.Attr.name is not labeled as read-only
In-Reply-To: <1318047492.07.0.217686953928.issue13127@psf.upfronthosting.co.za>
Message-ID: <1318631245.46.0.631483950995.issue13127@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

The docs are unchanged in 3.2. I presume the behavior is also.

----------
nosy: +terry.reedy
versions: +Python 3.2, Python 3.3

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

From report at bugs.python.org  Sat Oct 15 01:40:41 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 14 Oct 2011 23:40:41 +0000
Subject: [docs] [issue13144] Global Module Index link in the offline
	documentation is	incorrect
In-Reply-To: <1318248968.6.0.0439422849007.issue13144@psf.upfronthosting.co.za>
Message-ID: <1318635641.94.0.661215094004.issue13144@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti
versions:  -Python 2.6

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

From report at bugs.python.org  Sat Oct 15 02:43:19 2011
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 15 Oct 2011 00:43:19 +0000
Subject: [docs] [issue13171] Bug in file.read(), can access unknown data.
In-Reply-To: <1318531210.93.0.392401137226.issue13171@psf.upfronthosting.co.za>
Message-ID: <1318639399.69.0.124076706868.issue13171@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

This issue has come up enough (tracker and python-list) that I think adding a mild adaptation of the C standard paragraph might be a good idea. Changing to a doc issue.

----------
assignee:  -> docs at python
components: +Documentation -IO, Library (Lib), Windows
nosy: +docs at python, terry.reedy

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

From report at bugs.python.org  Sat Oct 15 16:31:29 2011
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 15 Oct 2011 14:31:29 +0000
Subject: [docs] [issue13139] multiprocessing.map skips finally blocks
In-Reply-To: <1318125947.15.0.13973515193.issue13139@psf.upfronthosting.co.za>
Message-ID: <1318689089.73.0.125572241768.issue13139@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

As mentioned in http://docs.python.org/dev/library/multiprocessing#multiprocessing.pool.AsyncResult.get
?If the remote call raised an exception then that exception will be reraised by get().?

map() is just map_async() followed by a get() call on the result.
Also, worker processes are called in daemon mode, which explains that children get killed as soon as the parent exits.

If you rephrase your example as:

try:
    Pool(3).map(Process, ['1','2','3'])
finally:
    sleep(1)

then all the children's finally clauses get a chance to be executed before the parent exits.

I would therefore call it "not a bug", although you might add a sentence in the map() documentation stating that an exception is raised as soon as one of the worker fails.

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

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

From report at bugs.python.org  Sat Oct 15 20:52:05 2011
From: report at bugs.python.org (Jesse Noller)
Date: Sat, 15 Oct 2011 18:52:05 +0000
Subject: [docs] [issue13139] multiprocessing.map skips finally blocks
In-Reply-To: <1318125947.15.0.13973515193.issue13139@psf.upfronthosting.co.za>
Message-ID: <1318704725.79.0.365613884786.issue13139@psf.upfronthosting.co.za>


Jesse Noller <jnoller at gmail.com> added the comment:

Antoine is correct, as he usually is. This is more of a documentation issue than bug.

----------

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

From report at bugs.python.org  Sun Oct 16 22:09:04 2011
From: report at bugs.python.org (Mike Hoy)
Date: Sun, 16 Oct 2011 20:09:04 +0000
Subject: [docs] [issue13191] Typo in argparse documentation
Message-ID: <1318795744.19.0.406202573511.issue13191@psf.upfronthosting.co.za>


New submission from Mike Hoy <mhoy09 at gmail.com>:

In the Docs mailing list a typo was pointed out in argparse docs.

http://docs.python.org/dev/library/argparse.html#metavar

> "So, a single positional argument with dest='bar' will that argument 
> will be referred to as bar."

> "So, a single positional argument with dest='bar' WITH that argument 
> will be referred to as bar."

Eli Bendersky:

> I agree the original sentence makes little sense. But I'm not sure
> your correction fully fixes it either - "a single positional argument
> ... with that argument" doesn't sound right.

> Perhaps it should just say:

> "So, a single positional argument with dest='bar' will be referred to  > as bar" ?

Patch says "So,a single positional argument with dest='bar' will be referred to as bar"

----------
assignee: docs at python
components: Documentation
files: typo-argparse.diff
keywords: patch
messages: 145636
nosy: docs at python, mikehoy
priority: normal
severity: normal
status: open
title: Typo in argparse documentation
Added file: http://bugs.python.org/file23420/typo-argparse.diff

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

From report at bugs.python.org  Sun Oct 16 23:34:17 2011
From: report at bugs.python.org (Mike Hoy)
Date: Sun, 16 Oct 2011 21:34:17 +0000
Subject: [docs] [issue11776] types.MethodType() params and usage is not
	documented
In-Reply-To: <1302036805.33.0.506634428921.issue11776@psf.upfronthosting.co.za>
Message-ID: <1318800857.72.0.738672035507.issue11776@psf.upfronthosting.co.za>


Changes by Mike Hoy <mhoy09 at gmail.com>:


----------
nosy: +mikehoy

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

From report at bugs.python.org  Mon Oct 17 07:44:42 2011
From: report at bugs.python.org (Eli Bendersky)
Date: Mon, 17 Oct 2011 05:44:42 +0000
Subject: [docs] [issue13191] Typo in argparse documentation
In-Reply-To: <1318795744.19.0.406202573511.issue13191@psf.upfronthosting.co.za>
Message-ID: <1318830282.71.0.302403557882.issue13191@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/issue13191>
_______________________________________

From report at bugs.python.org  Mon Oct 17 13:21:33 2011
From: report at bugs.python.org (anatoly techtonik)
Date: Mon, 17 Oct 2011 11:21:33 +0000
Subject: [docs] [issue13195] subprocess: args with shell=True is not
	documented on	Windows
Message-ID: <1318850493.84.0.375275631996.issue13195@psf.upfronthosting.co.za>


New submission from anatoly techtonik <techtonik at gmail.com>:

For UNIX, it is said that if shell=False then you need to pass `args` as a list (if you want to pass any parameters to executable). Is that true for Windows (and perhaps other platforms) as well?

Again, for UNIX it is said that with shell=True, and args is a list - every item except the first one is an argument to the shell itself. Is it the same on Windows?


It would be better to just give advice in `shell` parameter description to "pass args as a list with shell=False or else you'll lose params in Unix. If shell=True you need to pass args as a string, because list is needed only if you need to pass arguments to shell itself."

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 145662
nosy: docs at python, techtonik
priority: normal
severity: normal
status: open
title: subprocess: args with shell=True is not documented on Windows

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

From report at bugs.python.org  Mon Oct 17 13:24:20 2011
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 17 Oct 2011 11:24:20 +0000
Subject: [docs] [issue13195] subprocess: args with shell=True is not
	documented on	Windows
In-Reply-To: <1318850493.84.0.375275631996.issue13195@psf.upfronthosting.co.za>
Message-ID: <1318850660.85.0.288673336677.issue13195@psf.upfronthosting.co.za>


STINNER Victor <victor.stinner at haypocalc.com> added the comment:

See also issues #7839, #8972 and #10197.

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

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

From report at bugs.python.org  Mon Oct 17 13:27:21 2011
From: report at bugs.python.org (anatoly techtonik)
Date: Mon, 17 Oct 2011 11:27:21 +0000
Subject: [docs] [issue13196] subprocess: undocumented if shell=True is
	necessary to	find executable in Windows PATH
Message-ID: <1318850841.68.0.83326141038.issue13196@psf.upfronthosting.co.za>


New submission from anatoly techtonik <techtonik at gmail.com>:

The reason I ask is this changeset - http://code.google.com/p/spyderlib/source/detail?spec=svne5d86b685619a470d593aa5f9ee360ba60779bc1&r=323c6c697f045166e384cdc15803d40eebed0a2b - seems like without shell=True, subprocess.Popen is unable to find Mercurial executable in PATH.

----------
assignee: docs at python
components: Documentation
messages: 145664
nosy: docs at python, techtonik
priority: normal
severity: normal
status: open
title: subprocess: undocumented if shell=True is necessary to find executable in Windows PATH

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

From report at bugs.python.org  Mon Oct 17 13:30:51 2011
From: report at bugs.python.org (anatoly techtonik)
Date: Mon, 17 Oct 2011 11:30:51 +0000
Subject: [docs] [issue13196] subprocess: undocumented if shell=True is
	necessary to	find executable in Windows PATH
In-Reply-To: <1318850841.68.0.83326141038.issue13196@psf.upfronthosting.co.za>
Message-ID: <1318851051.44.0.886757953068.issue13196@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Tracker is buggy - proper link to the changeset - http://bit.ly/qT1o4g

----------

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

From report at bugs.python.org  Mon Oct 17 13:32:17 2011
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 17 Oct 2011 11:32:17 +0000
Subject: [docs] [issue13196] subprocess: undocumented if shell=True is
	necessary to	find executable in Windows PATH
In-Reply-To: <1318850841.68.0.83326141038.issue13196@psf.upfronthosting.co.za>
Message-ID: <1318851137.59.0.458213447072.issue13196@psf.upfronthosting.co.za>


STINNER Victor <victor.stinner at haypocalc.com> added the comment:

Can't you merge this issue with #13195?

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

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

From report at bugs.python.org  Mon Oct 17 13:48:18 2011
From: report at bugs.python.org (anatoly techtonik)
Date: Mon, 17 Oct 2011 11:48:18 +0000
Subject: [docs] [issue13195] subprocess: args with shell=True is not
	documented on	Windows
In-Reply-To: <1318850493.84.0.375275631996.issue13195@psf.upfronthosting.co.za>
Message-ID: <1318852098.08.0.171098744753.issue13195@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Looks like a can of worms. For now I'll be pretty fine if this stuff is at least properly documented.

----------

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

From report at bugs.python.org  Mon Oct 17 13:50:11 2011
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 17 Oct 2011 11:50:11 +0000
Subject: [docs] [issue13195] subprocess: args with shell=True is not
	documented on	Windows
In-Reply-To: <1318850493.84.0.375275631996.issue13195@psf.upfronthosting.co.za>
Message-ID: <1318852210.99.0.414423218673.issue13195@psf.upfronthosting.co.za>


STINNER Victor <victor.stinner at haypocalc.com> added the comment:

> For now I'll be pretty fine if this stuff is at least
> properly documented.

Can you propose a document patch describing the current behaviour?

----------

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

From report at bugs.python.org  Mon Oct 17 13:50:46 2011
From: report at bugs.python.org (anatoly techtonik)
Date: Mon, 17 Oct 2011 11:50:46 +0000
Subject: [docs] [issue13196] subprocess: undocumented if shell=True is
	necessary to	find executable in Windows PATH
In-Reply-To: <1318850841.68.0.83326141038.issue13196@psf.upfronthosting.co.za>
Message-ID: <1318852246.65.0.0134890582917.issue13196@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Although they both touch the same components, they are completely different user stories.

----------

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

From report at bugs.python.org  Mon Oct 17 14:01:58 2011
From: report at bugs.python.org (anatoly techtonik)
Date: Mon, 17 Oct 2011 12:01:58 +0000
Subject: [docs] [issue13195] subprocess: args with shell=True is not
	documented on	Windows
In-Reply-To: <1318850493.84.0.375275631996.issue13195@psf.upfronthosting.co.za>
Message-ID: <1318852918.89.0.395085149566.issue13195@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Certainly not right now as I don't have development environment setup. Perhaps in a few days if somebody pings me. It could be a lot easier with online editor, of course - http://code.google.com/p/pydotorg/issues/detail?id=6

----------

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

From report at bugs.python.org  Mon Oct 17 14:12:15 2011
From: report at bugs.python.org (Ross Lagerwall)
Date: Mon, 17 Oct 2011 12:12:15 +0000
Subject: [docs] [issue13195] subprocess: args with shell=True is not
	documented on	Windows
In-Reply-To: <1318850493.84.0.375275631996.issue13195@psf.upfronthosting.co.za>
Message-ID: <1318853535.08.0.559470790737.issue13195@psf.upfronthosting.co.za>


Changes by Ross Lagerwall <rosslagerwall at gmail.com>:


----------
nosy: +rosslagerwall

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

From report at bugs.python.org  Mon Oct 17 14:12:30 2011
From: report at bugs.python.org (Ross Lagerwall)
Date: Mon, 17 Oct 2011 12:12:30 +0000
Subject: [docs] [issue13196] subprocess: undocumented if shell=True is
	necessary to	find executable in Windows PATH
In-Reply-To: <1318850841.68.0.83326141038.issue13196@psf.upfronthosting.co.za>
Message-ID: <1318853550.96.0.0142732714488.issue13196@psf.upfronthosting.co.za>


Changes by Ross Lagerwall <rosslagerwall at gmail.com>:


----------
nosy: +rosslagerwall

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

From report at bugs.python.org  Mon Oct 17 14:24:23 2011
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 17 Oct 2011 12:24:23 +0000
Subject: [docs] [issue13195] subprocess: args with shell=True is not
	documented on	Windows
In-Reply-To: <1318850493.84.0.375275631996.issue13195@psf.upfronthosting.co.za>
Message-ID: <1318854263.1.0.735170960455.issue13195@psf.upfronthosting.co.za>


STINNER Victor <victor.stinner at haypocalc.com> added the comment:

> Certainly not right now as I don't have development environment setup

See our development guide to get such environment:
http://docs.python.org/devguide/setup.html

> It could be a lot easier with online editor

Would like like to work on this project? (provide an online editor)

----------

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

From report at bugs.python.org  Mon Oct 17 16:00:59 2011
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Mon, 17 Oct 2011 14:00:59 +0000
Subject: [docs] [issue13195] subprocess: args with shell=True is not
	documented on	Windows
In-Reply-To: <1318850493.84.0.375275631996.issue13195@psf.upfronthosting.co.za>
Message-ID: <1318860059.62.0.32431981517.issue13195@psf.upfronthosting.co.za>


Changes by Arfrever Frehtes Taifersar Arahesis <Arfrever.FTA at GMail.Com>:


----------
nosy: +Arfrever

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

From report at bugs.python.org  Mon Oct 17 16:01:18 2011
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Mon, 17 Oct 2011 14:01:18 +0000
Subject: [docs] [issue13196] subprocess: undocumented if shell=True is
	necessary to	find executable in Windows PATH
In-Reply-To: <1318850841.68.0.83326141038.issue13196@psf.upfronthosting.co.za>
Message-ID: <1318860078.21.0.544637913042.issue13196@psf.upfronthosting.co.za>


Changes by Arfrever Frehtes Taifersar Arahesis <Arfrever.FTA at GMail.Com>:


----------
nosy: +Arfrever

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

From report at bugs.python.org  Mon Oct 17 17:43:35 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 17 Oct 2011 15:43:35 +0000
Subject: [docs] [issue13191] Typo in argparse documentation
In-Reply-To: <1318795744.19.0.406202573511.issue13191@psf.upfronthosting.co.za>
Message-ID: <1318866215.38.0.514980715481.issue13191@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
nosy: +bethard
versions: +Python 2.7, Python 3.2, Python 3.3

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

From report at bugs.python.org  Mon Oct 17 17:58:40 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 17 Oct 2011 15:58:40 +0000
Subject: [docs] [issue13144] Global Module Index link in the offline
	documentation is	incorrect
In-Reply-To: <1318248968.6.0.0439422849007.issue13144@psf.upfronthosting.co.za>
Message-ID: <1318867120.9.0.40382907421.issue13144@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Can you clone the repository, build the doc with ?make html? as explained in http://docs.python.org/documenting/building and tell us if the bug is there?  If not, it?s specific to Debian or Ubuntu.

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

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

From report at bugs.python.org  Mon Oct 17 18:22:46 2011
From: report at bugs.python.org (anatoly techtonik)
Date: Mon, 17 Oct 2011 16:22:46 +0000
Subject: [docs] [issue13195] subprocess: args with shell=True is not
	documented on	Windows
In-Reply-To: <1318854263.1.0.735170960455.issue13195@psf.upfronthosting.co.za>
Message-ID: <CAPkN8xJOrfboM62NrSZ0st2UcfNsnCCFuATqmFz=fS_zO_8haA@mail.gmail.com>


anatoly techtonik <techtonik at gmail.com> added the comment:

On Mon, Oct 17, 2011 at 3:24 PM, STINNER Victor <report at bugs.python.org> wrote:
>
>> Certainly not right now as I don't have development environment setup
>
> See our development guide to get such environment:
> http://docs.python.org/devguide/setup.html

I know. There is better tool at
https://bitbucket.org/techtonik/devinabox but I have only 500Mb left
on my system drive and there are still more problems I need to handle.

>> It could be a lot easier with online editor
>
> Would like like to work on this project? (provide an online editor)

Do you mean would I like to work on it? Actually, I made a prototype
on AppEngine that waits for JS guru to tune CodeMirror interface. If
somebody is interested to help, I've just uploaded the code to
http://code.google.com/p/pydotorg/source/browse/?repo=doceditor

----------

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

From report at bugs.python.org  Mon Oct 17 19:50:35 2011
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 17 Oct 2011 17:50:35 +0000
Subject: [docs] [issue13203] Doc: say id() is only useful for existing
	objects
Message-ID: <1318873835.36.0.466865504792.issue13203@psf.upfronthosting.co.za>


New submission from Terry J. Reedy <tjreedy at udel.edu>:

Newbies too often do something like (3.2.2, )

>>> id(getattr(x, 'pop')) == id(x.pop)
True

and get confused by the (invalid) result, whereas

>>> a,b=getattr(x, 'pop'),x.pop
>>> id(a)==id(b)
False

works properly. I think we should add a sentence or two or three to the id() doc, such as

Since a newly created argument object is either destroyed or becomes inaccessible before the function returns, *id(obj)* is only useful and valid if *obj* exists prior to the call and therefore after its return.
The value of an expression such as *id(666)== id(667)* is arbitrary and meaningless. The id of the first int object might or might not be reused for the second one.

----------
assignee: docs at python
components: Documentation
messages: 145743
nosy: docs at python, terry.reedy
priority: normal
severity: normal
status: open
title: Doc: say id() is only useful for existing objects
versions: Python 2.7, Python 3.2, Python 3.3

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

From report at bugs.python.org  Mon Oct 17 20:36:17 2011
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 17 Oct 2011 18:36:17 +0000
Subject: [docs] [issue13203] Doc: say id() is only useful for existing
	objects
In-Reply-To: <1318873835.36.0.466865504792.issue13203@psf.upfronthosting.co.za>
Message-ID: <1318876577.62.0.553369339157.issue13203@psf.upfronthosting.co.za>


Georg Brandl <georg at python.org> added the comment:

If we add something at all, it should be much shorter. After all, the current doc already states "unique during its lifetime".

----------
nosy: +georg.brandl, rhettinger
priority: normal -> low

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

From report at bugs.python.org  Mon Oct 17 20:44:49 2011
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 17 Oct 2011 18:44:49 +0000
Subject: [docs] [issue13203] Doc: say id() is only useful for existing
	objects
In-Reply-To: <1318873835.36.0.466865504792.issue13203@psf.upfronthosting.co.za>
Message-ID: <1318877089.48.0.380690767494.issue13203@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

I gave a maximum addition. The first sentence may be enough (or even just the second half of it). What people do not get is that the lifetime of new arg objects is the duration of the function call -- and that the output of id for departed objects is uniquely useless and invalid.

----------

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

From report at bugs.python.org  Mon Oct 17 20:45:17 2011
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 17 Oct 2011 18:45:17 +0000
Subject: [docs] [issue13144] Global Module Index link in the offline
	documentation is	incorrect
In-Reply-To: <1318248968.6.0.0439422849007.issue13144@psf.upfronthosting.co.za>
Message-ID: <1318877117.03.0.596913719534.issue13144@psf.upfronthosting.co.za>


Georg Brandl <georg at python.org> added the comment:

2.x docs are supposed to be built with Sphinx 0.6.x -- there the link is correct.

If Ubuntu chooses to ignore this and build with 1.0.x, they will have to include a patch fixing the link.

----------
nosy: +georg.brandl
resolution:  -> invalid
status: open -> closed

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

From report at bugs.python.org  Tue Oct 18 01:50:06 2011
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 17 Oct 2011 23:50:06 +0000
Subject: [docs] [issue13203] Doc: say id() is only useful for existing
	objects
In-Reply-To: <1318873835.36.0.466865504792.issue13203@psf.upfronthosting.co.za>
Message-ID: <1318895406.18.0.0538633457055.issue13203@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

I think this is over-explaining an implementation detail and it makes the docs for id() harder to understand.

Possibly there can be a FAQ entry about identity but the id() function itself is no place to go into the quirks of when new objects are created or destroyed.

Also, "getting confused" is often a step in the learning process -- it can't be taken out entirely.

----------

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

From report at bugs.python.org  Tue Oct 18 01:55:24 2011
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 17 Oct 2011 23:55:24 +0000
Subject: [docs] [issue13203] Doc: say id() is only useful for existing
	objects
In-Reply-To: <1318873835.36.0.466865504792.issue13203@psf.upfronthosting.co.za>
Message-ID: <1318895724.6.0.458630067465.issue13203@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Oct 18 10:25:57 2011
From: report at bugs.python.org (Petri Lehtinen)
Date: Tue, 18 Oct 2011 08:25:57 +0000
Subject: [docs] [issue12174] Multiprocessing logging levels unclear
In-Reply-To: <1306324447.9.0.976036464224.issue12174@psf.upfronthosting.co.za>
Message-ID: <1318926357.56.0.330697503707.issue12174@psf.upfronthosting.co.za>


Petri Lehtinen <petri at digip.org> added the comment:

Should there be another issue opened to do something about the extra logging levels?

----------

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

From report at bugs.python.org  Tue Oct 18 10:32:11 2011
From: report at bugs.python.org (Petri Lehtinen)
Date: Tue, 18 Oct 2011 08:32:11 +0000
Subject: [docs] [issue12277] Missing comma in os.walk docs
In-Reply-To: <1307439951.32.0.810805209718.issue12277@psf.upfronthosting.co.za>
Message-ID: <1318926731.27.0.357242047922.issue12277@psf.upfronthosting.co.za>


Petri Lehtinen <petri at digip.org> added the comment:

?ric: It's been 3 months now. Have you already committed the big documentation issues change?

----------

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

From report at bugs.python.org  Tue Oct 18 10:48:20 2011
From: report at bugs.python.org (=?utf-8?q?Bo=C5=A1tjan_Mejak?=)
Date: Tue, 18 Oct 2011 08:48:20 +0000
Subject: [docs] [issue12277] Missing comma in os.walk docs
In-Reply-To: <1307439951.32.0.810805209718.issue12277@psf.upfronthosting.co.za>
Message-ID: <1318927700.2.0.994512381388.issue12277@psf.upfronthosting.co.za>


Bo?tjan Mejak <bostjan.mejak at gmail.com> added the comment:

Yes, Eric, please fix this already. :)

----------

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

From report at bugs.python.org  Tue Oct 18 12:02:25 2011
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 18 Oct 2011 10:02:25 +0000
Subject: [docs] [issue12277] Missing comma in os.walk docs
In-Reply-To: <1307439951.32.0.810805209718.issue12277@psf.upfronthosting.co.za>
Message-ID: <E1RG6V4-0008UR-4L@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset b41def1851b6 by Ezio Melotti in branch '3.2':
#12277: add missing comma.
http://hg.python.org/cpython/rev/b41def1851b6

New changeset 7e57c95898d3 by Ezio Melotti in branch 'default':
#12277: merge with 3.2.
http://hg.python.org/cpython/rev/7e57c95898d3

New changeset 09a1bd44d96f by Ezio Melotti in branch '2.7':
#12277: add missing comma.
http://hg.python.org/cpython/rev/09a1bd44d96f

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

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

From report at bugs.python.org  Tue Oct 18 12:05:13 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 18 Oct 2011 10:05:13 +0000
Subject: [docs] [issue12277] Missing comma in os.walk docs
In-Reply-To: <1307439951.32.0.810805209718.issue12277@psf.upfronthosting.co.za>
Message-ID: <1318932313.47.0.381790466158.issue12277@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Done.

----------
assignee: eric.araujo -> ezio.melotti
nosy: +ezio.melotti
resolution: accepted -> fixed
stage: commit review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Tue Oct 18 15:06:09 2011
From: report at bugs.python.org (Jason R. Coombs)
Date: Tue, 18 Oct 2011 13:06:09 +0000
Subject: [docs] [issue13211] urllib2.HTTPError does not have 'reason'
	attribute.
Message-ID: <1318943168.93.0.520705450261.issue13211@psf.upfronthosting.co.za>


New submission from Jason R. Coombs <jaraco at jaraco.com>:

The urllib2 docs indicate that HTTPError is a subclass of URLError and that URLError has an attribute of 'reason', but HTTPError does not have this attribute. The docs should be updated to reflect this deviance.

It appears the Python 3.2 docs no longer include documentation for URLError

Python 2.7.2
>>> try:urllib2.urlopen('http://api.wordnik.com/v4/word.json/foo/examples')
... except urllib2.HTTPError as exc:
...   print(dir(exc))
...
['_HTTPError__super_init', '__class__', '__delattr__', '__dict__', '__doc__', '__format__', '__getattribute__', '__getitem__', '__getslice__', '__hash__', '__init__', '__iter__', '__module__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__setstate__', '__sizeof__', '__str__', '__subclasshook__', '__unicode__', '__weakref__', 'args', 'close', 'code', 'errno', 'filename', 'fileno', 'fp', 'getcode', 'geturl', 'hdrs', 'headers', 'info', 'message', 'msg', 'next', 'read', 'readline', 'readlines', 'strerror', 'url']

The same issue exists in Python 3.2.2.

Here's what I propose:
  - For Python 3.2 and 3.3, update HTTPError to supply a @property, aliasing .msg (will .msg always be a suitable .reason?).
  - For Python 2.7, document the deviance, such as by adding the following wording to the HTTPError docs: "Unlike URLError, HTTPError does not supply a reason attribute. The reason can be retrieved through the msg attribute."

----------
assignee: docs at python
components: Documentation
messages: 145805
nosy: docs at python, jason.coombs
priority: normal
severity: normal
status: open
title: urllib2.HTTPError does not have 'reason' attribute.
versions: Python 2.7, Python 3.2, Python 3.3

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

From report at bugs.python.org  Tue Oct 18 17:58:16 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 18 Oct 2011 15:58:16 +0000
Subject: [docs] [issue12277] Missing comma in os.walk docs
In-Reply-To: <1307439951.32.0.810805209718.issue12277@psf.upfronthosting.co.za>
Message-ID: <1318953496.06.0.663364409203.issue12277@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Sorry, I was too busy with real bugs to fix this minor one.

----------

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

From report at bugs.python.org  Tue Oct 18 20:16:43 2011
From: report at bugs.python.org (Petri Lehtinen)
Date: Tue, 18 Oct 2011 18:16:43 +0000
Subject: [docs] [issue13213] generator.throw() behavior
Message-ID: <1318961803.9.0.966531589594.issue13213@psf.upfronthosting.co.za>


New submission from Petri Lehtinen <petri at digip.org>:

The documentation of generator.throw() gives this signature:

    generator.throw(type[, value[, traceback]])

Looking at the code, it accepts the following arguments:

  g.throw(ExcType)  --> raise ExcType()

  g.throw(ExcType, None)  --> raise ExcType()

  g.throw(ExcType, None, tb)  --> raise ExcType().with_traceback(tb)

  g.throw(ExcType, instace_of_ExcType)  --> raise instance_of_ExcType

  g.throw(ExcType, instace_of_ExcType, tb)  --> raise instance_of_ExcType.with_traceback(tb)

  g.throw(ExcType, other_value)  --> raise ExcType(other_value)

  g.throw(ExcType, other_value, tb)  --> raise ExcType(other_value).with_traceback(tb)

Up to this point, I think everything is in line with the documentation. But it also accepts the following (now that issue 13188 is fixed):

  g.throw(exc_instance) --> raise exc_instance (preserving the traceback of exc_instance)

  g.throw(exc_instance, None) --> raise exc_instance (preserving the traceback of exc_instance)

  g.throw(exc_instance, None, tb) --> raise exc_instance.with_traceback(tb)

It does not accept these, throwing a TypeError:

  g.throw(exc_instance, some_value_other_than_None)
  g.throw(exc_instance, some_value_other_than_None, tb)
  g.throw(exc_instance, tb)

The documentation is really unclear on throwing existing exception instances with (exc_instance) or (exc_instance, None), and that calling with (type, value) or (type, value, tb) will create a new exception if not isinstance(value, type).

----------
assignee: docs at python
components: Documentation, Interpreter Core
messages: 145848
nosy: docs at python, ezio.melotti, ncoghlan, petri.lehtinen, pitrou
priority: normal
severity: normal
status: open
title: generator.throw() behavior
type: behavior
versions: Python 2.7, Python 3.2, Python 3.3

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

From report at bugs.python.org  Tue Oct 18 20:48:57 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Tue, 18 Oct 2011 18:48:57 +0000
Subject: [docs] [issue13213] generator.throw() behavior
In-Reply-To: <1318961803.9.0.966531589594.issue13213@psf.upfronthosting.co.za>
Message-ID: <1318963737.44.0.281485361522.issue13213@psf.upfronthosting.co.za>


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


----------
nosy: +flox

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

From report at bugs.python.org  Tue Oct 18 22:05:23 2011
From: report at bugs.python.org (Vinay Sajip)
Date: Tue, 18 Oct 2011 20:05:23 +0000
Subject: [docs] [issue12174] Multiprocessing logging levels unclear
In-Reply-To: <1318926357.56.0.330697503707.issue12174@psf.upfronthosting.co.za>
Message-ID: <1318968319.2616.YahooMailNeo@web25806.mail.ukl.yahoo.com>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

> Should there be another issue opened to do something about the extra logging 

> levels?

IMO they shouldn't have been added in the first place, but I'm not sure if they're part of the public API and hence subject to backward-compatibility constraints. It would be nice to hear a justification for them from Jesse (or someone else). Of course levels are a bit subjective and logging supports user-defined levels for special cases, but using multiple libs with different added levels would be a headache. I think at least the stdlib should stick to the standard levels.

----------

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

From report at bugs.python.org  Wed Oct 19 09:44:14 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Wed, 19 Oct 2011 07:44:14 +0000
Subject: [docs] [issue13141] get rid of old threading API in the examples
In-Reply-To: <1318192627.46.0.311858462486.issue13141@psf.upfronthosting.co.za>
Message-ID: <1319010254.58.0.924689496834.issue13141@psf.upfronthosting.co.za>


Florent Xicluna <florent.xicluna at gmail.com> added the comment:

Proposed patch to refresh the socketserver examples.

----------
keywords: +patch
stage: needs patch -> patch review
versions: +Python 3.2
Added file: http://bugs.python.org/file23459/issue13141.diff

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

From report at bugs.python.org  Wed Oct 19 16:14:40 2011
From: report at bugs.python.org (becky lewis)
Date: Wed, 19 Oct 2011 14:14:40 +0000
Subject: [docs] [issue13219] re module doc has minor inaccuracy in character
	sets
Message-ID: <1319033680.8.0.92268984905.issue13219@psf.upfronthosting.co.za>


New submission from becky lewis <bex.lewis at gmail.com>:

The documentation for the re module  (specifically the section for []) states that:

"If you want to include a ']' or a '-' inside a set, precede it with a backslash, or place it as the first character."

However, after finding a typo in a regex I wrote it turns out to be false.

Using the following regex finds a match:
>>> regex = re.compile(r'[123ab-f-]+')
>>> regex.match('-')
<_sre.SRE_Match object at 0x8dd1b10>

I am not sure if this is an issue with the documentation or if the re module itself should not allow this behaviour. It would be nice if the documentation warned that hyphens (and other 'special' characters such as [) that are not escaped may still be matched, even though they are not the first character.

----------
assignee: docs at python
components: Documentation
messages: 145911
nosy: becky.lewis, docs at python
priority: normal
severity: normal
status: open
title: re module doc has minor inaccuracy in character sets
versions: Python 2.7

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

From qppazaro at gmail.com  Sat Oct 15 17:26:26 2011
From: qppazaro at gmail.com (Alexander Ivanyuta)
Date: Sat, 15 Oct 2011 19:26:26 +0400
Subject: [docs] Grammar specification
Message-ID: <CA+6YinN_6Tp=EgiuX0iZw3CKMDpj_bS1W=iC+cUxvOsOhARJZA@mail.gmail.com>

Hello,

I found that there is no operator in python such as '<>' in this rule -
                comp_op: '<'|'>'|'=='|'>='|'<='|'<>'|'!='|'in'|'not' 'in'|
'is'|'is' 'not'

http://docs.python.org/py3k/reference/grammar.html


Best Regards,
Alexander Ivanyuta
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111015/8dc802e6/attachment-0001.html>

From rickwillp at gmail.com  Sun Oct 16 14:35:46 2011
From: rickwillp at gmail.com (rick petch)
Date: Sun, 16 Oct 2011 13:35:46 +0100
Subject: [docs] disable python
Message-ID: <CAMmDNjyFvz9u-D1a0jb_dbhT7=37rGkKiK7Ck_e1bf29SaxUsQ@mail.gmail.com>

hi,
i run windows vista 64 bit on my hp pc and until this last week it has done
me really well but now i find that all my web browsers have been taken over
by this python thing,
could you please tell me how to disable python on my pc,
i have read somewhere that it is part of windows system but i have never
ever seen it on any of my pc's before and it is very annoying,
i do not like things taking over my machines,
so would you be so kind as to tell me how to disable python.
thanks very much.
rick.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111016/01ef4de0/attachment-0001.html>

From michael at python.org  Mon Oct 17 15:16:25 2011
From: michael at python.org (Michael Foord)
Date: Mon, 17 Oct 2011 14:16:25 +0100
Subject: [docs] Fwd: Issue with the link to python modules documentation
In-Reply-To: <4E9B4244.6010309@ohmytux.com>
References: <4E9B4244.6010309@ohmytux.com>
Message-ID: <4E9C2AA9.6000206@python.org>

Hey folks,

The title of the "Global Module Index" for 3.2 documentation is "Python 
3.1.3 documentation".

http://docs.python.org/py3k/modindex.html

See the report below (attached screenshot removed).

All the best,

Michael Foord

-------- Original Message --------
Subject: 	Issue with the link to python modules documentation
Date: 	Sun, 16 Oct 2011 22:44:52 +0200
From: 	Carl Chenet <chaica at ohmytux.com>
Reply-To: 	chaica at ohmytux.com
To: 	webmaster at python.org



Hi,

Browsing http://www.python.org/doc/ , I click on the link to Python 3.x
Module Index linking to http://docs.python.org/3.2/modindex.html and I'm
redirected to http://docs.python.org/py3k/modindex.html to the Python
module list documentation but for the version 3.1.3.

I'm using Chromium 12. I tried several times and cleared the cache
before retrying but the issue remains.

I'm joining a screenshot showing the finale page with the url
http://docs.python.org/py3k/modindex.html which should be the Python
Module list for current 3.x version, which is I guess 3.2.

Bye,
Carl Chenet


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111017/1d813ca0/attachment-0001.html>

From edonan at gmail.com  Mon Oct 17 19:07:56 2011
From: edonan at gmail.com (Edoardo)
Date: Mon, 17 Oct 2011 19:07:56 +0200
Subject: [docs] Little demo program for curses with Python's Howto
	(lineograph.py)
Message-ID: <CAB4nO-x1ZEpK2HhF=OjjHT8zJqCQV5sqcxohyGLTvWof2KdyQA@mail.gmail.com>

Hi,
reading the curses programming HOWTO
(http://docs.python.org/dev/howto/curses.html) I noticed it lacks a
full running demo.
Moreover, the document ends inviting developers to contribuite with a
short program.

I took such invitation and this is my two cents: a program that turns
the terminal into a lineographic tool (kind of Etch A Sketch).
It uses only the curses facilities explained in the HOWTO (except
window.getmaxyx(), that is trivial) and works with both Python 2.7.1+
and Python 3.2.
Input controls are arrow keys to paint and "q" to quit.

I hope I have been helpful. Best regards,
Edoardo Nannotti
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lineograph.py
Type: text/x-python
Size: 767 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20111017/f63afb2f/attachment-0001.py>

From szepesva at ualberta.ca  Tue Oct 18 16:54:14 2011
From: szepesva at ualberta.ca (Csaba Szepesvari)
Date: Tue, 18 Oct 2011 08:54:14 -0600
Subject: [docs] Turtle graphics, what is the function done doing?
Message-ID: <4E9D9316.60008@sztaki.hu>

Hi,

Look at the example code at:
http://docs.python.org/py3k/library/turtle.html#turtle.towards

from  turtle  import  *
color('red',  'yellow')
begin_fill()
while  True:
     forward(200)
     left(170)
     if  abs(pos())  <  1:
         break
end_fill()
done()


It calls the done() function at the end. However, this function is not 
documented.
My experimentation shows that this is really coming from the turtle 
module, so it should be documented here.. (or at least pls give some 
pointer to its documentation).
Bests,
   Csaba
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111018/4216b3cf/attachment-0001.html>

From report at bugs.python.org  Wed Oct 19 22:49:01 2011
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 19 Oct 2011 20:49:01 +0000
Subject: [docs] [issue12185] Decimal documentation lists "first" and
	"second"	arguments, should be "self" and "other"
In-Reply-To: <1306411163.06.0.644918639795.issue12185@psf.upfronthosting.co.za>
Message-ID: <1319057341.48.0.0274203786654.issue12185@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Sorry, I'm going to reject this one.  I applied the patch and looked at the generated docs, finding them to be less readable than before.  AFAICT, we've had no issues with people mis-reading the text as currently presented.   Also, I looked back at the underlying spec, http://speleotrove.com/decimal/daops.html , and found that it tended to refer to first and second operand.  I would like to keep our docs as close to that as possible.

----------
resolution:  -> rejected
status: open -> closed

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

From report at bugs.python.org  Wed Oct 19 23:11:01 2011
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 19 Oct 2011 21:11:01 +0000
Subject: [docs] [issue11931] Regular expression documentation patch
In-Reply-To: <1303855586.52.0.604026571441.issue11931@psf.upfronthosting.co.za>
Message-ID: <E1RGdPc-0002ns-RJ@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 068d89194ffd by Raymond Hettinger in branch '3.2':
Issue 11931: Minor punctuation/grammar/wording fixups to the regex docs
http://hg.python.org/cpython/rev/068d89194ffd

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

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

From report at bugs.python.org  Wed Oct 19 23:11:57 2011
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 19 Oct 2011 21:11:57 +0000
Subject: [docs] [issue11931] Regular expression documentation patch
In-Reply-To: <1303855586.52.0.604026571441.issue11931@psf.upfronthosting.co.za>
Message-ID: <1319058717.42.0.549635507412.issue11931@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Applied many of these changes to 3.2 and 3.3.
If someone is interested, feel free to backport them to 2.7.

----------
resolution:  -> fixed
status: open -> closed
versions:  -Python 3.1, Python 3.2, Python 3.3

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

From report at bugs.python.org  Wed Oct 19 23:17:00 2011
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 19 Oct 2011 21:17:00 +0000
Subject: [docs] [issue12668] 3.2 What's New: it's integer->string,
	not the opposite
In-Reply-To: <1312147179.72.0.252519921224.issue12668@psf.upfronthosting.co.za>
Message-ID: <E1RGdVR-0003IB-0S@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 48e0db1cf7e4 by Raymond Hettinger in branch '3.2':
Issue 12668: Fix wording in Whatsnew3.2
http://hg.python.org/cpython/rev/48e0db1cf7e4

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

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

From report at bugs.python.org  Wed Oct 19 23:17:38 2011
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 19 Oct 2011 21:17:38 +0000
Subject: [docs] [issue12668] 3.2 What's New: it's integer->string,
	not the opposite
In-Reply-To: <1312147179.72.0.252519921224.issue12668@psf.upfronthosting.co.za>
Message-ID: <1319059058.36.0.502350794315.issue12668@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Thanks for the report.

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

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

From report at bugs.python.org  Thu Oct 20 00:43:32 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 19 Oct 2011 22:43:32 +0000
Subject: [docs] [issue13219] re module doc has minor inaccuracy in character
	sets
In-Reply-To: <1319033680.8.0.92268984905.issue13219@psf.upfronthosting.co.za>
Message-ID: <1319064212.67.0.0794454247538.issue13219@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Here's a patch against 2.7.  I rephrased the section a bit.  If it's more understandable I'll commit it.

----------
assignee: docs at python -> ezio.melotti
keywords: +patch
nosy: +ezio.melotti
stage:  -> commit review
versions: +Python 3.2, Python 3.3
Added file: http://bugs.python.org/file23474/issue13219.diff

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

From report at bugs.python.org  Thu Oct 20 05:41:59 2011
From: report at bugs.python.org (Eric Snow)
Date: Thu, 20 Oct 2011 03:41:59 +0000
Subject: [docs] [issue13124] Add "Running a Build Slave" page to the devguide
In-Reply-To: <1318011517.56.0.343886781977.issue13124@psf.upfronthosting.co.za>
Message-ID: <1319082119.46.0.936539106731.issue13124@psf.upfronthosting.co.za>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:

Per Ezio's and Stefan's feedback I cleaned things up a little:

* consolidated on "Buildbot"
* clarified the meaning of the "standard development toolchain"
* % changed to $
* cleaned up the network ports section
* removed a bunch of outdated/unnecessary info

I did not do anything about syntax highlighting for lack of know-how.  I also did not add anything about the responsibilities of running a build slave, mostly because I have no idea what those are.  :)

Much of the section on installation needs double-checking as I am not sure how much of it is necessary and how much not.

This is about as far as I think I will be able to take this tracker issue.  Unfortunately I don't have a lot of time to get up to speed on how Buildbot works, and I know nearly nothing about it currently.

I'm hoping that finishing this won't be much work for someone with a working knowledge of our buildbots.  I've tried to get it close.  It's a gap in the devguide that I think would be worth filling.

Incidently, I pulled the section on security (which motivated me here in the first place) and stuck it into the wiki page.  If any of that is worth pulling back in, there it is.  Thanks!

----------

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

From report at bugs.python.org  Thu Oct 20 06:22:56 2011
From: report at bugs.python.org (Eric Snow)
Date: Thu, 20 Oct 2011 04:22:56 +0000
Subject: [docs] [issue13124] Add "Running a Build Slave" page to the devguide
In-Reply-To: <1318011517.56.0.343886781977.issue13124@psf.upfronthosting.co.za>
Message-ID: <1319084576.55.0.982001626807.issue13124@psf.upfronthosting.co.za>


Changes by Eric Snow <ericsnowcurrently at gmail.com>:


Added file: http://bugs.python.org/file23479/devguide-buildbots-2.diff

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

From report at bugs.python.org  Thu Oct 20 09:40:21 2011
From: report at bugs.python.org (anatoly techtonik)
Date: Thu, 20 Oct 2011 07:40:21 +0000
Subject: [docs] [issue13231] sys.settrace - document 'some other code
	blocks' for	'call' event type
Message-ID: <1319096421.5.0.420840017987.issue13231@psf.upfronthosting.co.za>


New submission from anatoly techtonik <techtonik at gmail.com>:

http://docs.python.org/library/sys.html#sys.settrace

While writing settrace function you need to know what kind of data is expected and how to get more information about it. Current documentation for sys.settrace doesn't give too much answers. To improve that situation at least with 'call' event:

 1. Link 'frame' to the middle of table on inspect module page [1]
 2. List all possible 'code blocks' for 'call' event (I know there is module in addition to function)
 3. Provide example how to extract popular data for corresponding 'code block' (name for functions, name for modules, name for classes/methods, relative file path, line no, how to detect labmbda function) in a safe manner (inspect page contains some FUD about memory usage)


1. http://docs.python.org/library/inspect#types-and-members

----------
assignee: docs at python
components: Documentation
messages: 146009
nosy: docs at python, techtonik
priority: normal
severity: normal
status: open
title: sys.settrace - document 'some other code blocks' for 'call' event type

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

From report at bugs.python.org  Thu Oct 20 18:20:41 2011
From: report at bugs.python.org (Guilherme Moro)
Date: Thu, 20 Oct 2011 16:20:41 +0000
Subject: [docs] [issue13233] os.acces documentation error
Message-ID: <1319127640.96.0.83884717457.issue13233@psf.upfronthosting.co.za>


New submission from Guilherme Moro <guilherme.moro at gmail.com>:

http://docs.python.org/library/os.html#os.access

points out that I should use
try:
    fp = open("myfile")
except IOError as e:
    if e.errno == errno.EACCESS:
        return "some default data"
    # Not a permission error.
    raise
else:
    with fp:
        return fp.read()

but theres a typo the correct is errno.EACCES: not errno.EACCESS:

----------
assignee: docs at python
components: Documentation
messages: 146024
nosy: Guilherme.Moro, docs at python
priority: normal
severity: normal
status: open
title: os.acces documentation error
versions: Python 2.7

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

From report at bugs.python.org  Thu Oct 20 18:46:02 2011
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 20 Oct 2011 16:46:02 +0000
Subject: [docs] [issue13219] re module doc has minor inaccuracy in character
	sets
In-Reply-To: <1319033680.8.0.92268984905.issue13219@psf.upfronthosting.co.za>
Message-ID: <E1RGvkk-0006to-8Y@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 07eca800cdb4 by Ezio Melotti in branch '2.7':
#13219: clarify section about character sets in the re documentation.
http://hg.python.org/cpython/rev/07eca800cdb4

New changeset dc96a89ac192 by Ezio Melotti in branch '3.2':
#13219: clarify section about character sets in the re documentation.
http://hg.python.org/cpython/rev/dc96a89ac192

New changeset 78540d1264d9 by Ezio Melotti in branch 'default':
#13219: merge with 3.2.
http://hg.python.org/cpython/rev/78540d1264d9

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

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

From report at bugs.python.org  Thu Oct 20 18:47:01 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 20 Oct 2011 16:47:01 +0000
Subject: [docs] [issue13219] re module doc has minor inaccuracy in character
	sets
In-Reply-To: <1319033680.8.0.92268984905.issue13219@psf.upfronthosting.co.za>
Message-ID: <1319129221.75.0.159374345723.issue13219@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Done, thanks for the report!

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

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

From report at bugs.python.org  Thu Oct 20 18:53:59 2011
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 20 Oct 2011 16:53:59 +0000
Subject: [docs] [issue13233] os.acces documentation error
In-Reply-To: <1319127640.96.0.83884717457.issue13233@psf.upfronthosting.co.za>
Message-ID: <E1RGvsR-0007Zd-2F@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 1d8fad82c32d by Ezio Melotti in branch '3.2':
#13233: fix typo.
http://hg.python.org/cpython/rev/1d8fad82c32d

New changeset 99c8b93c57cd by Ezio Melotti in branch 'default':
#13233: null merge with 3.2.
http://hg.python.org/cpython/rev/99c8b93c57cd

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

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

From report at bugs.python.org  Thu Oct 20 18:54:54 2011
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 20 Oct 2011 16:54:54 +0000
Subject: [docs] [issue13233] os.acces documentation error
In-Reply-To: <1319127640.96.0.83884717457.issue13233@psf.upfronthosting.co.za>
Message-ID: <E1RGvtJ-0007eZ-M1@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 8bf9724dcd49 by Ezio Melotti in branch '2.7':
#13233: fix typo.
http://hg.python.org/cpython/rev/8bf9724dcd49

----------

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

From report at bugs.python.org  Thu Oct 20 18:55:40 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 20 Oct 2011 16:55:40 +0000
Subject: [docs] [issue13233] os.acces documentation error
In-Reply-To: <1319127640.96.0.83884717457.issue13233@psf.upfronthosting.co.za>
Message-ID: <1319129740.0.0.403389137443.issue13233@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> 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
versions: +Python 3.2, Python 3.3

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

From report at bugs.python.org  Thu Oct 20 19:10:50 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Thu, 20 Oct 2011 17:10:50 +0000
Subject: [docs] [issue13219] re module doc has minor inaccuracy in character
	sets
In-Reply-To: <1319033680.8.0.92268984905.issue13219@psf.upfronthosting.co.za>
Message-ID: <1319130650.1.0.43682111564.issue13219@psf.upfronthosting.co.za>


Florent Xicluna <florent.xicluna at gmail.com> added the comment:

Well, the actual behavior is a little bit more complex to describe.

>>> re.match('[.-_a-z]', '-')
>>> re.match('[._-a-z]', '-')
<_sre.SRE_Match object at 0x100418e80>


>>> re.match('[.-_a-z]', 'b')
<_sre.SRE_Match object at 0x100418b88>
>>> re.match('[._-a-z]', 'b')

However, I don't think it is worth changing again the documentation.

----------
nosy: +flox
type:  -> behavior

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

From report at bugs.python.org  Thu Oct 20 19:17:23 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 20 Oct 2011 17:17:23 +0000
Subject: [docs] [issue13219] re module doc has minor inaccuracy in character
	sets
In-Reply-To: <1319033680.8.0.92268984905.issue13219@psf.upfronthosting.co.za>
Message-ID: <1319131043.66.0.101947767997.issue13219@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Indeed.
The "tricks" of putting '-' at the beginning/end and ']' at the beginning are well known and works with most of the implementations afaik, but I would consider the behavior of [._-a-z] as an implementation detail and don't expect it to work elsewhere.

----------

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

From sandro.tosi at gmail.com  Thu Oct 20 19:19:33 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Thu, 20 Oct 2011 19:19:33 +0200
Subject: [docs] disable python
In-Reply-To: <CAMmDNjyFvz9u-D1a0jb_dbhT7=37rGkKiK7Ck_e1bf29SaxUsQ@mail.gmail.com>
References: <CAMmDNjyFvz9u-D1a0jb_dbhT7=37rGkKiK7Ck_e1bf29SaxUsQ@mail.gmail.com>
Message-ID: <CAPdtAj39eJ0BXBXuox=3dcDHpVDDnYjbvjYkG6YQqZtUXF0eqg@mail.gmail.com>

Hello Rick,

On Sun, Oct 16, 2011 at 14:35, rick petch <rickwillp at gmail.com> wrote:
> i run windows vista 64 bit on my hp pc and until this last week it has done
> me really well but now i find that all my web browsers have been taken over
> by this python thing,
> could you please tell me how to disable python on my pc,
> i have read somewhere that it is part of windows system but i have never
> ever seen it on any of my pc's before and it is very annoying,
> i do not like things taking over my machines,
> so would you be so kind as to tell me how to disable python.

This is not the correct mailing list for such questions (this ml is
for bugs enhancement of Python documentation) - you should try to
contact a general python/windows support forum; for python you may try
http://mail.python.org/pipermail/python-list/

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Thu Oct 20 19:48:50 2011
From: report at bugs.python.org (anatoly techtonik)
Date: Thu, 20 Oct 2011 17:48:50 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
Message-ID: <1319132930.0.0.280764890807.issue13235@psf.upfronthosting.co.za>


New submission from anatoly techtonik <techtonik at gmail.com>:

No docs for logging.warn() alias.

----------
assignee: docs at python
components: Documentation
messages: 146039
nosy: docs at python, techtonik
priority: normal
severity: normal
status: open
title: logging.warn() is not documented
versions: Python 2.7, Python 3.3

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

From report at bugs.python.org  Thu Oct 20 19:49:26 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 20 Oct 2011 17:49:26 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
In-Reply-To: <1319132930.0.0.280764890807.issue13235@psf.upfronthosting.co.za>
Message-ID: <1319132966.13.0.131545463925.issue13235@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Oct 20 20:43:38 2011
From: report at bugs.python.org (Vinay Sajip)
Date: Thu, 20 Oct 2011 18:43:38 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
In-Reply-To: <1319132930.0.0.280764890807.issue13235@psf.upfronthosting.co.za>
Message-ID: <1319136218.71.0.2573971309.issue13235@psf.upfronthosting.co.za>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

That's deliberate. The original code (before incorporation into Python) had warn(), which was kept for backward compatibility. The docs refer to warning() because that's what everyone is supposed to use. The method names map to the lower case of the appropriate logging level name.

----------
resolution:  -> invalid
status: open -> closed

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

From report at bugs.python.org  Thu Oct 20 21:32:50 2011
From: report at bugs.python.org (anatoly techtonik)
Date: Thu, 20 Oct 2011 19:32:50 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
In-Reply-To: <1319132930.0.0.280764890807.issue13235@psf.upfronthosting.co.za>
Message-ID: <1319139170.51.0.777564314772.issue13235@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

I've got a traceback, because forgot to implement this method in logging wrapper. It should be either deprecated and removed or documented.

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

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

From report at bugs.python.org  Thu Oct 20 22:26:04 2011
From: report at bugs.python.org (Vinay Sajip)
Date: Thu, 20 Oct 2011 20:26:04 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
In-Reply-To: <1319139170.51.0.777564314772.issue13235@psf.upfronthosting.co.za>
Message-ID: <1319142359.42055.YahooMailNeo@web25805.mail.ukl.yahoo.com>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

It is deprecated by not being documented. It certainly isn't going to have documentation added for it.

Which code was calling the warn() method? Is it not possible to change this to call warning()?

----- Original Message -----
> From: anatoly techtonik <report at bugs.python.org>
> To: vinay_sajip at yahoo.co.uk
> Cc: 
> Sent: Thursday, 20 October 2011, 20:32
> Subject: [issue13235] logging.warn() is not documented
> 
> 
> anatoly techtonik <techtonik at gmail.com> added the comment:
> 
> I've got a traceback, because forgot to implement this method in logging 
> wrapper. It should be either deprecated and removed or documented.
> 
> ----------
> status: closed -> open
> 
> _______________________________________
> Python tracker <report at bugs.python.org>
> <http://bugs.python.org/issue13235>
> _______________________________________
>

----------

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

From report at bugs.python.org  Fri Oct 21 02:43:18 2011
From: report at bugs.python.org (anatoly techtonik)
Date: Fri, 21 Oct 2011 00:43:18 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
In-Reply-To: <1319132930.0.0.280764890807.issue13235@psf.upfronthosting.co.za>
Message-ID: <1319157798.22.0.992439823252.issue13235@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

./trac/env.py:                self.log.warn('base_url option not set in configuration, '
./trac/env.py:            self.log.warn('Couldn\'t write sample configuration file (%s)', e,
./trac/web/main.py:            ##    env.log.warn("%d uncollectable objects found.", uncollectable)
./trac/web/main.py:            env.log.warn(exception_to_unicode(e))
./trac/web/.svn/text-base/main.py.svn-base:            ##    env.log.warn("%d uncollectable objects found.", uncollectable)
./trac/web/.svn/text-base/main.py.svn-base:            env.log.warn(exception_to_unicode(e))
./trac/wiki/formatter.py:            self.env.log.warn(e)
./trac/wiki/.svn/text-base/formatter.py.svn-base:            self.env.log.warn(e)
./trac/versioncontrol/api.py:                        self.log.warn("Discarding duplicate repository '%s'",
./trac/versioncontrol/api.py:            self.log.warn("Found no repositories matching '%s' base.",
./trac/versioncontrol/svn_prop.py:                    self.log.warn("svn:externals entry %s doesn't contain "
./trac/versioncontrol/.svn/text-base/api.py.svn-base:                        self.log.warn("Discarding duplicate repository '%s'",
./trac/versioncontrol/.svn/text-base/api.py.svn-base:            self.log.warn("Found no repositories matching '%s' base.",
./trac/versioncontrol/.svn/text-base/svn_prop.py.svn-base:                    self.log.warn("svn:externals entry %s doesn't contain "
./trac/ticket/roadmap.py:        def warn(msg):
./trac/ticket/roadmap.py:                warn(_('Milestone "%(name)s" already exists, please '
./trac/ticket/roadmap.py:                warn(_('You must provide a name for the milestone.'))
./trac/ticket/roadmap.py:                warn(_('Completion date may not be in the future'))
./trac/ticket/.svn/text-base/roadmap.py.svn-base:        def warn(msg):
./trac/ticket/.svn/text-base/roadmap.py.svn-base:                warn(_('Milestone "%(name)s" already exists, please '
./trac/ticket/.svn/text-base/roadmap.py.svn-base:                warn(_('You must provide a name for the milestone.'))
./trac/ticket/.svn/text-base/roadmap.py.svn-base:                warn(_('Completion date may not be in the future'))
./trac/admin/web_ui.py:                        self.env.log.warn("Adding %s to group %s: " \
./trac/admin/.svn/text-base/web_ui.py.svn-base:                        self.env.log.warn("Adding %s to group %s: " \
./trac/prefs/web_ui.py:            self.log.warn('Unknown preference panel %r', panel_id)
./trac/prefs/.svn/text-base/web_ui.py.svn-base:            self.log.warn('Unknown preference panel %r', panel_id)
./trac/.svn/text-base/env.py.svn-base:                self.log.warn('base_url option not set in configuration, '
./trac/.svn/text-base/env.py.svn-base:            self.log.warn('Couldn\'t write sample configuration file (%s)', e,


quite a lot + probably trac plugins. So it's better to go through deprecation cycle and show appropriate message (but frankly - I don't mind against convenience alias - we already have some in testing modules).

----------

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

From report at bugs.python.org  Fri Oct 21 04:28:27 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 21 Oct 2011 02:28:27 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
In-Reply-To: <1319132930.0.0.280764890807.issue13235@psf.upfronthosting.co.za>
Message-ID: <1319164107.53.0.281640993772.issue13235@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

I think it's better to avoid "deprecations by missing documentation" and document explicitly if something is deprecated.
What happens is that people working on some old code find the deprecated method, check the doc to see what it does, don't find anything, get puzzled for a while until they figure out how it works, and then use it.
If they find it and see that is deprecated they will stop using it and start using the right method.
While it's true that new users don't need to know that there's a deprecated method, it's unlikely that they will start using it, so documenting deprecated methods makes more good than harm.
If you want to remove it eventually you'll also have to go through an actual deprecation process with warnings.

----------
nosy: +ezio.melotti
resolution: invalid -> 
stage:  -> needs patch
versions: +Python 3.2

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

From report at bugs.python.org  Fri Oct 21 07:25:02 2011
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 21 Oct 2011 05:25:02 +0000
Subject: [docs] [issue13237] subprocess docs should use emphasise
	convenience	functions
Message-ID: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>


New submission from Nick Coghlan <ncoghlan at gmail.com>:

Many typical subprocess use cases can now be handled simply via the convenience functions:

  subprocess.call()
  subprocess.check_call()
  subprocess.check_output()

However, readers of the documentation could be forgiven for not realising that, since the docs dive right in with Popen() and will scare most readers away in search of more user friendly APIs (or even other languages).

The module documentation should be reordered to introduce the helper function first, then Popen afterwards.

The "subprocess replacements" [1] section would ideally help address this, but it hasn't been updated to use the convenience function, instead using confusing direct calls to Popen.

[1] http://docs.python.org/library/subprocess.html#subprocess-replacements

----------
assignee: docs at python
components: Documentation
messages: 146059
nosy: docs at python, ncoghlan
priority: normal
severity: normal
stage: needs patch
status: open
title: subprocess docs should use emphasise convenience functions
versions: Python 2.7, Python 3.2, Python 3.3

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

From report at bugs.python.org  Fri Oct 21 07:29:37 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 21 Oct 2011 05:29:37 +0000
Subject: [docs] [issue13237] subprocess docs should use emphasise
	convenience	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319174977.54.0.106077836162.issue13237@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/issue13237>
_______________________________________

From report at bugs.python.org  Fri Oct 21 08:06:21 2011
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 21 Oct 2011 06:06:21 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319177181.29.0.09661671749.issue13237@psf.upfronthosting.co.za>


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


----------
title: subprocess docs should use emphasise convenience functions -> subprocess docs should emphasise convenience functions

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

From report at bugs.python.org  Fri Oct 21 08:33:53 2011
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 21 Oct 2011 06:33:53 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
In-Reply-To: <1319132930.0.0.280764890807.issue13235@psf.upfronthosting.co.za>
Message-ID: <E1RH8fs-0005tR-Mv@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 37479f0f68bc by Vinay Sajip in branch 'default':
Closes #13235: Added deprecation for warn() methods and function in logging.
http://hg.python.org/cpython/rev/37479f0f68bc

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

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

From report at bugs.python.org  Fri Oct 21 09:27:38 2011
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 21 Oct 2011 07:27:38 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319182058.79.0.270416948125.issue13237@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

+1

----------
nosy: +rhettinger

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

From report at bugs.python.org  Fri Oct 21 10:01:07 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Fri, 21 Oct 2011 08:01:07 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319184067.16.0.379523334677.issue13237@psf.upfronthosting.co.za>


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


----------
nosy: +flox
type:  -> behavior

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

From report at bugs.python.org  Fri Oct 21 11:11:31 2011
From: report at bugs.python.org (Eli Bendersky)
Date: Fri, 21 Oct 2011 09:11:31 +0000
Subject: [docs] [issue13239] Remove <> operator from Grammar/Grammar
Message-ID: <1319188291.02.0.897231487042.issue13239@psf.upfronthosting.co.za>


New submission from Eli Bendersky <eliben at gmail.com>:

Operator <> was removed in Python 3, but still appears in Grammar/Grammar (and hence in Doc/reference/grammar.rst)

Reported by Alexander Ivanyuta on the docs mailing list

----------
assignee: docs at python
components: Documentation, Interpreter Core
messages: 146070
nosy: docs at python, eli.bendersky
priority: normal
severity: normal
status: open
title: Remove <> operator from Grammar/Grammar
versions: Python 3.2, Python 3.3

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

From eliben at gmail.com  Fri Oct 21 11:11:48 2011
From: eliben at gmail.com (Eli Bendersky)
Date: Fri, 21 Oct 2011 11:11:48 +0200
Subject: [docs] Grammar specification
In-Reply-To: <CA+6YinN_6Tp=EgiuX0iZw3CKMDpj_bS1W=iC+cUxvOsOhARJZA@mail.gmail.com>
References: <CA+6YinN_6Tp=EgiuX0iZw3CKMDpj_bS1W=iC+cUxvOsOhARJZA@mail.gmail.com>
Message-ID: <CAF-Rda-Zd+2R=bhpoVnk-TRRghgOH2oJ5ZTXZGdH+EN=b4KX7A@mail.gmail.com>

The '<>' operator has been removed in Python 3.x
(http://docs.python.org/release/3.0.1/whatsnew/3.0.html)

However, it appears to still exist in Grammar/Grammar

I've opened issue http://bugs.python.org/issue13239 to track this.
Thanks for reporting, Alexander.

Eli




On Sat, Oct 15, 2011 at 17:26, Alexander Ivanyuta <qppazaro at gmail.com> wrote:
> Hello,
> I found that there is no operator in python such as?'<>'?in this rule -
> ? ? ? ? ? ? ? ??comp_op: '<'|'>'|'=='|'>='|'<='|'<>'|'!='|'in'|'not'
> 'in'|'is'|'is' 'not'
> http://docs.python.org/py3k/reference/grammar.html
>
> Best Regards,
> Alexander Ivanyuta
> _______________________________________________
> docs mailing list
> docs at python.org
> http://mail.python.org/mailman/listinfo/docs
>
>

From report at bugs.python.org  Fri Oct 21 11:20:21 2011
From: report at bugs.python.org (Eli Bendersky)
Date: Fri, 21 Oct 2011 09:20:21 +0000
Subject: [docs] [issue13239] Remove <> operator from Grammar/Grammar
In-Reply-To: <1319188291.02.0.897231487042.issue13239@psf.upfronthosting.co.za>
Message-ID: <1319188821.69.0.880362595614.issue13239@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

The relevant code in Parser/parsetok.c is:

#ifdef PY_PARSER_REQUIRES_FUTURE_KEYWORD
        if (type == NOTEQUAL) {
            if (!(ps->p_flags & CO_FUTURE_BARRY_AS_BDFL) &&
                            strcmp(str, "!=")) {
                err_ret->error = E_SYNTAX;
                break;
            }
            else if ((ps->p_flags & CO_FUTURE_BARRY_AS_BDFL) &&
                            strcmp(str, "<>")) {
                err_ret->text = "with Barry as BDFL, use '<>' "
                                "instead of '!='";
                err_ret->error = E_SYNTAX;
                break;
            }
        }
#endif


Hmm... I'm too new to remember this joke, but here it presents a practical problem - since Grammar/Grammar is being directly reflected into the documentation (.. literalinclude:: ../../Grammar/Grammar) and thus can confuse.

Is it safe to just remove the whole thing from Grammar/Grammar and correspondingly Parser/parsetok.c ?

----------

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

From report at bugs.python.org  Fri Oct 21 11:23:26 2011
From: report at bugs.python.org (Eli Bendersky)
Date: Fri, 21 Oct 2011 09:23:26 +0000
Subject: [docs] [issue13239] Remove <> operator from Grammar/Grammar
In-Reply-To: <1319188291.02.0.897231487042.issue13239@psf.upfronthosting.co.za>
Message-ID: <1319189006.83.0.603376664022.issue13239@psf.upfronthosting.co.za>


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


----------
nosy: +barry, brett.cannon, fdrake, ncoghlan

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

From report at bugs.python.org  Fri Oct 21 11:28:25 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Fri, 21 Oct 2011 09:28:25 +0000
Subject: [docs] [issue13239] Remove <> operator from Grammar/Grammar
In-Reply-To: <1319188291.02.0.897231487042.issue13239@psf.upfronthosting.co.za>
Message-ID: <1319189305.06.0.387718012831.issue13239@psf.upfronthosting.co.za>


Florent Xicluna <florent.xicluna at gmail.com> added the comment:

This is PEP 401.

"[Because] the != inequality operator ... was a horrible, finger pain inducing mistake, the FLUFL reinstates the <> diamond operator as the sole spelling. This change is important enough to be implemented for, and released in Python 3.1. To help transition to this feature, a new future statement, from __future__ import barry_as_FLUFL has been added."

----------
nosy: +flox
type:  -> behavior

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

From report at bugs.python.org  Fri Oct 21 17:23:02 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 21 Oct 2011 15:23:02 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319210582.34.0.519230865524.issue13237@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

>From a quick look it seems to me that only 
-   output = Popen(["mycmd", "myarg"], stdout=PIPE).communicate()[0]
+   output = check_output(["mycmd", "myarg"])

can be changed.
Most of the other example access attributes of the Popen objects, such as stdin/stdout. subprocess.call is already used in a few places.

Another thing that I wanted to fix for a while is the syntax highlight in these examples.  Using '# becomes' instead of '==>' solves the problem for most of the examples, except for the first two that use `...`.  Using two separate blocks is another option.  A table with two columns (before/after) might also work, but it's difficult to get it wide enough to contain both the examples side by side.

About moving the convenience functions first, I'm not sure it works too well.
"This module defines one class called Popen:"
could be replaced by
"This module defines a class called Popen, and the convenience functions call(), check_call(), and check_output():"
where the three functions and possibly 'convenience functions' link to to the part of the page where they are defined.

----------
type: behavior -> 

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

From michal.sourek at centrum.cz  Fri Oct 21 17:10:28 2011
From: michal.sourek at centrum.cz (michal.sourek at centrum.cz)
Date: Fri, 21 Oct 2011 17:10:28 +0200
Subject: [docs] PYTHON Principal error - loss of coherence - observed in
	modules time, datetime
Message-ID: <20111021171028.6406F617@centrum.cz>

Dear sirs,
? ? ? ? first,
? ? ? ? let me express a highest level of admiration for all the genuine people involved in Python world
?
? ? ? ? second,
? ? ? ? please forgive me, as an "informed amateur", to direct this notice to you, instead of may-be a specialised dev/error team
?
? ? ? ? third,
? ? ? ? might be, that this piece of information has already been handled in some other bug/error/PEP
?
after some years spent with Python
I?ve observed recently an incoherence - a feature in time / datetime modules,
that,
in a fair belief,
both should and can be handled
so that the function are coherent - meaning the "promised" behaviour keeps really "being delivered" even under bellow-described circumstances, that are quite common in recent years
?
 In a hope
 this can help
 please forward the not to the appropriate hands
 and let me know if it did help - thank you
?
?
With respect
Michal
?
use scenario: a procedure loopLineDATA( anObj ) ...demo-ed bellow ... gets an object to monitor
 and each 10-secs?performs regular processing,
 it uses several about-one-second time.sleep()-s to wait till next 10-sec-time-period
?
the point: as gets up and running ( loop forever )
 it prints every 10 secs a "status-report" on time/data
 and
 once
 a notebook gets "hibernated" .. a quite often state ( be it a power saving policy, or an intention )
 the process persists in some state throughout the hibernation epoch
 and after the notebook gets re-activated, the process continues
?
the issue / non-conformity-note [NCN]
 The [NCN] claims,
 that after continuing the processing ( post-hibernation state ),
 Python displays [ uses and displays ]
 wrong time values (as if no hibernation epoch did appear ?... continuing second-by-second right ahead from "old"-time of the moment, when the machine turned hibernated )
 the hibenrated-time-shift is correctly reported by machine clock,
 but not in the Python time / datetime functions - those keep continue counting time as if there were no hibernate-epoch ( areal-wolrd time-shift ) in the meantime
?
an interim fix: to prevent such, perform?
 at some reasonable frequency, to keep low latency/overhead thereof,
 time-base?re-adjustment to renew the coherence of Python-time with the machine RTC-clock (real-world-time)
?
" /*-------------------------------------------------------------------
# a demonstration sample ... not any kind of an optimised / HiPerf code :o)
import time, datetime


def loopLineDATA ( anObj )
 last_N = 0
 while True:
 try:
 now = datetime.datetime.now()
 ntt = now.timetuple()
 N ? = ntt.tm_sec
 if ( N % 10 ) == 0: # to get 00 10 20 30 .. 50 "round-values"
 if N/ 10 == last_N: # to sleep/loop, should still in the "same-10-sec-time-period"
 time.sleep( 0.95 ) # to provide system a slight time-elasticity for?SIG/overhead processing
 else:
 last_N = N / 10 # shuffle N as "10-sec-time-period" 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111021/11c59d35/attachment.html>

From report at bugs.python.org  Fri Oct 21 20:34:47 2011
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 21 Oct 2011 18:34:47 +0000
Subject: [docs] [issue13239] Remove <> operator from Grammar/Grammar
In-Reply-To: <1319189305.06.0.387718012831.issue13239@psf.upfronthosting.co.za>
Message-ID: <CAP1=2W5_ri-UBTDxvK+t8BN071oFTJJfJvvYi8ACo1ZtHW4M_g@mail.gmail.com>


Brett Cannon <brett at python.org> added the comment:

Probably need a comment in the Grammar file so people know why an
unused operator is in there.

----------

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

From report at bugs.python.org  Fri Oct 21 20:35:49 2011
From: report at bugs.python.org (Benjamin Peterson)
Date: Fri, 21 Oct 2011 18:35:49 +0000
Subject: [docs] [issue13239] Remove <> operator from Grammar/Grammar
In-Reply-To: <1319188291.02.0.897231487042.issue13239@psf.upfronthosting.co.za>
Message-ID: <1319222149.64.0.847135952688.issue13239@psf.upfronthosting.co.za>


Benjamin Peterson <benjamin at python.org> added the comment:

Or perhaps we don't need joke backward compatibility? (That's nearly 3 years old.)

----------
nosy: +benjamin.peterson

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

From report at bugs.python.org  Fri Oct 21 20:43:00 2011
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 21 Oct 2011 18:43:00 +0000
Subject: [docs] [issue13239] Remove <> operator from Grammar/Grammar
In-Reply-To: <1319222149.64.0.847135952688.issue13239@psf.upfronthosting.co.za>
Message-ID: <CAP1=2W58wX+MnJE19ji2ZVX0B+WYo9ezL7icFza_C_2MCCPQCw@mail.gmail.com>


Brett Cannon <brett at python.org> added the comment:

On Fri, Oct 21, 2011 at 11:35, Benjamin Peterson <report at bugs.python.org> wrote:
>
> Benjamin Peterson <benjamin at python.org> added the comment:
>
> Or perhaps we don't need joke backward compatibility? (That's nearly 3 years old.)

Then you tell the FLUFL that you want to take his precious operator away. =)

----------

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

From report at bugs.python.org  Fri Oct 21 21:30:21 2011
From: report at bugs.python.org (Barry A. Warsaw)
Date: Fri, 21 Oct 2011 19:30:21 +0000
Subject: [docs] [issue13239] Remove <> operator from Grammar/Grammar
In-Reply-To: <1319222149.64.0.847135952688.issue13239@psf.upfronthosting.co.za>
Message-ID: <20111021153010.63a4451d@resist.wooz.org>


Barry A. Warsaw <barry at python.org> added the comment:

On Oct 21, 2011, at 06:35 PM, Benjamin Peterson wrote:

>Benjamin Peterson <benjamin at python.org> added the comment:
>
>Or perhaps we don't need joke backward compatibility? (That's nearly 3 years
>old.)

OTOH, __future__ imports (even jokes) should never be removed.

----------

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

From report at bugs.python.org  Fri Oct 21 21:33:04 2011
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 21 Oct 2011 19:33:04 +0000
Subject: [docs] [issue13239] Remove <> operator from Grammar/Grammar
In-Reply-To: <1319188291.02.0.897231487042.issue13239@psf.upfronthosting.co.za>
Message-ID: <1319225584.49.0.651128725242.issue13239@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

> OTOH, __future__ imports (even jokes) should never be removed.

But their meaning can be altered?
(as part of another joke if you want :)

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

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

From report at bugs.python.org  Fri Oct 21 21:35:11 2011
From: report at bugs.python.org (Barry A. Warsaw)
Date: Fri, 21 Oct 2011 19:35:11 +0000
Subject: [docs] [issue13239] Remove <> operator from Grammar/Grammar
In-Reply-To: <1319225584.49.0.651128725242.issue13239@psf.upfronthosting.co.za>
Message-ID: <20111021153503.7602a3a7@resist.wooz.org>


Barry A. Warsaw <barry at python.org> added the comment:

On Oct 21, 2011, at 07:33 PM, Antoine Pitrou wrote:

>Antoine Pitrou <pitrou at free.fr> added the comment:
>
>> OTOH, __future__ imports (even jokes) should never be removed.
>
>But their meaning can be altered?
>(as part of another joke if you want :)

Well, you have 6 months to work that out then. :)

----------

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

From report at bugs.python.org  Fri Oct 21 23:47:03 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 21 Oct 2011 21:47:03 +0000
Subject: [docs] [issue13239] Remove <> operator from Grammar/Grammar
In-Reply-To: <1319188291.02.0.897231487042.issue13239@psf.upfronthosting.co.za>
Message-ID: <1319233623.48.0.877699889165.issue13239@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


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

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

From report at bugs.python.org  Sat Oct 22 00:07:18 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 21 Oct 2011 22:07:18 +0000
Subject: [docs] [issue13203] Doc: say id() is only useful for existing
	objects
In-Reply-To: <1318873835.36.0.466865504792.issue13203@psf.upfronthosting.co.za>
Message-ID: <1319234838.16.0.155612471803.issue13203@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


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

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

From report at bugs.python.org  Sat Oct 22 01:07:29 2011
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 21 Oct 2011 23:07:29 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319238449.6.0.88225478088.issue13237@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

You couldn't just move them - you'd need to change the wording of how they cross-link to each other, since the explanations of the convenience function currently assume you understand how Popen works. I'd like us to get to the point where you only need to understand the whole Popen swiss army knife if you actually want that level of flexibility.

----------

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

From report at bugs.python.org  Sat Oct 22 01:18:58 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 21 Oct 2011 23:18:58 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319239138.56.0.707807650379.issue13237@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Yep, what I was suggesting was an easier approach, but if someone is willing to reorganize the document, I agree that is better to start with an example that shows the most common use cases with the convenience functions and then gradually explain the convenience functions used in the example before moving to Popen and its intricacies.
The unittest doc for example follows the same approach, example first and then explanation.

----------

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

From report at bugs.python.org  Sat Oct 22 04:35:44 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 22 Oct 2011 02:35:44 +0000
Subject: [docs] [issue13203] Doc: say id() is only useful for existing
	objects
In-Reply-To: <1318873835.36.0.466865504792.issue13203@psf.upfronthosting.co.za>
Message-ID: <1319250944.48.0.0309154995593.issue13203@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

A FAQ entry sounds good to me.

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

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

From report at bugs.python.org  Sat Oct 22 11:18:33 2011
From: report at bugs.python.org (anatoly techtonik)
Date: Sat, 22 Oct 2011 09:18:33 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
In-Reply-To: <1319132930.0.0.280764890807.issue13235@psf.upfronthosting.co.za>
Message-ID: <1319275113.05.0.175878615547.issue13235@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Just to me it clear - why do you want warn() to be removed aside from code duplication?

My argument to leave it and document is that it is convenient and makes lines shorter (and won't break existing code). From logging module I also see that there are also logging.WARN aliases that you'll need to deprecate also.

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

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

From report at bugs.python.org  Sat Oct 22 11:29:30 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 22 Oct 2011 09:29:30 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
In-Reply-To: <1319132930.0.0.280764890807.issue13235@psf.upfronthosting.co.za>
Message-ID: <1319275770.51.0.899332971161.issue13235@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Because there should be only one way to do things.

BTW, you could have used a DeprecationWarning instead of a PendingDeprecationWarning, especially if it was already deprecated.

----------

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

From report at bugs.python.org  Sat Oct 22 13:00:19 2011
From: report at bugs.python.org (Vinay Sajip)
Date: Sat, 22 Oct 2011 11:00:19 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
In-Reply-To: <1319275113.05.0.175878615547.issue13235@psf.upfronthosting.co.za>
Message-ID: <1319281214.29104.YahooMailNeo@web25802.mail.ukl.yahoo.com>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

> Just to me it clear - why do you want warn() to be removed aside from code 

> duplication?
> 
> My argument to leave it and document is that it is convenient and makes lines 
> shorter (and won't break existing code). From logging module I also see that 
> there are also logging.WARN aliases that you'll need to deprecate also.

Sorry, I don't agree. I was happy to leave it as is until you raised this issue, but now I think the right thing to do is deprecate and remove warn(). I'm not too fussed about the WARN level, and I can't easily issue a deprecation warning for it as it's a module attribute, so I'll leave it in as an internal implementation detail, for which the usual caveats apply.

----------

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

From report at bugs.python.org  Sat Oct 22 13:01:23 2011
From: report at bugs.python.org (Vinay Sajip)
Date: Sat, 22 Oct 2011 11:01:23 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
In-Reply-To: <1319275770.51.0.899332971161.issue13235@psf.upfronthosting.co.za>
Message-ID: <1319281277.19997.YahooMailNeo@web25805.mail.ukl.yahoo.com>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

> BTW, you could have used a DeprecationWarning instead of a 

> PendingDeprecationWarning, especially if it was already deprecated.

It wasn't officially deprecated, just "deprecation via obscurity";-) which is why I made it a PendingDeprecationWarning.

----------

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

From report at bugs.python.org  Sat Oct 22 13:03:18 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 22 Oct 2011 11:03:18 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
In-Reply-To: <1319132930.0.0.280764890807.issue13235@psf.upfronthosting.co.za>
Message-ID: <1319281398.21.0.186084316846.issue13235@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

PendingDeprecations are not so useful now that warnings are silenced by default. Since it wasn't documented, you could deprecate it in 3.3 and remove it in 3.4 IMHO.

----------

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

From report at bugs.python.org  Sat Oct 22 13:10:33 2011
From: report at bugs.python.org (Vinay Sajip)
Date: Sat, 22 Oct 2011 11:10:33 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
In-Reply-To: <1319281398.21.0.186084316846.issue13235@psf.upfronthosting.co.za>
Message-ID: <1319281827.53874.YahooMailNeo@web25802.mail.ukl.yahoo.com>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

> PendingDeprecations are not so useful now that warnings are silenced by default. 

> Since it wasn't documented, you could deprecate it in 3.3 and remove it in 
> 3.4 IMHO.

Hmmm, you're probably right. I'll change it to a DeprecationWarning.

----------

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

From report at bugs.python.org  Sat Oct 22 14:34:59 2011
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 22 Oct 2011 12:34:59 +0000
Subject: [docs] [issue13235] logging.warn() is not documented
In-Reply-To: <1319132930.0.0.280764890807.issue13235@psf.upfronthosting.co.za>
Message-ID: <E1RHams-00013c-3e@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 4a90d1ed115d by Vinay Sajip in branch 'default':
Closes #13235: Changed PendingDeprecationWarning to DeprecationWarning.
http://hg.python.org/cpython/rev/4a90d1ed115d

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

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

From sandro.tosi at gmail.com  Sat Oct 22 18:05:19 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Sat, 22 Oct 2011 18:05:19 +0200
Subject: [docs] Subprocess Starup Error
In-Reply-To: <8F693A3A31F74FB1AAFF6E781A1C4E1F@PC127417878215>
References: <8F693A3A31F74FB1AAFF6E781A1C4E1F@PC127417878215>
Message-ID: <CAPdtAj20vQgUSg1OEHko6Kc3Z-JGyeH2g91J1o9YNouR6YdQZg@mail.gmail.com>

Hello Larry,

On Thu, Oct 13, 2011 at 01:15, Larry Horn <lhorn003 at woh.rr.com> wrote:
> I am running 2.7.2 on a Windows XP machine Python worked fine for a week,
> but then developed this problem. When ever I start python a get the error
> message:???--IDLE's subprocess didn't make connection. Either IDLE can't
> start a subprocess or firewall software is blocking the connection. There
> must be some fix for this problem. Please let me know.

This mailing list is about fixing bugs/enhance python documentation,
so your question doesn't fit here. I suggest to ask such questions to
a general forum about python, for example:
http://mail.python.org/mailman/listinfo/python-list

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Sat Oct 22 22:13:50 2011
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 22 Oct 2011 20:13:50 +0000
Subject: [docs] [issue13246] Py_UCS4_strlen and friends needn't be public
Message-ID: <1319314430.74.0.993573606288.issue13246@psf.upfronthosting.co.za>


New submission from Antoine Pitrou <pitrou at free.fr>:

It seems there's no reason to document these functions which operate on null-terminated unicode arrays.

----------
assignee: docs at python
components: Documentation
messages: 146187
nosy: docs at python, ezio.melotti, georg.brandl, haypo, loewis, pitrou
priority: normal
severity: normal
status: open
title: Py_UCS4_strlen and friends needn't be public
versions: Python 3.3

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

From report at bugs.python.org  Sat Oct 22 22:55:14 2011
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 22 Oct 2011 20:55:14 +0000
Subject: [docs] [issue13246] Py_UCS4_strlen and friends needn't be public
In-Reply-To: <1319314430.74.0.993573606288.issue13246@psf.upfronthosting.co.za>
Message-ID: <1319316914.09.0.192431592943.issue13246@psf.upfronthosting.co.za>


Georg Brandl <georg at python.org> added the comment:

If they aren't public, they should get an underscore.

All our API functions are either public or private; all public ones should be documented.

----------

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

From report at bugs.python.org  Sun Oct 23 04:30:19 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 23 Oct 2011 02:30:19 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319337019.64.0.536715571895.issue13237@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


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

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

From report at bugs.python.org  Sun Oct 23 11:08:30 2011
From: report at bugs.python.org (STINNER Victor)
Date: Sun, 23 Oct 2011 09:08:30 +0000
Subject: [docs] [issue13246] Py_UCS4_strlen and friends needn't be public
In-Reply-To: <1319314430.74.0.993573606288.issue13246@psf.upfronthosting.co.za>
Message-ID: <1319360910.1.0.634191736155.issue13246@psf.upfronthosting.co.za>


STINNER Victor <victor.stinner at haypocalc.com> added the comment:

> It seems there's no reason to document these functions
> which operate on null-terminated unicode arrays.

It's the easiest way to create a new string with the new Unicode API, when it's difficult to predict the exact output length and maximum character:

Py_UCS4 *buffer = PyMem_Malloc(...);
...
str = PyUnicode_FromKindAndBuffer(buffer, PyUnicode_4BYTE_KIND);
PyMem_Free(buffer);

PyUCS4_* functions are useful in the "..." (to write characters, expecially when you manipulate multiple strings).

For examples, see Python/import.c which used char*, then Py_UNICODE* and now Py_UCS4*. It's maybe possible to avoid functions like xxx_strlen(), but it was easier to replace str*() functions by Py_UNICODE_* and then PyUCS4_* functions.

--

Py_UNICODE_* and PyUCS4_* functions are not part of the stable API.

----------

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

From report at bugs.python.org  Sun Oct 23 14:30:07 2011
From: report at bugs.python.org (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 23 Oct 2011 12:30:07 +0000
Subject: [docs] [issue13246] Py_UCS4_strlen and friends needn't be public
In-Reply-To: <1319314430.74.0.993573606288.issue13246@psf.upfronthosting.co.za>
Message-ID: <1319373007.67.0.308116153963.issue13246@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

Before the release, we should consider whether we can drop these functions altogether.

----------

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

From report at bugs.python.org  Sun Oct 23 14:40:31 2011
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 23 Oct 2011 12:40:31 +0000
Subject: [docs] [issue13246] Py_UCS4_strlen and friends needn't be public
In-Reply-To: <1319314430.74.0.993573606288.issue13246@psf.upfronthosting.co.za>
Message-ID: <1319373631.88.0.509592662322.issue13246@psf.upfronthosting.co.za>


Georg Brandl <georg at python.org> added the comment:

Making sure we don't forget that :)

----------
priority: normal -> release blocker

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

From report at bugs.python.org  Sun Oct 23 20:39:12 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Sun, 23 Oct 2011 18:39:12 +0000
Subject: [docs] [issue13249] argparse.ArgumentParser() lists arguments in
	the wrong	order
In-Reply-To: <1319394759.74.0.692830705102.issue13249@psf.upfronthosting.co.za>
Message-ID: <1319395152.39.0.913326580198.issue13249@psf.upfronthosting.co.za>


Florent Xicluna <florent.xicluna at gmail.com> added the comment:

in 3.x, same issue.
IMHO documentation should be fixed.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +bethard, docs at python, flox
stage:  -> needs patch
versions: +Python 3.2, Python 3.3

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

From report at bugs.python.org  Sun Oct 23 21:02:13 2011
From: report at bugs.python.org (Petri Lehtinen)
Date: Sun, 23 Oct 2011 19:02:13 +0000
Subject: [docs] [issue13249] argparse.ArgumentParser() lists arguments in
	the wrong	order
In-Reply-To: <1319394759.74.0.692830705102.issue13249@psf.upfronthosting.co.za>
Message-ID: <1319396533.24.0.902260555796.issue13249@psf.upfronthosting.co.za>


Petri Lehtinen <petri at digip.org> added the comment:

Fixing the documentation is better, as changing the argument order would break existing code.

----------
keywords: +easy
nosy: +petri.lehtinen

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

From report at bugs.python.org  Sun Oct 23 21:06:00 2011
From: report at bugs.python.org (Santoso Wijaya)
Date: Sun, 23 Oct 2011 19:06:00 +0000
Subject: [docs] [issue13249] argparse.ArgumentParser() lists arguments in
	the wrong	order
In-Reply-To: <1319394759.74.0.692830705102.issue13249@psf.upfronthosting.co.za>
Message-ID: <1319396760.66.0.677060927405.issue13249@psf.upfronthosting.co.za>


Changes by Santoso Wijaya <santoso.wijaya at gmail.com>:


----------
nosy: +santa4nt

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

From report at bugs.python.org  Sun Oct 23 21:11:03 2011
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 23 Oct 2011 19:11:03 +0000
Subject: [docs] [issue13249] argparse.ArgumentParser() lists arguments in
	the wrong	order
In-Reply-To: <1319394759.74.0.692830705102.issue13249@psf.upfronthosting.co.za>
Message-ID: <1319397063.2.0.604319843974.issue13249@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

In the doc, the signature line is followed by a list of short descriptions in a third order. That perhaps should be changed to follow the same corrected order as the signature line. On the other hand, it matches the order of the detail sections that follow. On the third hand, that current order is confusing as it intermixes parameters that affect the help message behavior with those that affect the actual argument parsing behavior. I think these should be separated with one group following the other.

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

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

From report at bugs.python.org  Sun Oct 23 21:16:12 2011
From: report at bugs.python.org (Roy Smith)
Date: Sun, 23 Oct 2011 19:16:12 +0000
Subject: [docs] [issue13249] argparse.ArgumentParser() lists arguments in
	the wrong	order
In-Reply-To: <1319394759.74.0.692830705102.issue13249@psf.upfronthosting.co.za>
Message-ID: <1319397372.68.0.934562589756.issue13249@psf.upfronthosting.co.za>


Roy Smith <roy at panix.com> added the comment:

An Nth place is in the docstring:

    Keyword Arguments:                                                                              
        - prog -- The name of the program (default: sys.argv[0])                                    
        - usage -- A usage message (default: auto-generated from arguments)                         
        - description -- A description of what the program does                                     
        - epilog -- Text following the argument descriptions                                        
        - parents -- Parsers whose arguments should be copied into this one                         
        - formatter_class -- HelpFormatter class for printing help messages                         
        - prefix_chars -- Characters that prefix optional arguments                                 
        - fromfile_prefix_chars -- Characters that prefix files containing                          
            additional arguments                                                                    
        - argument_default -- The default value for all arguments                                   
        - conflict_handler -- String indicating how to handle conflicts                             
        - add_help -- Add a -h/-help option

which omits 'version'.

----------

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

From report at bugs.python.org  Sun Oct 23 21:47:52 2011
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 23 Oct 2011 19:47:52 +0000
Subject: [docs] [issue12965] longobject: documentation improvements
In-Reply-To: <1315846670.45.0.93309834122.issue12965@psf.upfronthosting.co.za>
Message-ID: <E1RI41F-0004na-Cr@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset d4839fea4a5a by Mark Dickinson in branch 'default':
Issue #12965: Fix some inaccurate comments in Objects/longobject.c.  Thanks Stefan Krah.
http://hg.python.org/cpython/rev/d4839fea4a5a

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

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

From report at bugs.python.org  Sun Oct 23 21:55:01 2011
From: report at bugs.python.org (Mark Dickinson)
Date: Sun, 23 Oct 2011 19:55:01 +0000
Subject: [docs] [issue12965] longobject: documentation improvements
In-Reply-To: <1315846670.45.0.93309834122.issue12965@psf.upfronthosting.co.za>
Message-ID: <1319399701.74.0.394531537782.issue12965@psf.upfronthosting.co.za>


Mark Dickinson <dickinsm at gmail.com> added the comment:

I've fixed some of the inaccurate comments in Objects/longobject.c, for the default branch;  I'm still looking at the Doc update.

This really is a bit of a mess, especially for cases like PyLong_AsVoidPtr, which can either end up calling PyLong_As(Long)Long (which  allows conversion via __int__), or PyLong_AsUnsigned(Long)Long (which doesn't).

Ultimately, I think it would make sense to remove all __int__ conversions from Objects/longobject.c;  this would affect:

  - PyLong_AsLongAndOverflow
  - PyLong_AsLong
  - PyLong_AsUnsignedLongMask

and the 'LongLong' variants of these.  The ramifications of such a change might be quite long-reaching;  in particular, I seem to recall that this would affect the 'getargs' machinery.

It could be fun to remove these conversions and see how much of the test-suite fails. :-)

----------

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

From report at bugs.python.org  Sun Oct 23 22:14:40 2011
From: report at bugs.python.org (Mark Dickinson)
Date: Sun, 23 Oct 2011 20:14:40 +0000
Subject: [docs] [issue12965] longobject: documentation improvements
In-Reply-To: <1315846670.45.0.93309834122.issue12965@psf.upfronthosting.co.za>
Message-ID: <1319400880.4.0.27885284992.issue12965@psf.upfronthosting.co.za>


Mark Dickinson <dickinsm at gmail.com> added the comment:

> It could be fun to remove these conversions and see how much of the
> test-suite fails. :-)

... On my machine, just test_ctypes and test_getargs2, as it turns out.

----------

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

From report at bugs.python.org  Sun Oct 23 22:31:55 2011
From: report at bugs.python.org (Roy Smith)
Date: Sun, 23 Oct 2011 20:31:55 +0000
Subject: [docs] [issue13249] argparse.ArgumentParser() lists arguments in
	the wrong	order
In-Reply-To: <1319394759.74.0.692830705102.issue13249@psf.upfronthosting.co.za>
Message-ID: <1319401915.74.0.749008630165.issue13249@psf.upfronthosting.co.za>


Roy Smith <roy at panix.com> added the comment:

I'm working on a doc patch now...

----------

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

From report at bugs.python.org  Sun Oct 23 22:48:15 2011
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 23 Oct 2011 20:48:15 +0000
Subject: [docs] [issue13141] get rid of old threading API in the examples
In-Reply-To: <1318192627.46.0.311858462486.issue13141@psf.upfronthosting.co.za>
Message-ID: <E1RI4xm-0000Zw-4e@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset d34beaaf7060 by Florent Xicluna in branch '3.2':
Issue 13141: Demonstrate recommended style for socketserver examples.
http://hg.python.org/cpython/rev/d34beaaf7060

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

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

From report at bugs.python.org  Sun Oct 23 23:08:25 2011
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 23 Oct 2011 21:08:25 +0000
Subject: [docs] [issue13141] get rid of old threading API in the examples
In-Reply-To: <1318192627.46.0.311858462486.issue13141@psf.upfronthosting.co.za>
Message-ID: <E1RI5HI-0001tp-4J@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 8de472fb8cfe by Florent Xicluna in branch '2.7':
Issue #13141: Demonstrate recommended style for SocketServer examples.
http://hg.python.org/cpython/rev/8de472fb8cfe

----------

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

From report at bugs.python.org  Sun Oct 23 23:09:37 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Sun, 23 Oct 2011 21:09:37 +0000
Subject: [docs] [issue13141] get rid of old threading API in the examples
In-Reply-To: <1318192627.46.0.311858462486.issue13141@psf.upfronthosting.co.za>
Message-ID: <1319404177.04.0.429832495528.issue13141@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Oct 23 23:12:59 2011
From: report at bugs.python.org (Roy Smith)
Date: Sun, 23 Oct 2011 21:12:59 +0000
Subject: [docs] [issue13249] argparse.ArgumentParser() lists arguments in
	the wrong	order
In-Reply-To: <1319394759.74.0.692830705102.issue13249@psf.upfronthosting.co.za>
Message-ID: <1319404379.51.0.929534798441.issue13249@psf.upfronthosting.co.za>


Roy Smith <roy at panix.com> added the comment:

Patch attached.  I just deal with putting all the items into the same order, not terry.reedy's idea for separating them into two groups.

Added a recommendation to only use keywords, which seems sane given the number of arguments.

----------
keywords: +patch
Added file: http://bugs.python.org/file23505/Issue13249.patch

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

From report at bugs.python.org  Sun Oct 23 23:14:32 2011
From: report at bugs.python.org (Roy Smith)
Date: Sun, 23 Oct 2011 21:14:32 +0000
Subject: [docs] [issue13249] argparse.ArgumentParser() lists arguments in
	the wrong	order
In-Reply-To: <1319394759.74.0.692830705102.issue13249@psf.upfronthosting.co.za>
Message-ID: <1319404472.42.0.562503839638.issue13249@psf.upfronthosting.co.za>


Roy Smith <roy at panix.com> added the comment:

PS -- this is against the 2.7 branch.

----------

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

From michael at voidspace.org.uk  Sun Oct 23 23:31:09 2011
From: michael at voidspace.org.uk (Michael Foord)
Date: Sun, 23 Oct 2011 22:31:09 +0100
Subject: [docs] I want to contribute
In-Reply-To: <tencent_0FDD57181DE029307DBCF165@qq.com>
References: <tencent_0FDD57181DE029307DBCF165@qq.com>
Message-ID: <193D56BF-4C18-410B-A3BE-B03C0644A35D@voidspace.org.uk>

Hello,

Thanks for wanting to contribute. I believe the correct place to contribute to translations of the Python documentation is:

	http://pootle.python.org/pootle

The right place to discuss this is the Python documentation mailing list:

	http://mail.python.org/mailman/listinfo/docs

All the best,

Michael Foord


On 21 Oct 2011, at 10:22, ?? wrote:

> Hi dear,
> For a long time,I find that Python's website or doc  is lack of multiple language support.
> I'm a chinese,now i work for a internet security company.
> I like write Python .it's a amazing programming.
> I want to translate some primary doc for the new guys especially the college student who want to learn programming.
>       When I was a college student in china ,I firstly studied the C language ,then the C++,etc.But when the moment I known how to write with Python ,I find it extremely faster and easier.I was shaked.
>     Now i just have a idea to  translate something.But I don't know how to perform it into truth.Can you give me a guide?


--
http://www.voidspace.org.uk/


May you do good and not evil
May you find forgiveness for yourself and forgive others
May you share freely, never taking more than you give.
-- the sqlite blessing 
http://www.sqlite.org/different.html






From jpeak at futurepointsystems.com  Sun Oct 23 23:32:48 2011
From: jpeak at futurepointsystems.com (Jim Peak)
Date: Sun, 23 Oct 2011 14:32:48 -0700
Subject: [docs] filecmp.cmp- confusion allowed by what we do NOT say
Message-ID: <E9DBDEA2BCD702468DE88C8E2FF39041F3E022@fpserver.futurepointsystems.com>

Hi!  While tracking down a problem, I came across a source of confusion
that our docs leave open concerning filecmp.cmp.

 

I believe that with the addition of a single sentence, we can resolve
it.

 

Problem: 

Currently, we have the text that's in black font, shown between the
lines of hyphens, below.  Our text specs what happens when os.stat()
signatures are equal, but does not spec what happens when they're
unequal.  

 

Because of this, it's easy for readers to assume that unequal os.stat()
signatures are treated as UNequal: but that's not true:

 

Suggested Solution:

I suggest the addition of the sentence (or one like it) in green (and
italics).

 

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

filecmp.cmp(f1, f2[, shallow])

 

Compare the files named f1 and f2, returning True if they seem equal,
False otherwise.

 

Unless shallow is given and is false, files with identical os.stat
<http://docs.python.org/library/os.html#os.stat> () signatures are taken
to be equal. When os.stat() signatures differ, the contents of files are
compared, regardless of the value of shallow.

Files that were compared using this function will not be compared again
unless their os.stat()signature changes.
<http://docs.python.org/library/os.html#os.stat> 

Note that no external programs are called from this function, giving it
portability and efficiency.
<http://docs.python.org/library/os.html#os.stat> 

---------------------------------------------------
<http://docs.python.org/library/os.html#os.stat> 

(taken from the 2.7.2 doc, section 10.5, here:
http://docs.python.org/library/filecmp.html- but our 3.1.3 doc, in
section 10.4, reads identically)

 

 

We're not "technically" incorrect, but people can easily conclude from
our verbiage that since "identical os.stat() signatures are taken to be
equal," that different signatures are taken to be different.   See, for
example, the confusion of the user here:
<http://docs.python.org/library/os.html#os.stat> 

http://www.velocityreviews.com/forums/t732652-filecmp-cmp-doesnt-seem-to
-do-what-it-says-in-the-documentation.html
<http://docs.python.org/library/os.html#os.stat> 

 

Here's another example of confusion.  This is from Doug Hellman's site:
he's actually written a book on the Std Lib (The Python Standard Library
by Example), and has another in development, which is quoted here:  (He
<http://www.velocityreviews.com/forums/t732652-filecmp-cmp-doesnt-seem-t
o-do-what-it-says-in-the-documentation.html>  knows about this being
wrong, now: sent him a note just today):

(taken from http://www.doughellmann.com/PyMOTW/filecmp/ )
<http://www.velocityreviews.com/forums/t732652-filecmp-cmp-doesnt-seem-t
o-do-what-it-says-in-the-documentation.html> 

 

By default, cmp() looks only at the information available from
os.stat(). The shallow argument tells cmp() whether to look at the
contents of the file, as well. The default is to perform a shallow
comparison, without looking inside the files. Notice that files of the
same size created at the same time seem to be the same if their contents
are not compared.
<http://www.velocityreviews.com/forums/t732652-filecmp-cmp-doesnt-seem-t
o-do-what-it-says-in-the-documentation.html> 

 

I believe that the addition of a single sentence can tighten up our doc
to help eliminate this confusion / these errors.
<http://www.doughellmann.com/PyMOTW/filecmp/> 

 

Thanks for all of your work on Python!
<http://www.doughellmann.com/PyMOTW/filecmp/> 

 

Jim Peak <http://www.doughellmann.com/PyMOTW/filecmp/> 

Software Test Engineer <http://www.doughellmann.com/PyMOTW/filecmp/> 

Future Point Systems, Inc. <http://www.doughellmann.com/PyMOTW/filecmp/>


(509) 619-2517 cell <http://www.doughellmann.com/PyMOTW/filecmp/> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111023/2e4270f3/attachment.html>

From report at bugs.python.org  Mon Oct 24 02:01:15 2011
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 24 Oct 2011 00:01:15 +0000
Subject: [docs] [issue13141] get rid of old threading API in the examples
In-Reply-To: <1318192627.46.0.311858462486.issue13141@psf.upfronthosting.co.za>
Message-ID: <1319414475.24.0.491165167676.issue13141@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

Should be closed, no?

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

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

From report at bugs.python.org  Mon Oct 24 08:08:01 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Mon, 24 Oct 2011 06:08:01 +0000
Subject: [docs] [issue13141] get rid of old threading API in the examples
In-Reply-To: <1318192627.46.0.311858462486.issue13141@psf.upfronthosting.co.za>
Message-ID: <1319436481.64.0.96814398758.issue13141@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Oct 24 12:48:07 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Mon, 24 Oct 2011 10:48:07 +0000
Subject: [docs] [issue13255] wrong docstring for array.fromunicode
Message-ID: <1319453287.77.0.97617561601.issue13255@psf.upfronthosting.co.za>


New submission from Florent Xicluna <florent.xicluna at gmail.com>:

The docstring should say "ustr.encode" instead of "ustr.decode".
The documentation page is correct.

>>> print(array.array.fromunicode.__doc__)
fromunicode(ustr)

Extends this array with data from the unicode string ustr.
The array must be a unicode type array; otherwise a ValueError
is raised.  Use array.frombytes(ustr.decode(...)) to
append Unicode data to an array of some other type.

----------
assignee: docs at python
components: Documentation
messages: 146292
nosy: docs at python, flox
priority: normal
severity: normal
stage: needs patch
status: open
title: wrong docstring for array.fromunicode
type: behavior
versions: Python 3.2, Python 3.3

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

From report at bugs.python.org  Mon Oct 24 13:17:58 2011
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 24 Oct 2011 11:17:58 +0000
Subject: [docs] [issue13255] wrong docstring for array.fromunicode
In-Reply-To: <1319453287.77.0.97617561601.issue13255@psf.upfronthosting.co.za>
Message-ID: <E1RIIXR-0007sj-Hc@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 451fa5782145 by Florent Xicluna in branch '3.2':
Issue #13255: wrong docstrings in array module.
http://hg.python.org/cpython/rev/451fa5782145

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

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

From report at bugs.python.org  Mon Oct 24 13:18:53 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Mon, 24 Oct 2011 11:18:53 +0000
Subject: [docs] [issue13255] wrong docstrings in array module
In-Reply-To: <1319453287.77.0.97617561601.issue13255@psf.upfronthosting.co.za>
Message-ID: <1319455133.54.0.608811246498.issue13255@psf.upfronthosting.co.za>


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


----------
resolution:  -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
title: wrong docstring for array.fromunicode -> wrong docstrings in array module

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

From report at bugs.python.org  Mon Oct 24 14:23:18 2011
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 24 Oct 2011 12:23:18 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <E1RIJYf-00072E-0P@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 2184df0e0f89 by Nick Coghlan in branch '2.7':
Issue #13237: Rearrange subprocess module documentation to emphasise the convenience functions and commonly needed arguments
http://hg.python.org/cpython/rev/2184df0e0f89

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

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

From report at bugs.python.org  Mon Oct 24 14:54:31 2011
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 24 Oct 2011 12:54:31 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319460871.28.0.524554245167.issue13237@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

I'm reasonably happy with the changes I just checked in, but rather than doing multiple forward ports, my plan is to let them settle for a while, update them based on any feedback I get, then incorporate the final version into the 3.x series.

----------

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

From report at bugs.python.org  Mon Oct 24 20:01:43 2011
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 24 Oct 2011 18:01:43 +0000
Subject: [docs] [issue13256] Document and test new socket options
In-Reply-To: <1319456775.82.0.463656498781.issue13256@psf.upfronthosting.co.za>
Message-ID: <1319479303.38.0.650363424144.issue13256@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation, Tests
nosy: +docs at python
stage:  -> needs patch
versions: +Python 3.3

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

From report at bugs.python.org  Tue Oct 25 00:46:42 2011
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 24 Oct 2011 22:46:42 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319496402.49.0.849874986483.issue13237@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/issue13237>
_______________________________________

From report at bugs.python.org  Tue Oct 25 00:49:10 2011
From: report at bugs.python.org (Arkadiusz Wahlig)
Date: Mon, 24 Oct 2011 22:49:10 +0000
Subject: [docs] [issue13259] __bytes__ not documented
Message-ID: <1319496550.21.0.905326658417.issue13259@psf.upfronthosting.co.za>


New submission from Arkadiusz Wahlig <arkadiusz.wahlig at gmail.com>:

It looks like Python 3 supports the __bytes__ magic method (called by bytes(obj)). However, it's not documented anywhere.

Also, I could not find any reference to BDFL accepting it but it looks like it got in anyway.

Here are some posts back from 2007 where he argues against it:
http://mail.python.org/pipermail/python-3000/2007-August/009375.html

----------
assignee: docs at python
components: Documentation
messages: 146334
nosy: docs at python, yak
priority: normal
severity: normal
status: open
title: __bytes__ not documented
versions: Python 3.1, Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Tue Oct 25 00:58:09 2011
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 24 Oct 2011 22:58:09 +0000
Subject: [docs] [issue13259] __bytes__ not documented
In-Reply-To: <1319496550.21.0.905326658417.issue13259@psf.upfronthosting.co.za>
Message-ID: <1319497089.61.0.0246081291984.issue13259@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

Indeed. I didn't even remember we had that. There are tests, however, in Lib/test/test_bytes.py.
This was added in issue #2415, by the way.

----------
nosy: +pitrou
stage:  -> needs patch
versions:  -Python 3.1, Python 3.4

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

From report at bugs.python.org  Tue Oct 25 06:07:23 2011
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 25 Oct 2011 04:07:23 +0000
Subject: [docs] [issue13259] __bytes__ not documented
In-Reply-To: <1319496550.21.0.905326658417.issue13259@psf.upfronthosting.co.za>
Message-ID: <E1RIYIH-0007d0-IH@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 199d9e3fe0ce by Benjamin Peterson in branch '3.2':
document __bytes__ special method (closes #13259)
http://hg.python.org/cpython/rev/199d9e3fe0ce

New changeset 4128de054937 by Benjamin Peterson in branch 'default':
merge 3.2 (#13259)
http://hg.python.org/cpython/rev/4128de054937

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

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

From report at bugs.python.org  Tue Oct 25 13:46:42 2011
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 25 Oct 2011 11:46:42 +0000
Subject: [docs] [issue13256] Document and test new socket options
In-Reply-To: <1319456775.82.0.463656498781.issue13256@psf.upfronthosting.co.za>
Message-ID: <1319543202.7.0.620966926723.issue13256@psf.upfronthosting.co.za>


STINNER Victor <victor.stinner at haypocalc.com> added the comment:

For #12619, I added socket.SO_BINDTODEVICE constant.

----------

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

From report at bugs.python.org  Tue Oct 25 14:32:20 2011
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 25 Oct 2011 12:32:20 +0000
Subject: [docs] [issue13256] Document and test new socket options
In-Reply-To: <1319456775.82.0.463656498781.issue13256@psf.upfronthosting.co.za>
Message-ID: <1319545940.86.0.898989524577.issue13256@psf.upfronthosting.co.za>


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


----------
keywords: +patch
Added file: http://bugs.python.org/file23516/socket_options_doc.patch

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

From report at bugs.python.org  Wed Oct 26 06:32:56 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 26 Oct 2011 04:32:56 +0000
Subject: [docs] [issue13161] problems with help() documentation of __i*__
	operators
In-Reply-To: <1318436543.45.0.46958950416.issue13161@psf.upfronthosting.co.za>
Message-ID: <1319603576.88.0.28449612048.issue13161@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/issue13161>
_______________________________________

From report at bugs.python.org  Wed Oct 26 08:03:21 2011
From: report at bugs.python.org (Petri Lehtinen)
Date: Wed, 26 Oct 2011 06:03:21 +0000
Subject: [docs] [issue13211] urllib2.HTTPError does not have 'reason'
	attribute.
In-Reply-To: <1318943168.93.0.520705450261.issue13211@psf.upfronthosting.co.za>
Message-ID: <1319609001.29.0.984494426255.issue13211@psf.upfronthosting.co.za>


Petri Lehtinen <petri at digip.org> added the comment:

> It appears the Python 3.2 docs no longer include documentation for URLError

Both URLError and HTTPError are documented in 3.2 and 3.3:

http://docs.python.org/py3k/library/urllib.error.html#urllib.error.URLError

http://docs.python.org/dev/library/urllib.error.html#urllib.error.URLError

It needs to be investigated whether each point raising a HTTPError sets a good msg. If this is the case, reason can be aliased to msg.

This could be done for 2.7, too, because this is a bug (deviation from what the documentation says) rather than a new feature.

----------
keywords: +easy
nosy: +petri.lehtinen
stage:  -> needs patch

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

From report at bugs.python.org  Wed Oct 26 11:04:39 2011
From: report at bugs.python.org (Jason R. Coombs)
Date: Wed, 26 Oct 2011 09:04:39 +0000
Subject: [docs] [issue13211] urllib2.HTTPError does not have 'reason'
	attribute.
In-Reply-To: <1318943168.93.0.520705450261.issue13211@psf.upfronthosting.co.za>
Message-ID: <1319619879.58.0.237988374692.issue13211@psf.upfronthosting.co.za>


Jason R. Coombs <jaraco at jaraco.com> added the comment:

I scanned through the libs for Python 2.7, 3.2, and 3.3 and there is no construction of HTTPError that does not pass a string for msg. I believe it would be reasonable to alias reason to msg. I'll put together the changesets.

----------

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

From report at bugs.python.org  Wed Oct 26 13:06:24 2011
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 26 Oct 2011 11:06:24 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <E1RJ1JJ-0004Nn-NH@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 0b4df6701c4d by Nick Coghlan in branch '2.7':
Issue #13237: further updates to subprocess documentation
http://hg.python.org/cpython/rev/0b4df6701c4d

----------

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

From report at bugs.python.org  Wed Oct 26 13:16:11 2011
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 26 Oct 2011 11:16:11 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <E1RJ1Sn-00057F-PI@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset f445c125aca3 by Nick Coghlan in branch '2.7':
Issue #13237: remove some details that only apply to the 3.x version of this module and cross reference the relocated warning about the dangers of invoking the shell with untrusted input
http://hg.python.org/cpython/rev/f445c125aca3

----------

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

From report at bugs.python.org  Wed Oct 26 13:19:02 2011
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 26 Oct 2011 11:19:02 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319627942.67.0.613222649965.issue13237@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Absent any further feedback, I think I'm done with the changes to the 2.7 subprocess docs. I'll let them sit for a few days, then do the forward port to 3.2 and default.

There are a couple of additional changes I'll add to the 3.x versions:
- mention redirecting to DEVNULL as a way of suppressing output when using call() and check_call()
- mention the UTF-8 assumption involved in using the universal newlines mode for pipes in 3.x (i.e. the stuff I mistakenly checked in to 2.7 and then reverted)

----------

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

From report at bugs.python.org  Wed Oct 26 13:34:45 2011
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 26 Oct 2011 11:34:45 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <E1RJ1kk-0006oe-Nc@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 5dfe6d7f7c61 by Nick Coghlan in branch '2.7':
Issue #13237: fix typo
http://hg.python.org/cpython/rev/5dfe6d7f7c61

----------

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

From report at bugs.python.org  Wed Oct 26 18:13:11 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 26 Oct 2011 16:13:11 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319645591.02.0.949782576852.issue13237@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

I want to review the doc, but lack time right now.  For example, one function signature in your patch uses keyword-only arguments but 2.7 doesn?t support them.

----------

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

From zwegner at gmail.com  Tue Oct 25 01:25:28 2011
From: zwegner at gmail.com (Zach Wegner)
Date: Mon, 24 Oct 2011 18:25:28 -0500
Subject: [docs] documentation error w/ associativity
Message-ID: <CAF=CVUL-FoZg39mjcbpmiSw2mTfszO1t-jhDJ-ko=KnJkx2dYA@mail.gmail.com>

The operator precedence table given at the bottom of
http://docs.python.org/reference/expressions.html says that all
expressions have left associativity, except for comparisons, which
chain, and exponentiation, which has right associativity. However,
conditional expressions also have right associativity:

>>> 'a' if 1 else 'b' if 0 else 'c'
'a'

>>> import ast
>>> ast.dump(ast.parse("'a' if 1 else 'b' if 0 else 'c'"))
"Module(body=[Expr(value=IfExp(test=Num(n=1), body=Str(s='a'), orelse=IfExp(test
=Num(n=0), body=Str(s='b'), orelse=Str(s='c'))))])"

Thanks,
Zach

From suman.saha51 at gmail.com  Wed Oct 26 07:40:50 2011
From: suman.saha51 at gmail.com (Suman Saha)
Date: Wed, 26 Oct 2011 11:10:50 +0530
Subject: [docs] Thank You
Message-ID: <4EA79D62.2060009@gmail.com>

  Respected sir/madam,

This is to thank you for releasing such an extensive documentation for 
python.

I hope it will go miles in benifitting all those who wish to learn the 
language.

Thanking You

Yours truly
Suman Saha
Kolkata, India

From joelmontes01 at gmail.com  Wed Oct 26 18:48:52 2011
From: joelmontes01 at gmail.com (Joel Montes de Oca)
Date: Wed, 26 Oct 2011 12:48:52 -0400
Subject: [docs] GUI building with Python
Message-ID: <4EA839F4.3010008@gmail.com>

Hello folks!

First, I would like to say, great job on the documentation! I love it.

The reason I am emailing you good people is to see if there's any chance 
that the Python documentation team may write a tutorial on how to build 
GUIs with Python.

I know there's a hundred programs out there to build GUIs and writing 
one tutorial for one program would be inefficient but can at least the 
concept of using GUIs with Python be written about?

My current issue:

I have enough Python under my belt where I can build very small/simple 
programs. I want to build a GUI for these programs but the documentation 
on how to do this is either overly complicated or not clear enough..

I wish there were a tutorial that teaches how to build a 1 window 
application with 1 button that when the user clicks it, it will display 
a message that says, "Hello World!" Something like this will include all 
of the basic knowledge for creating the GUI files and using Python to 
call them up...

Maybe another simple tutorial can be something like a calculator that 
adds two numbers and spits out the sum. Simple stuff..

When I Google for Glade tutorials I find out-of-date tutorials that 
cover a program that is fairly complicated with a lot of focus on coding 
instead of the basics: Creating the GUI files, Using Python to call and 
load those files, passing signals, etc.

So.. Is there any chance a basic tutorial on GUIs with Python may be 
made for us noobs? :)

Thanks,

Joel Montes de Oca


From report at bugs.python.org  Wed Oct 26 22:48:49 2011
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 26 Oct 2011 20:48:49 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319645591.02.0.949782576852.issue13237@psf.upfronthosting.co.za>
Message-ID: <CADiSq7e1fxy3uCjLTfDfqUvUwyJn792=_42XF8MXEqbXqdVspQ@mail.gmail.com>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

That's deliberate, as I'm only showing a selected subset of the full
signature at that point and using the subprocess API's with positional
arguments would lead to almost incomprehensible code. I'm not in any great
hurry to forward port though, so I'm happy to wait until you get a chance to
review the changes.

----------

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

From report at bugs.python.org  Wed Oct 26 23:15:50 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Wed, 26 Oct 2011 21:15:50 +0000
Subject: [docs] [issue13270] all classes are new style
Message-ID: <1319663750.31.0.916391635164.issue13270@psf.upfronthosting.co.za>


New submission from Florent Xicluna <florent.xicluna at gmail.com>:

these last references to old/new classes should be dropped.
See patch.

----------
assignee: docs at python
components: Documentation
files: all_classes_belong_to_new_style.diff
keywords: patch
messages: 146455
nosy: docs at python, flox
priority: normal
severity: normal
stage: patch review
status: open
title: all classes are new style
type: behavior
versions: Python 3.2, Python 3.3
Added file: http://bugs.python.org/file23530/all_classes_belong_to_new_style.diff

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

From report at bugs.python.org  Thu Oct 27 05:51:09 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 27 Oct 2011 03:51:09 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319687468.97.0.364363368029.issue13237@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

I think ?ric is referring to the foo(bar, *, baz=None) syntax.  In 2.7 you can drop the '*' and still leave only the keyword arguments that you think are more useful.
I also see that you converted a few examples to use shell=True, but afaiu that should be avoided (even if the input is trusted, it can be a bad example and lead to escaping issues).
For the 'exit 1' example you could add a note saying that the example is run with shell=True because 'exit' requires a shell, or just keep the more verbose Python version.
My concern is that many people just go trough the examples and copy/paste what they see without reading the text around unless it's necessary to make the command work, so, if many examples use shell=True, they might end up picking one of those.

----------

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

From report at bugs.python.org  Thu Oct 27 09:30:57 2011
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 27 Oct 2011 07:30:57 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319700657.32.0.0489285752463.issue13237@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

We can only protect people from themselves so much - "shell=True" is invaluable when you actually want to invoke the shell, and the shell has much better tools for process invocation and pipeline processing than Python does (since shells are, in effect, domain specific languages dedicated to those tasks).

If someone is blindly copying and pasting code from the internet, then shell injection attacks are likely to be the *least* of the security problems in anything they're building.

The point of the examples is to demonstrate the return code handling and using the shell is the easiest way to do that. I'll add a note to the docstrings to be aware of the security issues with the parameter, though.

As far as the keyword arguments go, no, I can't just drop the bare '*' from the abbreviated signature, because that would be making claims about the signature that are just plain *wrong* (there are other positional arguments that appear before 'stdin'). I'll add a note explaining that point somewhere in the 2.7 version, though.

----------

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

From report at bugs.python.org  Thu Oct 27 09:55:49 2011
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 27 Oct 2011 07:55:49 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <E1RJKoR-000422-Eh@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 2a2df6a72ccb by Nick Coghlan in branch '2.7':
Issue #13237: Make the subprocess convenience helper documentation self-contained aside from the shared parameter description. Downgrade the pipe warnings at that level to notes (since those pipes are hidden, people are unlikely to even try it)
http://hg.python.org/cpython/rev/2a2df6a72ccb

----------

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

From report at bugs.python.org  Thu Oct 27 10:06:27 2011
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 27 Oct 2011 08:06:27 +0000
Subject: [docs] [issue13237] subprocess docs should emphasise convenience
	functions
In-Reply-To: <1319174702.47.0.36912184976.issue13237@psf.upfronthosting.co.za>
Message-ID: <1319702787.71.0.114868395611.issue13237@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

As the last checkin message says, I've made the documentation for the helper functions more self-contained. Each now has its own short "shell=True" warning with a pointer to the full explanation in the shared parameter description. There was also a copy-and-paste error in the Popen docs where the cross-reference for "shell=True" was a note rather than a warning, so I fixed that.

For the helper functions, people are unlikely to pass in "stdout=PIPE" or "stderr=PIPE" in the first place, since there's no point (you can't get at the Popen object, so you can't at the streams in order to read from them). Accordingly, I downgraded the relevant boxes to be notes rather than warnings (the boxes down near Popen.wait() and the data attribute descriptions remain warnings).

The latest version also uses the "keyword only" syntax for all three helper functions, but describes them with the following text in each case:

=========
The arguments shown above are merely the most common ones, described below in :ref:`frequently-used-arguments` (hence the slightly odd notation in the abbreviated signature).
=========

For 3.x, I'll reword that to:

=========
The arguments shown above are merely the most common ones, described below in :ref:`frequently-used-arguments` (hence the use of keyword only argument notation in the abbreviated signature).
=========

----------

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

From report at bugs.python.org  Thu Oct 27 12:05:59 2011
From: report at bugs.python.org (Alexey Shamrin)
Date: Thu, 27 Oct 2011 10:05:59 +0000
Subject: [docs] [issue13275] Recommend xml.etree for XML processing
Message-ID: <1319709959.84.0.984784684468.issue13275@psf.upfronthosting.co.za>


New submission from Alexey Shamrin <shamrin at gmail.com>:

There are many libraries in Python stdlib [1]

xml.dom
xml.dom.minidom
xml.dom.pulldom
xml.sax
xml.etree

Tutorial mentions xml.dom and xml.sax. [2]

In my experience xml.etree is the best library to quickly load some xml and mess with it. It would be nice to recommend people xml.etree in the tutorial [2] and in the beginning of section 19, "Structured Markup Processing Tools". [1]

[1]: http://docs.python.org/library/markup.html
[2]: http://docs.python.org/tutorial/stdlib.html#batteries-included

----------
assignee: docs at python
components: Documentation
messages: 146484
nosy: ash, docs at python
priority: normal
severity: normal
status: open
title: Recommend xml.etree for XML processing

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

From report at bugs.python.org  Thu Oct 27 12:16:37 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Thu, 27 Oct 2011 10:16:37 +0000
Subject: [docs] [issue13275] Recommend xml.etree for XML processing
In-Reply-To: <1319709959.84.0.984784684468.issue13275@psf.upfronthosting.co.za>
Message-ID: <1319710597.83.0.0923079084956.issue13275@psf.upfronthosting.co.za>


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


----------
components: +XML
type:  -> behavior
versions: +Python 2.7, Python 3.2, Python 3.3

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

From report at bugs.python.org  Thu Oct 27 12:16:49 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Thu, 27 Oct 2011 10:16:49 +0000
Subject: [docs] [issue13275] Recommend xml.etree for XML processing
In-Reply-To: <1319709959.84.0.984784684468.issue13275@psf.upfronthosting.co.za>
Message-ID: <1319710609.43.0.266750718699.issue13275@psf.upfronthosting.co.za>


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


----------
nosy: +flox

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

From report at bugs.python.org  Thu Oct 27 14:28:56 2011
From: report at bugs.python.org (Petri Lehtinen)
Date: Thu, 27 Oct 2011 12:28:56 +0000
Subject: [docs] [issue13275] Recommend xml.etree for XML processing
In-Reply-To: <1319709959.84.0.984784684468.issue13275@psf.upfronthosting.co.za>
Message-ID: <1319718536.25.0.600487861032.issue13275@psf.upfronthosting.co.za>


Changes by Petri Lehtinen <petri at digip.org>:


----------
nosy: +petri.lehtinen

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

From report at bugs.python.org  Thu Oct 27 17:44:20 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 27 Oct 2011 15:44:20 +0000
Subject: [docs] [issue13275] Recommend xml.etree for XML processing
In-Reply-To: <1319709959.84.0.984784684468.issue13275@psf.upfronthosting.co.za>
Message-ID: <1319730260.53.0.431545944737.issue13275@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

It makes sense that SAX and DOM would be mentioned in the tutorial: SAX is similar to how HTMLParser works and is used in many languages; DOM is the official W3C API and is used in many languages, despite its ugliness.  ElementTree is not a very elegant API in my opinion, but the majority seems to disagree as it was included in Python 2.5, so I wouldn?t object to a one-line edition in the doc to suggest it.

If you?d like to work on a doc patch, here are guidelines:
http://docs.python.org/documenting
http://docs.python.org/devguide

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

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

From report at bugs.python.org  Thu Oct 27 17:46:25 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 27 Oct 2011 15:46:25 +0000
Subject: [docs] [issue13275] Recommend xml.etree for XML processing
In-Reply-To: <1319709959.84.0.984784684468.issue13275@psf.upfronthosting.co.za>
Message-ID: <1319730385.92.0.385915698378.issue13275@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/issue13275>
_______________________________________

From report at bugs.python.org  Thu Oct 27 17:47:57 2011
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 27 Oct 2011 15:47:57 +0000
Subject: [docs] [issue13270] all classes are new style
In-Reply-To: <1319663750.31.0.916391635164.issue13270@psf.upfronthosting.co.za>
Message-ID: <1319730477.39.0.946583559866.issue13270@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

LGTM.

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

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

From report at bugs.python.org  Thu Oct 27 18:40:07 2011
From: report at bugs.python.org (Senthil Kumaran)
Date: Thu, 27 Oct 2011 16:40:07 +0000
Subject: [docs] [issue13277] tzinfo subclasses information
Message-ID: <1319733607.49.0.8093265907.issue13277@psf.upfronthosting.co.za>


New submission from Senthil Kumaran <senthil at uthcode.com>:

This was in the docs mailing list, not translated to bug report

Paul Koning wrote:

Section 8.1.6 of the library manual talks about utcoffset(dt)-dst(dt) as the "standard offset" and says that this should not depend on the date or +time but only on the location.

This is not true as there cases were certain locations changed the time offsets as per their convenience. 

It is either a doc fix to remove that sentence if the datetime.astimezone does not depend upon utcoffset(dt)-dst(dt), or if it does, then it is a code fix.

----------
assignee: docs at python
messages: 146501
nosy: docs at python, orsenthil
priority: normal
severity: normal
stage: needs patch
status: open
title: tzinfo subclasses information
type: behavior

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

From report at bugs.python.org  Thu Oct 27 18:53:43 2011
From: report at bugs.python.org (Senthil Kumaran)
Date: Thu, 27 Oct 2011 16:53:43 +0000
Subject: [docs] [issue13211] urllib2.HTTPError does not have 'reason'
	attribute.
In-Reply-To: <1318943168.93.0.520705450261.issue13211@psf.upfronthosting.co.za>
Message-ID: <1319734423.92.0.68332976915.issue13211@psf.upfronthosting.co.za>


Changes by Senthil Kumaran <senthil at uthcode.com>:


----------
nosy: +orsenthil

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

From report at bugs.python.org  Thu Oct 27 18:58:16 2011
From: report at bugs.python.org (Jeffrey Finkelstein)
Date: Thu, 27 Oct 2011 16:58:16 +0000
Subject: [docs] [issue13278] Typo in documentation for sched module
Message-ID: <1319734696.41.0.842696728904.issue13278@psf.upfronthosting.co.za>


New submission from Jeffrey Finkelstein <jeffrey.finkelstein at gmail.com>:

In the documentation for the sched.scheduler.enter() function, change the phrase "Other then the relative time" to "Other than the relative time" (i.e. change "then" to "than").

----------
assignee: docs at python
components: Documentation
messages: 146506
nosy: docs at python, jfinkels
priority: normal
severity: normal
status: open
title: Typo in documentation for sched module
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Thu Oct 27 18:58:52 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 27 Oct 2011 16:58:52 +0000
Subject: [docs] [issue13278] Typo in documentation for sched module
In-Reply-To: <1319734696.41.0.842696728904.issue13278@psf.upfronthosting.co.za>
Message-ID: <1319734732.09.0.452354640288.issue13278@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti
versions:  -Python 2.6, Python 3.1, Python 3.4

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

From report at bugs.python.org  Fri Oct 28 05:11:21 2011
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 28 Oct 2011 03:11:21 +0000
Subject: [docs] [issue13270] all classes are new style
In-Reply-To: <1319663750.31.0.916391635164.issue13270@psf.upfronthosting.co.za>
Message-ID: <1319771480.92.0.903264498068.issue13270@psf.upfronthosting.co.za>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Removed the newstyle/oldstyle comments is fine.  I don't see the reason for the type->class change though.

----------
nosy: +rhettinger

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

From report at bugs.python.org  Fri Oct 28 07:25:39 2011
From: report at bugs.python.org (Petri Lehtinen)
Date: Fri, 28 Oct 2011 05:25:39 +0000
Subject: [docs] [issue13277] tzinfo subclasses information
In-Reply-To: <1319733607.49.0.8093265907.issue13277@psf.upfronthosting.co.za>
Message-ID: <1319779539.67.0.161703520457.issue13277@psf.upfronthosting.co.za>


Changes by Petri Lehtinen <petri at digip.org>:


----------
nosy: +petri.lehtinen

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

From report at bugs.python.org  Fri Oct 28 07:26:15 2011
From: report at bugs.python.org (Petri Lehtinen)
Date: Fri, 28 Oct 2011 05:26:15 +0000
Subject: [docs] [issue13278] Typo in documentation for sched module
In-Reply-To: <1319734696.41.0.842696728904.issue13278@psf.upfronthosting.co.za>
Message-ID: <1319779575.73.0.0854124586139.issue13278@psf.upfronthosting.co.za>


Changes by Petri Lehtinen <petri at digip.org>:


----------
nosy: +petri.lehtinen

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

From report at bugs.python.org  Fri Oct 28 10:57:03 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Fri, 28 Oct 2011 08:57:03 +0000
Subject: [docs] [issue13270] all classes are new style
In-Reply-To: <1319663750.31.0.916391635164.issue13270@psf.upfronthosting.co.za>
Message-ID: <1319792223.56.0.359213920328.issue13270@psf.upfronthosting.co.za>


Florent Xicluna <florent.xicluna at gmail.com> added the comment:

the type>class change reflects the current output on 3.x

----------

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

From report at bugs.python.org  Fri Oct 28 11:24:04 2011
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 28 Oct 2011 09:24:04 +0000
Subject: [docs] [issue13270] all classes are new style
In-Reply-To: <1319663750.31.0.916391635164.issue13270@psf.upfronthosting.co.za>
Message-ID: <E1RJifL-0004MG-MX@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 54abca0ab03b by Florent Xicluna in branch '3.2':
Fixes #13270: obsolete reference to old-style/new-style classes.
http://hg.python.org/cpython/rev/54abca0ab03b

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

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

From report at bugs.python.org  Fri Oct 28 11:27:34 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Fri, 28 Oct 2011 09:27:34 +0000
Subject: [docs] [issue13270] all classes are new style
In-Reply-To: <1319663750.31.0.916391635164.issue13270@psf.upfronthosting.co.za>
Message-ID: <1319794054.35.0.0464847254834.issue13270@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Oct 28 11:33:52 2011
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 28 Oct 2011 09:33:52 +0000
Subject: [docs] [issue13278] Typo in documentation for sched module
In-Reply-To: <1319734696.41.0.842696728904.issue13278@psf.upfronthosting.co.za>
Message-ID: <E1RJios-0005JN-DD@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 3e72de3c8ad5 by Ezio Melotti in branch '2.7':
#13278: fix typo.
http://hg.python.org/cpython/rev/3e72de3c8ad5

New changeset 9c4b62f67a28 by Ezio Melotti in branch '3.2':
#13278: fix typo.
http://hg.python.org/cpython/rev/9c4b62f67a28

New changeset 64b2efa5009f by Ezio Melotti in branch 'default':
#13278: merge with 3.2.
http://hg.python.org/cpython/rev/64b2efa5009f

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

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

From report at bugs.python.org  Fri Oct 28 11:36:40 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 28 Oct 2011 09:36:40 +0000
Subject: [docs] [issue13278] Typo in documentation for sched module
In-Reply-To: <1319734696.41.0.842696728904.issue13278@psf.upfronthosting.co.za>
Message-ID: <1319794600.62.0.919466478523.issue13278@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Fixed, thanks for the report!

----------
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/issue13278>
_______________________________________

From report at bugs.python.org  Fri Oct 28 12:08:26 2011
From: report at bugs.python.org (wrobell)
Date: Fri, 28 Oct 2011 10:08:26 +0000
Subject: [docs] [issue13282] the table of contents in epub file is too long
Message-ID: <1319796506.79.0.347343158897.issue13282@psf.upfronthosting.co.za>


New submission from wrobell <wrobell at pld-linux.org>:

the table of contents in python documentation epub file is very very long. it takes several long minutes to jump from first page to a part containing language reference toc.

imho it would be great if first page of epub file contained pointers
to tutorial, lang ref, mod ref without detailed table of contents as it is at docs.python.org.

----------
assignee: docs at python
components: Documentation
messages: 146548
nosy: docs at python, wrobell
priority: normal
severity: normal
status: open
title: the table of contents in epub file is too long
versions: Python 2.7, Python 3.2

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

From report at bugs.python.org  Fri Oct 28 14:23:17 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Fri, 28 Oct 2011 12:23:17 +0000
Subject: [docs] [issue13270] all classes are new style
In-Reply-To: <1319663750.31.0.916391635164.issue13270@psf.upfronthosting.co.za>
Message-ID: <1319804597.47.0.757469167662.issue13270@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Oct 28 16:14:14 2011
From: report at bugs.python.org (Jeffrey Finkelstein)
Date: Fri, 28 Oct 2011 14:14:14 +0000
Subject: [docs] [issue13278] Typo in documentation for sched module
In-Reply-To: <1319794600.62.0.919466478523.issue13278@psf.upfronthosting.co.za>
Message-ID: <CAHz=fgB4OHEdRjuDMK=dkm7yygQYRuwd59WdyA4J+27bBRUtrg@mail.gmail.com>


Jeffrey Finkelstein <jeffrey.finkelstein at gmail.com> added the comment:

Thank you for the great work, Python project!

On Fri, Oct 28, 2011 at 5:36 AM, Ezio Melotti <report at bugs.python.org> wrote:
>
> Ezio Melotti <ezio.melotti at gmail.com> added the comment:
>
> Fixed, thanks for the report!
>
> ----------
> 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/issue13278>
> _______________________________________
>

----------

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

From report at bugs.python.org  Fri Oct 28 16:18:50 2011
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 28 Oct 2011 14:18:50 +0000
Subject: [docs] [issue13286] PEP 3151 breaks backward compatibility: it
	should be	documented
Message-ID: <1319811530.69.0.689775391155.issue13286@psf.upfronthosting.co.za>


New submission from STINNER Victor <victor.stinner at haypocalc.com>:

The following example works on Python 2.7 and 3.2, but fails on Python 3.3:
-----------
import errno
import os

try:
    os.rmdir("testdir")
except:
    pass
os.mkdir("testdir")

try:
    try:
        os.mkdir("testdir")
    except IOError as exc:
        # If can't get proper access, then just forget about writing
        # the data.
        if exc.errno == errno.EACCES:
            pass
        else:
            raise
    except OSError as exc:
        # Probably another Python process already created the dir.
        if exc.errno == errno.EEXIST:
            pass
        else:
            raise
except Exception:
    print("PEP 3151 broke backward compatibility on such pattern!")
-----------

I noticed the problem while reading the changeset e4d44c2e8e81.

----------
assignee: docs at python
components: Documentation
messages: 146562
nosy: docs at python, flox, haypo, pitrou
priority: normal
severity: normal
status: open
title: PEP 3151 breaks backward compatibility: it should be documented
versions: Python 3.3

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

From report at bugs.python.org  Fri Oct 28 16:24:35 2011
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 28 Oct 2011 14:24:35 +0000
Subject: [docs] [issue13286] PEP 3151 breaks backward compatibility: it
	should be	documented
In-Reply-To: <1319811530.69.0.689775391155.issue13286@psf.upfronthosting.co.za>
Message-ID: <1319811875.51.0.601383944396.issue13286@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

Why would you catch IOError after os.mkdir()?

----------

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

From report at bugs.python.org  Fri Oct 28 16:32:53 2011
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 28 Oct 2011 14:32:53 +0000
Subject: [docs] [issue13286] PEP 3151 breaks backward compatibility: it
	should be	documented
In-Reply-To: <1319811530.69.0.689775391155.issue13286@psf.upfronthosting.co.za>
Message-ID: <1319812373.27.0.956000617592.issue13286@psf.upfronthosting.co.za>


STINNER Victor <victor.stinner at haypocalc.com> added the comment:

The first example was extracted from Lib/importlib/_bootstrap.py. The code was maybe wrong, I don't know.

Another example:
----------------------
import errno
import os

try:
    os.rmdir("testdir")
except:
    pass
os.mkdir("testdir")

try:
    try:
        #os.mkdir("testdir")
        open("NOT EXISTING FILENAME")
    except OSError as exc:
        if exc.errno == errno.EEXIST:
            pass
        else:
            raise
    except IOError as exc:
        if exc.errno == errno.ENOENT:
            pass
        else:
            raise
except Exception:
    raise
    print("PEP 3151 broke backward compatibility on such pattern!")
----------------------

Uncomment mkdir() to test both paths.

----------

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

From report at bugs.python.org  Fri Oct 28 22:55:48 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Fri, 28 Oct 2011 20:55:48 +0000
Subject: [docs] [issue13286] PEP 3151 breaks backward compatibility: it
	should be	documented
In-Reply-To: <1319811530.69.0.689775391155.issue13286@psf.upfronthosting.co.za>
Message-ID: <1319835348.83.0.293783617184.issue13286@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Oct 29 02:24:19 2011
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 29 Oct 2011 00:24:19 +0000
Subject: [docs] [issue13275] Recommend xml.etree for XML processing
In-Reply-To: <1319709959.84.0.984784684468.issue13275@psf.upfronthosting.co.za>
Message-ID: <1319847859.26.0.0404629548836.issue13275@psf.upfronthosting.co.za>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

In the tutorial, "The xml.dom and xml.sax packages" should be expanded to "The xml.dom, xml.sax, and xml.etree packages". I suspect that the current line predates the addition of .etree.

We try to mostly not give opinion-based recommendations; the docs are for facts. Some people recommend using lxml instead of any of the above ;-).

"The documentation for the xml.dom and xml.sax packages are the definition of the Python bindings for the DOM and SAX interfaces."

could be followed by a factual sentence like "xml.etree provides an  third alternative."

Looking more: the intro to 19.6. xml.dom ? The Document Object Model API nicely explains the difference between SAX and DOM processing as sequential versus random access. The intro to 19.13. xml.etree.ElementTree ? The ElementTree XML API says nothing about how it compares to the others. Perhaps the sentence should be "xml.etree provides a tree-based interface different from xml.dom." (assuming this is a fact). Make your suggestion.

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

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

From report at bugs.python.org  Sat Oct 29 05:07:07 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Sat, 29 Oct 2011 03:07:07 +0000
Subject: [docs] [issue9708] cElementTree iterparse does not support "parser"
	argument
In-Reply-To: <1283032296.54.0.54816594665.issue9708@psf.upfronthosting.co.za>
Message-ID: <1319857627.45.0.497540717981.issue9708@psf.upfronthosting.co.za>


Florent Xicluna <florent.xicluna at gmail.com> added the comment:

Documentation should be fixed for 3.2 and 2.7.
Patch welcomed.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
stage: test needed -> needs patch

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

From dpb at donbennett.org  Wed Oct 26 20:15:16 2011
From: dpb at donbennett.org (Don Bennett)
Date: Wed, 26 Oct 2011 11:15:16 -0700
Subject: [docs] Small docs wording problem in sqlite3 module docs
Message-ID: <CAO1ZGb=m1y=DNAaYeP1v7bMsrrp+=SCSX7zh1F3wpS=EPSZxoA@mail.gmail.com>

On the page:
http://docs.python.org/library/sqlite3.html#module-sqlite3
in section 11.13.7.3,
It says:

# con.rollback() is called after the with block finishes with an
exception, the# exception is still raised and must be catched

The phrase "and must be catched" should be changed to "and must be caught" .

Thanks, -Don
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111026/58465846/attachment.html>

From tt.ren.cn at gmail.com  Fri Oct 28 02:25:00 2011
From: tt.ren.cn at gmail.com (tt ren)
Date: Fri, 28 Oct 2011 08:25:00 +0800
Subject: [docs] python tutorial ebook
Message-ID: <CAOS4J2n9M2pakGgFa8tpbSru0rRSPBMK8BqMKDOkfgA5OMyFXQ@mail.gmail.com>

hi, i am a new learner of python. is there any way i could acquire this
python tutorial EBOOK in the form of PDF or just common text? thank you so
much. i will read it on my cellphone.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111028/4367f7fd/attachment.html>

From famihug at gmail.com  Sat Oct 29 04:32:31 2011
From: famihug at gmail.com (Viet Hung Nguyen)
Date: Sat, 29 Oct 2011 09:32:31 +0700
Subject: [docs] Bug in email-examples
Message-ID: <CACgfMB4YXEnk+eVpJCR3FA98_J-zdDVQL=sXCX4fbSfN7HMuvw@mail.gmail.com>

hi, I found this bug in using MIME example

http://docs.python.org/library/email-examples.html

Here?s an example of how to send a MIME message containing a bunch of family
pictures that may be residing in a directory:
...

for file in pngfiles:
>     # Open the files in binary mode.  Let the MIMEImage class automatically
>
there is no pngfiles before this LOC

-- 
Thanks & Best regards,
Nguy?n Vi?t H?ng (Mr)
My blog: http://hvn.familug.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111029/579542e2/attachment.html>

From report at bugs.python.org  Sat Oct 29 17:58:21 2011
From: report at bugs.python.org (=?utf-8?q?Charles-Fran=C3=A7ois_Natali?=)
Date: Sat, 29 Oct 2011 15:58:21 +0000
Subject: [docs] [issue12760] Add create mode to open()
In-Reply-To: <1313502559.06.0.415498401391.issue12760@psf.upfronthosting.co.za>
Message-ID: <1319903901.43.0.632166989505.issue12760@psf.upfronthosting.co.za>


Changes by Charles-Fran?ois Natali <neologix at free.fr>:


----------
resolution:  -> duplicate
status: open -> closed
superseder:  -> io.FileIO and io.open should support openat

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

From report at bugs.python.org  Sat Oct 29 20:37:54 2011
From: report at bugs.python.org (Petri Lehtinen)
Date: Sat, 29 Oct 2011 18:37:54 +0000
Subject: [docs] [issue12761] Typo in Doc/license.rst
In-Reply-To: <1313512901.16.0.106548527378.issue12761@psf.upfronthosting.co.za>
Message-ID: <1319913474.64.0.101376740493.issue12761@psf.upfronthosting.co.za>


Changes by Petri Lehtinen <petri at digip.org>:


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

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

From report at bugs.python.org  Sun Oct 30 12:52:13 2011
From: report at bugs.python.org (Florent Xicluna)
Date: Sun, 30 Oct 2011 11:52:13 +0000
Subject: [docs] [issue13292] missing versionadded for bytearray
Message-ID: <1319975533.88.0.431386848219.issue13292@psf.upfronthosting.co.za>


New submission from Florent Xicluna <florent.xicluna at gmail.com>:

versionadded is missing here:
http://docs.python.org/library/functions.html#bytearray

----------
assignee: docs at python
components: Documentation
messages: 146633
nosy: docs at python, flox
priority: normal
severity: normal
stage: needs patch
status: open
title: missing versionadded for bytearray
type: behavior
versions: Python 2.7

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

From report at bugs.python.org  Sun Oct 30 14:01:53 2011
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 30 Oct 2011 13:01:53 +0000
Subject: [docs] [issue13277] tzinfo subclasses information
In-Reply-To: <1319733607.49.0.8093265907.issue13277@psf.upfronthosting.co.za>
Message-ID: <1319979713.69.0.204239244942.issue13277@psf.upfronthosting.co.za>


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


----------
nosy: +belopolsky, lemburg

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

From sandro.tosi at gmail.com  Mon Oct 31 02:09:16 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Mon, 31 Oct 2011 02:09:16 +0100
Subject: [docs] Thank You
In-Reply-To: <4EA79D62.2060009@gmail.com>
References: <4EA79D62.2060009@gmail.com>
Message-ID: <CAPdtAj0SPBeQTjt9u9=32XkzNydA1A=CMNGhBVoze8MF1ACMeg@mail.gmail.com>

Hello Suman,

On Wed, Oct 26, 2011 at 07:40, Suman Saha <suman.saha51 at gmail.com> wrote:
> ?Respected sir/madam,
>
> This is to thank you for releasing such an extensive documentation for
> python.
>
> I hope it will go miles in benifitting all those who wish to learn the
> language.

Thanks for your kind words: it's always a pleasure knowing your work
is valuable to others.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Mon Oct 31 02:15:54 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Mon, 31 Oct 2011 02:15:54 +0100
Subject: [docs] python tutorial ebook
In-Reply-To: <CAOS4J2n9M2pakGgFa8tpbSru0rRSPBMK8BqMKDOkfgA5OMyFXQ@mail.gmail.com>
References: <CAOS4J2n9M2pakGgFa8tpbSru0rRSPBMK8BqMKDOkfgA5OMyFXQ@mail.gmail.com>
Message-ID: <CAPdtAj2GVTuQbbVQaKDJr0Xa1hRb9Qu8WrZFSOa+5x-F9BMzUA@mail.gmail.com>

Hello,

On Fri, Oct 28, 2011 at 02:25, tt ren <tt.ren.cn at gmail.com> wrote:
> hi, i am a new learner of python. is there any way i could acquire this
> python tutorial EBOOK in the form of PDF or just common text? thank you so
> much. i will read it on my cellphone.

The same docs you can find at:

    http://docs.python.org/
    http://docs.python.org/py3k/

is also available for off-line reading at these addresses:

    http://docs.python.org/download.html
    http://docs.python.org/py3k/download.html

In the zip files you'll find a set of PDFs, one for each part of the
documentation. For Python3 you'll also be able to download an EPUB
version of the documentation.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Mon Oct 31 02:44:43 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Mon, 31 Oct 2011 02:44:43 +0100
Subject: [docs] Small docs wording problem in sqlite3 module docs
In-Reply-To: <CAO1ZGb=m1y=DNAaYeP1v7bMsrrp+=SCSX7zh1F3wpS=EPSZxoA@mail.gmail.com>
References: <CAO1ZGb=m1y=DNAaYeP1v7bMsrrp+=SCSX7zh1F3wpS=EPSZxoA@mail.gmail.com>
Message-ID: <CAPdtAj0-VTR_P5PAe4E0OB8o_3h0Lcq6g7gDpDmKvoOCy7wmsw@mail.gmail.com>

Hello Don,
thanks for your email.

On Wed, Oct 26, 2011 at 20:15, Don Bennett <dpb at donbennett.org> wrote:
> On the page:
> http://docs.python.org/library/sqlite3.html#module-sqlite3
> in section 11.13.7.3,
> It says:
>
> # con.rollback() is called after the with block finishes with an exception,
> the
> # exception is still raised and must be catched
>
> The phrase "and must be catched" should be changed to "and must be caught" .

You're right, and it's now been fixed in
http://hg.python.org/cpython/rev/66c16de4ab9d (and others).

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Mon Oct 31 02:50:48 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Mon, 31 Oct 2011 02:50:48 +0100
Subject: [docs] Bug in email-examples
In-Reply-To: <CACgfMB4YXEnk+eVpJCR3FA98_J-zdDVQL=sXCX4fbSfN7HMuvw@mail.gmail.com>
References: <CACgfMB4YXEnk+eVpJCR3FA98_J-zdDVQL=sXCX4fbSfN7HMuvw@mail.gmail.com>
Message-ID: <CAPdtAj20kEtgwVk+p+Desu-5KUg3Xwi73sSA1yrCY8PVi4pJdQ@mail.gmail.com>

Hello,

On Sat, Oct 29, 2011 at 04:32, Viet Hung Nguyen <famihug at gmail.com> wrote:
> hi, I found this bug in using MIME example
>
> http://docs.python.org/library/email-examples.html
>
> Here?s an example of how to send a MIME message containing a bunch of family
> pictures that may be residing in a directory:
>
> ...
>
>> for file in pngfiles:
>> ??? # Open the files in binary mode.? Let the MIMEImage class
>> automatically
>
> there is no pngfiles before this LOC

You're right about that, but I think it's some kind of "meta-example":
like for 'me' and 'family', they are not defined, but they clearly
speak for themselves what they contain (a list of png file names, the
address of the sender or the address of the family).

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Mon Oct 31 02:55:48 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Mon, 31 Oct 2011 02:55:48 +0100
Subject: [docs] GUI building with Python
In-Reply-To: <4EA839F4.3010008@gmail.com>
References: <4EA839F4.3010008@gmail.com>
Message-ID: <CAPdtAj0ihAWbo6ck_1qeM-j8p60a7vdb-gz8nRQ0oAhpAcdj7w@mail.gmail.com>

Hello Joel,

On Wed, Oct 26, 2011 at 18:48, Joel Montes de Oca
<joelmontes01 at gmail.com> wrote:
> Hello folks!
>
> First, I would like to say, great job on the documentation! I love it.

Thanks!

> The reason I am emailing you good people is to see if there's any chance
> that the Python documentation team may write a tutorial on how to build GUIs
> with Python.

Honestly, I don't think so. The aim of the python documentation is to
document the python language and the standard library. Python already
distributes a simple GUI mechanism: Tkinter.

If you want more, you need to look outside the standard library, and
so also for external documentation. There are tons of very well
written tutorials about GUI designing: choose what's the library you
want to use (f.e. in the linux world, the mail GUI libraries are:
GTK+, QT and WX), and once you define that, go for the GUI designer
ad-hoc for it.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Mon Oct 31 08:41:16 2011
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 31 Oct 2011 07:41:16 +0000
Subject: [docs] [issue13246] Py_UCS4_strlen and friends needn't be public
In-Reply-To: <1319314430.74.0.993573606288.issue13246@psf.upfronthosting.co.za>
Message-ID: <E1RKmUW-0007di-Fz@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 80a7ab9ac29f by Martin v. L?wis in branch 'default':
Drop Py_UCS4_ functions. Closes #13246.
http://hg.python.org/cpython/rev/80a7ab9ac29f

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

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

From sandro.tosi at gmail.com  Mon Oct 31 10:17:26 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Mon, 31 Oct 2011 10:17:26 +0100
Subject: [docs] Turtle graphics, what is the function done doing?
In-Reply-To: <4E9D9316.60008@sztaki.hu>
References: <4E9D9316.60008@sztaki.hu>
Message-ID: <CAPdtAj0n5SOEhv3g0ZGYcOuRZc7nOzLw+pWsNXtL64sm4mx1Gw@mail.gmail.com>

Hello Csaba,

On Tue, Oct 18, 2011 at 16:54, Csaba Szepesvari <szepesva at ualberta.ca> wrote:
> Hi,
>
> Look at the example code at:
> http://docs.python.org/py3k/library/turtle.html#turtle.towards
>
> from turtle import *
> color('red', 'yellow')
> begin_fill()
> while True:
>     forward(200)
>     left(170)
>     if abs(pos()) < 1:
>         break
> end_fill()
> done()
>
> It calls the done() function at the end. However, this function is not
> documented.
> My experimentation shows that this is really coming from the turtle module,
> so it should be documented here.. (or at least pls give some pointer to its
> documentation).

This has now been fixed with these commits:

    http://hg.python.org/cpython/rev/1588b678d634
    http://hg.python.org/cpython/rev/e23baae539f7
    http://hg.python.org/cpython/rev/c7963dff98fa

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Mon Oct 31 11:05:46 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Mon, 31 Oct 2011 11:05:46 +0100
Subject: [docs] filecmp.cmp- confusion allowed by what we do NOT say
In-Reply-To: <E9DBDEA2BCD702468DE88C8E2FF39041F3E022@fpserver.futurepointsystems.com>
References: <E9DBDEA2BCD702468DE88C8E2FF39041F3E022@fpserver.futurepointsystems.com>
Message-ID: <CAPdtAj1CG17em+EcdUnjJ4ftvajDYO-nDJRZ99twzQ0SnF+dYA@mail.gmail.com>

Hello Jim,
I've mentioned your message into http://bugs.python.org/issue1234674
that seems related to the problem you pointed out.

Regards,
Sandro

On Sun, Oct 23, 2011 at 23:32, Jim Peak <jpeak at futurepointsystems.com> wrote:
> Hi!? While tracking down a problem, I came across a source of confusion that
> our docs leave open concerning filecmp.cmp.
>
>
>
> I believe that with the addition of a single sentence, we can resolve it.
>
>
>
> Problem:
>
> Currently, we have the text that's in black font, shown between the lines of
> hyphens, below.? Our text specs what happens when os.stat() signatures are
> equal, but does not spec what happens when they're unequal.
>
>
>
> Because of this, it's easy for readers to assume that unequal os.stat()
> signatures are treated as UNequal: but that's not true:
>
>
>
> Suggested Solution:
>
> I suggest the addition of the sentence (or one like it) in green (and
> italics).
>
>
>
> ---------------------------------------------------
>
> filecmp.cmp(f1,?f2[,?shallow])
>
>
>
> Compare the files named?f1?and?f2, returning?True?if they seem
> equal,?False?otherwise.
>
>
>
> Unless?shallow?is given and is false, files with
> identical?os.stat()?signatures are taken to be equal. When os.stat()
> signatures differ, the contents of files are compared, regardless of the
> value of shallow.
>
> Files that were compared using this function will not be compared again
> unless their?os.stat()signature changes.
>
> Note that no external programs are called from this function, giving it
> portability and efficiency.
>
> ---------------------------------------------------
>
> (taken from the 2.7.2 doc, section 10.5, here:
> http://docs.python.org/library/filecmp.html- but our 3.1.3 doc, in section
> 10.4, reads identically)
>
>
>
>
>
> We're not "technically" incorrect, but people can easily conclude from our
> verbiage that since "identical os.stat() signatures are taken to be equal,"
> that different signatures are taken to be different.? ?See, for example, the
> confusion of the user here:
>
> http://www.velocityreviews.com/forums/t732652-filecmp-cmp-doesnt-seem-to-do-what-it-says-in-the-documentation.html
>
>
>
> Here's another example of confusion.? This is from Doug Hellman's site: he's
> actually written a book on the Std Lib (The Python Standard Library by
> Example), and has another in development, which is quoted here: ?(He knows
> about this being wrong, now: sent him a note just today):
>
> (taken from http://www.doughellmann.com/PyMOTW/filecmp/ )
>
>
>
> By default, cmp() looks only at the information available from os.stat().
> The shallow argument tells cmp() whether to look at the contents of the
> file, as well. The default is to perform a shallow comparison, without
> looking inside the files. Notice that files of the same size created at the
> same time seem to be the same if their contents are not compared.
>
>
>
> I believe that the addition of a single sentence can tighten up our doc to
> help eliminate this confusion / these errors.
>
>
>
> Thanks for all of your work on Python!
>
>
>
> Jim Peak
>
> Software Test Engineer
>
> Future Point Systems, Inc.
>
> (509) 619-2517 cell
>
> _______________________________________________
> docs mailing list
> docs at python.org
> http://mail.python.org/mailman/listinfo/docs
>
>



-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Mon Oct 31 11:22:04 2011
From: report at bugs.python.org (David Townshend)
Date: Mon, 31 Oct 2011 10:22:04 +0000
Subject: [docs] [issue12760] Add create mode to open()
In-Reply-To: <1313502559.06.0.415498401391.issue12760@psf.upfronthosting.co.za>
Message-ID: <1320056524.33.0.982594959643.issue12760@psf.upfronthosting.co.za>


David Townshend <aquavitae69 at gmail.com> added the comment:

I see this has been marked as a duplicate of http://bugs.python.org/issue12797.  Please explain how this is, since that proposal does not appear to provide the functionality discussed here.

----------

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

From report at bugs.python.org  Mon Oct 31 11:32:11 2011
From: report at bugs.python.org (Amaury Forgeot d'Arc)
Date: Mon, 31 Oct 2011 10:32:11 +0000
Subject: [docs] [issue12760] Add create mode to open()
In-Reply-To: <1313502559.06.0.415498401391.issue12760@psf.upfronthosting.co.za>
Message-ID: <1320057131.67.0.966689497472.issue12760@psf.upfronthosting.co.za>


Amaury Forgeot d'Arc <amauryfa at gmail.com> added the comment:

issue12797 would allow things like:

def create_exclusive_file(filename):
  return open(filename, "w",
              opener=lambda path, mode: os.open(path, mode|os.O_CREAT|os.O_EXCL))

----------

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

From report at bugs.python.org  Mon Oct 31 11:42:43 2011
From: report at bugs.python.org (Sandro Tosi)
Date: Mon, 31 Oct 2011 10:42:43 +0000
Subject: [docs] [issue13302] Clarification needed in C API arg parsing
Message-ID: <1320057763.71.0.58387430149.issue13302@psf.upfronthosting.co.za>


New submission from Sandro Tosi <sandro.tosi at gmail.com>:

Hello,
given I can't fully comprehend the user request (sent on docs@ as of http://mail.python.org/pipermail/docs/2011-September/005791.html), I'm just echoing it :

>>>
recently I embedded Python into one of my applications, which included
some string parsing.
In my opinion the doc page about parsing arguments
(http://docs.python.org/c-api/arg.html) is missing the information, that
you must not free the returned const char *, like e.g. said here
(http://docs.python.org/c-api/string.html#PyString_AsString).
It was quite confusing for my first, so I would suggest adding this tiny
bit of information.
<<<

----------
assignee: docs at python
components: Documentation
messages: 146687
nosy: docs at python, sandro.tosi
priority: normal
severity: normal
stage: needs patch
status: open
title: Clarification needed in C API arg parsing
versions: Python 2.7, Python 3.2, Python 3.3

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

From sandro.tosi at gmail.com  Mon Oct 31 11:43:21 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Mon, 31 Oct 2011 11:43:21 +0100
Subject: [docs] Missing information in the C api docs
In-Reply-To: <4E79ED0A.9090008@gmail.com>
References: <4E79ED0A.9090008@gmail.com>
Message-ID: <CAPdtAj3uRhj1BiV7nqsMBx1woGTEMX29bVcV3h+Qe0nMfVXyrg@mail.gmail.com>

Hello Alexander,

On Wed, Sep 21, 2011 at 15:56, Alexander Kauer
<alexanderkauer at googlemail.com> wrote:
> Hello everybody,
>
> recently I embedded Python into one of my applications, which included
> some string parsing.
> In my opinion the doc page about parsing arguments
> (http://docs.python.org/c-api/arg.html) is missing the information, that
> you must not free the returned const char *, like e.g. said here
> (http://docs.python.org/c-api/string.html#PyString_AsString).
> It was quite confusing for my first, so I would suggest adding this tiny
> bit of information.

I don't have any knowledge of C API, so I've just filed
http://bugs.python.org/issue13302 to track your request.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Mon Oct 31 17:18:21 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Mon, 31 Oct 2011 17:18:21 +0100
Subject: [docs] Confusing comment in docs for 3.2.2 section 2.1
In-Reply-To: <CAO-kHFYdU7A18e71bNf1g+iXwft3r56mT+6h-8jcLEpJKCWsmQ@mail.gmail.com>
References: <CAO-kHFYdU7A18e71bNf1g+iXwft3r56mT+6h-8jcLEpJKCWsmQ@mail.gmail.com>
Message-ID: <CAPdtAj37QGa7O5sBeBHFcCKWh_5V25zkv0RC-gnrWzG5GXbSeg@mail.gmail.com>

Hello AJ,

On Mon, Sep 26, 2011 at 14:55, AJ Hill <ajhill007 at gmail.com> wrote:
> To the wonderful folks who look after the Python docs,
>
> There is a confusing comment in the last paragraph of section 2.1, Invoking
> the Python Interpreter, of the 3.2.2 docs.
>
> Here is the page URL:
>
> http://docs.python.org/py3k/tutorial/interpreter.html#invoking-the-interpreter
>
> Here is the text I am referring to:
>
>> When a script file is used, it is sometimes useful to be able to run the
>> script and enter interactive mode afterwards. This can be done by passing -i
>> before the script. (This does not work if the script is read from standard
>> input, for the same reason as explained in the previous paragraph.)
>
> The last sentence refers to the previous paragraph (copied here):
>
>> Some Python modules are also useful as scripts. These can be invoked using
>> python -m module [arg] ..., which executes the source file for module as if
>> you had spelled out its full name on the command line.
>
> I do not see the connection; it does not seem to explain why you can run a
> script and enter interactive mode, but not if the script is included through
> standard input.

That sentence was referring to a paragraph that was removed in the
commit r87523, so I've now removed that line, since it's no more
relevant.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Mon Oct 31 17:19:24 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Mon, 31 Oct 2011 17:19:24 +0100
Subject: [docs] errant documentation in Tutorial Section 2.1 (2.7.2 and
 3.2 are affected)?
In-Reply-To: <CAPhiW4gmJzZaZ1Sjjev9uENcoMY0jaxQ5zN4+YGJmHG9mpk6fw@mail.gmail.com>
References: <CAPhiW4gmJzZaZ1Sjjev9uENcoMY0jaxQ5zN4+YGJmHG9mpk6fw@mail.gmail.com>
Message-ID: <CAPdtAj3jy_prYjyTYNn83eNi-Axkwx7YWBWfHgEw+SoZa6y1bQ@mail.gmail.com>

Hello Aron,

On Tue, Aug 23, 2011 at 13:57, Aron Ahmadia <aron at ahmadia.net> wrote:
> "When a script file is used, it is sometimes useful to be able to run the
> script and enter interactive mode afterwards. This can be done by
> passing?-i?before the script. (This does not work if the script is read from
> standard input, for the same reason as explained in the previous
> paragraph.)"
>
> Reading the previous paragraph doesn't explain why the Python interpreter
> cannot enter interactive mode when a file has replaced stdin, so I am left
> to guess that perhaps it is because once the file has been connected to
> standard input the interpreter can no longer receive input from the user's
> tty.

you're right, that line referred to a paragraph that was removed, so
I've just removed that line too.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Mon Oct 31 17:27:02 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Mon, 31 Oct 2011 17:27:02 +0100
Subject: [docs] Little demo program for curses with Python's Howto
	(lineograph.py)
In-Reply-To: <CAB4nO-x1ZEpK2HhF=OjjHT8zJqCQV5sqcxohyGLTvWof2KdyQA@mail.gmail.com>
References: <CAB4nO-x1ZEpK2HhF=OjjHT8zJqCQV5sqcxohyGLTvWof2KdyQA@mail.gmail.com>
Message-ID: <CAPdtAj1WpCUxLGBjrrrXjeHVH9s7Kf3AhnwsmHS-wFDv9AbWBg@mail.gmail.com>

Hello Edoardo,

On Mon, Oct 17, 2011 at 19:07, Edoardo <edonan at gmail.com> wrote:
> Hi,
> reading the curses programming HOWTO
> (http://docs.python.org/dev/howto/curses.html) I noticed it lacks a
> full running demo.
> Moreover, the document ends inviting developers to contribuite with a
> short program.
>
> I took such invitation and this is my two cents: a program that turns
> the terminal into a lineographic tool (kind of Etch A Sketch).
> It uses only the curses facilities explained in the HOWTO (except
> window.getmaxyx(), that is trivial) and works with both Python 2.7.1+
> and Python 3.2.
> Input controls are arrow keys to paint and "q" to quit.

Thanks a lot for your contribution: would you like to file an issue at
http://bugs.python.org attaching your code (maybe as a proper patch)?
This way, more eyes will look into it.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Mon Oct 31 17:48:55 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Mon, 31 Oct 2011 17:48:55 +0100
Subject: [docs] Dead Link in Documentation
In-Reply-To: <CAOrc4CzTYjPU+K+atuGKuMvKG_VQpO85MERKDJ0=2+c4TQm=gQ@mail.gmail.com>
References: <CAOrc4CzTYjPU+K+atuGKuMvKG_VQpO85MERKDJ0=2+c4TQm=gQ@mail.gmail.com>
Message-ID: <CAPdtAj2ycgiEa7gMa9perKGDabpgox8ZkzxikkPH=kNQ5LGWXg@mail.gmail.com>

Hello Josh,

On Thu, Oct 13, 2011 at 22:50, Josh Gachnang <josh at servercobra.com> wrote:
> The link to DiveIntoPython.org
> in?http://docs.python.org/using/windows.html?(and probably a few other
> pages)?is permanently down. Mark Pilgrim took down all his sites recently,
> so a bunch of people have mirrored his sites. I set up a mirror at
> www.DiveIntoPython.net. It doesn't have all the translations yet, but
> neither do any of the other mirrors I'm seeing. I'm working to scrape those
> from the Google cache and the WayBack machine and get them up ASAP.

Thanks for your service and this heads up: I've just updated the
references to DIP to point to DiveIntoPython.net .

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Mon Oct 31 18:46:23 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Mon, 31 Oct 2011 18:46:23 +0100
Subject: [docs] PYTHON Principal error - loss of coherence - observed in
 modules time, datetime
In-Reply-To: <20111021171028.6406F617@centrum.cz>
References: <20111021171028.6406F617@centrum.cz>
Message-ID: <CAPdtAj1ywDYoLsXavAxWrFALWSzCV-FaYBSaLyR2XpqW3=1KKw@mail.gmail.com>

Hello Michal,
thanks for your detailed email. This mailing list, though, is about
Python documentation while it seems to me you need a bit more than
that; so I suggest to contact the python-list mailing-list at
http://mail.python.org/mailman/listinfo/python-list

Regards,
Sandro

On Fri, Oct 21, 2011 at 17:10,  <michal.sourek at centrum.cz> wrote:
> Dear sirs,
>
> ? ? ? ? first,
>
> ? ? ? ? let me express a highest level of admiration for all the genuine
> people involved in Python world
>
>
>
> ? ? ? ? second,
>
> ? ? ? ? please forgive me, as an "informed amateur", to direct this notice
> to you, instead of may-be a specialised dev/error team
>
>
>
> ? ? ? ? third,
>
> ? ? ? ? might be, that this piece of information has already been handled in
> some other bug/error/PEP
>
>
>
> after some years spent with Python
>
> I?ve observed recently an incoherence - a feature in time / datetime
> modules,
>
> that,
>
> in a fair belief,
>
> both should and can be handled
>
> so that the function are coherent - meaning the "promised" behaviour keeps
> really "being delivered" even under bellow-described circumstances, that are
> quite common in recent years
>
>
>
> In a hope
>
> this can help
>
> please forward the not to the appropriate hands
>
> and let me know if it did help - thank you
>
>
>
>
>
> With respect
>
> Michal
>
>
>
> use scenario: a procedure loopLineDATA( anObj ) ...demo-ed bellow ... gets
> an object to monitor
>
> and each 10-secs?performs regular processing,
>
> it uses several about-one-second time.sleep()-s to wait till next
> 10-sec-time-period
>
>
>
> the point: as gets up and running ( loop forever )
>
> it prints every 10 secs a "status-report" on time/data
>
> and
>
> once
>
> a notebook gets "hibernated" .. a quite often state ( be it a power saving
> policy, or an intention )
>
> the process persists in some state throughout the hibernation epoch
>
> and after the notebook gets re-activated, the process continues
>
>
>
> the issue / non-conformity-note [NCN]
>
> The [NCN] claims,
>
> that after continuing the processing ( post-hibernation state ),
>
> Python displays [ uses and displays ]
>
> wrong time values (as if no hibernation epoch did appear ?... continuing
> second-by-second right ahead from "old"-time of the moment, when the machine
> turned hibernated )
>
> the hibenrated-time-shift is correctly reported by machine clock,
>
> but not in the Python time / datetime functions - those keep continue
> counting time as if there were no hibernate-epoch ( areal-wolrd time-shift )
> in the meantime
>
>
>
> an interim fix: to prevent such, perform
>
> at some reasonable frequency, to keep low latency/overhead thereof,
>
> time-base?re-adjustment to renew the coherence of Python-time with the
> machine RTC-clock (real-world-time)
>
>
>
> " /*-------------------------------------------------------------------
>
> # a demonstration sample ... not any kind of an optimised / HiPerf code :o)
>
> import time, datetime
>
> def loopLineDATA ( anObj )
>
> last_N = 0
>
> while True:
>
> try:
>
> now = datetime.datetime.now()
>
> ntt = now.timetuple()
>
> N ? = ntt.tm_sec
>
> if ( N % 10 ) == 0: # to get 00 10 20 30 .. 50 "round-values"
>
> if N/ 10 == last_N: # to sleep/loop, should still in the
> "same-10-sec-time-period"
>
> time.sleep( 0.95 ) # to provide system a slight time-elasticity
> for?SIG/overhead processing
>
> else:
>
> last_N = N / 10 # shuffle N as "10-sec-time-period" << { 0 1 2 3 4 5 }
>
> print now
>
> ''' process telemetry data -----
>
>
>
> ? ? (skipped for clarity) ------
>
> '''
>
> except: Keyboard Interrupt:
>
> ''' clear contexts / RET '''
>
> return
>
> " */--------------------------------------------------------------------
>
> _______________________________________________
> docs mailing list
> docs at python.org
> http://mail.python.org/mailman/listinfo/docs
>
>



-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Mon Oct 31 19:24:30 2011
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Mon, 31 Oct 2011 19:24:30 +0100
Subject: [docs] reverse/backwards quotes now displaying correctly
In-Reply-To: <CAEFwTqAbU5j3PjnLhrawQ92-AsOm9g0Th55URtyY97KLr1wGHQ@mail.gmail.com>
References: <CAEFwTqAbU5j3PjnLhrawQ92-AsOm9g0Th55URtyY97KLr1wGHQ@mail.gmail.com>
Message-ID: <CAPdtAj1kZpUkUe81NXwfqrZvUe4-OOwvJQU0_eVvQMhAoEpAXg@mail.gmail.com>

Hello Jonathan,

On Tue, Oct 11, 2011 at 23:07, Jonathan Blakes
<jonathan.blakes at gmail.com> wrote:
> Hello,
> I think that the "reverse (a.k.a) backwards quotes"
> in?http://docs.python.org/reference/expressions.html#string-conversions are
> not displaying correctly.

I've just corrected what you pointed out, using the backticks.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From danshved at gmail.com  Sun Oct 30 12:59:58 2011
From: danshved at gmail.com (Daniil Shved)
Date: Sun, 30 Oct 2011 14:59:58 +0300
Subject: [docs] A bug in the datetime module documentation
Message-ID: <CAFMS1CV5LM185rj=rpCbG7+tvY7qdMjazFPV34CThZ4ZxXm7zA@mail.gmail.com>

Hi there,

I found what seems to be an error in the python 2.7.2 docs for "datetime"
module:

http://docs.python.org/library/datetime.html?highlight=datetime#tzinfo-objects

In the documentation for method tzinfo.dst(self, dt) there are two code
samples (under "most implementations of dst() will probably look like one
of these two"). In these code samples the method is defined as "def
dst(self):", but it should be "def dst(self, dt)".

-- 
Dan Shved
danshved at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111030/03835aac/attachment.html>

From Tim.Bellis at metaswitch.com  Mon Oct 31 15:32:30 2011
From: Tim.Bellis at metaswitch.com (Tim Bellis)
Date: Mon, 31 Oct 2011 14:32:30 +0000
Subject: [docs] Python docs bug in 2.6 - 'as' is now a reserved keyword
Message-ID: <85B83C6EA7793D4884BF2179AC55EB1B2C23DB94@ENFICSMBX1.datcon.co.uk>

http://docs.python.org/whatsnew/2.6.html#porting-to-python-2-6 doesn't mention that 'as' is now a reserved keyword in Python 2.6 and so any variables named 'as' will need to be renamed.

Regards,

Tim

PS Handily, we're warned about this in Python 2.5 :)

Python 2.5 (r25, Dec 12 2008, 17:45:12)
[GCC 4.1.2 20070626 (Red Hat 4.1.2-14)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> as=1
<stdin>:1: Warning: 'as' will become a reserved keyword in Python 2.6

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20111031/149f8d47/attachment.html>