From pviktori at redhat.com Fri May 25 11:08:54 2018 From: pviktori at redhat.com (Petr Viktorin) Date: Fri, 25 May 2018 17:08:54 +0200 Subject: [python-ldap] ANN: python-ldap 3.1.0 Message-ID: <1bdebc11-9c46-b8e2-db69-2af7fe0d0c1f@redhat.com> Find a new release of python-ldap here: https://pypi.python.org/pypi/python-ldap/3.1.0 Notable changes since 3.1.0 are: - Long-deprecated functions `ldap.open()` and `ldap.init()` are removed - `LDAPObject.compare_s()` and `compare_ext_s` return bool instead of 0 or 1 If you find any issues, please report them either on this mailing list or on the GitHub tracker: https://github.com/python-ldap/python-ldap/issues About the project: python-ldap provides an object-oriented API to access LDAP directory servers from Python programs. It mainly wraps the OpenLDAP 2.x libs for that purpose. Additionally it contains modules for other LDAP-related stuff (e.g. processing LDIF, LDAP URLs and LDAPv3 schema). Project's web site: https://www.python-ldap.org/ Git commit hash for the release: python-ldap-3.0.0 a06254e6b75fb0430fc0eaa475c30bc370d18030 ---------------------------------------------------------------- Released 3.1.0 2018-05-25 This release brings two minor API changes: - Long-deprecated functions `ldap.open()` and `ldap.init()` are removed - `LDAPObject.compare_s()` and `compare_ext_s` return bool instead of 0 or 1 All changes since 3.0.0: Lib/ * Remove long deprecated functions ldap.open() and ldap.init() * LDAPObject.compare_s() and LDAPObject.compare_ext_s() now return a bool instead of 1 or 0. * Make iteration over cidict yield same values as keys() * Fail if pyasn1 is not installed * Fix parsing of PPolicyControl ASN.1 structure * Use items() when appropriate in dict iteration * Add support for tracing LDAP calls. Tracing can now be enabled with the env var PYTHON_LDAP_TRACE_LEVEL and redirected to a file with PYTHON_LDAP_TRACE_FILE. (This is mainly intended for debugging and internal testing; the configuration or output may change in future versions.) Modules/ * Fix ref counting bug in LDAPmessage_to_python Doc/ * Remove warning about unreleased version * Doc: Replace Mac OS X -> macOS Tests/ * Add tests and coverage for tracing * Disable warnings-as-errors for Python 3.4 * Fix assertTrue to assertEqual * Mark several test values as bytes Lib/slapdtest/ * Fix error message for missing commands * Make SlapdObject a context manager * Disable SASL external when missing SASL support * Make SlapdObject.root_dn a property * In SlapdObject, build include directives dynamically * Move import statements to top level Code style: * Add Makefile rules for automatic formatting of C and Python code * Reformat and indent all C files * Trim white space throughout the project Infrastructure: * Add py3-trace tox environment to Travis CI config * Add new Pytest cache directory to gitignore General: * Update all pypi.python.org URLs to pypi.org From pviktori at redhat.com Tue Jun 12 04:37:27 2018 From: pviktori at redhat.com (Petr Viktorin) Date: Tue, 12 Jun 2018 10:37:27 +0200 Subject: [python-ldap] New commiters Message-ID: Please welcome Jon Dufresne and Christian Heimes as python-ldap committers! The committer bit means they will be able to formally review and merge contributions. They made many new fixes, features and reviews over the past months, and I increasingly felt that the limited time I can devote to the project is slowing the development down. Jon and Christian frequently have different opinions about the direction of the projects. While the discussions can sometimes be heated or drag on for longer than necessary, I believe they're quite healthy to the project in the long run. For those interested, committer responsibilities are documented in the docs: https://python-ldap.org/en/latest/contributing.html#instructions-for-core-committers Full disclosure: Like me, Christian works at Red Hat. This isn't ideal ? while we're trying to work for the good of the project overall, we can tend to test against and improve support for certain technologies/use cases, and depend on other contributors and automated testing to support others. But if anyone feels that we're blocking or discouraging someone from improving python-ldap for their use case, then something is wrong ? please complain loudly.