Fermilab Computing Division

CS Document 2944-v2

Python Best Practices

Document #:
CS-doc-2944-v2
Document type:
Documentation
Submitted by:
Randolph Herber
Updated by:
Randolph Herber
Document Created:
07 Oct 2008, 15:49
Contents Revised:
09 Oct 2008, 10:00
Metadata Revised:
09 Oct 2008, 10:00
Viewable by:
  • Public document
Modifiable by:

Quick Links:
Latest Version

Other Versions:
CS-doc-2944-v1
07 Oct 2008, 15:49
Abstract:
Written for CD/LSC/DBI/DBA by Randolph J Herber, Oct 6, 2008.

This document tries to describe some of the issues involved
in using the Python language properly.
Python has typed values instead of typed variables,
which means the programmer and code reviewer needs to
assure that appropriate values are passed to functions and methods.
Python uses white space instead of punctuation or keywords to
delimit boundaries of program constructs,
which means the programmer and code reviewer needs to
assure that only and all appropriate code is within
such program constructs.
When Python detects programming errors, it usually is at execution time;
therefore testing is required.
Python supports object oriented design and coding.

Files in Document:
Keywords:
python
Notes and Changes:
Syntax errors in some examples and experiments showed that
'from' statement placement as implemented in the compiler
are less strict than the language documentation indicates.
DocDB Home ]  [ Search ] [ Authors ] [ Events ] [ Topics ]

DocDB Version 8.8.9, contact Document Database Administrators