https://github.com/dataflake/dataflake.fakeldap
Fake layer over python-ldap/pyldap for testing purposes
https://github.com/dataflake/dataflake.fakeldap
ldap-client python testing-tools
Last synced: 2 months ago
JSON representation
Fake layer over python-ldap/pyldap for testing purposes
- Host: GitHub
- URL: https://github.com/dataflake/dataflake.fakeldap
- Owner: dataflake
- License: other
- Created: 2017-05-31T13:54:30.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2024-03-14T08:17:40.000Z (over 1 year ago)
- Last Synced: 2024-03-15T08:23:16.722Z (over 1 year ago)
- Topics: ldap-client, python, testing-tools
- Language: Python
- Homepage: https://dataflakefakeldap.readthedocs.io/
- Size: 290 KB
- Stars: 0
- Watchers: 2
- Forks: 4
- Open Issues: 0
-
Metadata Files:
- Readme: README.rst
- Changelog: CHANGES.rst
- Contributing: CONTRIBUTING.md
- License: LICENSE.txt
Awesome Lists containing this project
README
.. 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.