New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python 3.10.0a7 test_history:test_timestamp_type fails #12906
Comments
Ok, now I know how to reproduce the issue in pure Python - the converters from dbapi2 have to be enabled manually:
The question still is what is the pure return value from sqlite which the converter tries to parse. |
The answer is: the value converter gets to parse the timestamp is an empty bytestring:
|
I think this is an error in Python so I'm gonna report it. |
Bug report: https://bugs.python.org/issue43831 In the end, it turned out that the problem is in the |
Note to self: the original BPO issue is in stage: patch review. |
@frenzymadness looks like the BPO ticket is fixed. Could you please confirm? |
@MrMino @frenzymadness The PR has been merged. Please let us know if you still see the error on the latest branch of CPython. |
I've tried to run the tests but the pytest is not compatible with the latest Python :( pytest-dev/pytest#8539 |
pytest is fixed now so with pytest from its master branch:
This issue can be closed, thank you! |
Thanks @frenzymadness ! |
We are trying to test IPython with the latest Python 3.10.0a7 on Fedora and one test fails. I'm trying to debug it but I'm not able to reproduce it yet.
The original traceback is:
If I pause the test and try to investigate the database, everything looks fine (
lsof
shows me where the file is):I've tried to create the same table in the new database and open it directly in Python, and everything works:
convert_timestamp converter in dbapi2 is there untouched for many years. I've also tried to reproduce the issue with an older sqlite and everything behaves the same.
The text was updated successfully, but these errors were encountered: