Mailman 3 July 2012 - Python-Dev

Re: [Python-Dev] Python-Dev Digest, Vol 108, Issue 14
by Ryan Paullin July 12, 2012

July 12, 2012

looks like theres no forgiveness except for dj yoda On Thu, Jul 12, 2012 at 3:00 AM, <python-dev-request(a)python.org> wrote: > Send Python-Dev mailing list submissions to > python-dev(a)python.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.python.org/mailman/listinfo/python-dev > or, via email, send a message with subject or body 'help' to > python-dev-request(a)python.org > > You can reach the person … [View More]

2 3

Testing 3.3 framework builds on OS X
by Marc Abramowitz July 11, 2012

July 11, 2012

Anyone know how to build and run tests on an OS X build with —enable-framework, without installing the framework? I want to test that something works in my tree without polluting /Library/Frameworks with stuff that could mess up future tests. I've been mucking around with DYLD_FRAMEWORK_PATH but not having much luck. If I build with ./configure --enable-framework --with-dtrace && make and use DYLD_FRAMEWORK_PATH=. then I suspect it's still loading from /Library/Frameworks, because my … [View More]

3 3

Re: [Python-Dev] Python-Dev Digest, Vol 108, Issue 7
by Ryan Paullin July 10, 2012

July 10, 2012

thanks for the reply hastings ive been working on a loopback interface its done On Fri, Jul 6, 2012 at 3:00 AM, <python-dev-request(a)python.org> wrote: > Send Python-Dev mailing list submissions to > python-dev(a)python.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.python.org/mailman/listinfo/python-dev > or, via email, send a message with subject or body 'help' to > python-dev-request(a)python.org > > … [View More]You can reach the person managing the list at > python-dev-owner(a)python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Python-Dev digest..." > > > Today's Topics: > > 1. Re: GitHub mirror (Was: Bitbucket mirror?) (martin(a)v.loewis.de) > 2. Bloody FAQ (Was: [Python-ideas] itertools.chunks(iterable, > size, fill=None)) (anatoly techtonik) > 3. Re: Bloody FAQ (Was: [Python-ideas] > itertools.chunks(iterable, size, fill=None)) (Mark Lawrence) > 4. Re: Bloody FAQ (Was: [Python-ideas] > itertools.chunks(iterable, size, fill=None)) (Stefan Behnel) > 5. Re: Bloody FAQ (Was: [Python-ideas] > itertools.chunks(iterable, size, fill=None)) (Paul Boddie) > 6. EuroPython 2012 Language Summit is Canceled. (Larry Hastings) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 05 Jul 2012 20:27:02 +0200 > From: martin(a)v.loewis.de > To: python-dev(a)python.org > Subject: Re: [Python-Dev] GitHub mirror (Was: Bitbucket mirror?) > Message-ID: > <20120705202702.Horde.Yh-RBqGZi1VP9dx2H7Nj-nA(a)webmail.df.eu> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed; DelSp=Yes > > >> You won't get any changes in to CPython by creating pull requests. We > >> use http://bugs.python.org/ for that, sorry. > > > > Question -- is there a reason to abide by this rule for docs? That is, > if we > > could get a sympathetic core dev to look at pull requests for docs as > part of > > a streamlined process, would it cause problems? > > How do you communicate a "pull request"? On bitbucket, there is a > "pull request" > UI resulting in a tracker item being generated (and an email being sent), > but > hg.python.org doesn't have a notion of pull requests. Of course, you could > use any communication means (email, telephone call, carrier pigeon) to > request > a pull from a "sympathetic core dev". > > > (What I'm really asking is whether or the bugs.python.org process is > > considered critical for potentially minor doc changes and additions.) > > The sympathetic core dev is mostly free to bypass any submission process > initially; commits that bypass established procedures will likely be > questioned > only after the fact. > > In the specific case, I'd be worried to verify that the submitter has > provided > a contributor form. That's easy to do in the bug tracker, but difficult to > do > in an offline pull request. Of course, for a really minor doc change > (e.g. typo > fixes), no contrib form is necessary. > > Regards, > Martin > > > > > ------------------------------ > > Message: 2 > Date: Thu, 5 Jul 2012 22:41:29 +0300 > From: anatoly techtonik <techtonik(a)gmail.com> > To: Stefan Behnel <stefan_ml(a)behnel.de> > Cc: python-ideas(a)python.org, python-dev(a)python.org > Subject: [Python-Dev] Bloody FAQ (Was: [Python-ideas] > itertools.chunks(iterable, size, fill=None)) > Message-ID: > <CAPkN8x+A-OYWNLNKDH= > 6GnQn+o_Tb3LMnimHYs9zkYmWR1GTgA(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Thu, Jul 5, 2012 at 7:50 PM, Stefan Behnel <stefan_ml(a)behnel.de> wrote: > > anatoly techtonik, 05.07.2012 15:36: > >> On Sun, Jul 1, 2012 at 12:09 AM, Terry Reedy wrote: > >>> From Raymond's first message on http://bugs.python.org/issue6021 , add > >>> grouper: > >>> > >>> "This has been rejected before. > >> > >> I quite often see such arguments and I can't stand to repeat that > >> these are not arguments. It is good to know, but when people use that > >> as a reason to close tickets - that's just disgusting. > > > > The *real* problem is that people keep bringing up topics (and even spell > > them out in the bug tracker) without searching for existing discussions > > and/or tickets first. That's why those who do such a search (or who know > > what they are talking about anyway) close these tickets with the remark > > "this has been rejected before", instead of repeating an entire heap of > > arguments all over again to feed a discussion that would only lead to the > > same result as it did before, often several times before. > > Make the bloody FAQ and summarize this stuff? Why waste each others > time? If people don't enjoy repeating themselves over and over - there > is a bloody wiki. What should happen to people to start extracting > gems of knowledge from piles of dusty sheets called list "archives" > for others to admire. > > No, it is easier to say "it was already discussed many times", "why > don't you Google yourself", "so far you're only complaining", etc. If > people can't find anything - why everybody thinks they are ignorant > and lazy. Even if it so, why nobody thinks that maybe that bloody > Xapian index is dead again for a bloody amount of moons nobody knows > why and how many exactly? Why nobody thinks that lazy coders can also > help with development? Maybe that laziness is the primary reason some > major groups actually prefer Python to Java, C++ and other more > interesting languages (such as PHP) when it comes to typing? Make it > easy and the patches will follow. Answers like "this was discussed > before" don't make it easy to understand, and leaving users rereading > old 19xx archives that people don't reread themselves will likely make > users bounce and never (NEVER!) come up with some proposal again. An > "organic" way to keep traffic low. > > Miscommunication is a bad experience for users, bad experience for > developers, everybody is annoyed and as a result such nice language as > Python loses points on TIOBE (and convenient chunk() functions to > munch-munch on the sequence data). > > Wheew. :-F > > > ------------------------------ > > Message: 3 > Date: Thu, 05 Jul 2012 20:55:09 +0100 > From: Mark Lawrence <breamoreboy(a)yahoo.co.uk> > To: python-dev(a)python.org > Cc: python-ideas(a)python.org > Subject: Re: [Python-Dev] Bloody FAQ (Was: [Python-ideas] > itertools.chunks(iterable, size, fill=None)) > Message-ID: <jt4re5$3gs$1(a)dough.gmane.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 05/07/2012 20:41, anatoly techtonik wrote: > > On Thu, Jul 5, 2012 at 7:50 PM, Stefan Behnel <stefan_ml(a)behnel.de> > wrote: > >> anatoly techtonik, 05.07.2012 15:36: > >>> On Sun, Jul 1, 2012 at 12:09 AM, Terry Reedy wrote: > >>>> From Raymond's first message on http://bugs.python.org/issue6021 , > add > >>>> grouper: > >>>> > >>>> "This has been rejected before. > >>> > >>> I quite often see such arguments and I can't stand to repeat that > >>> these are not arguments. It is good to know, but when people use that > >>> as a reason to close tickets - that's just disgusting. > >> > >> The *real* problem is that people keep bringing up topics (and even > spell > >> them out in the bug tracker) without searching for existing discussions > >> and/or tickets first. That's why those who do such a search (or who know > >> what they are talking about anyway) close these tickets with the remark > >> "this has been rejected before", instead of repeating an entire heap of > >> arguments all over again to feed a discussion that would only lead to > the > >> same result as it did before, often several times before. > > > > Make the bloody FAQ and summarize this stuff? Why waste each others > > time? If people don't enjoy repeating themselves over and over - there > > is a bloody wiki. What should happen to people to start extracting > > gems of knowledge from piles of dusty sheets called list "archives" > > for others to admire. > > > > No, it is easier to say "it was already discussed many times", "why > > don't you Google yourself", "so far you're only complaining", etc. If > > people can't find anything - why everybody thinks they are ignorant > > and lazy. Even if it so, why nobody thinks that maybe that bloody > > Xapian index is dead again for a bloody amount of moons nobody knows > > why and how many exactly? Why nobody thinks that lazy coders can also > > help with development? Maybe that laziness is the primary reason some > > major groups actually prefer Python to Java, C++ and other more > > interesting languages (such as PHP) when it comes to typing? Make it > > easy and the patches will follow. Answers like "this was discussed > > before" don't make it easy to understand, and leaving users rereading > > old 19xx archives that people don't reread themselves will likely make > > users bounce and never (NEVER!) come up with some proposal again. An > > "organic" way to keep traffic low. > > > > Miscommunication is a bad experience for users, bad experience for > > developers, everybody is annoyed and as a result such nice language as > > Python loses points on TIOBE (and convenient chunk() functions to > > munch-munch on the sequence data). > > > > Wheew. :-F > > > > Can I safely assume that you are volunteering to do the work required? > > -- > Cheers. > > Mark Lawrence. > > > > > > ------------------------------ > > Message: 4 > Date: Thu, 05 Jul 2012 21:58:52 +0200 > From: Stefan Behnel <stefan_ml(a)behnel.de> > To: python-dev(a)python.org > Cc: python-ideas(a)python.org > Subject: Re: [Python-Dev] Bloody FAQ (Was: [Python-ideas] > itertools.chunks(iterable, size, fill=None)) > Message-ID: <jt4rlt$45k$1(a)dough.gmane.org> > Content-Type: text/plain; charset=UTF-8 > > anatoly techtonik, 05.07.2012 21:41: > > On Thu, Jul 5, 2012 at 7:50 PM, Stefan Behnel wrote: > >> anatoly techtonik, 05.07.2012 15:36: > >>> On Sun, Jul 1, 2012 at 12:09 AM, Terry Reedy wrote: > >>>> From Raymond's first message on http://bugs.python.org/issue6021 , > add > >>>> grouper: > >>>> > >>>> "This has been rejected before. > >>> > >>> I quite often see such arguments and I can't stand to repeat that > >>> these are not arguments. It is good to know, but when people use that > >>> as a reason to close tickets - that's just disgusting. > >> > >> The *real* problem is that people keep bringing up topics (and even > spell > >> them out in the bug tracker) without searching for existing discussions > >> and/or tickets first. That's why those who do such a search (or who know > >> what they are talking about anyway) close these tickets with the remark > >> "this has been rejected before", instead of repeating an entire heap of > >> arguments all over again to feed a discussion that would only lead to > the > >> same result as it did before, often several times before. > > > > Make the bloody FAQ and summarize this stuff? Why waste each others > > time? > > Yes, that is exactly the question. > > It takes time to write things up nicely. I mean, once someone has pointed > out to you that this has been discussed before, you could just go, look it > up (or search for it), and then put it into a Wiki or blog post yourself, > or sum it up and send it to the mailing list as a reply. Why rely on others > to do it for you? > > Stefan > > > > ------------------------------ > > Message: 5 > Date: Thu, 5 Jul 2012 23:11:46 +0200 > From: Paul Boddie <paul(a)boddie.org.uk> > To: python-dev(a)python.org > Subject: Re: [Python-Dev] Bloody FAQ (Was: [Python-ideas] > itertools.chunks(iterable, size, fill=None)) > Message-ID: <201207052311.46867.paul(a)boddie.org.uk> > Content-Type: text/plain; charset="utf-8" > > Stefan Behnel wrote: > > anatoly techtonik, 05.07.2012 21:41: > > > > > > Make the bloody FAQ and summarize this stuff? Why waste each others > > > time? > > > > Yes, that is exactly the question. > > > > It takes time to write things up nicely. I mean, once someone has pointed > > out to you that this has been discussed before, you could just go, look > it > > up (or search for it), and then put it into a Wiki or blog post yourself, > > or sum it up and send it to the mailing list as a reply. Why rely on > others > > to do it for you? > > To be fair, Anatoly has done quite a bit of maintenance on some of the Wiki > content around various aspects of the project, so it's not as if he's > demanding anything out of the ordinary or asking for others to do things > that > he isn't already doing in some sense. My experience is that there usually > needs to be some willingness on the other end of the transaction, and if it > takes repetition to encourage it amongst those who don't see the current > situation as a problem for them, then so be it. > > Of course, this kind of documentation activity, where one gathers together > historical decisions and the consensus from long-forgotten discussions, is > pretty thankless work. I occasionally regard it as worthwhile if only to > bring up something someone said as an inconvenient interruption in any > current discussion, but that's a pretty minimal reward for all the effort > unless one has such work as part of one's daily routine. > > Paul > > > ------------------------------ > > Message: 6 > Date: Fri, 06 Jul 2012 08:47:30 +0200 > From: Larry Hastings <larry(a)hastings.org> > To: python-dev(a)python.org, python-committers(a)python.org > Subject: [Python-Dev] EuroPython 2012 Language Summit is Canceled. > Message-ID: <4FF68A02.8000500(a)hastings.org> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > > > I only got one more RSVP and zero topics for the docket. So let's > sprint instead. > > See you at the PyCon 2013 Language Summit, > > > //arry/ > [View Less]

