Skip to content

rename and deprecate top-level modules #640

Open

Description

@mistotebe

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)
  • ldif -> ldap.ldif
  • ldapurl -> ldap.url

And update the documentation to match.

Activity

  1. added this to the 4.0 milestone on Sep 8, 2026
  2. spaceone commented on Sep 16, 2026

    @spaceone
    Contributor

    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.

  3. mistotebe commented on Sep 24, 2026

    @mistotebe
    ContributorAuthor

    You mean for now to make e.g. ldap.ldif a stub for ldif? I guess we could and then swap them around after 3.5

  4. spaceone commented on Sep 24, 2026

    @spaceone
    Contributor

    yes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions