Skip to content

fix: remove debug print statement and improve error handling in yolo_mapping.py #1221

@ajithhraj

Description

@ajithhraj

yolo_mapping.py has two problems:

  • Contains a debug print(os.getcwd()) statement that should not be in production code
  • db_create_YOLO_classes_table has no exception handling — if SQLite fails, the error is silent

Proposed fix

  • Remove the debug print and unused import os
  • Add sqlite3.Error exception handling with proper logging
  • Add success log message

I'd like to fix this if maintainers agree.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions