Just stumbled on this. JobQueue.put seems to be gone since some 5 years … Anyway, if you have access to a job, then you also have access to either the JobQueue directly or at least a CallbackContext instance, which already contains the job_queue, so IMO there is no need to keep this double reference alive (job_queue contains job, contains job_queue)

Checklist for PRs

• Added .. versionadded:: version, .. versionchanged:: version or .. deprecated:: version to the docstrings for user facing changes (for methods/class descriptions, arguments and attributes)
• Created new or adapted existing unit tests

Breaking changes:

• the title