Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

On 23 November 2014 at 17:14, Donald Stufft wrote: >> On Nov 23, 2014, at 2:01 AM, Nick Coghlan wrote: >> Travis isn't the only CI system on the internet, and for pure Sphinx >> documentation cases, ReadTheDocs runs just as well off BitBucket as it >> does off GitHub. > > Sure it’s not the only C

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

> On Nov 23, 2014, at 2:01 AM, Nick Coghlan wrote: > > On 23 November 2014 at 16:27, Donald Stufft wrote: >>> On Nov 23, 2014, at 1:25 AM, Nick Coghlan wrote: >>> By contrast, proposals to switch from Mercurial to Git impose a >>> *massive* burden on contributors that don't already know git. T

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

> On Nov 23, 2014, at 1:49 AM, Nick Coghlan wrote: > > On 23 November 2014 at 16:10, Guido van Rossum wrote: >> On Saturday, November 22, 2014, Nick Coghlan wrote: >>> The learning curve on git is still awful - it offers no compelling >>> advantages over hg, and GitHub doesn't offer any huge b

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

On 23 November 2014 at 16:27, Donald Stufft wrote: >> On Nov 23, 2014, at 1:25 AM, Nick Coghlan wrote: >> By contrast, proposals to switch from Mercurial to Git impose a >> *massive* burden on contributors that don't already know git. That >> significant increase in the time investment required w

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

On 23 November 2014 at 16:10, Guido van Rossum wrote: > On Saturday, November 22, 2014, Nick Coghlan wrote: >> The learning curve on git is still awful - it offers no compelling >> advantages over hg, and GitHub doesn't offer any huge benefits over >> BitBucket for Sphinx based documentation (Rea

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

On Sun, Nov 23, 2014 at 5:03 PM, Wes Turner wrote: > hg imuutability is certainly a primarily attractive feature; > along with the keyring support. What exactly do you mean by immutability? Are you talking about how git allows a "force push" that can destroy data? That can be rejected in a repo's

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

> On Nov 23, 2014, at 1:25 AM, Nick Coghlan wrote: > > On 23 November 2014 at 16:03, Donald Stufft wrote: >>> On Nov 23, 2014, at 12:59 AM, Nick Coghlan wrote: >>> >>> Note that if folks prefer Git, BitBucket supports both. I would object >>> strongly to unilaterally forcing existing contribu

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

On 23 November 2014 at 16:03, Donald Stufft wrote: >> On Nov 23, 2014, at 12:59 AM, Nick Coghlan wrote: >> >> Note that if folks prefer Git, BitBucket supports both. I would object >> strongly to unilaterally forcing existing contributors to switch from >> Mercurial to git. > > Going to all the t

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

On Saturday, November 22, 2014, Nick Coghlan wrote: > On 23 November 2014 at 15:19, Guido van Rossum > wrote: > > This thread seems to beg for a decision. I think Donald Stufft has it > > exactly right: we should move to GitHub, because it is the easiest to use > > and most contributors already

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

> The learning curve on git is still awful - it offers no compelling advantages over hg, and GitHub doesn't offer any huge benefits over BitBucket for Sphinx based documentation (ReadTheDocs works just as well with either service). This was a most helpful resource: https://github.com/sympy/sympy/

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

On Sun, Nov 23, 2014 at 4:59 PM, Nick Coghlan wrote: > The learning curve on git is still awful - it offers no compelling > advantages over hg, and GitHub doesn't offer any huge benefits over > BitBucket for Sphinx based documentation (ReadTheDocs works just as > well with either service). The le

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

> On Nov 23, 2014, at 1:03 AM, Donald Stufft wrote: > >> >> On Nov 23, 2014, at 12:59 AM, Nick Coghlan wrote: >> >> On 23 November 2014 at 15:19, Guido van Rossum wrote: >>> This thread seems to beg for a decision. I think Donald Stufft has it >>> exactly right: we should move to GitHub, bec

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

> On Nov 23, 2014, at 12:59 AM, Nick Coghlan wrote: > > On 23 November 2014 at 15:19, Guido van Rossum wrote: >> This thread seems to beg for a decision. I think Donald Stufft has it >> exactly right: we should move to GitHub, because it is the easiest to use >> and most contributors already kn

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

On 23 November 2014 at 15:19, Guido van Rossum wrote: > This thread seems to beg for a decision. I think Donald Stufft has it > exactly right: we should move to GitHub, because it is the easiest to use > and most contributors already know it (or are eager to learn thee). > Honestly, the time for c

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

