refactor: explicitly import gitlab.const values into top-level namespace

JohnVillalovos · JohnVillalovos · commit ba3b38aaa466 · 2021-11-16T16:43:58.000-08:00
We are planning on adding enumerated constants into gitlab/const.py,
but if we do that than they will end up being added to the top-level
gitlab namespace. We really want to get users to start using
`gitlab.const.` to access the constant values in the future.

Explicitly add the current values defined in gitlab.const into the
top-level namespace and stop using the previous
'from gitlab.const import *' method.
diff --git a/gitlab/__init__.py b/gitlab/__init__.py
@@ -28,7 +28,36 @@
     __version__,
 )
 from gitlab.client import Gitlab, GitlabList  # noqa: F401
-from gitlab.const import *  # noqa: F401,F403
+from gitlab.const import (
+    DEFAULT_URL,
+    DEVELOPER_ACCESS,
+    GUEST_ACCESS,
+    MAINTAINER_ACCESS,
+    MINIMAL_ACCESS,
+    NO_ACCESS,
+    NOTIFICATION_LEVEL_CUSTOM,
+    NOTIFICATION_LEVEL_DISABLED,
+    NOTIFICATION_LEVEL_GLOBAL,
+    NOTIFICATION_LEVEL_MENTION,
+    NOTIFICATION_LEVEL_PARTICIPATING,
+    NOTIFICATION_LEVEL_WATCH,
+    OWNER_ACCESS,
+    REPORTER_ACCESS,
+    SEARCH_SCOPE_BLOBS,
+    SEARCH_SCOPE_COMMITS,
+    SEARCH_SCOPE_GLOBAL_SNIPPET_TITLES,
+    SEARCH_SCOPE_ISSUES,
+    SEARCH_SCOPE_MERGE_REQUESTS,
+    SEARCH_SCOPE_MILESTONES,
+    SEARCH_SCOPE_PROJECT_NOTES,
+    SEARCH_SCOPE_PROJECTS,
+    SEARCH_SCOPE_USERS,
+    SEARCH_SCOPE_WIKI_BLOBS,
+    USER_AGENT,
+    VISIBILITY_INTERNAL,
+    VISIBILITY_PRIVATE,
+    VISIBILITY_PUBLIC,
+)
 from gitlab.exceptions import *  # noqa: F401,F403
 
 warnings.filterwarnings("default", category=DeprecationWarning, module="^gitlab")
