Mailman 3 April 2006 - pypy-dev

security prototype & workshop plans/ideas
by hpk＠trillke.net 25 Apr '06

25 Apr '06

Hi folks, from the EU side of things there is the plan to organize a security workshop and implement security features within PyPy. I now talked to my IBM research lab contact in Zuerich, and we discussed a few possibilities for such a workshop and the prototype, in particular two possibilities: - data tagging or "label control", or more generally attaching (security) metainformations to a python object and having those propagate through the program automatically. See e.g. http://www.pmg.lcs.mit.edu/papers/myers-popl99.pdf for some more information in this direction. This is especially interesting for PyPy as - i think - we can probably do better by e.g. also allowing to tag primitive types (JFlow doesn't do that, i think) and allowing things to happen more dynamically at runtime. - sandboxing: allowing to execute (user-supplied/induced) code and preventing it from accessing critical resources, e.g. system IO. Label control could be used for tagging e.g. user-level input with the "untrusted" label and then protecting certain functions to require trusted input (e.g. database/file modifications). Then, there could be explicit untrusted_to_trusted() conversions, turning an untrusted input into a trusted output. This would allow to concisely localise how user-supplied/untrusted input is parsed and checked. I also guess we could also go for a more general metadata-tagging approach which might be useful in more than just the security context. This are just initial ideas - there are arbitrary other possibilities (somewhere care to discuss the "E" lang here?), or are there not? :) The challenge is to find an interesting mechanism that elegantly enables such approaches - which should be the topic of our upcoming security prototype and workshop. Sandboxing and/or e.g. limiting RAM/CPU usage are also interesting to the Python world but probably are a rather orthogonal matter. Regarding the timing of the workshop it seems that something like October this year fits best. It depends on our actual plan and availability/selection of workshop participants if we rather should try to meet in Zuerich or in New York. We can also try to first arrange a discussion with them and then a meeting for presenting the results but that may be a bit much for us (we are not really lacking challenges currently :). I am posting here on pypy-dev (rather than just to selected pypy developers) because others may be interested, have comments, suggestions or might think about contributing. Security is certainly not the central topic of PyPy but our design should make it considerably easier to implement strong security features. Hum, and i guess that it's not impossible that the project might for contributors come up with funding for travels at least. best, holger

2 1

Re: [pypy-eu-svn] r26155 - pypy/extradoc/sprintinfo/tokyo
by Nicolas Chauvat 25 Apr '06

25 Apr '06

Hi Sprinters, On Sun, Apr 23, 2006 at 05:16:38AM +0200, nik(a)codespeak.net wrote: > + - PyPy debian packaging (Yutaka, Holger?) Alexandre has an ITP on this package and he has spent some time thinking about it. You should probably ask him how far he went. What about tasklet serialisation, any chance this could get done during the sprint ? It's becoming a blocker for WP09. Or should we tackle that on our side as soon as we get the chance ? -- Nicolas Chauvat logilab.fr - services en informatique avancée et gestion de connaissances

4 4

Tokyo sprint status
by Sanghyeon Seo 24 Apr '06

24 Apr '06

Hi, everybody! Greeting from Tokyo, You can read about past 2 days here: http://codespeak.net/pypy/extradoc/sprintinfo/tokyo/tokyo-planning.html Despite the file name, it's really records of planning session we have at the beginning of the day, so after that day, it's no more planning. :-) And the document is updated to match the reality then. I think "proper" sprint report will be here soon too. Yours, Sanghyeon

2 1

Re: [pypy-dev] Re: [pypy-eu-svn] r26155 - pypy/extradoc/sprintinfo/tokyo
by Laura Creighton 23 Apr '06

23 Apr '06

In a message of Sun, 23 Apr 2006 19:33:13 +0200, Aurélien Campéas writes: >> So - it is not a topic on this sprint. People here seem more interested >> in Lisp and Javascript backends and sockets and other weird things ;-) > >Lisp backend ? I'd be interested in seeing that. Who did express such an >idea btw ? - I don't remember having seen this talked about on pypy-dev >or other places. sanxiyn has been working on this, but had to take time off for compulsory military service. He was able to make it to the Sprint in Japan <loud cheer>. Laura

1 0

Re: /pypy/irc-logs/pypy
by Laura Creighton 23 Apr '06

23 Apr '06

In a message of Sun, 23 Apr 2006 19:37:51 +0200, Laura Creighton writes: >Can we rename them from DayMonthYear format to YearMonthDay format so >they will list and sort in the correct order on the webpage? > >Laura Upon looking further, I see we have started to do this. So all that is needed is clean-up. I'd do it if I had an account on the correct machine ... Laura

1 0

/pypy/irc-logs/pypy
by Laura Creighton 23 Apr '06

23 Apr '06

Can we rename them from DayMonthYear format to YearMonthDay format so they will list and sort in the correct order on the webpage? Laura

1 0

minutes pypy-sync last thursday
by hpk＠trillke.net 23 Apr '06

23 Apr '06

Hi folks, find below the minutes of the pypy-sync meeting last thursday. best, holger pypy-sync 20th April 2006, 05:30 PM (UTC+2) ===================================================== attendants: michael, anto, carl, samuele, christian, richard, eric, aurelien, gromit, arre, anders l. - activity reports + blockers everybody posted (see at the end of these minutes) - summer of X, how do we go about it? we quickly agreed to a) go for being mentors through PSF at Google's Summe of Code campaign b) determined mentors c) to create a directory in extradoc/soc-2006 listing all info (mentors, topics) d) next week Michael will communicate all the info to Neal / PSF / SoC - what needs to be done until Iceland (21st May) for 0.9? There was some initial and involved discussion on this topic, which quickly moved to sorting out EU tasks and responsibilities for some involved people. Also related to the brief pypy-dev discussion between Armin and Holger, we determined a need to settle and agree on a distribution of tasks until and after Iceland. This we agreed to do at a specific meeting for EU developers on TUESDAY, 23rd April, 5pm (UTC+2) where Christian, Michael, Samuele, Holger, Carl, Aurelien, Anders L., and Gromit agreed to attend already. IRC log ------------------------------- Apr 20 17:28:55 <mwh> stakkars: hi! Apr 20 17:29:25 <stakkars> hi friends Apr 20 17:29:59 <stakkars> I'll give rxe a call Apr 20 17:30:25 <hpk> hi all! Apr 20 17:30:33 stakkars stedi67 Apr 20 17:30:37 <hpk> stakkars: want to wake him up? :) Apr 20 17:30:45 <Gromit> hi Apr 20 17:30:53 <mwh> T-0 according to me Apr 20 17:30:58 <hpk> yip Apr 20 17:31:01 <mwh> who is moderating? hpk ? Apr 20 17:31:06 <hpk> yes, i guess so Apr 20 17:31:17 <hpk> topics: Apr 20 17:31:17 <hpk> * activity reports Apr 20 17:31:17 <hpk> * summer of X Apr 20 17:31:17 <hpk> * work until iceland for 0.9 topics Apr 20 17:31:17 <hpk> * assigning major 0.9 topics Apr 20 17:31:23 <stakkars> he's early, probably in the company, swamped with work Apr 20 17:31:43 <hpk> so let's start with activity reports (and we can see who is actually really here on the channel active :) Apr 20 17:31:59 <arre> PREV: vacation, configuring new laptop Apr 20 17:31:59 <arre> NEXT: Tokyo sprint Apr 20 17:31:59 <arre> BLOCKERS: - Apr 20 17:32:05 <aleale> PREV: Vacation Apr 20 17:32:06 <hpk> LAST: Leysin Sprint, iceland organisation, some testing and playing around Apr 20 17:32:06 <hpk> NEXT: work on testing and build environment Apr 20 17:32:06 <hpk> BLOCKERS: - Apr 20 17:32:06 <mwh> LAST: slept off leysin, ACCU Apr 20 17:32:07 <mwh> NEXT: stackless transform? Apr 20 17:32:07 <mwh> BLOCKERS: insane busyness Apr 20 17:32:09 <auc> LAST: investigating translatability of constraint stuff Apr 20 17:32:10 <auc> NEXT: playing with choose() Apr 20 17:32:10 <auc> BLOCKERS: working, clonable coroutines Apr 20 17:32:13 <ericvrp> LAST: travelling Apr 20 17:32:13 <ericvrp> NEXT: Tokyo sprint Apr 20 17:32:13 <ericvrp> BLOCKERS: - Apr 20 17:32:16 <aleale> NEXT: Sprint Apr 20 17:32:18 <aleale> BLOCKERS: - Apr 20 17:32:23 <stedi67> LAST: set implementation, finding bugs Apr 20 17:32:23 <stedi67> NEXT: finding and documenting more bugs... Apr 20 17:32:23 <stedi67> BLOCKERS: - Apr 20 17:32:26 <antocuni> LAST: completed rlist support for ootypesystem Apr 20 17:32:27 <antocuni> NEXT: more works on ootypesystem (probably rdict) Apr 20 17:32:29 <antocuni> BLOCKER: my still poor knowledge of pypy internals :-) Apr 20 17:32:34 <cfbolz> LAST: GC work, optimizations Apr 20 17:32:35 <cfbolz> NEXT: uni stuff, trying to implement __del__ with the framework Apr 20 17:32:35 <cfbolz> BLOCKERS: new environment, time constraints Apr 20 17:32:43 <pedronis> LAST: {}[[]], tweaks and fixing various transformation problems, rested during easter Apr 20 17:32:45 <pedronis> NEXT: tokyo sprint Apr 20 17:32:46 <pedronis> BLOCKERS: - Apr 20 17:33:03 * auc is away for 5 minutes Apr 20 17:33:07 <hpk> auc: how badly do you depend on "clonable coroutines" and in which way? Apr 20 17:33:11 <hpk> oh, never mind then Apr 20 17:33:37 <hpk> ok, let's head on then Apr 20 17:33:43 <hpk> * summer of X Apr 20 17:34:05 <hpk> from in-between discussions and opinions i gather that we are all leaning towards participating in SoC as mentors through PSF Apr 20 17:34:11 <mwh> yes Apr 20 17:34:12 <stakkars> DONE: wrapping Apr 20 17:34:12 <stakkars> NEXT: finalizing, prepare next PyPy work Apr 20 17:34:12 <stakkars> BLOCK: complexity Apr 20 17:34:12 <hpk> is that correct or are there other opinions? Apr 20 17:34:35 <cfbolz> sounds good to me Apr 20 17:34:51 <aleale> ditto Apr 20 17:34:56 <arre> +1 Apr 20 17:35:00 <pedronis> +1 Apr 20 17:35:04 <hpk> fine, then let's see how we go about it Apr 20 17:35:05 <hpk> a) mentors Apr 20 17:35:06 <hpk> b) topics Apr 20 17:35:15 <Gromit> hpk: just removed last years's mentorship entry from the wiki Apr 20 17:35:21 <hpk> i suggest that we open a soc-2006 directory in extradoc with such information Apr 20 17:35:32 <mwh> everyone willing to mentor should email neal norwitz Apr 20 17:35:35 <hpk> (Aurelien already committed something today to pypy/doc) Apr 20 17:35:48 <hpk> mwh: i think we should gather on our side and then someone sends all the info Apr 20 17:36:02 <hpk> should gather info Apr 20 17:36:04 <mwh> if you need "personal references" as on the python.org wiki, feel free to mention me :) Apr 20 17:36:05 <stakkars> +1 Apr 20 17:36:11 <mwh> hpk: if you like Apr 20 17:36:24 <mwh> i'm already signed up as a mentor, cause i was one last year Apr 20 17:36:44 <hpk> mwh: ok, carl is as well i think Apr 20 17:37:03 <cfbolz> or will soon be Apr 20 17:37:06 <hpk> ok, then let's put all info into soc-2006 and send info off on the weekend Apr 20 17:37:15 <cfbolz> just to get a quick impression: Apr 20 17:37:16 <mwh> is there a deadline for mentoring? Apr 20 17:37:20 <cfbolz> who would mentor? Apr 20 17:37:25 <cfbolz> mwh: yes, there is one Apr 20 17:37:32 <hpk> 1st may i think Apr 20 17:37:38 <mwh> cfbolz: me, you, armin for certain Apr 20 17:37:40 <hpk> (but i may confuse the various deadlines) Apr 20 17:37:56 <mwh> hpk: i thought 1 may was the deadline for being a mentoring *organization* Apr 20 17:37:57 <hpk> i would also mentor but preferably to py.test, build-tool stuff i guess Apr 20 17:38:06 <cfbolz> hpk: neal writes "soon" :-) Apr 20 17:38:17 <hpk> mwh: ok, might well be, whatever, let's just get this sorted and communicate to them Apr 20 17:38:25 <mwh> hpk: sure Apr 20 17:38:28 <mwh> it shouldn't be hard Apr 20 17:38:48 <cfbolz> anybody else? Apr 20 17:39:07 <hpk> i am sure that aurelien or so would be interested Apr 20 17:39:10 <arre> Add me as well Apr 20 17:39:16 <aleale> I would prefer not to Apr 20 17:39:31 <hpk> eric also said that he would not like to Apr 20 17:39:41 <hpk> ok, then that's it for now Apr 20 17:39:44 <stakkars> I would, of course Apr 20 17:39:46 <ericvrp> I would like to b a mentor but I think it would not be a good idea (indeed) Apr 20 17:39:49 <mwh> pedronis, i guess Apr 20 17:40:03 <hpk> let's just open the soc-2006 directory and put info there Apr 20 17:40:08 <mwh> hpk: are you going to be the one who checks this in? Apr 20 17:40:17 <pedronis> mwh: ye Apr 20 17:40:17 <hpk> cfbolz: can you make this happen and make sure we communicate next week to them? Apr 20 17:40:34 <cfbolz> hpk: not before sunday, no Apr 20 17:41:00 <hpk> ok, then i start but would like you or someone else to communicate to the SoC people (Neal) Apr 20 17:41:08 <hpk> eventually Apr 20 17:41:12 <hpk> as i haven't been involved there Apr 20 17:41:23 <cfbolz> mwh: do you know neal? Apr 20 17:41:34 <mwh> cfbolz: i talked to him a bit at pycon Apr 20 17:41:45 <mwh> i can do the communicating Apr 20 17:41:52 <hpk> cool, thanks Apr 20 17:41:57 <mwh> i am away 29 apr -> 8 may (ish) Apr 20 17:42:02 <mwh> so i'll do it before then :) Apr 20 17:42:06 <hpk> ok, let's try to do it before then Apr 20 17:42:07 <hpk> yes Apr 20 17:42:10 <hpk> next topic Apr 20 17:42:24 <hpk> * 0.9 related work until iceland Apr 20 17:42:44 --> rxe (n=rxe(a)66.151.59.5) has joined #pypy-sync Apr 20 17:42:47 <hpk> hi richard :) Apr 20 17:42:57 <rxe> Hi everyone! :-) Apr 20 17:42:59 <stakkars> :-) Apr 20 17:43:01 <ericvrp> hey richard Apr 20 17:43:02 <rxe> sorry it has been a long time Apr 20 17:43:03 <mwh> hey rxe Apr 20 17:43:48 <hpk> so there has been a bit of discussion on pypy-dev Apr 20 17:44:05 <hpk> what do the others think? Apr 20 17:45:31 <cfbolz> the truth is somewhere in the middle. there is definitively more to do than just stackless pickling Apr 20 17:45:51 <ericvrp> My feeling is that a 0.9 version should be almost a 1.0 version (which I consider a "this is it" version) does that make sense? Apr 20 17:46:07 <ericvrp> which I think we are not quiet yet Apr 20 17:46:08 <cfbolz> like finishing the stackless-applevel exposure Apr 20 17:46:33 <hpk> the major topics of the 0.9 release are the ext-module compiler and stackless features Apr 20 17:46:37 <pedronis> well, there's also other stuff in the WP7 tasks which is explcitly listed Apr 20 17:46:48 <cfbolz> yes, __del__, weakref Apr 20 17:47:09 <stakkars> that's just work. pickling is hard since I still don't know how Apr 20 17:47:10 <pedronis> I don't think WP7 says anything about __dell__ or weakrefr Apr 20 17:47:26 <pedronis> well, even just work takes time Apr 20 17:47:31 <cfbolz> pedronis: then not :-) Apr 20 17:47:33 <cfbolz> pedronis: indeed Apr 20 17:47:53 <stakkars> yes but I can distribute if I know how Apr 20 17:48:06 <mwh> stakkars: what are you working planning on working on? Apr 20 17:48:21 <mwh> damn timezones mean i don't get to chat much... Apr 20 17:49:02 <stakkars> well pickling first thing, although it might depend on the new transform Apr 20 17:49:05 <hpk> cfbolz: the thing regarding "middle ground": we really only have 7 months left for tons of stuff we want to do - just postponing things from a "we don't neccessarily need to do it" will backfire IMO Apr 20 17:49:21 <hpk> so we should strike a good balance Apr 20 17:49:26 stakkars stedi67 Apr 20 17:49:33 <pedronis> cfbolz: the fact is that some unfinished WP7ish stuff is really WP5 leftovers Apr 20 17:49:34 <hpk> stakkars: note that the new transform is not fully integrated Apr 20 17:49:45 <mwh> stakkars: have you looked at the transforrm code? Apr 20 17:49:45 <hpk> it just mostly works but certainly requires work Apr 20 17:50:10 <stakkars> that's what I'm saying, might be blocker Apr 20 17:50:25 <cfbolz> pedronis: what is a wp5 leftover? Apr 20 17:50:35 <pedronis> cfbolz: well part of the GC stuff Apr 20 17:50:53 <hpk> stakkars: michael and me worked on stackless to support you, not to block you :) Apr 20 17:50:58 <mwh> i mean, maybe in the short term it makes sense for stakkars to work on channels and greenlets, and for me to try to polish the stackless transform Apr 20 17:51:00 <pedronis> stakkars: you have 9 mm in WP7 Apr 20 17:51:19 * auc is back (ouch) Apr 20 17:51:28 <stakkars> gosh. I appreciate of course. Apr 20 17:51:30 <mwh> by "short term" i mean "for a week" Apr 20 17:51:59 <stakkars> I just didn't realize that it's necessary,, before i saw pedronis message Apr 20 17:52:21 <hpk> the idea of the current topic is that we identify the issues and assign responsible persons Apr 20 17:52:30 <hpk> i am not sure we can achieve it in some minutes Apr 20 17:52:40 <hpk> but we should aim for getting that clarified latest next week Apr 20 17:53:23 <cfbolz> yes Apr 20 17:53:35 <hpk> because not discussing it will not help either :) Apr 20 17:53:47 <mwh> indeed :) Apr 20 17:53:54 <stakkars> mwh: that makes a lot of sense Apr 20 17:53:56 <pedronis> stakkars: is really your workpackage. Helping you is shifting things around. It may even become a serious issue after a point. Apr 20 17:54:25 <pedronis> but is not the right forum for that discussion Apr 20 17:54:29 <hpk> yes, i agree Apr 20 17:55:10 <stakkars> pedronis:I considered the grapg transform as an add-on, nice to have. as said, didn't know Apr 20 17:55:27 <cfbolz> stakkars: well, it will be necessary for graph pickling Apr 20 17:55:35 <cfbolz> stakkars: so it is not an addon Apr 20 17:55:36 <hpk> so we need a discussion next week about this specific "how to tackle 0.9 tasks" topic and to define the scope Apr 20 17:55:46 <mwh> cfbolz: necessary is a strong word, but i more or less agree Apr 20 17:56:03 <mwh> another point that isn't entirely irrelevant is that i'm enjoying working on 'stackless style' stuff Apr 20 17:56:12 <mwh> :) Apr 20 17:56:12 * hpk too actually Apr 20 17:56:14 <pedronis> anyway task pickling plus the other missing stuff is not a small task Apr 20 17:56:19 <hpk> yes Apr 20 17:56:24 <pedronis> to finish in less than a month Apr 20 17:56:50 <pedronis> that we are so late was not expected Apr 20 17:56:58 <hpk> ok, as we are discussing things mostly from an EU perspective i'd like to invite to a specific meeting for EU developers early next week Apr 20 17:57:15 <pedronis> yes, this is not the right forum Apr 20 17:57:21 <hpk> tuesday? Apr 20 17:57:28 <hpk> big thing is to find the right time for everyone :) Apr 20 17:57:35 <mwh> tuesday would be fine Apr 20 17:57:38 <hpk> 5pm seems likes the best compromise Apr 20 17:57:44 <hpk> midnight in japan, 8am in CA Apr 20 17:57:45 <mwh> (i will be in dÃ¼sseldorf) Apr 20 17:57:58 stakkars stedi67 Apr 20 17:58:20 <hpk> mwh, stakkars, cfbolz, pedronis, auc, aleale, arre, ...: fine for you? Apr 20 17:58:23 <stakkars> for me, the other way goes as well (midnight +) Apr 20 17:58:35 <aleale> ok Apr 20 17:58:37 <mwh> yes Apr 20 17:59:00 stakkars stedi67 Apr 20 17:59:05 <auc> ok Apr 20 17:59:14 <cfbolz> ok Apr 20 17:59:28 <stakkars> ok Apr 20 17:59:45 <hpk> great, than we close this topic (and the next one, which relates to it) Apr 20 17:59:46 <Gromit> ok Apr 20 17:59:58 <hpk> see you all, i will mail to pypy-dev to not forget anyone Apr 20 18:00:31 <hpk> auc: you are available for mentoring as well, right? Apr 20 18:00:36 <hpk> auc: mentoring SoC Apr 20 18:01:12 --> Gromit_ (n=bear(a)does-d9b90ad6.pool.mediaWays.net) has joined #pypy-sync Apr 20 18:01:49 <auc> hpk: i guesss so ... Apr 20 18:02:12 <auc> but not necessarily about all of what i posted in pypy/doc

