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
TypeError: can't compare datetime.datetime to NoneType #125
Comments
@adtrombley Can you give some more info on what lines of code came before the |
I'm using python 2.7, this must be the problem.
…On Fri, Jan 13, 2017 at 5:40 AM, Daniel Bader ***@***.***> wrote:
@adtrombley <https://github.com/adtrombley> Can you give some more info
on what lines of code came before the run_pending() call? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#125 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACU-QM2DLBwUrAUQQ1OdRbEvfiTSFGSOks5rR37KgaJpZM4LiPhP>
.
--
regards,
Austin D. Trombley, MBA
CTO - Random Forest Capital, LLC
cell: 415-767-6179
|
@adtrombley Mmh... This should work fine on 2.7 and 3.X. I'll need some more context to be able to help you out though :) |
I've also encountered this error.
The issue would mainly hit those who just wants to play with the module in a python shell. |
I'm also getting this error using an ipython notebook. I am following the example. It does work, however, if you restart the kernel/shell |
Thanks @KennyRIM, will look into this. I'm not sure when I'll be able to get to it, so if anyone want's to get started with a PR fix I'd appreciate it. |
IPython runs
the only way I was able to reproduce op's traceback is by incorrect use of
traceback:
quick fix would be to check for job initialization before run:
and maybe do the same in fix proposal: |
I think I'm getting something similar:
I assume it's from trying to run the scheduler without having any jobs configured. |
Will be fixed in the next release now that #143 is merged. |
Hi @dbader |
Has been released as part of 0.5.0 on nov 16, 2017 |
Hi @dbader , I had the below error for Schedule 1.1.0 which seems to be the same bug but not sure.
I can't share the full code but its essentially scheduling two different function which each run some API's calls (REST/SOAP) and store the results to MySQL. One runs every minute and one runs every day. Looking a the logs, the scheduler for the every minute tasks kept running about 30 times before it stopped suddenly. The fatal error is the only clue I was able to find.
I am updating to schedule 1.2 and hopefully it resolved the issue. |
I ran your example, and I got the following error -->
The text was updated successfully, but these errors were encountered: