Unicode Chars in UTF8 instead of Latin1

I am using since today Libretime version 3.1.0 on a Debian 11 server.

I am facing a problem that we use UTF8 and Libretime is using “Latin1” internaly.
I noticed this error in the playout.log:

2023-07-15 21:08:22,868 | ERROR    | libretime_playout.history.stats:run:157 - 'latin-1' codec can't encode character '\u20ac' in position 4: ordinal not                                     in range(256)
Traceback (most recent call last):
  File "/opt/libretime/lib/python3.9/site-packages/libretime_playout/history/stats.py", line 155, in run
  File "/opt/libretime/lib/python3.9/site-packages/libretime_playout/history/stats.py", line 112, in collect
    cache[output_url] = self.collect_output_stats(output)
  File "/opt/libretime/lib/python3.9/site-packages/libretime_playout/history/stats.py", line 48, in collect_output_stats
    response = self._session.get(
  File "/opt/libretime/lib/python3.9/site-packages/requests/sessions.py", line 602, in get
    return self.request("GET", url, **kwargs)
  File "/opt/libretime/lib/python3.9/site-packages/requests/sessions.py", line 575, in request
    prep = self.prepare_request(req)
  File "/opt/libretime/lib/python3.9/site-packages/requests/sessions.py", line 486, in prepare_request
  File "/opt/libretime/lib/python3.9/site-packages/requests/models.py", line 372, in prepare
    self.prepare_auth(auth, url)
  File "/opt/libretime/lib/python3.9/site-packages/requests/models.py", line 603, in prepare_auth
    r = auth(self)
  File "/opt/libretime/lib/python3.9/site-packages/requests/auth.py", line 95, in __call__
    r.headers["Authorization"] = _basic_auth_str(self.username, self.password)
  File "/opt/libretime/lib/python3.9/site-packages/requests/auth.py", line 60, in _basic_auth_str
    password = password.encode("latin1")

I guess this is also the problem for the Icecast streams since there are special characters in the password. The streams are working but Libretime is not able to get the stats.
I have also noticed that this problem was already there in 2020. Is there a github bug for this item?

3.1.0 is working just fine, keep up the fantastic work!