Changes between Version 2 and Version 3 of PeriodicTable

Timestamp:

12/21/06 14:34:43 (6 years ago)

Author:

CakeProphet

Comment:

--

PeriodicTable

@@ -5 +5 @@
 == Hypothetical example of use ==
 
-The user should only need to import the package itself, at which point __init__.py will construct all the elemental information and instantiate an object of the Periodic class.
+The user should only need to import the package itself, at which point {{{__init__.py}}} will construct all the elemental information and instantiate an object of the Periodic class.
 
 The periodic table consists of "element" objects. Each element object contains attributes which correspond to elemental properties such as freezing point, atomic mass, and electon configuration.
@@ -65 +65 @@
 
 The primary focus at the moment is accuracy, ease-of-use, and power. Optimization can come later.
+
+=== Some conventions to follow ===
+I don't require any conventions unless they're required for the code to operate properly.
+
+* All temperatures should be in Celsius. Conversions will be performed by methods (or a package in scipy, if scipy has a unit conversion system)[[BR]]
+* A dictionary mapping properties to Element objects should follow the naming convention of "bypropname" (for example, the dictionary mapping symbol to Element is named "bysymbol"). See {{{Periodic.__getitem__}}} for why this should be done.