The common - widely accustomed - configuration file format is mainly section oriented with limits for the application. Namely for the file based "executable-setup' of software components including graphical user interfaces. Alternatives are already available, e.g. ConfigParser and ConfigObj.
The main for yet another issue arose from the requirements:
1. to supply an integrated solution of simple configuration files with the internal data representation by PyObjectTrees
2. to supply a facility for the customizable setup of complex software components including graphical interfaces by a 'simple' syntax - applicable for almost anyone.
Therefore e.g. following features are introduced:
-> path-like section names - representing tree structures with name spaces, e.g. '[a.b.c]'
-> introduction of multiple keywords for recursive resolution and replacement during the scan, e.g. for environment, executables, includes, GUI masks, SW components, ..
Be the first to post a review of PyConfigExtended - Jarngreipr!