[Pythonmac-SIG] "Official" mac python Docs Project
Tue, 12 Sep 2000 12:01:38 +0200
Recently, Chris Barker <firstname.lastname@example.org> said:
> I think that's a fine idea. See my next post. Any modules that are not
> there can be sent to me, with as much info as possible. If nothing else,
> I will put the doc string in (if it has anything of use at all) and a
> list of the members of the module. What the members do can then be
> filled in.
> I just went through the doc, and I think I can get it correct pretty
> quickly, but there really isn't much point in doing this unless we can
> fill it out some, soI'll be focussing on that.
Ok, great. Do you have checkin permissions on the sourceforge.net
repository? No, it appears not. Then it's probably easiest if you
forward modified/new files to me and I'll check them in. Or (better)
ask one of the admins to give you checkin permissions. That is: if you
have a unix machine available, checkin permission is difficult from a
Mac at the moment.
> Hmm. when is 2.0 final expected o be released? IN the mean time, I'll go
> get the beta. Is 2.0b1 as stable as teh 1.6 beta you had out?
2.0 is expected to have a short beta cycle, so it shouldn't take too
long. As to 2.0b1 stability compared to 1.6a2: my guess is that it's
more stable, but as it's only been out for 12 hours I can't really
promise this. I _do_ promise that I won't be doing wild things between
2.0b1 and 2.0final, just work on missing stuff (distutils comes to
mind). Carbon MacPython will have to wait until after 2.0.
Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++
Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++
www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm