Mailman 3 September 2004 - Doc-SIG

Re: [Python-Dev] Planning to drop gzip compression for future releases.
by Fred L. Drake, Jr. Sept. 21, 2004

Sept. 21, 2004

[Responding to an absolutely enormous deluge of emails on python-dev...] On Sunday 19 September 2004 10:06 pm, Anthony Baxter wrote: > I have no intention of dropping tar.gz source releases. I think Fred > was talking about the documentation tarballs. Even then, I think there's > some advantages to keeping both, and I don't really see the advantage > to dropping the tar.gz format. But hey, that's up to Fred - he's the > one who makes the doc releases. Dang, it doesn't pay to be away from email for three days, does it? Yes, I was only talking about documentation releases. It never occurred to me anyone would think I was talking about Python source releases. Maybe I shouldn't have added python-dev to the recipients list for my original email, but too often objections get heard quite late if I don't include python-dev. For the documentation, there's a much longer history of providing the bz2 versions of the archives. There are also many more archives we can drop per release. While in theory disk space isn't supposed to be an issue, it seems to be something our sysadmin group is dealing with on a regular basis (mostly cleaning up old webserver logs). So while the space itself may not be an issue, it certainly generates tedious work for volunteers. My motivation in dropping the bz2 archives is two-fold: 1. Reduce disk space consumed per release, mostly to ease the burden on the sysadmin group. 2. Reduce the number of files posted for the documentation per release, so that choices for end-users are easier to pick through. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org>

1 1

Planning to drop gzip compression for future releases.
by Fred L. Drake, Jr. Sept. 17, 2004

Sept. 17, 2004

At this point, I'm planning to drop the gzip-compressed archives for all future Python releases. The bzip2 archives are much smaller (saving bandwidth, disk space, and download time), and supporting software seems to have become widely available in both free and commercial tools. I'm still planning to make ZIP archives available. If anyone would like to argue that I should drop that as well, feel free. ;-) -Fred -- Fred L. Drake, Jr. <fdrake at acm.org>

1 0

Annotatable copy of Python docs
by A.M. Kuchling Sept. 10, 2004

Sept. 10, 2004

As an experiment, I've paired the HTML version of the 2.3.4 docs with a Wiki thanks to frames and some JavaScript. The starting point is at http://pydoc.amk.ca/frame.html . Feel free to add commentary, links, or other material to the Wiki. If people actually use it, it'll get moved to python.org. --amk

1 0

partial rewrite of the "extending and embedding" manual
by Michael Hudson Sept. 3, 2004

Sept. 3, 2004

I've been heard before now to complain about the extending and embedding manual. Some time ago I started a rewrite, and found it again this morning ;-) I've uploaded what I have here: http://starship.python.net/crew/mwh/toext/ >From the introduction, a sort of manifesto for the document is: This document is intended to make sense when read from beginning to end and is written in a terse style with an emphasis on examples. Extreme Programming applied to documentation, if you like. Comments welcome. Feel free to be very critical of what's there, and suggestions of missing material are also welcome. I'm quite keen on the idea of it all being in one person's (i.e. mine, unless someone much more enthusiastic takes over) prose style, so I'm not particularly looking for contributions of content (but obviously can handle such, if you're prepared to see me rewrite your carefully wrought sentences :-). Cheers, mwh -- > Touche! But this confirms you are composed of logic gates. Crud, I thought those were neurons in there. -- Thomas F. Burdick, Kenny Tilton, comp.lang.lisp

4 8