-
Notifications
You must be signed in to change notification settings - Fork 19
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
Correct data type of start date #22
Comments
Can you provide the code that is able to reproduce the error? |
I think that I mixed up two problems which give me the same error above. 🙈 The first problem is that it does not work to pass the start date as a
When I give the start date as a str like The second problem is that I get the above error message if I omit the
Passing the mode is optional and it is therefore clear that I have to pass the argument as |
Yeah, that is the problem when the first argument is optional. Let me think about whether I should enforce keyword argument. |
I have added keyword argument for date. You will need to pass in |
When I try to generate example roadmaps, I sometimes get the error message
TypeError: strptime() argument 1 must be str, not datetime.datetime
for the methodset_timeline
. However, I pass the argument of the start date as"2023-01-01"
, which should be a string. Naming the argument (start="2023-01-01"
) often seems to work.The issue is that method expects a
datetime
while it seems to be okay (and common) to pass it astr
. If I look through the source code, the argument is usually passed as astr
(while the method expects adatetime
). To introduce some more consistency, the expected value should be astr
which will then be transformed to adatetime
internally.The text was updated successfully, but these errors were encountered: