Skip to content

Conversation

@thomasgoirand
Copy link

Currently, q is using datetime.datetime.utcnow(). Unfortunately, this produces a big warning in Python 3.12, which makes q not really useable anymore. This warning also breaks all unit tests.

This patch fixes this by using datetime.datetime.now() instead.

Currently, q is using datetime.datetime.utcnow(). Unfortunately,
this produces a big warning in Python 3.12, which makes q not
really useable anymore. This warning also breaks all unit tests.

This patch fixes this by using datetime.datetime.now() instead.
@tgandor
Copy link

tgandor commented Nov 3, 2025

It's true. After installation I generate my .qrc, and then go to /usr/bin/q and do a string replace from utcnow to now (ignoring the timezone, but the program mostly still works ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants