refactor: use absolute imports
Summary
feeler for whether absolute imports is worth it
Documentation build overview
📚 disnake | 🛠️ Build #30032265 | 📁 Comparing 344f67d9e596189a348ce339443712c0b2b73a0f against latest (7c3b4f031493606ae0919b9555f8289760d9bdab)
Show files changed (48 files in total): 📝 48 modified | ➕ 0 added | ➖ 0 deleted
(also, for reference: https://github.com/DisnakeDev/disnake/pull/951)
+1 from me, in any case
(also, for reference: https://github.com/DisnakeDev/disnake/pull/951)
In disnake.ext.*, imports from the main lib and ext previously were visually separated (by virtue of using absolute imports for the former); the new order is confusing
disnake.ext can be configured as forced separate, or we can configure custom import groups and order
(also, for reference: #951)
In disnake.ext.*, imports from the main lib and ext previously were visually separated (by virtue of using absolute imports for the former); the new order is confusing
disnake.extcan be configured as forced separate, or we can configure custom import groups and order
Already did that :smile:
Fyi, there's also a python.analysis.importFormat pylance setting that controls how pylance auto-imports stuff, but it is set to "absolute" by default