Tomasz Kłoczko
Tomasz Kłoczko
setuptools `install` command automatically install in correct place `.egg.info` ```console + /usr/bin/python3 setup.py install -O1 --skip-build --root /home/tkloczko/rpmbuild/BUILDROOT/python-anyio-3.3.4-2.fc35.x86_64 running install running install_lib creating /home/tkloczko/rpmbuild/BUILDROOT/python-anyio-3.3.4-2.fc35.x86_64/usr creating /home/tkloczko/rpmbuild/BUILDROOT/python-anyio-3.3.4-2.fc35.x86_64/usr/lib creating /home/tkloczko/rpmbuild/BUILDROOT/python-anyio-3.3.4-2.fc35.x86_64/usr/lib/python3.8 creating /home/tkloczko/rpmbuild/BUILDROOT/python-anyio-3.3.4-2.fc35.x86_64/usr/lib/python3.8/site-packages...
I'm trying to package your module as an rpm package. So I'm using the typical build, install and test cycle used on building packages from non-root account. - "setup.py build"...
> So do you install all the dependencies manually via RPM or DNF? Yes ad here is liest of BuildRequires from mysopec file: ```spec BuildRequires: python3dist(setuptools-scm) BuildRequires: python3dist(sphinx) BuildRequires: python3dist(sphinx-autodoc-typehints)...
`pytest-mock` is in the dependencies (indirectly). ```[tkloczko@ss-desktop SPECS]$ rpm -q python-pytest-mock python-pytest-mock-3.6.1-4.g2v.noarch ```
Just joined
Just tested 3.4.0 ```console + /usr/bin/pytest -ra =========================================================================== test session starts ============================================================================ platform linux -- Python 3.8.12, pytest-6.2.5, py-1.10.0, pluggy-0.13.1 rootdir: /home/tkloczko/rpmbuild/BUILD/anyio-3.4.0, configfile: pyproject.toml, testpaths: tests plugins: anyio-3.4.0, shutil-1.7.0, virtualenv-1.7.0,...
You can just disable ipv6 stack and run test suite.
Nope and as I'm busy now will do test later or my automation will try do that when next release will ba tagged.
Python 2.x is already EOSed +1.5y. IIRC none of the even oldest moduels are removed from PyPI. > I'm not sure how you got into that situation because the package...
> If you want to submit a patch that wraps `import unittest2` in a `try`/`except ImportError` in the tests, would that work? I'm not familiar with how the packaging situation...