You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These modules should not really be at the top level, they conflict with other people's packages (main one being ldif which is a big source of confusion), add a stub that reexports the same names and have imports trigger a Warning of some sort saying the stubs are going away in 5.0:
_ldap -> ldap._ldap (rename+stub already happening in 3.5)
Activity
spaceone commentedon Sep 16, 2026
What speaks against adding the stubs already in 3.5?
Then a migration path is more easily possible: People can start to use the new variant during the 3.5 lifecycle and are done with it.
mistotebe commentedon Sep 24, 2026
You mean for now to make e.g.
ldap.ldifa stub forldif? I guess we could and then swap them around after 3.5spaceone commentedon Sep 24, 2026
yes.
feat: Introduce ldap.ldif and ldap.url
feat: Introduce ldap.ldif and ldap.url