3 3

educational python environment squeak/python (from edu-sig)
by Laura Creighton 22 Apr '06

22 Apr '06

I'll let Guido's message speak for itself. Laura ------- Forwarded Message Return-Path: edu-sig-bounces(a)python.org Delivery-Date: Sat Apr 22 12:20:54 2006 Date: Sat, 22 Apr 2006 11:19:02 +0100 From: "Guido van Rossum" <guido(a)python.org> To: edu-sig(a)python.org I'm looking for someone to "own" the development of a Squeak-like environment for Python. I can help by getting you in touch with Alan Kay and other Squeak folks. But I just can't be managing this project myself -- I need to focus on Python 3000, which has quite a different set of goals (not incompatible, just different, and enough to keep me very busy in the next two years). To provide some background, here is (with permission, and slightly edited) a forwarded message from Mark Shuttleworth in response to something I sent him this morning. - --Guido - ---------- Forwarded message ---------- From: Mark Shuttleworth <mark(a)canonical.com> Date: Apr 22, 2006 8:56 AM Subject: Re: Moving forward the educational Python code development To: Guido van Rossum <guido(a)python.org> Cc: Kirby Urner <urnerk(a)qwest.net>, [...] Guido van Rossum wrote: > After Kirby's posts and mine on the Python mailing list for the >education Special Interest Group (edu-sig(a)python.org), several threads >have spun up showing that there is a lot of interest in the topic of >making Python more "Squeak-like", however you might want to define >this. This is great news. My sense is that it will take three or more years to get a Squeak-like environment built up in the Python world. It will take a lot of work, more raw development work than TSF is willing to fund. Our project deliverable is the curriculum and the training program for teachers to teach it, we don't want to be responsible for delivering the unified development environment through we recognise that having a unified environment is beneficial to the project. The only way the unified development environment will actually happen is if the SqueakLand community, with Alan's leadership, makes this their goal, and figures out how to work with the Python community. It's the SqueakLand folks who understand what that environment needs to "feel" like. They have the strong vision as to what the tools should do. At the same time, the Python community will need some people to step up and welcome that effort, contributing to it over time, because the SqueakLand folks are used to Squeak and they will need to learn how best to execute their vision in Python. TSF can provide some limited funding, but we're not setup to lead development efforts (we learned the hard way with SchoolTool which is now in good shape). Most of the TSF funding will go towards actual curriculum development that USES the tools available. We will initially use Logo, Squeak and Python as-is, because they are there right now, and will develop the curriculum using what's currently available with a view to consolidating it all around Python as Python gains the ability to deliver Logo-like and Squeak-like environments. > I believe now is the time to delegate to someone other than me the >task of researching the course of action; what exactly is needed, >which toolkit to use (e.g. Mozilla, pygame, OpenGL, or something >else?), and to manage the development. Unfortunately I don't have the >time to do this myself. Does the Shuttleworth Foundation have >resources to pick up this project, now that there's momentum building >up? >This could take the form of an existing Shuttleworth employee jumping >in, or some Foundation money to get one of the interested contributors >(perhaps ) to put in their time (part-time). I don't see this >happening (at the time scale envisioned) on a purely volunteer basis. >I'm sure we can get volunteers to do coding for the project; but >managing it, researching the possible options, and making decisions >probably requires someone dedicated to this task. Yes, agreed, and we can contribute some funding towards the leadership of the effort. I'm not keen to fund "part time work with no clear deliverables" because its hard to get predictable results that way. I guess what we need are you and Alan to figure out between you who will make the most effective leader, bringing together the SqueakLand vision in a Python execution, and we would step up to fund portion of that person's time. [...] I think the leadership of this effort needs to be decided after discussion with Alan too, so that whoever is the funded driving force has buy in from both communities. If you'd like to forward this message to other folks in the community as a statement of the parts TSF is able to contribute to, please do. Mark - ---------- End forwarded message ---------- - -- - --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Edu-sig mailing list Edu-sig(a)python.org http://mail.python.org/mailman/listinfo/edu-sig ------- End of Forwarded Message

