CpSc 236, Selected Programming Languages: Python

Syllabus, Spring 2002

Meets: MWF 1 (8:30-9:20 a.m.), ECB 119

Instructor	Office	Phone	E-mail
Michael P. Conlon, Ph.D.	106D Maltby Center	724-738-2143	michael.conlon@sru.edu

Office Hours: see my home page.

Course Goals:Upon successful completion of this course, students will be able to:

• List standard Python data types, identifying the domain of each type and the operations defined on it.
• Identify and write code containing the full range of standard data types, control structures, and other features/objects supported in Python.
• Write well-designed and well-documented programs that meet specified requirements and make proper use of the special features and exploit the strengths of Python.

Texts:

• Learning Python, Lutz and Ascher, O'Reilly, ISBN #1-56592-464-9

• Python Standard Library, Lundh, O'Reilly, ISBN #0-596-00096-0

Worldwide Web Resources

• www.python.org

• www.wxwindows.org

• www.wxpython.org

• cs.sru.edu/~conlon/py_intro.html

Attendance Policy: You are expected to attend and participate in class. Your grade will be reduced if your attendance is not regular. For this purpose, being late to class three times will be counted as one absence.

Grading:	Exams	Projects	Misc.
	45%	45%	10%

Plagiarism Policy: Students are reminded of the University plagiarism policies in the catalog. I do not consider all "working together" as plagiarism, but you must write your own code. If projects from two students are substantially similar, I will consider both as guilty of plagiarism. You are responsible for keeping your work secure. Students judged guilty of plagiarism will receive WF or F for the course.

Code Re-use Policy: You may incorporate code from sources other than fellow students into your programs, provided you indicate via comments what the source of such code is. (The incorporation of copyrighted code is prohibited, unless you are licensed to use the code. For example, GPL'd code or code from the texts may be reused. Code in Web tutorials or Linux HOWTO's is implicitly licensed for code reuse, provided you do not copy the Web pages in their entirety.)

Grading Policies:

• To pass this course you must both complete all assignments (tests, programs, projects, homework, etc.) and earn a passing average.

• Late work will be downgraded 10 points for each school day or fraction thereof that it is late, down to a minimum of 1 point. Regardless of this rule, programs submitted after the program is reviewed in class will receive at most 50 points, and less if your solution is too much like mine.

• No project over one week late will be accepted once the final week of the semester has begun.

• Exams will be open-book. This applies only to your textbooks and any documentation handouts I have supplied, but not to notebooks, project handouts, or project solutions.

• If, on an exam, you cannot write a program for a problem similar to one you successfully tackled as a programming project, it will be assumed that the programming project was plagiarized.