This patch adds `Collection.count_search_results()` method which
counts results from a search.

It's much faster than count `get_all_search_results()`, as we avoid
to create Entry instances for every results.

On a collection with 264 items, doing a search for '+', counting
all results with

    len(list(collection.get_all_search_results()))

takes ~930 ms on my system, while

    collection.count_search_results()
[message trimmed]

running

	lesana search -e <query>


(with `query` having or not any template var in it) results in:

Traceback (most recent call last):
  File "scripts/lesana", line 39, in <module>
    Lesana().main()
  File "lesana/command.py", line 55, in main
    self.args.func(self.args)
  File "/lesana/command.py", line 65, in _main
    self.main()

- ignore libraries without typing info
- add `py.typed` marker file
- update .gitignore
---
 .gitignore           | 5 +++++
 lesana/collection.py | 2 +-
 lesana/command.py    | 2 +-
 lesana/py.typed      | 0
 lesana/types.py      | 2 +-
 setup.py             | 2 +-
 6 files changed, 9 insertions(+), 4 deletions(-)
 create mode 100644 lesana/py.typed

diff --git a/.gitignore b/.gitignore

---
 setup.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/setup.py b/setup.py
index abda1b7..2545196 100644
--- a/setup.py
+++ b/setup.py
@@ -13,7 +13,7 @@ setup(
     packages=find_packages(),
     scripts=['scripts/lesana'],
     package_data={
-        '': ['*.yaml']
+        '': ['*.yaml', 'post-checkout']
[message trimmed]

Package in AUR has been updated to 0.9.0

https://aur.archlinux.org/packages/lesana/

Nothing really new, here.
It's all about visual changes to addres issues in
https://gitlab.gnome.org/Teams/Circle/-/issues/73

Updated in AUR, waiting for flathub to update.

when using lesana as a library, having a per-module logger is better
instead of logging everything in root.

When `lesana` cli command is used, logger is configured to print simple
logline and loglevel is set to INFO, unless user pass the option `-v` or
`--verbose` which sets the level to DEBUG
---
Set loglevel as a library makes no sense...

 lesana/collection.py | 34 ++++++++++++++++++----------------
 lesana/command.py    | 40 ++++++++++++++++++++++++----------------
 lesana/types.py      |  9 +++++----
 scripts/lesana       | 11 ++++++++++-
 4 files changed, 57 insertions(+), 37 deletions(-)
[message trimmed]

when using lesana as a library, having a per-module logger is better
instead of logging everything in root.
An env var `LESANA_LOGLEVEL` is used to set logging level for the
library.

When `lesana` cli command is used, logger is configured to print simple
logline and loglevel is set to INFO, unless user pass the option `-v` or
`--verbose` which sets the level to DEBUG
---
 lesana/__init__.py   |  8 ++++++++
 lesana/collection.py | 34 ++++++++++++++++++----------------
 lesana/command.py    | 40 ++++++++++++++++++++++++----------------
 lesana/types.py      |  9 +++++----
 scripts/lesana       | 11 ++++++++++-
[message trimmed]

---
 lesana/types.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lesana/types.py b/lesana/types.py
index 6e5d21d..677fbdf 100644
--- a/lesana/types.py
+++ b/lesana/types.py
@@ -278,7 +278,7 @@ class LesanaDate(LesanaType):
         # compatibility with dateutil before 2.8
         ParserError = getattr(dateutil.parser, 'ParserError', ValueError)
         try:
-            return dateutil.parser.parse(data)
+            return dateutil.parser.parse(data).date()
[message trimmed]

Merged!
Thank you!