fix: resolve circular import by renaming aitbc.logging module
All checks were successful
audit / audit (push) Has been skipped
ci-cd / build (push) Has been skipped
ci / build (push) Has been skipped
autofix / fix (push) Has been skipped
python-tests / test (push) Successful in 20s
python-tests / test-specific (push) Has been skipped
security-scanning / audit (push) Has been skipped
test / test (push) Has been skipped
ci-cd / deploy (push) Has been skipped
ci / deploy (push) Has been skipped
All checks were successful
audit / audit (push) Has been skipped
ci-cd / build (push) Has been skipped
ci / build (push) Has been skipped
autofix / fix (push) Has been skipped
python-tests / test (push) Successful in 20s
python-tests / test-specific (push) Has been skipped
security-scanning / audit (push) Has been skipped
test / test (push) Has been skipped
ci-cd / deploy (push) Has been skipped
ci / deploy (push) Has been skipped
CIRCULAR IMPORT FIX: Avoid conflict with Python built-in logging Issue: - aitbc/logging.py conflicts with Python's built-in logging module - Circular import when pip tries to import logging - AttributeError: partially initialized module 'logging' has no attribute 'Logger' Solution: - Rename aitbc/logging.py to aitbc/aitbc_logging.py - Update aitbc/__init__.py to import from renamed module - Maintains same API (get_logger, setup_logger) - Avoids naming conflict with built-in logging Expected results: - No more circular import errors - pip should work properly - aitbc.logging imports should still work - Test workflow should proceed to execution This resolves the circular import that was blocking pip and preventing the test workflow from running.
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
AITBC Package
|
||||
"""
|
||||
|
||||
from .logging import get_logger, setup_logger
|
||||
from .aitbc_logging import get_logger, setup_logger
|
||||
|
||||
__version__ = "0.2.0"
|
||||
__all__ = ["get_logger", "setup_logger"]
|
||||
|
||||
Reference in New Issue
Block a user