ModuleNotFoundError: No module named 'mysql_to_sqlite3' #104
Description
Describe the bug
Whilst upgrading to mysql2sqlite from 2.4.2 to 2.4.3 usage now throws an exception on all usage claiming mysql_to_sqlite3 can not be found.
Expected behaviour
It should not do that?
Actual result
$ mysql2sqlite --version
Traceback (most recent call last):
File "/opt/homebrew/bin/mysql2sqlite", line 5, in <module>
from mysql_to_sqlite3.cli import cli
ModuleNotFoundError: No module named 'mysql_to_sqlite3'
System Information
Have tested this locally on macos 15.6.1 and our ubuntu 24 workflow runners.
$ mysql2sqlite --versionmacos
Traceback (most recent call last):
File "/opt/homebrew/bin/mysql2sqlite", line 5, in <module>
from mysql_to_sqlite3.cli import cli
ModuleNotFoundError: No module named 'mysql_to_sqlite3'
our own internal aws ubuntu 24 runners
Traceback (most recent call last):
File "/opt/actions-runner/_work/_tool/Python/3.13.7/x64/bin/mysql2sqlite", line 3, in <module>
from mysql_to_sqlite3.cli import cli
ModuleNotFoundError: No module named 'mysql_to_sqlite3'
This command is only available on v1.3.2 and greater. Otherwise, please provide some basic information about your system (Python version, operating system, etc.).
Additional context
Add any other context about the problem here.
- We have locked ourselfs to using 2.4.2 and this is functioning fine.
- We suspect the issue is related to this specific change and the functionality is throwing an internal not found.