1 0

extregistry refactoring
by Armin Rigo 21 Apr '06

21 Apr '06

Hi all, Warning: if you're using the extregistry, I just refactored its interface. I think the result is nicer -- you don't have to define a bunch of functions and link them together in a register_xxx() call; instead, all relevant functions are now methods on a class that is linked via a class method call or automatically with a metaclass trick. The motivation for this was a subtle annotation crash in rctypes: indeed, in the previous model, families of built-in functions (e.g. all ctypes function objects) would get annotated in a way that kept creating new closures. The annotator was then complaining about the resulting SomeBuiltin annotation: as it stores the closure in question, it was always different whenever a block was reflown through the annotator. This refactoring was pending for some time, because previously some functions were missing some information and had to hack around to get at it. A bientot, Armin.

1 0

Upcoming Iceland sprint: 21-28 May
by Armin Rigo 21 Apr '06

21 Apr '06

Hi folks, We're pleased to announce the next PyPy sprint in Iceland from 21st (arrival) to 28th (depature) of May 2006. This sprint is kindly hosted and sponsored by EWT and CCPgames and thus we should be able to arrange funding for travels and accomodation for interested people. There are also non-PyPy activities going on -- see the full `EWT announcement`_ and people such as Tim Peters and other python-dev core developers plan to attend. If you'd like to help and join PyPy hacking around some geysers (actually we are meeting in Reykjavik, but well :), please mail us, preferrably on the `pypy-sprint mailing list`_. Please state your interest *until end this week* (friday 21st) to help the organizers plan for the sprint. The sprint goals for PyPy are, as usual, kept open to the interest of the participants, especially more so that there will be many non-PyPy people at the sprint to talk to. However, it is also likely that we will have to keep some focus on the goals of the upcoming June 0.9 release: * The extension module compiler. The goal is to be able to use a single RPython source code as an extension module for both PyPy and CPython. The means to get there is -- most likely -- by compiling ctypes-based modules into either pypy-c or a CPython dll/so. * Write some more modules in this style with ctypes. Sockets come to mind :-) * Stackless: the big missing feature is pickling running tasklets. There is also some smaller work that needs to be done, like exposing all the existing RPython-level interfaces to app-level (e.g. greenlets). * Write more documentation. * Misc topics, depending on interests: back-ends (CLI, Squeak), testing framework, modified semantics (security/sandboxing...), etc. A bientot, Armin + Holger .. _`EWT announcement`: http://mail.python.org/pipermail/python-announce-list/2006-April/004849.html .. _`pypy-sprint mailing list`: http://codespeak.net/mailman/listinfo/pypy-sprint

2 1