From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Joshua Watt <jpewhacker@gmail.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: bitbake/lib/hashserv/sqlite.py:294: DeprecationWarning: The default datetime adapter is deprecated as of Python 3.12
Date: Mon, 1 Jan 2024 19:30:43 +0100 [thread overview]
Message-ID: <CANNYZj89yvc0EPJL0iJVPY-XPFSfsgiUm4U87rW-kq2fAjSO-Q@mail.gmail.com> (raw)
In-Reply-To: <CAJdd5GbWTeo9FSd_uE2Z0oaXv9M38e94EOq8jFJJu+7JOG6yRQ@mail.gmail.com>
Here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15333
Alex
On Sun, 31 Dec 2023 at 17:13, Joshua Watt <jpewhacker@gmail.com> wrote:
>
> Ah, I suspect they want you to register an explicit converter instead of relying on the default. I don't think that should be too hard to do. Would you be able to open a bug and assign it to me? I won't have computer access for a few days
>
> On Sun, Dec 31, 2023, 2:39 AM Alexander Kanavin <alex.kanavin@gmail.com> wrote:
>>
>> Hello Joshua,
>>
>> I'm seeing this with python 3.12:
>>
>> /srv/work/alex/poky/bitbake/lib/hashserv/sqlite.py:294:
>> DeprecationWarning: The default datetime adapter is deprecated as of
>> Python 3.12; see the sqlite3 documentation for suggested replacement
>> recipes
>> cursor.execute(query, data)
>>
>> The documentation that is supposed to help (but doesn't, not for me :) is:
>> https://docs.python.org/3/library/sqlite3.html#default-adapters-and-converters-deprecated
>>
>> Just thought it would be good to address this warning well in advance
>> of it becoming a hard error.
>>
>> Alex
prev parent reply other threads:[~2024-01-01 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 9:39 bitbake/lib/hashserv/sqlite.py:294: DeprecationWarning: The default datetime adapter is deprecated as of Python 3.12 Alexander Kanavin
2023-12-31 16:13 ` Joshua Watt
2024-01-01 18:30 ` Alexander Kanavin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANNYZj89yvc0EPJL0iJVPY-XPFSfsgiUm4U87rW-kq2fAjSO-Q@mail.gmail.com \
--to=alex.kanavin@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=jpewhacker@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).