Re: [Python-Dev] Proposed revision of PEP 3 (using the issue tracker)

2008-02-24 Thread Steven H. Rogers
Ron Adam wrote: > Nick Coghlan wrote: > >> Martin v. Löwis wrote: >> >>> One issue to consider is also politeness. People sometimes complain that >>> they feel treated unfair if their report is declared "invalid" - they >>> surely believed it was a valid report, at the time they made it. >>

Re: [Python-Dev] Exploration PEP : Concurrency for moderately massive (4 to 32 cores) multi-core architectures

2007-09-19 Thread Steven H. Rogers
Krishna Sankar wrote: > Folks, >As a follow-up to the py3k discussions started by Bruce and Guido, I > pinged Brett and he suggested I submit an exploratory proposal. Would > appreciate insights, wisdom, the good, the bad and the ugly. > > A)Does it make sense ? > B)Which application

Re: [Python-Dev] Product function patch [issue 1093]

2007-09-04 Thread Steven H. Rogers
Robert Kern wrote: > I invite Greg and Steven and whoever else is interested to discuss ideas for > the > PEP on numpy-discussion. I'm skeptical, seeing what currently has been > suggested, but some more details could easily allay that. > > http://projects.scipy.org/mailman/listinfo/numpy-discus

Re: [Python-Dev] Product function patch [issue 1093]

2007-09-04 Thread Steven H. Rogers
Guido van Rossum wrote: > What makes 3.0 so special? Additions to the stdlib can be considered > at any feature release. Frankly, 3.0 is already so loaded with new > features (and removals) that I'm not sure it's worth pile this onto > it. > I actually wrote 3.x, not 3.0. I agree that it makes

Re: [Python-Dev] Product function patch [issue 1093]

2007-09-04 Thread Steven H. Rogers
Greg Ewing wrote: > Martin v. Löwis wrote: > >> I think this requires a PEP, and explicit support from the >> NumPy people. >> > > Someone who knows more about numpy's internals would > be needed to figure out what the details should be > like in order to be usable by numpy. But I could wri

Re: [Python-Dev] Product function patch [issue 1093]

2007-09-04 Thread Steven H. Rogers
Guido van Rossum wrote: > I still don't see why the standard library needs to be weighed down > with a competitor to numpy. Including a subset of numpy was considered > in the past, but it's hard to decide on the right subset. In the end > it was decided that numpy is too big to become a standard l

Re: [Python-Dev] Product function patch [issue 1093]

2007-09-04 Thread Steven H. Rogers
Greg Ewing wrote: > Guido van Rossum wrote: > >> But what's the point, given that numpy already exists? Wouldn't you >> just be redoing the work that numpy has already done? >> > > Sometimes I just want to do something simple like > adding two vectors together, and it seems unreasonable > t

Re: [Python-Dev] PyPy 1.0: JIT compilers for free and more

2007-03-27 Thread Steven H. Rogers
Aahz wrote: > On Tue, Mar 27, 2007, Armin Rigo wrote: >> Sorry for the spamming. I hope this will be of interest to some of you. > > This is not spamming, this is wonderful news! Congratulations! Second the congrats! ___ Python-Dev mailing list Python

Re: [Python-Dev] Policy Decisions, Judgment Calls, and Backwards Compatibility (was Re: splitext('.cshrc'))

2007-03-08 Thread Steven H. Rogers
[EMAIL PROTECTED] wrote: > > In the past I've begged off of actually writing PEPs because I don't > have the time, but if there is interest in codifying this I think I > don't have the time *not* to write it. I'd prefer to document the > pending/deprecate/remove policy first, but I can write u