Skip to content

Conversation

@guitargeek
Copy link
Contributor

Using relative imports is better, because we can freely change the names of modules without having to update hardcoded import paths.

@guitargeek guitargeek self-assigned this Feb 5, 2026
@guitargeek guitargeek force-pushed the relative_imports branch 6 times, most recently from c8a0ee5 to f484533 Compare February 5, 2026 12:43
@github-actions
Copy link

github-actions bot commented Feb 5, 2026

Test Results

    22 files      22 suites   3d 16h 53m 51s ⏱️
 3 776 tests  3 776 ✅ 0 💤 0 ❌
75 119 runs  75 119 ✅ 0 💤 0 ❌

Results for commit 087a33a.

♻️ This comment has been updated with latest results.

It's better to explicitly check if the dependencies are avaialble rather
than barring whole code sections behind a `try-except ImportError`.
Otherwise, we're not letting surface other import errors in our own
code, making them difficult to debug.
Make sure the context destructor is called: don't rely on Python garbage
collection. This was spotted by a ruff unused variable warning.
Using relative imports is better, because we can freely change the names
of modules without having to update hardcoded import paths.
@guitargeek guitargeek force-pushed the relative_imports branch 2 times, most recently from 8fcd2c8 to feb5d20 Compare February 5, 2026 15:30
Copy link
Member

@vepadulano vepadulano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't agree that using relative imports it's better, it's a choice. But I'm not opposed to the changes per se.

@guitargeek guitargeek merged commit 647bf1a into root-project:master Feb 5, 2026
30 checks passed
@guitargeek guitargeek deleted the relative_imports branch February 5, 2026 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants