Fix bugs with datetime objects and strings

[meatballs]

No description provided.

[drvinceknight]

Is the bug here that we were writing them as date time objects but the way we do this is to only take strings as inputs? (Just checking I understand :))

[meatballs]

Yep. That was exactly the problem. If you pass the events and slots lists from the howto into the scheduler, it all falls over!

[meatballs]

I may have a look at doing that datetime stuff in a smarter fashion but at least for now, it's correct!

[drvinceknight]

I may have a look at doing that datetime stuff in a smarter fashion but at least for now, it's correct!

Instead of a string we could take a datetime as input (so the way you had it here would be correct)? That makes things simpler on the library's side? The user just needs to create the datetime objects?

[meatballs]

I think so, but part of me was reluctant to go to version 3.0.0 just for that. silly really