[Twisted-Python] Understanding the role of .tap files

Sergio Trejo serj_trejo at hotmail.com
Sun Aug 15 06:18:01 EDT 2004

Did someone mention recently on #twisted.web (or maybe a related IRC channel 
such as #divmod ) that .tac files are going to be deprecated in the next 
major rev of Twisted, or maybe I misunderstood (I thought I read this a few 
days ago an IRC conversation but can't recall).


>From: Itamar Shtull-Trauring <itamar at itamarst.org>
>Reply-To: Twisted general discussion <twisted-python at twistedmatrix.com>
>To: Twisted general discussion <twisted-python at twistedmatrix.com>
>Subject: Re: [Twisted-Python] Understanding the role of .tap files
>Date: Fri, 13 Aug 2004 10:33:44 -0400
>On Thu, 2004-08-12 at 21:58, Abe Fettig wrote:
> > I'm looking for help understanding how .tap files are meant to be used
> > in production.  I know that a .tap, when generated, contains the
> > configuration info for an application.  And there are tools like tap2deb
> > and tap2ntsvc that take the information in a .tap and convert it into an
> > installable packages.
>tap2deb and friends also work on .tac files, which are Python files (see
>the application howto for an example). .tac files allow you to give
>users a Python file for config that they can edit. Or, your .tap or .tac
>could load a config  file in the format of your choice and use that to
>configure your app, and then users could edit that.
>Twisted-Python mailing list
>Twisted-Python at twistedmatrix.com

Help STOP SPAM with the new MSN 8 and get 2 months FREE*  

More information about the Twisted-Python mailing list