You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my Windows 10, after fresh repository update and debug build, 3.10 sqlite3 tests do not run.
(3.11 and 3.12 are fine.) In 3.10, test_sqlite/ only contains test_dbapi.py
python -m test test_sqlite3 is OK after no tests run. (I though we made this an error.) python -m test.test_sqlite3 fails because test_sqlite3/ is missing __main__.py, as well as __init__.py
In 3.11, test_sqlite3.__main__.py is
from test.test_sqlite3 import load_tests # Needed for the "load tests" protocol.
import unittest
if __name__ == "__main__":
unittest.main()
The comment seems not needed. The other 3.10 test.test_x directories all run and have variations of this. Some have from . import load_tests. Some have unittest.main('test.test_x') instead of a load_tests import. Most omit the redundant if-clause.
After adding __main__.py, tests still do not run because __init__.py is needed. I may try to do a PR tomorrow.
On my Windows 10, after fresh repository update and debug build, 3.10 sqlite3 tests do not run.
(3.11 and 3.12 are fine.) In 3.10,
test_sqlite/only containstest_dbapi.pypython -m test test_sqlite3is OK after no tests run. (I though we made this an error.)python -m test.test_sqlite3fails because test_sqlite3/ is missing__main__.py, as well as__init__.pyIn 3.11,
test_sqlite3.__main__.pyisThe comment seems not needed. The other 3.10 test.test_x directories all run and have variations of this. Some have
from . import load_tests. Some haveunittest.main('test.test_x')instead of a load_tests import. Most omit the redundant if-clause.After adding
__main__.py, tests still do not run because__init__.pyis needed. I may try to do a PR tomorrow.