Difference between revisions of "Configuration Files For Python"
Jump to navigation
Jump to search
Russ hensel (talk | contribs) |
Russ hensel (talk | contribs) |
||
| Line 3: | Line 3: | ||
= Why Configuration Files = | = Why Configuration Files = | ||
| + | Most larger program should have configuration files: | ||
| + | * Program becomes more flexible without reprogramming. | ||
| + | * Users can inject their own preferences. | ||
| + | * The environment changes, requiring that the program adapt. | ||
| + | |||
| + | There are a large number of formats for configuration files, some are accessed only through wizzards to they can have a secret format. Some configuration files are not even really files but instead are entries in a data base. But most are stored in some sort of human readable text format and can be edited with a straight ahead text editor. | ||
= Configuration in .py Files = | = Configuration in .py Files = | ||
Revision as of 10:47, 11 February 2018
This is an article started by Russ Hensel, see "http://www.opencircuits.com/index.php?title=Russ_hensel#About My Articles" About My Articles for a bit of info. The page is only partly finished.
Why Configuration Files
Most larger program should have configuration files:
- Program becomes more flexible without reprogramming.
- Users can inject their own preferences.
- The environment changes, requiring that the program adapt.
There are a large number of formats for configuration files, some are accessed only through wizzards to they can have a secret format. Some configuration files are not even really files but instead are entries in a data base. But most are stored in some sort of human readable text format and can be edited with a straight ahead text editor.
Configuration in .py Files
Why Not
Other Links
code
