Re: [pypy-dev] missing things for making PyPy "production" ready (for some value of production)

2007-11-14 Thread David Cournapeau
Martijn Faassen wrote: > > Yes, this one would be a major challenge. If you can crack it and the > PyPy interpreter offers another benefit (an obvious one is speed), you > will be in awesome position. If not, the other benefits will have to > weigh more strongly. This is definitely one to evolve

Re: [pypy-dev] Pypy and app-level ctypes

2007-11-14 Thread Maciek Fijalkowski
Martijn Faassen wrote: > Maciek Fijalkowski wrote: > >> As a discussion regarding pypy being production-ready heats a bit, I've >> go a practical question: >> >> How useful would be to have app-level ctypes for pypy? Another question >> how less useful it would be if it won't provide python-ap

Re: [pypy-dev] Pypy and app-level ctypes

2007-11-14 Thread Martijn Faassen
Maciek Fijalkowski wrote: > As a discussion regarding pypy being production-ready heats a bit, I've > go a practical question: > > How useful would be to have app-level ctypes for pypy? Another question > how less useful it would be if it won't provide python-api part (which > would be as easy

[pypy-dev] Pypy and app-level ctypes

2007-11-14 Thread Maciek Fijalkowski
As a discussion regarding pypy being production-ready heats a bit, I've go a practical question: How useful would be to have app-level ctypes for pypy? Another question how less useful it would be if it won't provide python-api part (which would be as easy to provide as C-level bindings for CPy

Re: [pypy-dev] another pypy blog entry from sun

2007-11-14 Thread Martijn Faassen
Stephan Diehl wrote: > just in case you don't read programming.reddit.com: > there is another blog enty from somebody at Sun (John Rose) > http://blogs.sun.com/jrose/entry/a_day_with_pypy It's also interesting to read the comments on Reddit: http://programming.reddit.com/info/60jlu/comments/ It'

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Terry Reedy
"Laura Creighton" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] My reading of Bray's post is that it was cautiously positive -- about as much as you could expect in public comments from someone *considering* funding some work. The first comment about 'vibrant community' is alrea

Re: [pypy-dev] missing things for making PyPy "production" ready (for some value of production)

2007-11-14 Thread Martijn Faassen
Hey Carl, Carl Friedrich Bolz wrote: > I thought I would start a new thread for discussing what PyPy needs to > become "production ready" (whatever that is) and succeed as a Python > implementation. This is something were outside opinions are very welcome > (of course there is no guarantee we can

Re: [pypy-dev] missing things for making PyPy "production" ready (for some value of production)

2007-11-14 Thread Ondrej Certik
> >From previous discussions, I suspect I'm not the only lurker-fan who would > be willing to commit time to working on numericentric graph optimizations > when that becomes a worthwhile investment. There's no reason that the > mostly-fortran bits of python code shouldn't run almost as fast as for

Re: [pypy-dev] missing things for making PyPy "production" ready (for some value of production)

2007-11-14 Thread Antonio Cuni
Charles Oliver Nutter wrote: >> Moreover, I would add to this list that the possibility to compile >> python to jvm bytecode instead of python bytecode; maybe a pypy-jvm >> would be usable even without it, but e.g. developing applets requires >> it. >> >> Hopefully, I'll be able to work on t

Re: [pypy-dev] missing things for making PyPy "production" ready (for some value of production)

2007-11-14 Thread Antonio Cuni
Martijn Faassen wrote: >> - for PyPy-JVM: bindings to allow the interaction with arbitrary Java >> libraries, threading support > > Does this already exist for PyPy-CLR? yes, but it's more or less only a proof of concept. You can use .NET classes from Python but you can't, e.g., inherit fr

Re: [pypy-dev] missing things for making PyPy "production" ready (for some value of production)

2007-11-14 Thread Charles Oliver Nutter
Antonio Cuni wrote: > Carl Friedrich Bolz wrote: > >> - for PyPy-JVM: bindings to allow the interaction with arbitrary Java >> libraries, threading support > > Moreover, I would add to this list that the possibility to compile > python to jvm bytecode instead of python bytecode; maybe a py

Re: [pypy-dev] missing things for making PyPy "production" ready (for some value of production)

2007-11-14 Thread Maciej Fijalkowski
Just a small note. We've got nowadays pieces of code that can help you handle safety-for-speed even in compiled rpython code, --sandbox uses those. (Like check for NULL pointers, enable assertions, etc.) But besides, I fully agree to the BIG FAT WARNING. This code is mostly there for tests. Even s

Re: [pypy-dev] missing things for making PyPy "production" ready (for some value of production)

2007-11-14 Thread Antonio Cuni
Douglas McNeil wrote: > This is probably the most low-hanging fruit there could be for a (fully > float-aware) JIT. The functions tends to be embarrassingly simple, and > seldom leave the int/float/list domain. Most numerical code is borderline > RPython as-is. if everything you need is to e

Re: [pypy-dev] missing things for making PyPy "production" ready (for some value of production)

2007-11-14 Thread Douglas McNeil
cfb wrote: > I thought I would start a new thread for discussing what PyPy needs to > become "production ready" (whatever that is) and succeed as a Python > implementation. > [...] > - Speed. The JIT is still not in a state where it really speeds up >arbitrary Python code. I expect this to c

Re: [pypy-dev] missing things for making PyPy "production" ready (for some value of production)

2007-11-14 Thread Antonio Cuni
Carl Friedrich Bolz wrote: > - for PyPy-JVM: bindings to allow the interaction with arbitrary Java > libraries, threading support Moreover, I would add to this list that the possibility to compile python to jvm bytecode instead of python bytecode; maybe a pypy-jvm would be usable even wit

[pypy-dev] missing things for making PyPy "production" ready (for some value of production)

2007-11-14 Thread Carl Friedrich Bolz
Hi all, I thought I would start a new thread for discussing what PyPy needs to become "production ready" (whatever that is) and succeed as a Python implementation. This is something were outside opinions are very welcome (of course there is no guarantee we can implement all of your wishes :-) ).

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Gary Robinson
> Well, I guess what we really need to get adoption in this area is a > reason for people to switch to PyPy's Python interpreter. Right now > doing this means you get a slower Python, with less available > extensions. Of course you get nice features like lazy objects, > Stackless, transparent proxi

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Martijn Faassen
Hey Paul, On Nov 14, 2007 4:19 PM, Paul deGrandis <[EMAIL PROTECTED]> wrote: [snip] > Financial concerns have become a part of PyPy, it's just the way it is. I do understand that. I've been writing open source software for a living and paying the rent since 2001 or thereabouts. I want to make sur

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Paul deGrandis
Martijn, Don't get me wrong, like Carl, without taking finances into account, I agree with you totally. As a software engineering major, I can also see most of your arguments from a purely engineering and practical perspective. I mean, c'mon, who doesn't want to see PyPy offer you the ultimate P

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Martijn Faassen
David Cournapeau wrote: [snip] > Sorry for jumping in, and I hope this is not too OT, but what is missing > for a 'real' CPython alternative ? I'm happy you are jumping in, I think stuff like this should be discussed. Perhaps we should start another thread, though. > - some bits of the stan

Re: [pypy-dev] another pypy blog entry from sun

2007-11-14 Thread Martijn Faassen
Hey, Stephan Diehl wrote: > just in case you don't read programming.reddit.com: > there is another blog enty from somebody at Sun (John Rose) > http://blogs.sun.com/jrose/entry/a_day_with_pypy Yeah, I saw it too. Nice and positive, and in many parts over my head. :) Regards, Martijn __

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Martijn Faassen
Sanghyeon Seo wrote: > 2007/11/14, Martijn Faassen <[EMAIL PROTECTED]>: >> Your Python-centric work is not done until I have a serious shot at >> downloading or building a PyPy-based interpreter, run it on top of >> *some* backend, and can start porting, say, Zope 3 on top of it. Or >> Twisted. Or

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Maciej Fijalkowski
On Nov 14, 2007 3:38 PM, David Cournapeau <[EMAIL PROTECTED]> wrote: > Carl Friedrich Bolz wrote: > > Hi Martijn, > > > > let me first note that I agree with a lot of your points, when not > > taking the financial side of things into account. I will ignore the > > financial side of things in this

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Martijn Faassen
Hey, On Nov 14, 2007 3:41 PM, Carl Friedrich Bolz <[EMAIL PROTECTED]> wrote: > Martijn Faassen wrote: [snip] > > * writing CPython modules in RPython (I completely lost track of what > > the state of this is since there have been a lot of changes) > > It's still working but mostly accidentally.

Re: [pypy-dev] thunk object space : become() quirks

2007-11-14 Thread Carl Friedrich Bolz
Hi Boris, Boris Borcic wrote: > Looking for a way to use pypy in any manner, I came up with an idea for a > deterministic sudoku solver that would use the 'become()' feature of the thunk > object space. However, this doesn't work as I expected. The following shell > trace illustrates my problem. I

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread David Cournapeau
Carl Friedrich Bolz wrote: > Hi Martijn, > > let me first note that I agree with a lot of your points, when not > taking the financial side of things into account. I will ignore the > financial side of things in this mail (since I don't think anybody > proposes to focus on something completely diff

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Maciej Fijalkowski
> > Martijn Faassen wrote: > [snip] > > Again, I'm not trying to criticize what the project has already done. > > I'm trying to be a voice of pragmatism and the voice of a potential > open > > source end-user. Listen to me if you like; it's not an enemy voice. > > There are two PyPy technologie

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Carl Friedrich Bolz
Hi Martijn, let me first note that I agree with a lot of your points, when not taking the financial side of things into account. I will ignore the financial side of things in this mail (since I don't think anybody proposes to focus on something completely different than our Python interpreter _wit

[pypy-dev] another pypy blog entry from sun

2007-11-14 Thread Stephan Diehl
just in case you don't read programming.reddit.com: there is another blog enty from somebody at Sun (John Rose) http://blogs.sun.com/jrose/entry/a_day_with_pypy Have fun Stephan ___ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev

[pypy-dev] thunk object space : become() quirks

2007-11-14 Thread Boris Borcic
Hello, Looking for a way to use pypy in any manner, I came up with an idea for a deterministic sudoku solver that would use the 'become()' feature of the thunk object space. However, this doesn't work as I expected. The following shell trace illustrates my problem. Is this a bug or otherwise ? Can

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Martijn Faassen
Paul deGrandis wrote: > I have stayed quiet thus far but I wanted to make sure everyone knew I > was still around and thought I'd contribute to the discussion now. > > I have been asked to give the same PyPy talk three times in the > Philadelphia area, and everytime I give a talk based on some of

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Sanghyeon Seo
2007/11/14, Martijn Faassen <[EMAIL PROTECTED]>: > Your Python-centric work is not done until I have a serious shot at > downloading or building a PyPy-based interpreter, run it on top of > *some* backend, and can start porting, say, Zope 3 on top of it. Or > Twisted. Or lxml. Or Pygame. Well, no

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Martijn Faassen
Laura Creighton wrote: > In a message of Wed, 14 Nov 2007 03:53:18 +0100, Jacob Hallén writes: > >>> So I'll definitely complain if you spend a lot of time on Ruby (or >>> Smalltalk for that matter) before Python's all the way there. I think >>> that'd be a bad idea for a whole range of reasons -

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Martijn Faassen
Hey, Jacob Hallén wrote: > Den Tuesday 13 November 2007 19.42.03 skrev Martijn Faassen: >> I'm convinced the body count of Python users is probably still quite a >> bit larger than Ruby users. I also have a strong suspicion far more >> people are using Python web frameworks than there are people u

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Jean-Paul Calderone
On Wed, 14 Nov 2007 13:24:41 +0100, Laura Creighton <[EMAIL PROTECTED]> wrote: >In a message of Wed, 14 Nov 2007 03:53:18 +0100, Jacob Hallén writes: > >>> So I'll definitely complain if you spend a lot of time on Ruby (or >>> Smalltalk for that matter) before Python's all the way there. I think >>

Re: [pypy-dev] pypy on Tim Bray's blog

2007-11-14 Thread Laura Creighton
In a message of Wed, 14 Nov 2007 03:53:18 +0100, Jacob Hallén writes: >> So I'll definitely complain if you spend a lot of time on Ruby (or >> Smalltalk for that matter) before Python's all the way there. I think >> that'd be a bad idea for a whole range of reasons - get the last 10% >> done for P