On Tue, 2005-02-01 at 10:30 +1100, Donovan Baarda wrote:
> On Mon, 2005-01-31 at 15:16 -0500, Nathan Binkert wrote:
> > > Wouldn't it be nicer to have a facility that let you send messages
> > > between processes and manage concurrency properly instead? You'll need
[...]
> A quick google search re
On Mon, 2005-01-31 at 15:16 -0500, Nathan Binkert wrote:
> > Wouldn't it be nicer to have a facility that let you send messages
> > between processes and manage concurrency properly instead? You'll need
> > most of this anyway to do multithreading sanely, and the benefit to the
> > multiple proces
> Wouldn't it be nicer to have a facility that let you send messages
> between processes and manage concurrency properly instead? You'll need
> most of this anyway to do multithreading sanely, and the benefit to the
> multiple process model is that you can scale to multiple machines, not
> just pr
Barry Warsaw wrote:
I've heard rumors that SF was going to be making svn available. Anybody
know more about that? I'd be +1 on moving from cvs to svn.
It was on their "things we do in 2005" list. 2005 isn't over yet...
I wouldn't be surprised if it gets moved to their "things we do in 2006"
list
Evan Jones wrote:
The next page has a
micro-benchmark that shows reference counting performing very poorly.
Not to mention that Python has a garbage collector *anyway,* so wouldn't
it make sense to get rid of the reference counting?
It's not clear what these numbers exactly mean, but I don't bel
On Jan 31, 2005, at 10:43, Evan Jones wrote:
On Jan 31, 2005, at 0:17, Guido van Rossum wrote:
The "just kidding" applies to the whole list, right? None of these
strike me as good ideas, except for improvements to function argument
passing.
Really? You see no advantage to moving to garbage collecti
On Jan 31, 2005, at 0:17, Guido van Rossum wrote:
The "just kidding" applies to the whole list, right? None of these
strike me as good ideas, except for improvements to function argument
passing.
Really? You see no advantage to moving to garbage collection, nor
allowing Python to leverage multiple
On Mon, 2005-01-31 at 00:00, Skip Montanaro wrote:
> Raymond> I had hoped for the core of p3k to be built for scratch ...
>
> Then we should just create a new CVS module for it (or go whole hog and try
> a new revision control system altogether - svn, darcs, arch, whatever).
I've heard rumors
On Mon, 2005-01-31 at 00:17, Guido van Rossum wrote:
> > I had hoped for the core of p3k to be built for scratch [...]
>
> Stop right there.
Phew!
-Barry
signature.asc
Description: This is a digitally signed message part
___
Python-Dev mailing list
P
> I had hoped for the core of p3k to be built for scratch [...]
Stop right there.
I used to think that was a good idea too, and was hoping to do exactly
that (after retirement :). However, the more I think about it, the
more I believe it would be throwing away too much valuable work.
Please read
Raymond> I had hoped for the core of p3k to be built for scratch ...
Then we should just create a new CVS module for it (or go whole hog and try
a new revision control system altogether - svn, darcs, arch, whatever).
Skip
___
Python-Dev mailing lis
Neal Norwitz
> I thought about making a p3k branch in CVS
I had hoped for the core of p3k to be built for scratch so that even the
most pervasive and fundamental implementation choices would be open for
discussion:
* Possibly write in C++.
* Possibly replace bytecode with Forth style threaded co
Neal Norwitz wrote:
On Wed, 26 Jan 2005 09:47:41 -0500, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
[SNIP]
Any ideas how we could start to realize some benefits of Py3.0 before
it arrives? I'm not sure if this is worth it, if it's premature, or
if there are other ways to acheive the goal of easin
On Wed, 26 Jan 2005 09:47:41 -0500, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
>
> This is what I mean about the patch taking on a life of its own. It's
> an optimization patch that slows down METH_O and METH_NOARGS. It's a
> incremental change that throws away backwards compatibility. It's a
14 matches
Mail list logo
