Skip to content

fix: move from __future__ import to top of did_agent_extension.py#511

Closed
Subhajitdas99 wants to merge 2 commits intoGetBindu:mainfrom
Subhajitdas99:fix/did-future-import-order
Closed

fix: move from __future__ import to top of did_agent_extension.py#511
Subhajitdas99 wants to merge 2 commits intoGetBindu:mainfrom
Subhajitdas99:fix/did-future-import-order

Conversation

@Subhajitdas99
Copy link
Copy Markdown
Contributor

Summary

  • Problem: from __future__ import annotations was placed after import os and import platform in did_agent_extension.py, causing a SyntaxError at import time.
  • Why it matters: This SyntaxError breaks ALL unit tests across the entire repo — any test that imports from bindu.server fails because the import chain reaches did_agent_extension.py.
  • What changed: Moved from __future__ import annotations to line 28 — immediately after the module docstring, before all other imports. This is required by Python.
  • What did NOT change: No logic changes. One line moved.

Change Type

  • Bug fix

Scope

  • Extensions (DID, x402, etc.)

Impact

This single fix unblocks CI for all open PRs that were showing unit test failures due to this SyntaxError.

Checklist

  • Verified locally: from bindu.extensions.did.did_agent_extension import DIDAgentExtension imports cleanly
  • No logic changes — purely import order fix
  • Backward compatible

from __future__ import annotations must appear before all other imports.
It was placed after import os and import platform, causing SyntaxError
at import time and breaking all unit tests across the repo.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants