On Tue, Jan 11, 2011 at 11:10 AM, Maciej Fijalkowski <fij...@gmail.com> wrote: > On Tue, Jan 11, 2011 at 2:58 PM, holger krekel <hol...@merlinux.eu> wrote: >> Hi Maciej, >> >> it's not clear to me what posts your are refering to. Certainly >> not the original post from Nathan? >> >> If you think it's a general issue then do a top-level posting and please >> suggest how "non-active" (defined how?) pypy developers are supposed to >> know if some topic is interesting without posting about it. And include >> some concrete rules about when side discussions are ok and when not. >> Probably all harder to do than improving your ignoring techniques? > > Well, I can easily ignore things that are not interesting to me. > > My point was that discussions about topics (like capabilities) only > make sense if there is someone even remotely interested in > implementing that in PyPy. Otherwise discussions tend to drift into > "but that's also a cool idea", which is off-topic for PyPy, since > noone actually wants to implement any of those.
Well we could tell him how to implement capabilities in pypy and how easy/hard this seems. Without looking much at it I think you could implement it by creating a new object space, like those: http://codespeak.net/pypy/dist/pypy/doc/objspace-proxies.html > For example I would say all GIL-removal discussions are offtopic > unless someone has a will to experiment with implementing it. This is also something I see as a problem in communication, there should be at least a FAQ question about this or even a good description of how pypy does Threads and why it does the same thing as CPython. > That's, as I said above, my personal opinion, backed by a fact that > this is the list for discussing developing PyPy (so some people, like > me, feel obliged to read whole discussions here). Feel free to propose > some other guidelines for what is on-topic and what is off-topic for > that list. Maybe pypy developers could steers discussions into being on topic. > As active I mean anyone doing any work on PyPy. Be it a typo in documentation > :) People feel that they are helping by discussing on the list ideas and approaches that maybe the pypy team might not know. > Cheers, > fijal > -- Leonardo Santagada _______________________________________________ pypy-...@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
