pypy 1.0 release meeting invitation
Hi PyPy-developers! The release is drawing closer (the currently planned date is February, 15th) and it is time to meet and discuss the necessary work. Therefore we invite you all to a sync-meeting on Friday, February 2nd, 2007 14.00 UTC+1 #pypy-sync Regular Topics ============== * activity reports (LAST/NEXT/BLOCKERS, everybody posts prepared comma-separated lists of things) * resolving blockers/dependencies Release Goals ============= This topic is to get a common view on what the release goals are. A preliminary list of goals is: * object optimizations * pypy.net * more working modules * some performance * maturity * build tool * JIT preview * security prototype * js backend? * debian packaging? Task Planning ============= This topic is to collect tasks to be done for the release and divide them among people. Some tasks that we could think of: * work out a timeframe for jit usefulness * fix llvm(?) * test pypy-cs, run benchmarks. * windows testing! * documentation!!! * pypy.net * object optimizations (WP6) * release announcement * improve getting-started * transparent proxies * security prototype * make build-tool useable * polish js backend? Hope to see you all on friday! Cheers, mwh -- Python enjoys making tradeoffs that drive *someone* crazy <wink>. -- Tim Peters, comp.lang.python
Hi Michael! On Tue, 30 Jan 2007, Michael Hudson wrote:
Hi PyPy-developers!
The release is drawing closer (the currently planned date is February, 15th)
cool & congrats!
by this do you mean implement weakrefs and other gc stuff - or it is more fundamentally broken? :-) Cheers, Richard
Richard Emslie <rxe@ukshells.co.uk> writes:
The recent refactoring to implement more external functions using rctypes broke pypy-llvm -- llvm doesn't support some rctypes-ish operations like direct_arrayitems. But also, it turns out that just about all pypy-llvm's ever segfault when running commands like "./pypy-llvm --no-compile --backendopt translate.py targetpystonedalone.py". So, er, both, in summary :-) Will you be at PyCon? Cheers, mwh --
Thanks I can't wait! On 1/30/07, Michael Hudson <mwh@python.net> wrote:
Hi Michael, Carl Friedrich, thanks for inviting! it may make sense to also have a brief topic about the upcoming py lib release, and some changes that are soon going to be merged - not sure though if we wait until pypy-sync for that, so be warned already now, and please add the topic. best & thanks, holger On Tue, Jan 30, 2007 at 17:22 +0100, Michael Hudson wrote:
-- merlinux GmbH Steinbergstr. 42 31139 Hildesheim http://merlinux.de tel +49 5121 20800 75 (fax 77)
Hi all! Michael Hudson wrote:
Another task that I came up with: we should try to document our config options. Maybe not the more obscure ones, though :-). Imo this is quite important, since the list of options is very big and makes it hard to find what you are looking for. There should also be more "high-level" options like --allworkingmodules and --faassen (which should be renamed for the release, I guess :-) ). And maybe a small "guide through the option jungle" or something like this. Cheers, Carl Friedrich
Hi Michael! On Tue, 30 Jan 2007, Michael Hudson wrote:
Hi PyPy-developers!
The release is drawing closer (the currently planned date is February, 15th)
cool & congrats!
by this do you mean implement weakrefs and other gc stuff - or it is more fundamentally broken? :-) Cheers, Richard
Richard Emslie <rxe@ukshells.co.uk> writes:
The recent refactoring to implement more external functions using rctypes broke pypy-llvm -- llvm doesn't support some rctypes-ish operations like direct_arrayitems. But also, it turns out that just about all pypy-llvm's ever segfault when running commands like "./pypy-llvm --no-compile --backendopt translate.py targetpystonedalone.py". So, er, both, in summary :-) Will you be at PyCon? Cheers, mwh --
Thanks I can't wait! On 1/30/07, Michael Hudson <mwh@python.net> wrote:
Hi Michael, Carl Friedrich, thanks for inviting! it may make sense to also have a brief topic about the upcoming py lib release, and some changes that are soon going to be merged - not sure though if we wait until pypy-sync for that, so be warned already now, and please add the topic. best & thanks, holger On Tue, Jan 30, 2007 at 17:22 +0100, Michael Hudson wrote:
-- merlinux GmbH Steinbergstr. 42 31139 Hildesheim http://merlinux.de tel +49 5121 20800 75 (fax 77)
Hi all! Michael Hudson wrote:
Another task that I came up with: we should try to document our config options. Maybe not the more obscure ones, though :-). Imo this is quite important, since the list of options is very big and makes it hard to find what you are looking for. There should also be more "high-level" options like --allworkingmodules and --faassen (which should be renamed for the release, I guess :-) ). And maybe a small "guide through the option jungle" or something like this. Cheers, Carl Friedrich
participants (6)
-
Carl Friedrich Bolz -
holger krekel -
James Matthews -
Michael Hudson -
Paul deGrandis -
Richard Emslie