Metadata-Version: 1.1
Name: options
Version: 1.2.1
Summary: Simple, super-flexible options. Does magic upon request.
Home-page: https://bitbucket.org/jeunice/options
Author: Jonathan Eunice
Author-email: jonathan.eunice@gmail.com
License: Apache License 2.0
Description: 
        | |version| |downloads| |supported-versions| |supported-implementations| |wheel|
        
        .. |version| image:: http://img.shields.io/pypi/v/options.svg?style=flat
            :alt: PyPI Package latest release
            :target: https://pypi.python.org/pypi/options
        
        .. |downloads| image:: http://img.shields.io/pypi/dm/options.svg?style=flat
            :alt: PyPI Package monthly downloads
            :target: https://pypi.python.org/pypi/options
        
        .. |supported-versions| image:: https://img.shields.io/pypi/pyversions/options.svg
            :alt: Supported versions
            :target: https://pypi.python.org/pypi/options
        
        .. |supported-implementations| image:: https://img.shields.io/pypi/implementation/options.svg
            :alt: Supported implementations
            :target: https://pypi.python.org/pypi/options
        
        .. |wheel| image:: https://img.shields.io/pypi/wheel/withref.svg
            :alt: Wheel packaging support
            :target: https://pypi.python.org/pypi/withref
        
        ``options`` helps represent option and configuration data in a clean,
        high-function way. Changes to options can "overlay" earlier or default
        settings.
        
        For most functions and classes, ``options`` is overkill. Python's regular function
        arguments, ``*args``, ``**kwargs``, and inheritance patterns are elegant and
        sufficient for 99.9% of all development situations. ``options`` is for the
        top 0.1%:
        
          * highly functional classes or functions,
          * with many different features and options,
          * which might be adjusted or overriden at any time,
          * yet that need "reasonable" or "intelligent" defaults, and
          * that yearn for a simple, unobtrusive API.
        
        In those cases, Python's simpler built-in, inheritance-based model
        adds complexity. Non-trivial options and argument-management
        code spreads through many individual methods. This is where
        ``options``'s layered, delegation-based approach begins to shine.
        
        .. image:: http://content.screencast.com/users/jonathaneunice/folders/Jing/media/15fd180f-a6a8-45ee-a9bb-d99c527b739e/00000742.png
            :align: center
        
        For more backstory, see `this StackOverflow.com discussion of how to combat "configuration sprawl"
        <http://stackoverflow.com/questions/11702437/where-to-keep-options-values-paths-to-important-files-etc/11703813#11703813>`_.
        ``options`` full documentation
        can be found at `Read the Docs <http://options.readthedocs.org/en/latest/>`_. For examples of ``options``
        in use, see `say <https://pypi.python.org/pypi/say>`_ and `show <https://pypi.python.org/pypi/show>`_.
        
Keywords: options config configuration parameters arguments
Platform: UNKNOWN
Classifier: Development Status :: 5 - Production/Stable
Classifier: Operating System :: OS Independent
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 2.6
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.2
Classifier: Programming Language :: Python :: 3.3
Classifier: Programming Language :: Python :: 3.4
Classifier: Programming Language :: Python :: 3.5
Classifier: Programming Language :: Python :: Implementation :: CPython
Classifier: Programming Language :: Python :: Implementation :: PyPy
Classifier: Topic :: Software Development :: Libraries :: Python Modules
