Ben Greiner

> With [this patch](https://github.com/eventlet/eventlet/files/5076724/newdnspython.patch.txt) I am able to run the testsuite and it breaks only on 8 errors: Not really, It breaks during collection on 8 errors. No tests are...

> We can finally use stable something and not worry about dependency updates. **stable != unmaintained** Nose is outdated. Period. The very first section of its [website](https://nose.readthedocs.io/en/latest/) reads: > Nose...

It's a result of https://github.com/PyCQA/isort/blob/44e3b5d179da5033ce23f796b014e74f3a3259cd/example_isort_sorting_plugin/pyproject.toml#L13 which would work with natsort 8. So if you unpin, do it there and recreate the poetry.lock

Yes, of course. We stumbled over it, because openSUSE like many other distributions have a policy to check python packages through their unit tests. When someone updated natsort to version...

Seeing the same on rpmbuild for openSUSE: [skbuild-log.txt](https://github.com/scikit-build/scikit-build/files/8599866/skbuild-log.txt)

FTR, we still see this in scikit-build 0.15.0, preventing us to update from a working 0.13.1

``` docker run -it opensuse/tumbleweed ``` ``` zypper install tar gzip gcc-c++ gcc-fortran git-core ninja python3-devel python3-setuptools python3-setuptools_scm cmake python3-Cython python3-build python3-distro python3-flake8 python3-mock python3-path.py python3-pip python3-pytest python3-pytest-mock python3-pytest-virtualenv python3-requests...

Any news here?

Can confirm that the sdist errors go away with setuptools-scm uninstalled. Too bad that scikit-build requires it to build itself.

During my own investigations yesterday I stumbled across this discussion: #506