Skip to content
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

[QUESTION] JobQueue warning message still present #4008

Closed
intersecato opened this issue Dec 13, 2023 · 1 comment
Closed

[QUESTION] JobQueue warning message still present #4008

intersecato opened this issue Dec 13, 2023 · 1 comment
Labels

Comments

@intersecato
Copy link

intersecato commented Dec 13, 2023

Issue I am facing

In version 20.7 I still see the warning message that warns of the alignment of the days parameter in JobQueue with cron. In this regard, I had read about a pull request (#3046) in which it was specified that it was a message that would be removed in the following version, but it is still present. I don't know if it's intentional or if there is a way to hide it, it's starting to bother me.

Also this commit (97697ee) I think it was done to remember it

Traceback to the issue

PTBUserWarning: Prior to v20.0 the `days` parameter was not aligned to that of cron's weekday scheme. We recommend double checking if the passed value is correct.

Related part of your code

No response

Operating System

Linux

Version of Python, python-telegram-bot & dependencies

python-telegram-bot 20.7
Bot API 6.9
Python 3.12.0
@Bibo-Joshi
Copy link
Member

Hi. What this comment says is that the warning should be removed on the next major version, i.e. v21. Since PTB is using Pythons standart warnings module, warnings can also be ignored via Pythons standard features. We give a short primer on this on this wiki page which should help ease your sore eye ;)

@github-actions github-actions bot locked and limited conversation to collaborators Dec 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants