Metadata-Version: 2.1
Name: dataflake.fakeldap
Version: 3.0
Summary: Mocked-up LDAP connection library
Home-page: https://github.com/dataflake/dataflake.fakeldap
Author: Jens Vagelpohl
Author-email: jens@dataflake.org
License: ZPL 2.1
Project-URL: Source code, https://github.com/dataflake/dataflake.fakeldap
Project-URL: Issue Tracker, https://github.com/dataflake/dataflake.fakeldap/issues
Description: .. image:: https://github.com/dataflake/dataflake.fakeldap/actions/workflows/tests.yml/badge.svg
           :target: https://github.com/dataflake/dataflake.fakeldap/actions/workflows/tests.yml
           :alt: Unit test status
        
        .. image:: https://coveralls.io/repos/github/dataflake/dataflake.fakeldap/badge.svg?branch=master
           :target: https://coveralls.io/github/dataflake/dataflake.fakeldap?branch=master
           :alt: Coverage Status
        
        .. image:: https://readthedocs.org/projects/dataflakefakeldap/badge/?version=latest
           :target: https://dataflakefakeldap.readthedocs.io
           :alt: Documentation Status
        
        .. image:: https://img.shields.io/pypi/v/dataflake.fakeldap.svg
           :target: https://pypi.python.org/pypi/dataflake.fakeldap
           :alt: PyPI
        
        .. image:: https://img.shields.io/pypi/pyversions/dataflake.fakeldap.svg
           :target: https://pypi.python.org/pypi/dataflake.fakeldap
           :alt: Python versions
        
        ====================
         dataflake.fakeldap
        ====================
        This package offers a mock ``python-ldap`` library that can be used 
        for testing code relying on ``python-ldap`` without having to configure 
        and populate a real directory server.
        
        Starting with version 3.0 the library will behave just like ``python-ldap``
        version 3.3 or higher:
        
        - distinguished names, relative distinguished names, attribute names and
          queries are expected to be native un-encoded string values.
        
        - attribute values are expected to be bytes values.
        
        If you pass the wrong type of string, the library will raise a ``TypeError``.
        See https://www.python-ldap.org/en/latest/bytes_mode.html for a short
        description of this behavior.
        
        Since queries are un-encoded string values and attribute values passed in the
        query would never match bytes values in the data store, searches will always
        test against both unencoded and bytes values.
        
        
        Documentation
        =============
        Full documentation is available at
        https://dataflakefakeldap.readthedocs.io/
        
        
        Bug tracker
        ===========
        A bug tracker is available at
        https://github.com/dataflake/dataflake.fakeldap/issues
        
Keywords: ldap ldapv3
Platform: UNKNOWN
Classifier: Development Status :: 5 - Production/Stable
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: Zope Public License
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.5
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Programming Language :: Python :: Implementation :: CPython
Classifier: Programming Language :: Python :: Implementation :: PyPy
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Classifier: Topic :: Software Development :: Testing
Classifier: Topic :: System :: Systems Administration :: Authentication/Directory :: LDAP
Requires-Python: >=3.5
Provides-Extra: docs
