Add type hints to better understand source

[NicoHood]

I currently try to find out if the between() function can take a date and/or datetime object. I think it can parse both (as that's what I remember I've tested), but I am not sure. Also I do not understand the source with that tuple and int instance checking, thats confusing to me.

Could you please clarify what the accepted inputs of between() are and maybe add this as a typehint?

---

We're using [Polar.sh](https://polar.sh/niccokunzmann) so you can upvote and help fund this issue. We receive the funding once the issue is completed & confirmed by you. Thank you in advance for helping prioritize & fund our work.

[niccokunzmann]

I think, the README file describes which kinds of data structures you can pass to the between function. I did not use type-hints, yet. The motivation behind this is to be able to pass hard-coded arguments fast without needing to put them though a datetime.date or datetime.datetime on the user side.

[NicoHood]

Ah, now I see. I would not do that, but as long as date and datetime works, thats fine for me.

[NicoHood]

I just want to note, that if you input an end date as date it will not be included. What I expect the code to do is to combine that with:

if type(before) is date:
    before = datetime.combine(before, datetime.max.time())
if type(after) is date:
    after = datetime.combine(after, datetime.min.time())

[niccokunzmann]

yes, the end date is excluded. That should be documented this way if I remember correctly.

[niccokunzmann]

It seems that combine is not present.

Python 3.9.5 (default, Nov 23 2021, 15:27:38)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> help("datetime.combine")
No Python documentation found for 'datetime.combine'.

[NicoHood]

https://docs.python.org/3/library/datetime.html#datetime.datetime.combine

[niccokunzmann]

Thanks! I could have thought about that :,)
How would you formulate this issue so that it has closing criteria? Is it "Added type hints to at(), between() and of()"?
Or would be copying over examples from the README into the docstring?

[NicoHood]

I personally would:

• Add typehints to all public functions
• Think if a function should take 5 different types of variables, or if date|datetime isn't already enough
• Documenting the private function would also help you to build clearer and better understandable source code.

[NicoHood]

And I have to correct myself:

        if type(start) is date:
            start = datetime.combine(start, datetime.min.time())
        if type(end) is date:
            end = datetime.combine(end + timedelta(days=1), datetime.min.time())

Is better

[niccokunzmann]

Hm. I just saw this example concerning py.typed: https://github-redirect.dependabot.com/certifi/python-certifi/issues/196 That reminded me of this issue.

[niccokunzmann]

If someone likes to add type hints, this is welcome. I will support that but not do it myself at the moment.

[NicoHood]

Why? It is so much easier to understand your own code. At least for newer code this should be done. You can also then do typechecks using pylance in vscode.

[niccokunzmann]

I do it in my free time, I do not get paid and I do not see the value. Other people see value, have time. I am more in survival mode at the moment. When a basic income is secured I can gift my time. Yes, it might take me less time and it would be efficient if I did it and I would learn but under the circumstances, I choose to work on other issues.