[pypy-svn] r28176 - in pypy/extradoc: minute soc-2006 sprintinfo talk talk/dls2006
hpk at codespeak.net
hpk at codespeak.net
Sat Jun 3 17:45:26 CEST 2006
Author: hpk
Date: Sat Jun 3 17:45:24 2006
New Revision: 28176
Added:
pypy/extradoc/talk/dls2006/conftest.py
Modified:
pypy/extradoc/minute/pypy-sync-2006-04-20.txt
pypy/extradoc/minute/pypy-sync-2006-05-11.txt
pypy/extradoc/soc-2006/code-templating.txt
pypy/extradoc/sprintinfo/conftest.py
pypy/extradoc/talk/solutions-linux-paris-2006.html
Log:
fix ReST issues, prevent some directory/patterns
from causing trouble (dls paper, sprintinfo/*planning.txt files)
Modified: pypy/extradoc/minute/pypy-sync-2006-04-20.txt
==============================================================================
--- pypy/extradoc/minute/pypy-sync-2006-04-20.txt (original)
+++ pypy/extradoc/minute/pypy-sync-2006-04-20.txt Sat Jun 3 17:45:24 2006
@@ -13,10 +13,8 @@
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
+ 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?
@@ -38,207 +36,209 @@
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 at 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 at 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
+::
+
+ 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 at 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 at 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
Modified: pypy/extradoc/minute/pypy-sync-2006-05-11.txt
==============================================================================
--- pypy/extradoc/minute/pypy-sync-2006-05-11.txt (original)
+++ pypy/extradoc/minute/pypy-sync-2006-05-11.txt Sat Jun 3 17:45:24 2006
@@ -46,8 +46,6 @@
IRC logs
-------------
-**** BEGIN LOGGING AT Thu May 11 17:00:48 2006
-
May 11 17:00:48 --> You are now talking on #pypy-sync
May 11 17:00:48 --- Topic for #pypy-sync is PyPy - the flexible snake. This channel is used for pair programming and sync meetings.
May 11 17:00:48 --- Topic for #pypy-sync set by xorAxAx at Sun Apr 16 21:44:23
Modified: pypy/extradoc/soc-2006/code-templating.txt
==============================================================================
--- pypy/extradoc/soc-2006/code-templating.txt (original)
+++ pypy/extradoc/soc-2006/code-templating.txt Sat Jun 3 17:45:24 2006
@@ -11,7 +11,7 @@
touching the grammar file (it means in short : making available the new
operator at runtime by way of importing some module).
-Examples of choice usage :
+Examples of choice usage::
def soft_color():
choice:
@@ -62,7 +62,7 @@
choice: <s1> or: <s2> or: ... or: <sN>
- which has to be rewritten as :
+ which has to be rewritten as ::
choice = choose(N)
if choice == 1:
@@ -83,7 +83,7 @@
creation-time (not even None) and can be bound only once. Currently,
the newvar() builtin is used instead of it in PyPy
-* :=: is a short-cut notation we might want instead of merely calling
+* `:=:` is a short-cut notation we might want instead of merely calling
unify, as in : unify(Term1, Term2)
* fail() makes the current computation space fail: it means that the
@@ -140,28 +140,29 @@
Annex
-----
+
A Common Lisp programmer would have a 'choice' operator like this :
(choice <s1> <s2>)
- ... for instance :
+ for instance ::
- (defun contrast (C1 C2)
- (choice
- ((unify C1 (soft-color))
- (unify C2 (hard-color)))
- ((unify C1 (hard-color))
- (unify C2 (soft-color)))))
-
- He would define choice as a macro, as follows :
-
- (defmacro choice (&body choice-points)
- (let ((choices (length choice-points))
- (choice (gensym "choice")))
- `(let ((,choice (choose ,choices)))
- (cond
- ,(loop for alternative in choice-points
- for i from 1 upto choices
- collect `((= ,i ,choice)
- (progn ,alternative)))))))
+ (defun contrast (C1 C2)
+ (choice
+ ((unify C1 (soft-color))
+ (unify C2 (hard-color)))
+ ((unify C1 (hard-color))
+ (unify C2 (soft-color)))))
+
+ He would define choice as a macro, as follows ::
+
+ (defmacro choice (&body choice-points)
+ (let ((choices (length choice-points))
+ (choice (gensym "choice")))
+ `(let ((,choice (choose ,choices)))
+ (cond
+ ,(loop for alternative in choice-points
+ for i from 1 upto choices
+ collect `((= ,i ,choice)
+ (progn ,alternative)))))))
Modified: pypy/extradoc/sprintinfo/conftest.py
==============================================================================
--- pypy/extradoc/sprintinfo/conftest.py (original)
+++ pypy/extradoc/sprintinfo/conftest.py Sat Jun 3 17:45:24 2006
@@ -29,3 +29,10 @@
class Directory(Directory):
ReSTChecker = PyPyReSTChecker
+ def run(self):
+ l = []
+ for x in super(Directory, self).run():
+ if x.endswith("planning.txt"):
+ continue
+ l.append(x)
+ return l
Added: pypy/extradoc/talk/dls2006/conftest.py
==============================================================================
--- (empty file)
+++ pypy/extradoc/talk/dls2006/conftest.py Sat Jun 3 17:45:24 2006
@@ -0,0 +1,11 @@
+
+import py
+
+class Directory(py.test.collect.Directory):
+ def run(self):
+ l = []
+ for x in super(Directory, self).run():
+ if x in ['draft.txt']:
+ continue
+ l.append(x)
+ return l
Modified: pypy/extradoc/talk/solutions-linux-paris-2006.html
==============================================================================
--- pypy/extradoc/talk/solutions-linux-paris-2006.html (original)
+++ pypy/extradoc/talk/solutions-linux-paris-2006.html Sat Jun 3 17:45:24 2006
@@ -1,327 +1,26 @@
-<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" />
-<meta name="version" content="S5 1.1" />
-<title>PyPy - un projet libre doté d'un financement européen</title>
-<style type="text/css">
-
-/*
-:Author: David Goodger
-:Contact: goodger at users.sourceforge.net
-:Date: $Date: 2005-12-18 01:56:14 +0100 (Sun, 18 Dec 2005) $
-:Revision: $Revision: 4224 $
-:Copyright: This stylesheet has been placed in the public domain.
-
-Default cascading style sheet for the HTML output of Docutils.
-
-See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to
-customize this style sheet.
-*/
-
-/* used to remove borders from tables and images */
-.borderless, table.borderless td, table.borderless th {
- border: 0 }
-
-table.borderless td, table.borderless th {
- /* Override padding for "table.docutils td" with "! important".
- The right padding separates the table cells. */
- padding: 0 0.5em 0 0 ! important }
-
-.first {
- /* Override more specific margin styles with "! important". */
- margin-top: 0 ! important }
-
-.last, .with-subtitle {
- margin-bottom: 0 ! important }
-
-.hidden {
- display: none }
-
-a.toc-backref {
- text-decoration: none ;
- color: black }
-
-blockquote.epigraph {
- margin: 2em 5em ; }
-
-dl.docutils dd {
- margin-bottom: 0.5em }
-
-/* Uncomment (and remove this text!) to get bold-faced definition list terms
-dl.docutils dt {
- font-weight: bold }
-*/
-
-div.abstract {
- margin: 2em 5em }
-
-div.abstract p.topic-title {
- font-weight: bold ;
- text-align: center }
-
-div.admonition, div.attention, div.caution, div.danger, div.error,
-div.hint, div.important, div.note, div.tip, div.warning {
- margin: 2em ;
- border: medium outset ;
- padding: 1em }
-
-div.admonition p.admonition-title, div.hint p.admonition-title,
-div.important p.admonition-title, div.note p.admonition-title,
-div.tip p.admonition-title {
- font-weight: bold ;
- font-family: sans-serif }
-
-div.attention p.admonition-title, div.caution p.admonition-title,
-div.danger p.admonition-title, div.error p.admonition-title,
-div.warning p.admonition-title {
- color: red ;
- font-weight: bold ;
- font-family: sans-serif }
-
-/* Uncomment (and remove this text!) to get reduced vertical space in
- compound paragraphs.
-div.compound .compound-first, div.compound .compound-middle {
- margin-bottom: 0.5em }
-
-div.compound .compound-last, div.compound .compound-middle {
- margin-top: 0.5em }
-*/
-
-div.dedication {
- margin: 2em 5em ;
- text-align: center ;
- font-style: italic }
-
-div.dedication p.topic-title {
- font-weight: bold ;
- font-style: normal }
-
-div.figure {
- margin-left: 2em ;
- margin-right: 2em }
-
-div.footer, div.header {
- clear: both;
- font-size: smaller }
-
-div.line-block {
- display: block ;
- margin-top: 1em ;
- margin-bottom: 1em }
-
-div.line-block div.line-block {
- margin-top: 0 ;
- margin-bottom: 0 ;
- margin-left: 1.5em }
-
-div.sidebar {
- margin-left: 1em ;
- border: medium outset ;
- padding: 1em ;
- background-color: #ffffee ;
- width: 40% ;
- float: right ;
- clear: right }
-
-div.sidebar p.rubric {
- font-family: sans-serif ;
- font-size: medium }
-
-div.system-messages {
- margin: 5em }
-
-div.system-messages h1 {
- color: red }
-
-div.system-message {
- border: medium outset ;
- padding: 1em }
-
-div.system-message p.system-message-title {
- color: red ;
- font-weight: bold }
-
-div.topic {
- margin: 2em }
-
-h1.section-subtitle, h2.section-subtitle, h3.section-subtitle,
-h4.section-subtitle, h5.section-subtitle, h6.section-subtitle {
- margin-top: 0.4em }
-
-h1.title {
- text-align: center }
-
-h2.subtitle {
- text-align: center }
-
-hr.docutils {
- width: 75% }
-
-img.align-left {
- clear: left }
-
-img.align-right {
- clear: right }
-
-ol.simple, ul.simple {
- margin-bottom: 1em }
-
-ol.arabic {
- list-style: decimal }
-
-ol.loweralpha {
- list-style: lower-alpha }
-
-ol.upperalpha {
- list-style: upper-alpha }
-
-ol.lowerroman {
- list-style: lower-roman }
-
-ol.upperroman {
- list-style: upper-roman }
-
-p.attribution {
- text-align: right ;
- margin-left: 50% }
-
-p.caption {
- font-style: italic }
-
-p.credits {
- font-style: italic ;
- font-size: smaller }
-
-p.label {
- white-space: nowrap }
-
-p.rubric {
- font-weight: bold ;
- font-size: larger ;
- color: maroon ;
- text-align: center }
-
-p.sidebar-title {
- font-family: sans-serif ;
- font-weight: bold ;
- font-size: larger }
-
-p.sidebar-subtitle {
- font-family: sans-serif ;
- font-weight: bold }
-
-p.topic-title {
- font-weight: bold }
-
-pre.address {
- margin-bottom: 0 ;
- margin-top: 0 ;
- font-family: serif ;
- font-size: 100% }
-
-pre.literal-block, pre.doctest-block {
- margin-left: 2em ;
- margin-right: 2em ;
- background-color: #eeeeee }
-
-span.classifier {
- font-family: sans-serif ;
- font-style: oblique }
-
-span.classifier-delimiter {
- font-family: sans-serif ;
- font-weight: bold }
-
-span.interpreted {
- font-family: sans-serif }
-
-span.option {
- white-space: nowrap }
-
-span.pre {
- white-space: pre }
-
-span.problematic {
- color: red }
-
-span.section-subtitle {
- /* font-size relative to parent (h1..h6 element) */
- font-size: 80% }
-
-table.citation {
- border-left: solid 1px gray;
- margin-left: 1px }
-
-table.docinfo {
- margin: 2em 4em }
-
-table.docutils {
- margin-top: 0.5em ;
- margin-bottom: 0.5em }
-
-table.footnote {
- border-left: solid 1px black;
- margin-left: 1px }
-
-table.docutils td, table.docutils th,
-table.docinfo td, table.docinfo th {
- padding-left: 0.5em ;
- padding-right: 0.5em ;
- vertical-align: top }
-
-table.docutils th.field-name, table.docinfo th.docinfo-name {
- font-weight: bold ;
- text-align: left ;
- white-space: nowrap ;
- padding-left: 0 }
-
-h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
-h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
- font-size: 100% }
-
-tt.docutils {
- background-color: #eeeeee }
-
-ul.auto-toc {
- list-style-type: none }
-
-</style>
-<!-- configuration parameters -->
-<meta name="defaultView" content="slideshow" />
-<meta name="controlVis" content="hidden" />
-<!-- style sheet links -->
-<script src="ui/default/slides.js" type="text/javascript"></script>
-<link rel="stylesheet" href="ui/default/slides.css"
- type="text/css" media="projection" id="slideProj" />
-<link rel="stylesheet" href="ui/default/outline.css"
- type="text/css" media="screen" id="outlineStyle" />
-<link rel="stylesheet" href="ui/default/print.css"
- type="text/css" media="print" id="slidePrint" />
-<link rel="stylesheet" href="ui/default/opera.css"
- type="text/css" media="projection" id="operaFix" />
-
-<style type="text/css">
-#currentSlide {display: none;}
-</style>
-</head>
-<body>
-<div class="layout">
-<div id="controls"></div>
-<div id="currentSlide"></div>
-<div id="header">
-
-</div>
-<div id="footer">
-<h1>PyPy - un projet libre doté d'un financement européen</h1>
-<h2>Nicolas Chauvat (Logilab)</h2>
-</div>
-</div>
-<div class="presentation">
-<div class="slide" id="slide0">
-<h1 class="title">PyPy - un projet libre doté d'un financement européen</h1>
+<html>
+ <head>
+ <title>PyPy[solutions-linux-paris-2006] </title>
+ <meta content="text/html;charset=ISO-8859-1" name="Content-Type"></meta>
+ <link href="http://codespeak.net/pypy/dist/pypy/doc/style.css" media="screen" rel="stylesheet" type="text/css"></link></head>
+ <body>
+ <div>
+ <a>
+ <img alt="PyPy" height="110" id="pyimg" src="http://codespeak.net/pypy/img/py-web1.png" width="149"></img></a></div>
+ <div id="metaspace">
+ <div class="project_title">PyPy[solutions-linux-paris-2006] </div>
+ <div id="menubar">
+ <a class="menu" href="/pypy/dist/pypy/doc/news.html">news</a>
+ <a class="menu" href="/pypy/dist/pypy/doc/index.html">doc</a>
+ <a class="menu" href="/pypy/dist/pypy/doc/contact.html">contact</a>
+ <a class="menu" href="/pypy/dist/doc/getting-started.html">getting-started</a>
+ <a class="menu" href="https://codespeak.net/issue/pypy-dev/">issue</a> </div></div>
+ <div id="contentspace">
+ <div id="docinfoline">
+ <div style="float: right; font-style: italic;"> modified 1 month ago by Carl Friedrich Bolz</div></div>
+<div class="document" id="pypy-un-projet-libre-dot-d-un-financement-europ-en">
+<h1 class="title">PyPy - un projet libre doté d'un financement européen</h1>
<table class="docinfo" frame="void" rules="none">
<col class="docinfo-name" />
<col class="docinfo-content" />
@@ -342,143 +41,146 @@
============================ -->
<!-- Display in Print Only
===================== -->
+<!-- Display in Handout Mode Only
+============================ -->
<!-- Incremental Display
=================== -->
-
-</div>
-<div class="slide" id="sujets-abord-s">
-<h1>Sujets abordés</h1>
+<div class="section">
+<h1><a id="sujets-abord-s" name="sujets-abord-s">Sujets abordés</a></h1>
<ul class="simple">
-<li>quels modèles économiques pour le logiciel libre ?</li>
-<li>le logiciel libre et les projets européens</li>
-<li>le langage Python et l'interpréteur PyPy</li>
+<li>quels modèles économiques pour le logiciel libre ?</li>
+<li>le logiciel libre et les projets européens</li>
+<li>le langage Python et l'interpréteur PyPy</li>
</ul>
</div>
-<div class="slide" id="plan">
-<h1>Plan</h1>
+<div class="section">
+<h1><a id="plan" name="plan">Plan</a></h1>
<ul class="simple">
<li>historique du projet</li>
-<li>procédure de candidature</li>
-<li>déroulement</li>
-<li>UE et agilité</li>
+<li>procédure de candidature</li>
+<li>déroulement</li>
+<li>UE et agilité</li>
<li>qu'est-ce que PyPy ?</li>
</ul>
</div>
-<div class="slide" id="historique">
-<h1>Historique</h1>
+<div class="section">
+<h1><a id="historique" name="historique">Historique</a></h1>
<ul class="simple">
-<li>débute mi-2003 suite à EuroPython</li>
+<li>débute mi-2003 suite à EuroPython</li>
<li>prototype prometteur en 2004</li>
-<li>début 2004, recherche des moyens nécessaires à la poursuite du projet</li>
+<li>début 2004, recherche des moyens nécessaires à la poursuite du projet</li>
<li>fin 2004, signature contrat</li>
</ul>
</div>
-<div class="slide" id="candidature">
-<h1>Candidature</h1>
+<div class="section">
+<h1><a id="candidature" name="candidature">Candidature</a></h1>
<ul class="simple">
-<li>appels à projet (IST - 6th Framework)</li>
+<li>appels à projet (IST - 6th Framework)</li>
<li>recherche partenaires manquants</li>
-<li>rédaction collaborative de l'offre (outils et méthodes du libre)</li>
+<li>rédaction collaborative de l'offre (outils et méthodes du libre)</li>
<li>soumission automne 2004</li>
-<li>signature contrat déc 2004</li>
+<li>signature contrat déc 2004</li>
</ul>
</div>
-<div class="slide" id="caract-ristiques">
-<h1>Caractéristiques</h1>
+<div class="section">
+<h1><a id="caract-ristiques" name="caract-ristiques">Caractéristiques</a></h1>
<ul class="simple">
<li>projet innovant</li>
<li>budget 1,3 Millions EUR</li>
<li>2 ans (2005/2006)</li>
-<li>7 partenaires européens</li>
-<li>15 années.homme</li>
+<li>7 partenaires européens</li>
+<li>15 années.homme</li>
<li>logiciel libre</li>
</ul>
</div>
-<div class="slide" id="consortium">
-<h1>Consortium</h1>
+<div class="section">
+<h1><a id="consortium" name="consortium">Consortium</a></h1>
<ul class="simple">
<li>DFKI (Allemagne)</li>
<li>HHU (Allemagne)</li>
<li>Logilab (France)</li>
-<li>Strakt (Suède)</li>
+<li>Strakt (Suède)</li>
<li>Merlinux (Allemagne)</li>
<li>Tismerysoft (Allemagne)</li>
-<li>Changemaker (Suède)</li>
+<li>Changemaker (Suède)</li>
</ul>
</div>
-<div class="slide" id="financement-europ-en">
-<h1>Financement européen</h1>
+<div class="section">
+<h1><a id="financement-europ-en" name="financement-europ-en">Financement européen</a></h1>
<ul class="simple">
<li>financement partiel:<ul>
-<li>50% pour partenaires privés</li>
+<li>50% pour partenaires privés</li>
<li>100% pour partenaires publics</li>
</ul>
</li>
<li>deniers publics financent biens publics</li>
-<li>délais de paiement</li>
+<li>délais de paiement</li>
</ul>
</div>
-<div class="slide" id="financement-public-pour-ll">
-<h1>Financement public pour LL</h1>
+<div class="section">
+<h1><a id="financement-public-pour-ll" name="financement-public-pour-ll">Financement public pour LL</a></h1>
<ul class="simple">
-<li>projets menés par administrations</li>
-<li>certaines réductions d'impôts</li>
+<li>projets menés par administrations</li>
+<li>certaines réductions d'impôts</li>
<li>approche politique au niveau local</li>
</ul>
</div>
-<div class="slide" id="diff-rences-culturelles">
-<h1>Différences culturelles</h1>
+<div class="section">
+<h1><a id="diff-rences-culturelles" name="diff-rences-culturelles">Différences culturelles</a></h1>
<ul class="simple">
-<li>gestion de projet par méthodes agiles</li>
+<li>gestion de projet par méthodes agiles</li>
<li>UE gestion plus "classique"</li>
-<li>documentation, processus de validation, délais, etc.</li>
+<li>documentation, processus de validation, délais, etc.</li>
<li>sprints toutes les 6 semaines</li>
<li>reste ouvert aux contributeurs externes</li>
</ul>
</div>
-<div class="slide" id="et-pypy">
-<h1>Et PyPy ?</h1>
+<div class="section">
+<h1><a id="et-pypy" name="et-pypy">Et PyPy ?</a></h1>
<ul class="simple">
-<li>interpréteur pour langage Python</li>
+<li>interpréteur pour langage Python</li>
<li>flexible</li>
<li>performant</li>
<li>modulable</li>
</ul>
</div>
-<div class="slide" id="objectifs-pypy">
-<h1>Objectifs PyPy</h1>
+<div class="section">
+<h1><a id="objectifs-pypy" name="objectifs-pypy">Objectifs PyPy</a></h1>
<ul class="simple">
<li>Python en Python</li>
-<li>respect de la définition du langage</li>
-<li>performances équivalentes à CPython</li>
+<li>respect de la définition du langage</li>
+<li>performances équivalentes à CPython</li>
<li>traduction vers langages cibles</li>
-<li>ajout fonctionnalités</li>
-<li>un interpréteur déclinable</li>
+<li>ajout fonctionnalités</li>
+<li>un interpréteur déclinable</li>
</ul>
</div>
-<div class="slide" id="etat-d-but-2006">
-<h1>Etat début 2006</h1>
+<div class="section">
+<h1><a id="etat-d-but-2006" name="etat-d-but-2006">Etat début 2006</a></h1>
<ul class="simple">
<li>version 0.8 est un Python 2.4 fonctionnel</li>
-<li>manque gestion de la mémoire</li>
+<li>manque gestion de la mémoire</li>
<li>10 fois plus lent que l'original</li>
-<li>génère code C (et autres)</li>
+<li>génère code C (et autres)</li>
</ul>
</div>
-<div class="slide" id="etapes-pour-fin-2006">
-<h1>Etapes pour fin 2006</h1>
+<div class="section">
+<h1><a id="etapes-pour-fin-2006" name="etapes-pour-fin-2006">Etapes pour fin 2006</a></h1>
<ul class="simple">
-<li>compilation et évaluation partielle</li>
+<li>compilation et évaluation partielle</li>
<li>logique, aspects, distribution</li>
<li>diffusion</li>
</ul>
</div>
-<div class="slide" id="pour-finir">
-<h1>Pour finir</h1>
+<div class="section">
+<h1><a id="pour-finir" name="pour-finir">Pour finir</a></h1>
<ul class="simple">
<li>Questions</li>
</ul>
</div>
</div>
-</body>
-</html>
+<div class="footer">
+<hr class="footer" />
+Nicolas Chauvat (Logilab)
+</div>
+</div></body></html>
\ No newline at end of file
More information about the Pypy-commit
mailing list