re: docs hg repos and static HTTP hosting * I can't remember what the GitHub Pages CDN cache time is * Does BitBucket support more than one pages repo? * Does support Sphinx .. index and :ref: syntax extensions? * https://github.com/yoloseem/awesome-sphinxdoc * https://github.com/rtfd/readthedoc

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

> On Nov 23, 2014, at 12:19 AM, Guido van Rossum wrote: > > This thread seems to beg for a decision. I think Donald Stufft has it exactly > right: we should move to GitHub, because it is the easiest to use and most > contributors already know it (or are eager to learn thee). Honestly, the time

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

This thread seems to beg for a decision. I think Donald Stufft has it exactly right: we should move to GitHub, because it is the easiest to use and most contributors already know it (or are eager to learn thee). Honestly, the time for core devs (or some other elite corps of dedicated volunteers) to

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

In order to save everyone's breath, I am *accepting* the proposal of PEP 479. The transition plan is: - "from __future__ import generator_stop" in 3.5, and a silent deprecation if StopIteration is allowed to bubble out of a generator (i.e. no warning is printed unless you explicitly turn it on) -

[Python-Dev] 2.7.9 delayed

As you may have noticed, 2.7.9rc1 wasn't tagged today. I've been much busier than I expected to be, so I haven't had the time to fix up some 2.7.9 lose ends. Hopefully, the delay won't be more than a few days. ___ Python-Dev mailing list Python-Dev@python

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On 11/22/2014 07:06 PM, Chris Angelico wrote: On Sun, Nov 23, 2014 at 11:51 AM, Ron Adam wrote: > > >On 11/22/2014 06:20 PM, Chris Angelico wrote: >> >>Hmmm, there's no such thing as tuple comprehensions. > >Just didn't think it through quite well enough. But you are correct, that >would b

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On 11/22/2014 05:11 PM, Raymond Hettinger wrote: >> On Nov 22, 2014, at 2:45 PM, Chris Angelico wrote: >> >> Does your middleware_generator work with just a single element, >> yielding either one output value or none? > > I apologize if I didn't make the point clearly. The middleware example was

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On Sun, Nov 23, 2014 at 12:11 PM, Raymond Hettinger wrote: > The worry is that your proposal intentionally breaks that code which is > currently > bug free, clean, fast, stable, and relying on a part of the API that has > been > guaranteed and documented from day one. (I'd just like to mention th

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

> On Nov 22, 2014, at 2:45 PM, Chris Angelico wrote: > > Does your middleware_generator work with just a single element, > yielding either one output value or none? I apologize if I didn't make the point clearly. The middleware example was just simple outline of calling next(), doing some pr

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On Sun, Nov 23, 2014 at 11:51 AM, Ron Adam wrote: > > > On 11/22/2014 06:20 PM, Chris Angelico wrote: >> >> Hmmm, there's no such thing as tuple comprehensions. > > Just didn't think it through quite well enough. But you are correct, that > would be a generator expression. > > One less case to wo

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On 11/22/2014 06:20 PM, Chris Angelico wrote: On Sun, Nov 23, 2014 at 11:05 AM, Ron Adam wrote: >Se we have these... > > Tuple Comprehension (...) > List Comprehension [...] > Dict Comprehension {...} Colon make's it different from sets. > Set Comprehension {...} > >I

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On Sun, Nov 23, 2014 at 11:05 AM, Ron Adam wrote: > Se we have these... > > Tuple Comprehension (...) > List Comprehension [...] > Dict Comprehension {...} Colon make's it different from sets. > Set Comprehension {...} > > I don't think there is any other way to create the

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On 11/22/2014 04:23 PM, Chris Angelico wrote: On Sun, Nov 23, 2014 at 8:03 AM, Ron Adam wrote: >>Making comprehensions work more like generator expressions >>would, IMO, imply making the same change to all for loops: having a >>StopIteration raised by the body of the loop quietly terminate th

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

On Sat Nov 22 2014 at 10:00:03 AM Nick Coghlan wrote: > > On 22 Nov 2014 07:37, "Donald Stufft" wrote: > > > On Nov 21, 2014, at 3:59 PM, Ned Deily wrote: > > > > Sure, I get that. But we're not even talking here about the main > Python > > > docs since they are part of the CPython repos, only

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On Sun, Nov 23, 2014 at 7:30 AM, Raymond Hettinger wrote: > Legitimate Use Cases for Raising StopIteration in a Generator > > > In a producer/consumer generator chain, the input generator signals > it is done by raising StopIteration and

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On Sun, Nov 23, 2014 at 8:03 AM, Ron Adam wrote: >> Making comprehensions work more like generator expressions >> would, IMO, imply making the same change to all for loops: having a >> StopIteration raised by the body of the loop quietly terminate the >> loop. > > > I'm not suggesting making any c

[Python-Dev] PCBuild project updates

​Hi all Just attracting some attention to http://bugs.python.org/issue22919 for those of us who build Python out of the PCBuild folder. More details/patches there, but the tl;dr is * Still works with VS 2010 (and now VS 2013 and VS 2015 too) * Build time should be reduced * Tools\buildbot\*.ba

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On 11/22/2014 03:01 PM, Terry Reedy wrote: Then both a comprehension and a generator expressions can be viewed as defining iterators, A comprehension is not an iterator. The above would make a list or set comprehension the same as feeding a genexp to list() or set(). Correct, but we coul

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On 11/22/2014 02:16 PM, Chris Angelico wrote: On Sun, Nov 23, 2014 at 6:49 AM, Ron Adam wrote: > >OPTION 1: > >Make comprehensions act more like generator expressions. > >It would mean a while loop in the object creation point is converted to a >for loop. (or something equivalent.) > >Then bo

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On 11/22/2014 2:49 PM, Ron Adam wrote: On 11/22/2014 08:31 AM, Nick Coghlan wrote: I'm definitely coming around to the point of view that, even if we wouldn't design it the way it currently works given a blank slate, the alternative design doesn't provide sufficient benefit to justify the cos

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

> On Nov 22, 2014, at 6:31 AM, Nick Coghlan wrote: > > I'm definitely coming around to the point of view that, even if we wouldn't > design it the way it currently works given a blank slate, the alternative > design doesn't provide sufficient benefit to justify the cost of changing the > beha

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On Sun, Nov 23, 2014 at 6:49 AM, Ron Adam wrote: > > OPTION 1: > > Make comprehensions act more like generator expressions. > > It would mean a while loop in the object creation point is converted to a > for loop. (or something equivalent.) > > Then both a comprehension and a generator expressions

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On 11/22/2014 06:31 AM, Nick Coghlan wrote: > > A particularly relevant variant of the idiom is the approach of writing > "__iter__" directly as a generator, rather than creating a separate custom > iterator class. In that context, the similarities between the __iter__ > implementation and the cor

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On 11/22/2014 08:31 AM, Nick Coghlan wrote: On 22 Nov 2014 02:51, "Antoine Pitrou" mailto:solip...@pitrou.net>> wrote: > > On Fri, 21 Nov 2014 05:47:58 -0800 > Raymond Hettinger mailto:raymond.hettin...@gmail.com>> wrote: > > > > Another issue is that it breaks the way I and others have t

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

> On Nov 22, 2014, at 9:59 AM, Nick Coghlan wrote: > > > On 22 Nov 2014 07:37, "Donald Stufft" > wrote: > > > On Nov 21, 2014, at 3:59 PM, Ned Deily > > > wrote: > > > Sure, I get that. But we're not even talking here about the main Python > > >

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

On Sun, 23 Nov 2014 00:59:42 +1000, Nick Coghlan wrote: > OK, different question. Has anyone here actually even *read* the workflow > PEPs I wrote? They were on the agenda for the language summit, but got > bumped due to lack of time (which I'm still annoyed about, given the > comparatively incons

Re: [Python-Dev] Move selected documentation repos to PSF BitBucket account?

On 22 Nov 2014 07:37, "Donald Stufft" wrote: > > On Nov 21, 2014, at 3:59 PM, Ned Deily wrote: > > Sure, I get that. But we're not even talking here about the main Python > > docs since they are part of the CPython repos, only ancillary repos like > > PEPs and the developer's guide. The level o

Re: [Python-Dev] PEP 479: Change StopIteration handling inside generators

On 22 Nov 2014 02:51, "Antoine Pitrou" wrote: > > On Fri, 21 Nov 2014 05:47:58 -0800 > Raymond Hettinger wrote: > > > > Another issue is that it breaks the way I and others have taught for years that generators are a kind of iterator (an object implementing the iterator protocol) and that a prima

Re: [Python-Dev] Support for Linux perf

On 17.11.2014 23:09, Francis Giraldeau wrote: > Hi, > ... > The PEP-418 is about performance counters, but there is no mention o > Anyway, I think we must change CPython to support tools such as perf. > Any thoughts? > there are some patches available adding systemtap and dtrace probes, which s