Hi@torresjrjr
Thanks for making this PR, and our excuse for not responding sooner.
I like the addition and the idea behind it, but I would like to see you add some tests reflecting the changes.

Could you add those please?

Actually, I like to open this for discussion with the other maintainers.
IMHO, servers should run on UTC . Timezones add so many questions and problems.
My vote is not to add this code to the library.

@tsnoam the point they make in the issue, is that sometimes you want to userun_daily for the user-aware timezone. This PR makes it possible to say:
Run daily on timezone +5 and it will convert to UTC to put in the job_queue.
It assumes the server on UTC and makes it easier to add jobs for all timezones without the hassle of calculating the timedelta manually or program it in every bot

Well, that's a subset of what a timezone is.
A timezone can also be "Asia/Jerusalem". Now go and map between summer and winter clock. Or, if you're on the edge of switching between them, switch.
Not to mention countries which change their decision when to move between summer & winter clock every year.
I prefer not to "put a healthy head inside a sick bed".

Actually, I'm not so invested in this PR as much, since this was an attempt at a solution to a problem I later solved. I wanted to "help my bot to be hosted on a server with any timezone without complications" but I ended up simply adding an extra step in my code.

I created atimedelta object of the time fromnow() to thedatetime, and submitted that to my job creations. It's a quick solution others might find useful :) and could be used in the final PR in the.put() method.

I should also stress that I'm a python noob/intermediate. I find PRs scary. So please, take my idea and do what you will. Thanks.

We were debating whether this should be a here, in helpers or in the programmers hands. I guess you helped us answering that. I'm closing this PR.