Home Search Download Documentation
Help Community SIGs Modules
Email us


Call for Papers

Sixth International Python Conference

October 14-17, 1997
San Jose, California

Sponsored by CNRI and the PSA
Co-sponsored by USENIX, the Advanced Computing Systems Association

Important Dates

  • June 20, 1997: email intent to submit a paper
  • July 25, 1997: deadline for papers and panel proposals
  • August 25, 1997: notification of acceptance to authors
  • September 19, 1997 deadline for camera-ready copy


    The Sixth International Python Conference is a forum for researchers, software engineers, and practitioners using Python to discuss current work and to plan for future development of the language. Authors are invited to submit papers describing original research, or substantial or novel applications and frameworks, using Python.

    The use of Python spans a broad range of areas, from specific application domains to software engineering techniques to language-implementation techniques. The program committee encourages papers in these and other areas. Possible paper topics include:

  • Novel applications
  • Experience building large systems
  • Extensions modules
  • New directions for core language
  • Implementation techniques
  • Integrating Python with other languages
  • Embedding Python in other applications or systems
  • Comparisons between Python and other languages (e.g. Java, Tcl, Perl)
  • Software engineering issues, programming tools (for/using Python)
  • Object-oriented and pattern-based design techniques
  • Portability issues, experience developing cross-platform
  • Using Python on Windows platforms, (e.g. COM, ActiveX)
  • Distributed objects (e.g. ILU & CORBA)
  • Database applications
  • World-Wide-Web applications
  • Scientific and engineering applications

    Papers will be judged on the significance and originality of the technical content, the quality of the presentation, and their relevance to the Python community.

    Note on application papers: Authors must balance the need to appeal to the Python community at-large against the application-specific details. A paper should focus on issues and techniques that are relevant to Python. It should also provide enough explanatory material, including references to related work, to make application specific issues understandable to a wider audience.

    Technical Requirements For Papers

    We prefer papers between 6 and 12 single-spaced, 8.5"x11" pages (about 3000-6000 words), including an abstract. Papers must be original works not published or submitted for publication elsewhere at the time of the conference. We plan on making both on-line and paper proceedings available; we will request authors to provide both PostScript and HTML versions of the final version of their paper. (If any of these requirements would be a problem for you, contact the program chairs as soon as possible.)

    Authors of accepted papers will have 20 minutes to present their work at the conference, plus 10 minutes to answer questions.

    We prefer to receive paper submission via electronic mail, to ipc6-papers@python.org. Submissions can be made in several formats: plain text, HTML (a single page, with no external links), MS-Word, or Postscript1. Please see the guidelines for authors for more information about how to submit your paper. Papers must be received by July 25.

    If you intend to submit a paper, please send a short email describing the intended paper to ipc6-papers@python.org by June 20.

    Program Committee


  • Guido van Rossum, CNRI
  • Jeremy Hylton, CNRI

    Committee members:

  • Jim Ahlstrom, Interet
  • Donald Beaudry, Silicon Graphics
  • David Beazley, University of Utah
  • Donn Cave, University of Washington
  • Tom Christiansen, consultant
  • Paul Dubois, Lawrence Livermore National Laboratory
  • Robin Friedrich, United Space Alliance
  • Konrad Hinsen, Institute for Structural Biology (CEA/CNRS), France
  • Jim Hugunin, MIT
  • Bill Janssen, Xerox PARC
  • Fredrik Lundh, Saab Combitech, Sweden
  • Mark Lutz, Coral Systems
  • Michael McLay, NIST
  • Skip Montanaro, Automatrix
  • Tim Peters, Dragon Systems
  • Jim Roskind, Netscape
  • Greg Stein, Microsoft
  • Aaron Watters, Lucent Technologies