Re: [Python-Dev] [Python-checkins] cpython: Add optional *func* argument to itertools.accumulate().

On Sun, Mar 27, 2011 at 10:53 PM, Nick Coghlan wrote: > On Mon, Mar 28, 2011 at 2:11 PM, Daniel Stutzbach > wrote: > > Is there a good use-case for the func argument? > > The examples that Raymond gives in the docs (cumulative > multiplication, running min/max, cash flow accumulation) look fai

Re: [Python-Dev] [Python-checkins] cpython: Add optional *func* argument to itertools.accumulate().

On Mar 28, 2011, at 12:38 AM, Daniel Stutzbach wrote: > On Sun, Mar 27, 2011 at 10:53 PM, Nick Coghlan wrote: > On Mon, Mar 28, 2011 at 2:11 PM, Daniel Stutzbach > wrote: > > Is there a good use-case for the func argument? > > The examples that Raymond gives in the docs (cumulative > multipl

Re: [Python-Dev] Hg: inter-branch workflow

On 27 March 2011 20:15, Neil Schemenauer wrote: > Guido van Rossum wrote: >> What is "rebase"? Why does everyone want it and hate it at the same time? [...] > The other school, which I am a member of, considers a logical > development sequence more important than actual development history. > I l

Re: [Python-Dev] Hg: inter-branch workflow

On Mon, Mar 28, 2011 at 8:13 PM, Paul Moore wrote: > For people in the "clean history" school, I'd recommend looking at mq > for your personal use. But it's definitely an advanced feature of > Mercurial, so it may be better to understand core Mercurial (and at > least temporarily accept that Mercu

Re: [Python-Dev] Hg: inter-branch workflow

On 28 March 2011 11:35, Nick Coghlan wrote: > On Mon, Mar 28, 2011 at 8:13 PM, Paul Moore wrote: >> For people in the "clean history" school, I'd recommend looking at mq >> for your personal use. But it's definitely an advanced feature of >> Mercurial, so it may be better to understand core Mercu

Re: [Python-Dev] Hg: inter-branch workflow

On 28/03/2011 11:35, Nick Coghlan wrote: On Mon, Mar 28, 2011 at 8:13 PM, Paul Moore wrote: For people in the "clean history" school, I'd recommend looking at mq for your personal use. But it's definitely an advanced feature of Mercurial, so it may be better to understand core Mercurial (and at

Re: [Python-Dev] Hg: inter-branch workflow

On Mon, Mar 28, 2011 at 10:48 PM, Michael Foord wrote: > On 28/03/2011 11:35, Nick Coghlan wrote: >> Mercurial makes merging easy enough that I'm happy with the way that >> approach is working so far. > > For any non-trivial work I think this is the best approach. You still get > all the advantage

Re: [Python-Dev] improvement to declaring abstract properties

On Sat, Mar 19, 2011 at 3:06 PM, Darren Dale wrote: > I suggested at python-ideas a way that the declaration of abstract > properties could be improved to support the decorator syntax: > http://mail.python.org/pipermail/python-ideas/2011-March/009411.html . > A relatively small change to the prope

Re: [Python-Dev] Python 2.7 on Irix 6.5.22 fails ctypes callback test

On Sun, 27 Mar 2011 19:07:08 -0400 (EDT) "David E. Cross" wrote: > Trying to compile and install Python 2.7 on irix 6.5.22 IP22 (N32 ABI > model), Using gcc-4.5.1 and binutils 2.20.1. Everything goes well (I > applied th patches listed at: > http://bugs.python.org/file15915/python-2.7-irix.pat

Re: [Python-Dev] Hg: inter-branch workflow

On Mar 27, 2011, at 01:39 PM, Neil Schemenauer wrote: >Barry Warsaw wrote: >> I'm asking because I don't know hg and git well enough to answer the >> question. In my own use of Bazaar over the last 4+ years, I've almost never >> rebased or even been asked to. > >Maybe it depends on what kind of

Re: [Python-Dev] [Python-checkins] cpython: Add optional *func* argument to itertools.accumulate().

On 28.03.2011 09:49, Raymond Hettinger wrote: > > On Mar 28, 2011, at 12:38 AM, Daniel Stutzbach wrote: > >> On Sun, Mar 27, 2011 at 10:53 PM, Nick Coghlan > > wrote: >> >> On Mon, Mar 28, 2011 at 2:11 PM, Daniel Stutzbach > > wrote:

[Python-Dev] Issue Tracker

Greetings! I'm not sure where the best place is to ask this question, so I'll start here -- feel free to redirect me if necessary. I would like to have some software to keep track of bugs, to-do's, ideas, etc., etc. -- you know, an issue tracker! Naturally I thought of the one we use to tra

Re: [Python-Dev] Issue Tracker

On Mon, Mar 28, 2011 at 15:05, Ethan Furman wrote: > Greetings! > > I'm not sure where the best place is to ask this question, so I'll start > here -- feel free to redirect me if necessary. > > I would like to have some software to keep track of bugs, to-do's, ideas, > etc., etc. -- you know, an

Re: [Python-Dev] Issue Tracker

On Mon, 28 Mar 2011 15:14:20 -0500 Brian Curtin wrote: > On Mon, Mar 28, 2011 at 15:05, Ethan Furman wrote: > > > Greetings! > > > > I'm not sure where the best place is to ask this question, so I'll start > > here -- feel free to redirect me if necessary. > > > > I would like to have some softw

Re: [Python-Dev] Issue Tracker

Brian Curtin wrote: On Mon, Mar 28, 2011 at 15:05, Ethan Furman > wrote: Greetings! I'm not sure where the best place is to ask this question, so I'll start here -- feel free to redirect me if necessary. I would like to have some software to keep trac

Re: [Python-Dev] Issue Tracker

Antoine Pitrou wrote: On Mon, 28 Mar 2011 15:14:20 -0500 Brian Curtin wrote: On Mon, Mar 28, 2011 at 15:05, Ethan Furman wrote: I would like to have some software to keep track of bugs, to-do's, ideas, etc., etc. -- you know, an issue tracker! Naturally I thought of the one we use to track P

Re: [Python-Dev] Hg: inter-branch workflow

On 3/28/2011 6:13 AM, Paul Moore wrote: This philosophy is essentially what the "mq" extension to Mercurial tries to capture. In mq, you maintain a series of patches "on top of" your repository, amending, refining and rebasing them as you wish until they are ready to commit, at which time you ta

Re: [Python-Dev] Hg: inter-branch workflow

On 28 March 2011 22:29, Terry Reedy wrote: > From what you write, it seems that mq is actually an unordered patch set, > not a queue (in the FIFO) sense. (Or do you have to commit and remove in > FIFO order?) Why the confusing mislabel, if indeed I understood correctly? It's a queue (FIFO). Sorry

Re: [Python-Dev] [Python-checkins] cpython: Add optional *func* argument to itertools.accumulate().

On Mon, Mar 28, 2011 at 12:49 AM, Raymond Hettinger < raymond.hettin...@gmail.com> wrote: > Do a google code search for R's builtin functions cumsum, cumprod, cummin, > and cummax. Look at mumpy's accumulate ufunc which works with many > operators. APL and K also have an accumulate tool which take

Re: [Python-Dev] Hg: inter-branch workflow

Michael Foord writes: > On 28/03/2011 11:35, Nick Coghlan wrote: > > I'm seeing if I can get the best of both worlds by having a public > > sandbox repo where I work on things (which has the full messy > > history of development on its feature branches), and then just drop > > them into the main

Re: [Python-Dev] Issue Tracker

On Mon, 28 Mar 2011 22:31:12 +0200, Antoine Pitrou wrote: > On Mon, 28 Mar 2011 15:14:20 -0500 > Brian Curtin wrote: > > On Mon, Mar 28, 2011 at 15:05, Ethan Furman wrote: > > > I would like to have some software to keep track of bugs, to-do's, ideas, > > > etc., etc. -- you know, an issue track