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!

Il giorno lun, 14/06/2021 alle 02.18 +0200, Evangelos Ribeiro Tzaras ha
scritto:
> --- a/src/pages.py
> +++ b/src/pages.py
> @@ -506,8 +506,14 @@ class EventDetailPage(BasePage):
>          w = self.get_allocated_width()
>  
>          dur = (obj.end.timestamp() - obj.start.timestamp())
> -        pos = (now.timestamp() - obj.start.timestamp())
> -        prc = min(max(pos/dur, 0.0), 1.0)
> +        if dur > 0:
> +            pos = (now.timestamp() - obj.start.timestamp())

If you move pos inside this branch...

Il giorno dom, 13/06/2021 alle 02.38 +0200, Evangelos Ribeiro Tzaras ha
scritto:
> 
> +        prc = min(max(pos/dur, 0.0), 1.0) if dur > 0 else int(pos >=
> 0)

While it's correct (and more correct than the code I was writting to
fix this), it's a little to difficult to read.
I would prefer an explicit if/else, with some comments, something like

```
if dur > 0:
	prc = min(max(pos/dur, 0.0), 1.0)
else:

Merged,

thought I'm not so strict with whitespaces :)

Confy 0.6.0 has been released

see changes here https://git.sr.ht/~fabrixxm/confy/refs/0.6.0

ArchLinux AUR package is updated
https://aur.archlinux.org/packages/confy/

Flatpak package is scheduled
https://flathub.org/apps/details/net.kirgroup.confy

Merged! Thank you!