From cotton@eniac.seas.upenn.edu Tue Jun 18 18:09:16 1996 From: cotton@eniac.seas.upenn.edu (cotton@eniac.seas.upenn.edu) Date: Tue, 18 Jun 1996 17:09:16 GMT Subject: [PYTHON META-SIG] sound-sig Message-ID: <199606181709.RAA00437@chronis.upenn.edu> ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From cotton@eniac.seas.upenn.edu Tue Jun 18 22:39:11 1996 From: cotton@eniac.seas.upenn.edu (Scott) Date: Tue, 18 Jun 1996 17:39:11 -0400 (EDT) Subject: [PYTHON META-SIG] Sound-sig Message-ID: <199606182139.RAA12055@blue.seas.upenn.edu> sound-sig: a special interest group for developing audio support in Python. The goal of this group is to help bring the realm of audio into Python. As of this writing, Python has audio support for only two platforms. For this reason, the primary goal for this group will be the development of builtin sound modules for various platform/soundcard combinations. However, the scope of the sound-sig may include discussions pertaining to the enhancement of basic sound support for such areas as speech/natural language processing and music. About this list: Additions and deletions are all automated via Majordomo. For details, send the word `help' in the body of a mail messages to the Administrivia address given below. the subscription policy is `open', meaning you can add or delete yourself at any time, but you cannot add or delete anyone else without approval. This list is unmoderated and unrestricted. This means that anybody can post messages to the list. Messages are archived and available for download, as are perhaps other useful files. for details, send the word `index' in the body of a messages to the Administrivia address. post messages to everyone on the list by using the List address. If you absolutely must contact a human being, use the Owner address. ======================================================================== List address: sound-sig@python.org Administrivia: sound-sig-request@python.org Owner: sound-sig-owner@python.org ========================================================================= ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From fredrik_lundh@ivab.se Tue Jun 18 22:57:06 1996 From: fredrik_lundh@ivab.se (Fredrik Lundh) Date: Tue, 18 Jun 1996 23:57:06 +0200 Subject: [PYTHON META-SIG] Sound-sig In-Reply-To: <199606182139.RAA12055@blue.seas.upenn.edu> (cotton@eniac.seas.upenn.edu) Message-ID: <9606182157.AA12066@arnold.image.ivab.se> Why not? Or should we merge this with the image-sig (which is slowly moving towards video as well) into a multimedia-sig? /F ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From rmasse@newcnri.CNRI.Reston.Va.US Tue Jun 18 23:04:17 1996 From: rmasse@newcnri.CNRI.Reston.Va.US (Roger Masse) Date: Tue, 18 Jun 1996 18:04:17 -0400 Subject: [PYTHON META-SIG] Sound-sig In-Reply-To: <9606182157.AA12066@arnold.image.ivab.se> References: <199606182139.RAA12055@blue.seas.upenn.edu> <9606182157.AA12066@arnold.image.ivab.se> Message-ID: <199606182204.SAA05077@newcnri.CNRI.Reston.Va.US> Fredrik Lundh writes: > > Why not? Or should we merge this with the image-sig (which is slowly > moving towards video as well) into a multimedia-sig? > > /F > Yes! I don't think there's that much traffic on the image SIG nor do I think the audio stuff will be that much long-term either... Good idea. -roj ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From guido@CNRI.Reston.Va.US Tue Jun 18 23:28:06 1996 From: guido@CNRI.Reston.Va.US (Guido van Rossum) Date: Tue, 18 Jun 1996 18:28:06 -0400 Subject: [PYTHON META-SIG] Sound-sig In-Reply-To: Your message of "Tue, 18 Jun 1996 17:39:11 EDT." <199606182139.RAA12055@blue.seas.upenn.edu> References: <199606182139.RAA12055@blue.seas.upenn.edu> Message-ID: <199606182228.SAA15818@monty> > sound-sig: a special interest group for developing audio support in Python. I haven't seen much discussion of audio support on the main mailing list, and I believe it's unwise to start a SIG based on a single post. --Guido van Rossum (home page: http://www.python.org/~guido/) ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From klm@CNRI.Reston.Va.US Wed Jun 19 16:37:49 1996 From: klm@CNRI.Reston.Va.US (Ken Manheimer) Date: Wed, 19 Jun 1996 11:37:49 -0400 (EDT) Subject: [PYTHON META-SIG] Sound-sig In-Reply-To: <199606182204.SAA05077@newcnri.CNRI.Reston.Va.US> Message-ID: On Tue, 18 Jun 1996, Roger Masse wrote: > Fredrik Lundh writes: > > > > Why not? Or should we merge this with the image-sig (which is slowly > > moving towards video as well) into a multimedia-sig? > > Yes! I don't think there's that much traffic on the image SIG nor > do I think the audio stuff will be that much long-term either... > > Good idea. I agree - i think it's a good idea to combine all these things into a multimedia-sig. In fact, i'd go further, and suggest bringing in some other low-volume sigs that i think are related - the web-sig and doc-sig. Would this make sense? I would further propose calling the resulting thing the "media-sig", which implies that it is about each of the media, individually, as well as any combinations of them. "Multimedia", on the other hand, implies to me particularly the combinations. (I realize that "media-sig" might sound like a public relations sig, but that doesn't stop, eg, the Media Lab at MIT from using that name...) Incidentally, should we be including the guy who made the proposal in this discussion? I see no reason to keep it from him, he may have ideas, and he's not on the meta-sig... Ken Manheimer klm@cnri.reston.va.us 703 620-8990 x268 (orporation for National Research |nitiatives 1895 Preston White Drive, Suite 100 Reston, VA 22091 ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From friedric@rose.rsoc.rockwell.com Wed Jun 19 18:34:46 1996 From: friedric@rose.rsoc.rockwell.com (Robin Friedrich) Date: Wed, 19 Jun 1996 12:34:46 -0500 Subject: [PYTHON META-SIG] Sound-sig Message-ID: <199606191734.MAA19308@darwin.rsoc.rockwell.com> |> From owner-meta-sig@python.org Wed Jun 19 11:44 CDT 1996 |> Date: Wed, 19 Jun 1996 11:37:49 -0400 (EDT) |> From: Ken Manheimer |> Reply-To: klm@CNRI.Reston.Va.US |> |> On Tue, 18 Jun 1996, Roger Masse wrote: |> |> > Fredrik Lundh writes: |> > > |> > > Why not? Or should we merge this with the image-sig (which is slowly |> > > moving towards video as well) into a multimedia-sig? |> > |> > Yes! I don't think there's that much traffic on the image SIG nor |> > do I think the audio stuff will be that much long-term either... |> > |> > Good idea. |> |> I agree - i think it's a good idea to combine all these things into a |> multimedia-sig. In fact, i'd go further, and suggest bringing in some |> other low-volume sigs that i think are related - the web-sig and doc-sig. |> Would this make sense? |> |> I would further propose calling the resulting thing the "media-sig", which |> implies that it is about each of the media, individually, as well as any |> combinations of them. "Multimedia", on the other hand, implies to me |> particularly the combinations. (I realize that "media-sig" might sound |> like a public relations sig, but that doesn't stop, eg, the Media Lab at |> MIT from using that name...) |> |> Incidentally, should we be including the guy who made the proposal in |> this discussion? I see no reason to keep it from him, he may have ideas, |> and he's not on the meta-sig... |> |> Ken Manheimer klm@cnri.reston.va.us 703 620-8990 x268 media-sig sounds awfully general to me and would violate one of the guidelines we set for sigs, (that is to have specific goals/projects to work on). I currently don't mind crossposting between web-sig and doc-sig (I'm about to do that soon myself with my HTMLgen stuff). BTW: doc-sig is still broken as far as I can tell. We've been trying to send out the new gendoc Daniel has written but have yet to see it. (Sent three times) -Robin ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From fdrake@CNRI.Reston.Va.US Wed Jun 19 18:42:21 1996 From: fdrake@CNRI.Reston.Va.US (Fred L. Drake) Date: Wed, 19 Jun 1996 13:42:21 -0400 (EDT) Subject: [PYTHON META-SIG] status of doc-sig mailing list In-Reply-To: <199606191734.MAA19308@darwin.rsoc.rockwell.com> from "Robin Friedrich" at Jun 19, 96 12:34:46 pm Message-ID: <199606191742.NAA20112@weyr.CNRI.Reston.Va.US> Robin wrote: > BTW: > doc-sig is still broken as far as I can tell. We've been trying to send > out the new gendoc Daniel has written but have yet to see it. > (Sent three times) Barry is still out today, and he's the one who deals with majordomo for the PSA machine. Hold off until he has a chance to get back and take a look at the problem. I'll try and be aware of his progress and let you & Daniel know when the problem has been fixed. -Fred -- Fred L. Drake, Jr. fdrake@cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive Reston, VA 22091 ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From klm@CNRI.Reston.Va.US Thu Jun 20 00:11:05 1996 From: klm@CNRI.Reston.Va.US (Ken Manheimer) Date: Wed, 19 Jun 1996 19:11:05 -0400 (EDT) Subject: [PYTHON META-SIG] Sound-sig In-Reply-To: <199606191734.MAA19308@darwin.rsoc.rockwell.com> Message-ID: > media-sig sounds awfully general to me and would violate one of the > guidelines we set for sigs, (that is to have specific goals/projects to > work on). I currently don't mind crossposting between web-sig and A couple of responses have opened my eyes to the fact that my proposal was off-base (and, in fact, would betray some of the principles i had advocated early on). I take it back! > doc-sig is still broken as far as I can tell. We've been trying to send > out the new gendoc Daniel has written but have yet to see it. > (Sent three times) Aargh. I tried a test posting (after trying a few less intrusive tests), only to have it delivered. I suggest you retry your post, but this time CC me on it. This may provide further information. (And i did recall seeing a post get through on that list, today - concerning the "cocoon utilities" documentation tool...) Ken Manheimer klm@cnri.reston.va.us 703 620-8990 x268 (orporation for National Research |nitiatives 1895 Preston White Drive, Suite 100 Reston, VA 22091 ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From klm@CNRI.Reston.Va.US Thu Jun 20 17:49:15 1996 From: klm@CNRI.Reston.Va.US (Ken Manheimer) Date: Thu, 20 Jun 1996 12:49:15 -0400 (EDT) Subject: [PYTHON META-SIG] Sound-sig In-Reply-To: Message-ID: On Wed, 19 Jun 1996, Ken Manheimer wrote: > Robin Friedrich wrote: > > doc-sig is still broken as far as I can tell. We've been trying to send > > out the new gendoc Daniel has written but have yet to see it. > > (Sent three times) > > Aargh. I tried a test posting (after trying a few less intrusive tests), > only to have it delivered. I suggest you retry your post, but this time Mike Mclay, the doc sig coordinator, notified me this morning of some bounce notifications he's been getting for the sig. Evidently the messages robin was forwarding were exceeding the _hard_ 40K limit that majordomo imposes. I suggest in the future either forwarding large submissions directly to the sig manager, for them to put in place using the sigs anonymous-ftp upload mechanism (see ), or upload them to the ftp.python.org incoming directory, and i'll put them in the sig dir when i have a moment, and leave the coordinator to link them in. In any case, it's not entirely appropriate to forward a software distribution to all the members on the list, particularly when there's an alternative - i realize this alternative is only just emerging, but it'd be good to work with it, and iron it out if necessary, so we can depend upon it... Ken ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From cotton@eniac.seas.upenn.edu Tue Jun 18 18:09:16 1996 From: cotton@eniac.seas.upenn.edu (cotton@eniac.seas.upenn.edu) Date: Tue, 18 Jun 1996 17:09:16 GMT Subject: [PYTHON META-SIG] sound-sig Message-ID: <199606181709.RAA00437@chronis.upenn.edu> ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From cotton@eniac.seas.upenn.edu Tue Jun 18 22:39:11 1996 From: cotton@eniac.seas.upenn.edu (Scott) Date: Tue, 18 Jun 1996 17:39:11 -0400 (EDT) Subject: [PYTHON META-SIG] Sound-sig Message-ID: <199606182139.RAA12055@blue.seas.upenn.edu> sound-sig: a special interest group for developing audio support in Python. The goal of this group is to help bring the realm of audio into Python. As of this writing, Python has audio support for only two platforms. For this reason, the primary goal for this group will be the development of builtin sound modules for various platform/soundcard combinations. However, the scope of the sound-sig may include discussions pertaining to the enhancement of basic sound support for such areas as speech/natural language processing and music. About this list: Additions and deletions are all automated via Majordomo. For details, send the word `help' in the body of a mail messages to the Administrivia address given below. the subscription policy is `open', meaning you can add or delete yourself at any time, but you cannot add or delete anyone else without approval. This list is unmoderated and unrestricted. This means that anybody can post messages to the list. Messages are archived and available for download, as are perhaps other useful files. for details, send the word `index' in the body of a messages to the Administrivia address. post messages to everyone on the list by using the List address. If you absolutely must contact a human being, use the Owner address. ======================================================================== List address: sound-sig@python.org Administrivia: sound-sig-request@python.org Owner: sound-sig-owner@python.org ========================================================================= ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From fredrik_lundh@ivab.se Tue Jun 18 22:57:06 1996 From: fredrik_lundh@ivab.se (Fredrik Lundh) Date: Tue, 18 Jun 1996 23:57:06 +0200 Subject: [PYTHON META-SIG] Sound-sig In-Reply-To: <199606182139.RAA12055@blue.seas.upenn.edu> (cotton@eniac.seas.upenn.edu) Message-ID: <9606182157.AA12066@arnold.image.ivab.se> Why not? Or should we merge this with the image-sig (which is slowly moving towards video as well) into a multimedia-sig? /F ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From rmasse@newcnri.CNRI.Reston.Va.US Tue Jun 18 23:04:17 1996 From: rmasse@newcnri.CNRI.Reston.Va.US (Roger Masse) Date: Tue, 18 Jun 1996 18:04:17 -0400 Subject: [PYTHON META-SIG] Sound-sig In-Reply-To: <9606182157.AA12066@arnold.image.ivab.se> References: <199606182139.RAA12055@blue.seas.upenn.edu> <9606182157.AA12066@arnold.image.ivab.se> Message-ID: <199606182204.SAA05077@newcnri.CNRI.Reston.Va.US> Fredrik Lundh writes: > > Why not? Or should we merge this with the image-sig (which is slowly > moving towards video as well) into a multimedia-sig? > > /F > Yes! I don't think there's that much traffic on the image SIG nor do I think the audio stuff will be that much long-term either... Good idea. -roj ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From guido@CNRI.Reston.Va.US Tue Jun 18 23:28:06 1996 From: guido@CNRI.Reston.Va.US (Guido van Rossum) Date: Tue, 18 Jun 1996 18:28:06 -0400 Subject: [PYTHON META-SIG] Sound-sig In-Reply-To: Your message of "Tue, 18 Jun 1996 17:39:11 EDT." <199606182139.RAA12055@blue.seas.upenn.edu> References: <199606182139.RAA12055@blue.seas.upenn.edu> Message-ID: <199606182228.SAA15818@monty> > sound-sig: a special interest group for developing audio support in Python. I haven't seen much discussion of audio support on the main mailing list, and I believe it's unwise to start a SIG based on a single post. --Guido van Rossum (home page: http://www.python.org/~guido/) ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From klm@CNRI.Reston.Va.US Wed Jun 19 16:37:49 1996 From: klm@CNRI.Reston.Va.US (Ken Manheimer) Date: Wed, 19 Jun 1996 11:37:49 -0400 (EDT) Subject: [PYTHON META-SIG] Sound-sig In-Reply-To: <199606182204.SAA05077@newcnri.CNRI.Reston.Va.US> Message-ID: On Tue, 18 Jun 1996, Roger Masse wrote: > Fredrik Lundh writes: > > > > Why not? Or should we merge this with the image-sig (which is slowly > > moving towards video as well) into a multimedia-sig? > > Yes! I don't think there's that much traffic on the image SIG nor > do I think the audio stuff will be that much long-term either... > > Good idea. I agree - i think it's a good idea to combine all these things into a multimedia-sig. In fact, i'd go further, and suggest bringing in some other low-volume sigs that i think are related - the web-sig and doc-sig. Would this make sense? I would further propose calling the resulting thing the "media-sig", which implies that it is about each of the media, individually, as well as any combinations of them. "Multimedia", on the other hand, implies to me particularly the combinations. (I realize that "media-sig" might sound like a public relations sig, but that doesn't stop, eg, the Media Lab at MIT from using that name...) Incidentally, should we be including the guy who made the proposal in this discussion? I see no reason to keep it from him, he may have ideas, and he's not on the meta-sig... Ken Manheimer klm@cnri.reston.va.us 703 620-8990 x268 (orporation for National Research |nitiatives 1895 Preston White Drive, Suite 100 Reston, VA 22091 ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From friedric@rose.rsoc.rockwell.com Wed Jun 19 18:34:46 1996 From: friedric@rose.rsoc.rockwell.com (Robin Friedrich) Date: Wed, 19 Jun 1996 12:34:46 -0500 Subject: [PYTHON META-SIG] Sound-sig Message-ID: <199606191734.MAA19308@darwin.rsoc.rockwell.com> |> From owner-meta-sig@python.org Wed Jun 19 11:44 CDT 1996 |> Date: Wed, 19 Jun 1996 11:37:49 -0400 (EDT) |> From: Ken Manheimer |> Reply-To: klm@CNRI.Reston.Va.US |> |> On Tue, 18 Jun 1996, Roger Masse wrote: |> |> > Fredrik Lundh writes: |> > > |> > > Why not? Or should we merge this with the image-sig (which is slowly |> > > moving towards video as well) into a multimedia-sig? |> > |> > Yes! I don't think there's that much traffic on the image SIG nor |> > do I think the audio stuff will be that much long-term either... |> > |> > Good idea. |> |> I agree - i think it's a good idea to combine all these things into a |> multimedia-sig. In fact, i'd go further, and suggest bringing in some |> other low-volume sigs that i think are related - the web-sig and doc-sig. |> Would this make sense? |> |> I would further propose calling the resulting thing the "media-sig", which |> implies that it is about each of the media, individually, as well as any |> combinations of them. "Multimedia", on the other hand, implies to me |> particularly the combinations. (I realize that "media-sig" might sound |> like a public relations sig, but that doesn't stop, eg, the Media Lab at |> MIT from using that name...) |> |> Incidentally, should we be including the guy who made the proposal in |> this discussion? I see no reason to keep it from him, he may have ideas, |> and he's not on the meta-sig... |> |> Ken Manheimer klm@cnri.reston.va.us 703 620-8990 x268 media-sig sounds awfully general to me and would violate one of the guidelines we set for sigs, (that is to have specific goals/projects to work on). I currently don't mind crossposting between web-sig and doc-sig (I'm about to do that soon myself with my HTMLgen stuff). BTW: doc-sig is still broken as far as I can tell. We've been trying to send out the new gendoc Daniel has written but have yet to see it. (Sent three times) -Robin ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From fdrake@CNRI.Reston.Va.US Wed Jun 19 18:42:21 1996 From: fdrake@CNRI.Reston.Va.US (Fred L. Drake) Date: Wed, 19 Jun 1996 13:42:21 -0400 (EDT) Subject: [PYTHON META-SIG] status of doc-sig mailing list In-Reply-To: <199606191734.MAA19308@darwin.rsoc.rockwell.com> from "Robin Friedrich" at Jun 19, 96 12:34:46 pm Message-ID: <199606191742.NAA20112@weyr.CNRI.Reston.Va.US> Robin wrote: > BTW: > doc-sig is still broken as far as I can tell. We've been trying to send > out the new gendoc Daniel has written but have yet to see it. > (Sent three times) Barry is still out today, and he's the one who deals with majordomo for the PSA machine. Hold off until he has a chance to get back and take a look at the problem. I'll try and be aware of his progress and let you & Daniel know when the problem has been fixed. -Fred -- Fred L. Drake, Jr. fdrake@cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive Reston, VA 22091 ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From klm@CNRI.Reston.Va.US Thu Jun 20 00:11:05 1996 From: klm@CNRI.Reston.Va.US (Ken Manheimer) Date: Wed, 19 Jun 1996 19:11:05 -0400 (EDT) Subject: [PYTHON META-SIG] Sound-sig In-Reply-To: <199606191734.MAA19308@darwin.rsoc.rockwell.com> Message-ID: > media-sig sounds awfully general to me and would violate one of the > guidelines we set for sigs, (that is to have specific goals/projects to > work on). I currently don't mind crossposting between web-sig and A couple of responses have opened my eyes to the fact that my proposal was off-base (and, in fact, would betray some of the principles i had advocated early on). I take it back! > doc-sig is still broken as far as I can tell. We've been trying to send > out the new gendoc Daniel has written but have yet to see it. > (Sent three times) Aargh. I tried a test posting (after trying a few less intrusive tests), only to have it delivered. I suggest you retry your post, but this time CC me on it. This may provide further information. (And i did recall seeing a post get through on that list, today - concerning the "cocoon utilities" documentation tool...) Ken Manheimer klm@cnri.reston.va.us 703 620-8990 x268 (orporation for National Research |nitiatives 1895 Preston White Drive, Suite 100 Reston, VA 22091 ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org ================= From klm@CNRI.Reston.Va.US Thu Jun 20 17:49:15 1996 From: klm@CNRI.Reston.Va.US (Ken Manheimer) Date: Thu, 20 Jun 1996 12:49:15 -0400 (EDT) Subject: [PYTHON META-SIG] Sound-sig In-Reply-To: Message-ID: On Wed, 19 Jun 1996, Ken Manheimer wrote: > Robin Friedrich wrote: > > doc-sig is still broken as far as I can tell. We've been trying to send > > out the new gendoc Daniel has written but have yet to see it. > > (Sent three times) > > Aargh. I tried a test posting (after trying a few less intrusive tests), > only to have it delivered. I suggest you retry your post, but this time Mike Mclay, the doc sig coordinator, notified me this morning of some bounce notifications he's been getting for the sig. Evidently the messages robin was forwarding were exceeding the _hard_ 40K limit that majordomo imposes. I suggest in the future either forwarding large submissions directly to the sig manager, for them to put in place using the sigs anonymous-ftp upload mechanism (see ), or upload them to the ftp.python.org incoming directory, and i'll put them in the sig dir when i have a moment, and leave the coordinator to link them in. In any case, it's not entirely appropriate to forward a software distribution to all the members on the list, particularly when there's an alternative - i realize this alternative is only just emerging, but it'd be good to work with it, and iron it out if necessary, so we can depend upon it... Ken ================= META-SIG - SIG on Python.Org SIGs and Mailing Lists send messages to: meta-sig@python.org administrivia to: meta-sig-request@python.org =================