>>> from ldap.extop.dds import RefreshRequest
>>> req = RefreshRequest(RefreshRequest.requestName, 'uid=temp,dc=freeiam,dc=org', 86400)
>>> repr(req)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3/dist-packages/ldap/extop/__init__.py", line 31, in __repr__
    return f'{self.__class__.__name__}({self.requestName},{self.requestValue})'
                                                           ^^^^^^^^^^^^^^^^^
AttributeError: 'RefreshRequest' object has no attribute 'requestValue'. Did you mean: 'requestName'?

requestName is already set at class member. It seems there is code out
there which is not giving it as value but passing None.
in that case, fallback to the class member.

Fixes: 414ae1d

Fixes: python-ldap#562

cherry-pick bf666e9

…in Python 3.14

fixes resource warnings in Python 3.14

> Ubuntu with Python pypy3.10
> Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Using a locally compiled OpenLDAP impossible without this as libtool
wrappers eat argv[0] of the symlinked binaries.

Using a locally compiled OpenLDAP still often needs changes to the
configuration, this should be a reasonably easy step forward.

and `ReconnectLDAPObject` to be consistent with `initialize()`.

Fixes: 7af3125
Issue: python-ldap#465

Add tests test_valid_attrlist_parameter_types and
test_invalid_attrlist_parameter_types which test the behaviour
when passing different Python types.

All iterables which return only strings should pass, everything else should
raise a TypeError.

Function `PySequence_Length` can return -1 on iterables like `dict`.
The following PyMem_NEW still succeeds due `PyMem_NEW(char *, -1 + 1)`
being equivalent to `char** PyMem_Malloc(1)`, which then can result in a
segmentation fault later on.

Solution: Use `seq` and `PySequence_Size` to determine the size of
the sequence. This way any iterable which contains only strings can be used.

Co-authored-by: Christian Heimes <christian@python.org>