- Fix a bug in which plaster would crash harder than expected if a URI is specified to a distribution that does not have the specified entry points. Now a LoaderNotFound exception will be raised instead of a bad unpacking of tuples.
1.1.1
==================
- Add support for Python 3.11.
- Fix an bug introduced in 1.1 on some systems where ``plaster.exceptions.MultipleLoadersFound`` would be raised due to ``lib`` and ``lib64`` being symlinked to each other and both added to the ``sys.path``. See https://github.com/Pylons/plaster/pull/27
1.1
================
- Drop support for Python 2.7, 3.4, 3.5, 3.6.
- Add support for Python 3.8, 3.9, 3.10.
- Drop runtime dependency on setuptools / pkg_resources by switching to ``importlib.metadata``.
1.0
================
- Improve the exception message for ``InvalidURI`` to show the ``config_uri``. See https://github.com/Pylons/plaster/pull/17
0.5
================
- 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``). See https://github.com/Pylons/plaster/pull/16
- 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 ``scheme+package``. See https://github.com/Pylons/plaster/pull/16
0.4
================
- Removed the ``plaster.NoSectionError`` exception. It's expected that individual loaders should return an empty dictionary of settings in the case that a section cannot be found. See https://github.com/Pylons/plaster/pull/12
- Expect the ``wsgi`` protocol to raise ``LookupError`` exceptions when a named wsgi component cannot be found. See https://github.com/Pylons/plaster/pull/12