Re: [Python-Dev] cpython (3.2): Fix closes Issue12315 - Updates to http.client documentation.
On 20.06.2011 02:00, senthil.kumaran wrote: > http://hg.python.org/cpython/rev/d801b570b1dd > changeset: 70882:d801b570b1dd > branch: 3.2 > parent: 70880:9e58a638f028 > user:Senthil Kumaran > date:Sun Jun 19 16:56:49 2011 -0700 > summary: > Fix closes Issue12315 - Updates to http.client documentation. > > files: > Doc/library/http.client.rst | 13 - > 1 files changed, 12 insertions(+), 1 deletions(-) > > > diff --git a/Doc/library/http.client.rst b/Doc/library/http.client.rst > --- a/Doc/library/http.client.rst > +++ b/Doc/library/http.client.rst > @@ -543,6 +543,9 @@ > A debugging hook. If :attr:`debuglevel` is greater than zero, messages > will be printed to stdout as the response is read and parsed. > > +.. attribute:: HTTPResponse.closed > + > + Is True if the stream is closed. > > Examples > This is not a big deal, and I'm not picking specially on you here, Senthil, it's just something that I've noticed several times: Newlines are a valuable tool for structuring reST files (just like in Python files). I tried to set up a convention to separate large blocks (such as sections) by two newlines, to make it easier to scroll and find what you're looking for. Please try to keep this intact. Thanks, Georg ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] cpython (3.2): Fix closes Issue12359 - Minor update to module import description.
On 20.06.2011 02:42, senthil.kumaran wrote: > http://hg.python.org/cpython/rev/bf8b4c43fb94 > changeset: 70886:bf8b4c43fb94 > branch: 3.2 > parent: 70884:afcfb22e > user:Senthil Kumaran > date:Sun Jun 19 17:37:06 2011 -0700 > summary: > Fix closes Issue12359 - Minor update to module import description. > > files: > Doc/tutorial/modules.rst | 15 --- > 1 files changed, 8 insertions(+), 7 deletions(-) > > > diff --git a/Doc/tutorial/modules.rst b/Doc/tutorial/modules.rst > --- a/Doc/tutorial/modules.rst > +++ b/Doc/tutorial/modules.rst > @@ -159,13 +159,14 @@ > > .. index:: triple: module; search; path > > -When a module named :mod:`spam` is imported, the interpreter searches for a > file > -named :file:`spam.py` in the current directory, and then in the list of > -directories specified by the environment variable :envvar:`PYTHONPATH`. This > -has the same syntax as the shell variable :envvar:`PATH`, that is, a list of > -directory names. When :envvar:`PYTHONPATH` is not set, or when the file is > not > -found there, the search continues in an installation-dependent default path; > on > -Unix, this is usually :file:`.:/usr/local/lib/python`. > +When a module named :mod:`spam` is imported, the interpreter searches for a > +file named :file:`spam.py` in the directory containing the input script (or > +thecurrent directory), and then in the list of directories specified by the By just adding "or the current directory", you've actually made this more confusing: now the reader will wonder when it's the script directory and when it's the current directory. Georg ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] cpython (3.2): Fix closes Issue12359 - Minor update to module import description.
On Mon, Jun 20, 2011 at 09:13:07AM +0200, Georg Brandl wrote:
> On 20.06.2011 02:42, senthil.kumaran wrote:
> > summary:
> > Fix closes Issue12359 - Minor update to module import description.
> > ...
> > +When a module named :mod:`spam` is imported, the interpreter searches for a
> > +file named :file:`spam.py` in the directory containing the input script (or
> > +thecurrent directory), and then in the list of directories specified by the
>
> By just adding "or the current directory", you've actually made this more
> confusing: now the reader will wonder when it's the script directory and when
> it's the current directory.
I added that statement in the bracket, after looking at another
instance in the next para which had this mention. I think, the point
here is that the reader would understand, where the import is looking
for the module based on the context. Fine with removing this sentence
("or the current directory"), if statement explains the idea better
without it.
--
Senthil
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] cpython (3.2): Fix closes Issue12315 - Updates to http.client documentation.
On Mon, Jun 20, 2011 at 09:11:20AM +0200, Georg Brandl wrote: > Newlines are a valuable tool for structuring reST files (just like in Python > files). I tried to set up a convention to separate large blocks (such as > sections) by two newlines, to make it easier to scroll and find what you're > looking for. Please try to keep this intact. > Noted. In the next checkin to this file, I shall correct this one and add extra line before the Example section. Thanks, Senthil ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Language summit writeup anyone?
Hi. Unfortunately I'm missing Europython (and language summit) this year. Did anyone do a writeup on what was discussed? Cheers, fijal ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Language summit writeup anyone?
On Jun 20, 2011, at 4:08 AM, Maciej Fijalkowski wrote: > Hi. > > Unfortunately I'm missing Europython (and language summit) this year. > Did anyone do a writeup on what was discussed? Brian Curtin or I can help get the writeup posted to the Python Insider blog. I'm sure there are a lot of people who don't follow this list who would be interested in hearing about the outcome. Doug ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Language summit writeup anyone?
Hi, Le Mon, 20 Jun 2011 10:08:04 +0200, Maciej Fijalkowski a écrit : > > Unfortunately I'm missing Europython (and language summit) this year. > Did anyone do a writeup on what was discussed? Mark Dickinson has been taking notes, but since there only a few of us (roughly 10 attendants), it was mostly casual and friendly chatting :) Regards Antoine. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] cpython (3.2): Fix closes Issue12359 - Minor update to module import description.
On 20.06.2011 09:34, Senthil Kumaran wrote:
> On Mon, Jun 20, 2011 at 09:13:07AM +0200, Georg Brandl wrote:
>> On 20.06.2011 02:42, senthil.kumaran wrote:
>> > summary:
>> > Fix closes Issue12359 - Minor update to module import description.
>> > ...
>> > +When a module named :mod:`spam` is imported, the interpreter searches for
>> > a
>> > +file named :file:`spam.py` in the directory containing the input script
>> > (or
>> > +thecurrent directory), and then in the list of directories specified by
>> > the
>>
>> By just adding "or the current directory", you've actually made this more
>> confusing: now the reader will wonder when it's the script directory and when
>> it's the current directory.
>
> I added that statement in the bracket, after looking at another
> instance in the next para which had this mention. I think, the point
> here is that the reader would understand, where the import is looking
> for the module based on the context. Fine with removing this sentence
> ("or the current directory"), if statement explains the idea better
> without it.
Thanks!
Georg
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] REMINDER: Participation Requested: Survey about Open-Source Software Development
Hi, Apologies for any inconvenience and thank you to those who have already completed the survey. We will keep the survey open for another couple of weeks. But, we do hope you will consider responding to the email request below (sent 2 weeks ago). Thanks, Dr. Jeffrey Carver Assistant Professor University of Alabama (v) 205-348-9829 (f) 205-348-0219 http://www.cs.ua.edu/~carver -Original Message- From: Jeffrey Carver [mailto:[email protected]] Sent: Monday, June 13, 2011 11:46 AM To: '[email protected]' Subject: Participation Requested: Survey about Open-Source Software Development Hi, Drs. Jeffrey Carver, Rosanna Guadagno, Debra McCallum, and Mr. Amiangshu Bosu, University of Alabama, and Dr. Lorin Hochstein, University of Southern California, are conducting a survey of open-source software developers. This survey seeks to understand how developers on distributed, virtual teams, like open-source projects, interact with each other to accomplish their tasks. You must be at least 19 years of age to complete the survey. The survey should take approximately 15 minutes to complete. If you are actively participating as a developer, please consider completing our survey. Here is the link to the survey: http://goo.gl/HQnux We apologize for inconvenience and if you receive multiple copies of this email. This survey has been approved by The University of Alabama IRB board. Thanks, Dr. Jeffrey Carver Assistant Professor University of Alabama (v) 205-348-9829 (f) 205-348-0219 http://www.cs.ua.edu/~carver ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Parser/intrcheck.c
I think it's safe to remove it. The last reference to it I found was in the 2.0 release, where there is a Parser/Makefile (generated from Parser/Makefile.in) which contains the following gem: # This target is used by the master Makefile to add the objects to the library add2lib:$(OBJS) $(AR) cr $(LIBRARY) $(AROBJS) if test ! -f ../Modules/hassignal; \ then echo adding intrcheck.o; $(AR) r $(LIBRARY) intrcheck.o; \ else echo leaving intrcheck.o out; fi touch add2lib This Makefile.in was deleted in http://svn.python.org/view?view=revision So I think you're fine killing that file. --Guido On Wed, Jun 15, 2011 at 3:21 PM, Antoine Pitrou wrote: > > Hello, > > I may be missing something, but I'm wondering whether > Parser/intrcheck.c is still used anywhere. > > It's only mentioned in some comments: > > $ grep -r intrcheck.c * > Modules/signalmodule.c:1197:/* Replacements for intrcheck.c functionality > PC/os2vacpp/makefile.omk:217: # intrcheck.c -- Not Referenced by Anyone > (?) > Python/sigcheck.c:3: interrupt occurs. It can't be in the intrcheck.c file > since that > > And if I remove it and "make clean", I can still rebuild successfully. > > Regards > > Antoine. > > > ___ > Python-Dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (python.org/~guido) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Parser/intrcheck.c
On Mon, Jun 20, 2011 at 4:40 PM, Guido van Rossum wrote: > I think it's safe to remove it. The last reference to it I found was > in the 2.0 release, where there is a Parser/Makefile (generated from > Parser/Makefile.in) which contains the following gem: > > # This target is used by the master Makefile to add the objects to the library > add2lib: $(OBJS) > $(AR) cr $(LIBRARY) $(AROBJS) > if test ! -f ../Modules/hassignal; \ > then echo adding intrcheck.o; $(AR) r $(LIBRARY) intrcheck.o; \ > else echo leaving intrcheck.o out; fi > touch add2lib > > This Makefile.in was deleted in http://svn.python.org/view?view=revision http://svn.python.org/view?view=revision&revision=19308 > So I think you're fine killing that file. > > --Guido > > On Wed, Jun 15, 2011 at 3:21 PM, Antoine Pitrou wrote: >> >> Hello, >> >> I may be missing something, but I'm wondering whether >> Parser/intrcheck.c is still used anywhere. >> >> It's only mentioned in some comments: >> >> $ grep -r intrcheck.c * >> Modules/signalmodule.c:1197:/* Replacements for intrcheck.c functionality >> PC/os2vacpp/makefile.omk:217: # intrcheck.c -- Not Referenced by Anyone >> (?) >> Python/sigcheck.c:3: interrupt occurs. It can't be in the intrcheck.c >> file since that >> >> And if I remove it and "make clean", I can still rebuild successfully. >> >> Regards >> >> Antoine. >> >> >> ___ >> Python-Dev mailing list >> [email protected] >> http://mail.python.org/mailman/listinfo/python-dev >> Unsubscribe: >> http://mail.python.org/mailman/options/python-dev/guido%40python.org >> > > > > -- > --Guido van Rossum (python.org/~guido) > -- --Guido van Rossum (python.org/~guido) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
