From: 
Subject: Debian changes

The Debian packaging of python-zamg is maintained in git, using a workflow
similar to the one described in dgit-maint-merge(7).
The Debian delta is represented by this one combined patch; there isn't a
patch queue that can be represented as a quilt series.

A detailed breakdown of the changes is available from their canonical
representation -- git commits in the packaging repository.
For example, to see the changes made by the Debian maintainer in the first
upload of upstream version 1.2.3, you could use:

    % git clone https://git.dgit.debian.org/python-zamg
    % cd python-zamg
    % git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian'

(If you have dgit, use `dgit clone python-zamg`, rather than plain `git clone`.)

We don't use debian/source/options single-debian-patch because it has bugs.
Therefore, NMUs etc. may nevertheless have made additional patches.

---

diff --git a/tests/test_zamg.py b/tests/test_zamg.py
index 3a1a2fa..7fcf6ba 100644
--- a/tests/test_zamg.py
+++ b/tests/test_zamg.py
@@ -8,13 +8,13 @@ import aiohttp
 import pytest
 from aiohttp.client_exceptions import ServerTimeoutError
 
-from src.zamg.exceptions import (
+from zamg.exceptions import (
     ZamgApiError,
     ZamgNoDataError,
     ZamgStationNotFoundError,
     ZamgStationUnknownError,
 )
-from src.zamg.zamg import ZamgData
+from zamg.zamg import ZamgData
 
 
 @pytest.mark.asyncio
