For poor people like me, pypy wannabe contributor, I think it would be good to have some updated documentation about type-inference/annotation as done in pypy. The only doc I can find is heavily outdated, as stated in the first lines of the file. Is this documentation planned? Sorry for the wrong post in py-dev ML :( cheers -- Valentino Volonghi aka Dialtone Now Running MacOSX 10.3.8 Blog: http://vvolonghi.blogspot.com http://weever.berlios.de
Valentino Volonghi aka Dialtone <dialtone@divmod.com> writes:
Would be nice, wouldn't it!
The only doc I can find is heavily outdated, as stated in the first lines of the file.
This is the danger of spending time writing documentation in the PyPy world. Mind you, I don't think we're going to throw everything out of the window again any time soon...
Is this documentation planned?
Well, certainly. I don't know how soon, though. It's also one of the most mind bending parts of the project currently. Maybe you should start somewhere else... Cheers, mwh -- <moshez> glyph: I don't know anything about reality. -- from Twisted.Quotes
Michael Hudson <mwh@python.net> writes:
Well, certainly. I don't know how soon, though. It's also one of the most mind bending parts of the project currently.
To make my point the way I originally intended too (sigh): If I was to work on lowering the bar to entry of the annotator, currently I would work on making it less incomprehensible before working on documentation. Cheers, mwh -- In that case I suggest that to get the correct image you look at the screen from inside the monitor whilst standing on your head. -- James Bonfield, http://www.ioccc.org/2000/rince.hint
On Sat, Feb 19, 2005 at 21:19 +0000, Michael Hudson wrote:
Some people even think that before making it less incrompehensible and writing documentation we should actually make it work :-) Nevertheless i would hope that some things can be said about annotation (our jargon for type inference) that would not be heavily outdated so soon. In fact, since the Vilnius sprint in November annotation seems to be relatively stable and we are shifting efforts to make the interpreter/StdObjectSpace behave in a way that allows the current annotation to work. Btw, in the just re-merged "interpapp" branch we wrestled quite a bit with the interactions between interpreter level code and application level code that are kind of a mine field for type inference, especially exposing interp-level functions at application level (like all the descriptors). Here it also seems to make sense to document the new cleaned up way of doing app/interp interactions, including the new "LazyModule" mechanism for the sys and builtin module which are now realized as packages whose name bindings get resolved lazily. (have a look into pypy/module/builtin and sys2). cheers, holger
Valentino Volonghi aka Dialtone <dialtone@divmod.com> writes:
Would be nice, wouldn't it!
The only doc I can find is heavily outdated, as stated in the first lines of the file.
This is the danger of spending time writing documentation in the PyPy world. Mind you, I don't think we're going to throw everything out of the window again any time soon...
Is this documentation planned?
Well, certainly. I don't know how soon, though. It's also one of the most mind bending parts of the project currently. Maybe you should start somewhere else... Cheers, mwh -- <moshez> glyph: I don't know anything about reality. -- from Twisted.Quotes
Michael Hudson <mwh@python.net> writes:
Well, certainly. I don't know how soon, though. It's also one of the most mind bending parts of the project currently.
To make my point the way I originally intended too (sigh): If I was to work on lowering the bar to entry of the annotator, currently I would work on making it less incomprehensible before working on documentation. Cheers, mwh -- In that case I suggest that to get the correct image you look at the screen from inside the monitor whilst standing on your head. -- James Bonfield, http://www.ioccc.org/2000/rince.hint
On Sat, Feb 19, 2005 at 21:19 +0000, Michael Hudson wrote:
Some people even think that before making it less incrompehensible and writing documentation we should actually make it work :-) Nevertheless i would hope that some things can be said about annotation (our jargon for type inference) that would not be heavily outdated so soon. In fact, since the Vilnius sprint in November annotation seems to be relatively stable and we are shifting efforts to make the interpreter/StdObjectSpace behave in a way that allows the current annotation to work. Btw, in the just re-merged "interpapp" branch we wrestled quite a bit with the interactions between interpreter level code and application level code that are kind of a mine field for type inference, especially exposing interp-level functions at application level (like all the descriptors). Here it also seems to make sense to document the new cleaned up way of doing app/interp interactions, including the new "LazyModule" mechanism for the sys and builtin module which are now realized as packages whose name bindings get resolved lazily. (have a look into pypy/module/builtin and sys2). cheers, holger
participants (3)
-
hpk＠trillke.net -
Michael Hudson -
Valentino Volonghi aka Dialtone