plaster is a loader interface around multiple config file formats. It
exists to define a common API for applications to use when they wish to load
configuration. The library itself does not aim to handle anything except
a basic API that applications may use to find and load configuration settings.
Any specific constraints should be implemented in a pluggable loader which can
be registered via an entrypoint.
See http://docs.pylonsproject.org/projects/plaster/en/latest/ or
docs/index.rst in this distribution for detailed documentation.
- When a scheme is not supplied, plaster.parse_uri will now autogenerate
a scheme from the file extension with the format file+<ext> instead of
simply <ext> (for example, file+ini instead of ini).
- Absolute lookups are now pulled from the start of the scheme instead of
the end. This means that if you want to explicitly define the package that
the loader is pulled from, use package+scheme instead of
- Lookup now works differently. First “foo+bar” looks for an installed project
distribution named “bar” with a loader named “foo”. If this fails then it
looks for any loader named “foo+bar”.
- Rename the loader entry point to plaster.loader_factory.
- Add the concept of protocols to plaster.get_loader and
- plaster.find_loaders now works on just schemes and protocols
instead of full PlasterURL objects and implements the lookup
algorithm for finding loader factories.
- Change the ILoaderInfo interface to avoid being coupled to a
particular uri. ILoaderInfo.load now takes a config_uri
- Add a options dictionary to PlasterURL containing any arguments
decoded from the query string. Loaders may use these for whatever they wish
but one good option is default values in a config file.
- Define the IWSGIProtocol interface which addons can use to implement
a loader that can return full wsgi apps, servers and filters.
- The scheme is now case-insensitive.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.