Python Programming Language
SIG Coordinator Resource Guide
Each PSA SIG coordinator has at their disposal:
These resources are available on python.org, under the name of the SIG. The SIG coordinator has remote control of them, with email- and web-mediated administrative authority of the mailing list, and special group privileges, invocable within anonymous-ftp, to control the contents of the sig directory. Both facilities are keyed on a single password, which is assigned to the SIG coordinator.
Mailman controlsUsing the SIG password, the coordinator can administer most attributes of the sig maillist, including the subscribership. To change list options, visit:
To change a subscriber's options, visit the listinfo page for the sig:
and click on or enter the user's address to go to the options page for the user. You can then us the list administrators password to authorize option changes or unsubscription of the user.
Finally, the list administrative db:
www.python.org Web Documents and The .ht Template FileThe SIG password also enables the SIG coordinator to change the contents of their SIG web directory via anonymous ftp. The following describes the organization and formatting considerations of the www.python.org web pages, and the procedure to upload and otherwise change the contents of the web directory.
www.python.org Web Documents Organization and FormattingThe python.org web pages are located at http://www.python.org/. While it's nice to be able to delegate authoring of pages to people outside the site, those people need to keep in mind a couple of constraints on the format of their pages:
The mirroring requires that all links going from one page to another within the python.org web site not presume anything about the location of the root of the hierarchy. That is, they should be relative links, strictly within the hierarchy.
The regular page layout entails producing your pages as template files, rather than regular html. (We conventionally qualify the template files with ".ht", instead of ".html".) It also requires processing your files after you've uploaded them to the www.python.org host, which is provide for with an exported make command, as described below.
The tempate file which you produce is basically html, but with the document header and footer mostly excluded. The standard header and footer are incorporated by processing your template file with a local utility, to produce the corresponding, regularly formatted ".html" result. This utility puts on the header and footer, including things like a handy-dandy quick-jump bar, link and border colors which indicate the category of the page (general vs psa vs documentation), and so forth - all using relative URL paths, so their integrity is preserved on the mirror sites.
The relative links situation should be fairly self explanatory - examine the source of some existing documents in the mainstream of the hierarchy for examples. To construct your own .ht files, see the Python Web Maintenance document, particularly the section concerning the template format, for details.
The following topics describe how to gain access privileges to upload your documents to your SIG directory, and to run the procedure to produce .html documents from .ht ones.
Getting Group Access Privileges
The anonymous-ftp group privileges enables you to upload to the SIG
directory. However, you are not able to overwrite anything - you have
to use a special site-exec command, sigjob, to remove
existing files, first, and then you can do a regular ftp
The sigjob CommandThe sigjob site command is necessary for a few reasons.
The sigs jobs daemon checks for and processes jobs immediately, but asynchronously, so the results will show up in the log file shortly after your submission of the command returns.
There is a small set of sigjob commands currently available.
This system is growing. Please send suggestions and questions to email@example.com.