A Sample of the Title of This Monograph

The Python Papers Monograph xxx

A Sample of the Title of this Monograph

First Author's or Editor's Name

First Author's Institutional Affiliation

Second Author's or Editor's Name

Second Author's Institutional Affiliation

The Python Papers Monograph

ISSN 1837-7092

A periodical of The Python Papers Anthology

This work is copyright under the Creative Commons 2.5 license subject to Attribution, Noncommercial and Share-Alike conditions. The full legal code may be found at

The Python Papers Anthology was first published in 2006 in Melbourne, Australia.

For information:

The Python Papers Anthology Editorial Committee

email:

Website:

Co-Editors-in-Chief: Maurice Ling

Tennessee Leeuwenburg

Associate Editors:

Andreas SchreiberSarah Mount

Guilherme PoloGuy K. Kloss

Mike DewhirstRichard Jones

Chetan Giridhar

Editorial Reviewers: Raymond Hettinger

Jacob Kaplan-Moss

Technical Reviewers for this Monograph

XXXX

Table of Contents

Series Editor's Introduction...... 1

Technical Reviewers...... 2

About the Author...... 3

Acknowledgement...... 4

1. Introduction ...... 5

1.1. Sub-section of Introduction...... 5

1.1.1. Sub-Subsection of Introduction...... 5

1.1.1.1. Sub-sub-Subsection of Introduction...... 5

2. The Bulk of Materials...... 6

3. References...... 7

I. Appendix A...... 7

Specific Peer Review Process for The Python Papers Monograph...... 8

Series Editor's Introduction

This page is written by Editor-in-Chief or Associate Editor of The Python Papers Anthology to introduce this monograph. Allows 2 page for this.

Technical Reviewers

FirstnameA LastnameA: Short biography of Technical Reviewer A

FirstnameB LastnameB: Short biography of Technical Reviewer A

FirstnameC LastnameC: Short biography of Technical Reviewer A

About the Author

Short biograph of the author – not more than one page.

Acknowledgement

Statement of acknowledgement. Not more than one page.

A Sample of the Title of this Monograph

First Author's or Editor's Name

First Author's Institutional Affiliation

Contact email

Second Author's or Editor's Name

Second Author's Institutional Affiliation

Contact email

1.Introduction

This is the introduction chapter. One line spacing before the subsection. You may have a synopsis or abstract before Introduction – it should be 2 lines spaces after the contact email of the last author.

1.1.Sub-section of Introduction

This is the subsection of introduction. One line spacing before the sub-section.

1.1.1.Sub-Subsection of Introduction

This is the sub-subsection of introduction. One line spacing before the sub-section.

1.1.1.1. Sub-sub-Subsection of Introduction

This is the sub-sub-subsection of introduction. Please try not to go beyond this. Two lines spacing before the next chapter.

2.The Bulk of Materials

This is bulk of the materials – repeat as needed.

Each paragraph is separated by an empty line.

This is an example of reference with a single author (Glenn, 2005), two authors (Hao and Naiman, 2007), more than 2 authors (Voon et al., 1995). Multiple references should be separated by semi-colon (Glenn, 2005; Hao and Naiman, 2007).

In-line codes should be in Courier font, size 10, as shown here:

class Poisson:

mean = 0.0

def __init__(self, lamb = 0.0):

self.mean = lamb

def PDF(self, x):

return math.exp(self.mean)* \

pow(self.mean,x)/self.factorial(x)

Table 2.1. Title of Table.

Figure 2.1. Caption of Figure.

3.References

Referencing should follow Harvard Style, in alphabetical order of first author.

I. Appendix A

Appendices are numbered in Roman numerals.

Specific Peer Review Process for The Python Papers Monograph

The Python Papers Monograph (ISSN under application) is a publication under The Python Papers Anthology. This monograph series provides a refereed format for publication of monograph-length reports including dissertations, conference proceedings, case studies, advanced-level lectures, and similar material of theoretical or empirical importance. It does so quickly, informally and at a high level, where the Python programming language is an integral aspect.

In some cases, the timeliness of a manuscript is more important than its form, which may be unfinished or unpolished. Hence, it is possible that proofs may be outlined with an intention to publish elsewhere at a later date.

Refereeing is done by members of the The Python Papers Anthology Editorial Committee and other authorities in the topic concerned and may be acknowledged in name in the published form. Scientific quality is the over-riding criterion for refereeing.

The full editorial policy of The Python Papers Anthology can be found at