> OK. But if we do this, we will probably forget when enabling python
> (which is a nice to have)
What do you mean by that, forget what? If python is ever enabled (why
isn't it, btw?), then just remove `--disable-python` and add back the
build-depends, no? You will also have to create new binary packages
for the python modules, so it's not just a small `./configure` command
line change that is needed.
The reason why only the static library has the python symbols seems to
come from this bit in d/rules:
```
override_dh_auto_install:
$(MAKE) install DESTDIR=$(DESTDIR)
ar cr libtevent.a bin/default/*.o
cp libtevent.a $(DESTDIR)/usr/lib/$(DEB_HOST_MULTIARCH)
```
That `*.o` globbing is including `pytevent*.o`. Why is the package
creating the static library by hand, do you know? Why is the static
library even needed?
When you say "what about removing libtevent.a", do you mean remove
that bit above after the make install? Or are there further
consequences, perhaps to other packages which depend on it, and that's
the whole reason the static library was created manually to begin
with?
