Bug#1071007: Update available upstream

Hey all Upstream has been bumped to 0.15.0, and with this, the importable module has been renamed from `sherlock` to `sherlock_project`. Repackaging should allow both Serious bugs to be closed. As indicated in the prior... With this, upstream has also moved to adopt properly tagged releases,

Bug#1071007: Sherlock bug update

We are planning to bump to 0.15.0 to coordinate merges for all our planned breaking changes at once With this, the importable module's name will be changed, avoiding conflict. I've proposed sherlock_project to match pypi and the egg, as Thomas recommended. We also plan to adopt proper tagged

Bug#1072733: Sherlock package name

Any opposition to naming the importable package `sherlocklib`? The installable package (via apt) would presumably remain `sherlock` The importable module (via python) would become `sherlocklib` The binary exec would remain `sherlock`

Bug#1071007:

When building the rpm, I named the (rpm) package sherlock-project to have parity with PyPI, due to the same conflicting package. The importable module is still simply sherlock, however, which is _less than ideal_, and should probably be addressed. With this discussion now being had on the deb

Bug#1071007:

Hey all Thanks for your patience. Life gets a bit busy sometimes. I've just merged #2127 [1] upstream, switching Sherlock from setup-tools to Poetry, from unittest to pytest, and adding tox. With this, the site-/dist-packages dir is no longer dirtied. This bug **should** be resolved with the new

Bug#1071007:

All -- ::: Re: 1071007, ALL CONCERNED ::: I am associated with the upstream project. This is a real bug. Discovered it some time last week. This seems to have been introduced when we added the new pyproject file with a setuptools backend. For some unknown reason, the installed package would