1 1

Re: [Python-Dev] cpython: Issue 15265: document the exception raised for invalid sample sizes.
by Georg Brandl July 9, 2012

July 9, 2012

On 09.07.2012 01:02, raymond.hettinger wrote: > http://hg.python.org/cpython/rev/72174d8af3ba > changeset: 78015:72174d8af3ba > user: Raymond Hettinger <python(a)rcn.com> > date: Sun Jul 08 16:01:53 2012 -0700 > summary: > Issue 15265: document the exception raised for invalid sample sizes. > > files: > Doc/library/random.rst | 3 +++ > 1 files changed, 3 insertions(+), 0 deletions(-) > > > diff --git a/Doc/library/random.rst … [View More]

1 0

Re: [Python-Dev] cpython: Issue #15283: Updated pyvenv documentation to expand on activation.
by Antoine Pitrou July 9, 2012

July 9, 2012

On Mon, 9 Jul 2012 10:25:58 +0200 (CEST) vinay.sajip <python-checkins(a)python.org> wrote: > + > + Common installation tools such as ``distribute`` and ``pip`` work as > + expected with venvs - i.e. when a venv is active, they install Python > + packages into the venv without needing to be told to do so explicitly. Not exactly. They will do so if you *install* them in the venv. A system-wide distribute or pip, AFAIK, will still install packages into the system-wide … [View More]

1 0

Re: [Python-Dev] [Python-checkins] cpython: Issue 14814: The new systematic tests aren't just about error reporting any
by Nick Coghlan July 9, 2012

July 9, 2012

On Mon, Jul 9, 2012 at 3:22 AM, Terry Reedy <tjreedy(a)udel.edu> wrote: > On 7/8/2012 9:14 AM, nick.coghlan wrote: > If you want to report both errors, when present: I don't really - when there are multiple things wrong with the address, ipaddress just reports the first one it notices (e.g. IPv4Address("google.com") will complain about the lack of "." separators rather than the fact that "google" and "com" are not valid octets). This was just a case where I started to reorder the … [View More]

1 0

Re: [Python-Dev] cpython: Fix 5931 - Python runtime hardcoded in wsgiref.simple_server - Now it specifies
by Georg Brandl July 8, 2012

July 8, 2012

On 07.07.2012 23:29, senthil.kumaran wrote: > http://hg.python.org/cpython/rev/34e705fa4da4 > changeset: 77983:34e705fa4da4 > user: Senthil Kumaran <senthil(a)uthcode.com> > date: Sat Jul 07 14:29:58 2012 -0700 > summary: > Fix 5931 - Python runtime hardcoded in wsgiref.simple_server - Now it specifies an implementation specific term. > > files: > Doc/library/wsgiref.rst | 5 +++++ > Lib/test/test_wsgiref.py | 10 ++++++++-- … [View More]

2 1

Re: [Python-Dev] cpython (3.2): Fix issue14826 - make urllib.request.Request quoted url consistent with
by Antoine Pitrou July 8, 2012

July 8, 2012

> > + def test_quote_url(self): > + Request = urllib.request.Request > + request = Request("http://www.python.org/foo bar") > + self.assertEqual(request.full_url, "http://www.python.org/foo%20bar") > + This means someone who already quotes URL will get a double escaping, right? Regards Antoine.

1 0

Re: [Python-Dev] cpython: Issue 14814: Correctly return NotImplemented from ipaddress._BaseNetwork.__eq__
by Antoine Pitrou July 7, 2012

July 7, 2012

On Sat, 7 Jul 2012 15:08:42 +0200 (CEST) nick.coghlan <python-checkins(a)python.org> wrote: > > def __eq__(self, other): > - if not isinstance(other, _BaseNetwork): > - raise TypeError('%s and %s are not of the same type' % ( > - self, other)) > - return (self._version == other._version and > - self.network_address == other.network_address and > - int(self.netmask) == int(… [View More]

2 2

Problem with hg hook for devguide repo?
by Ned Deily July 7, 2012

July 7, 2012

pushing to ssh://pyhg/devguide searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 1 changesets with 1 changes to 1 files remote: sent email to roundup at report(a)bugs.python.org remote: notified python-checkins(a)python.org of incoming changeset bbe197bf57a1 remote: 1 files updated, 0 files merged, 0 files removed, 0 files unresolved remote: sh: 1: source: not found remote: sh: 1: sphinx-build: not found remote: warning: … [View More]

2 1