From: ar-jan <ar-jan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-aiohttp_socks: update to 0.8.3 and add required dependencies
Date: Tue, 17 Oct 2023 00:18:33 +0200 [thread overview]
Message-ID: <20231016221833.iRkb-JUufHSq1FYHlQW3_1ZxncX3WekU5-5OlV4Tm98@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46383@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]
New comment by ar-jan on void-packages repository
https://github.com/void-linux/void-packages/pull/46383#issuecomment-1765361747
Comment:
OK, I've removed these new dependencies:
> New package: python3-httpx-socks-0.7.8
> New package: python3-tiny-proxy-0.2.0
> New package: python3-re_assert-1.1.0
> New package: python3-proxy.py-2.4.3
But python3-aiosignal is required for python3-aiohttp, and depends on python3-frozenlist (not just for tests). Previously tests were passing, now I get this for python3-aiosignal:
```
$ ./xbps-src pkg -Q python3-aiosignal
...
=> python3-aiosignal-1.3.1_1: building with [python3-module] [python3] for x86_64...
...
[check] python3-frozenlist-1.4.0_1: found (/host/binpkgs/aiohttp-socks084-fewer-deps)
[runtime] python3-frozenlist-1.4.0_1: found (/host/binpkgs/aiohttp-socks084-fewer-deps)
...
==================================== ERRORS ====================================
____________________ ERROR collecting tests/test_signals.py ____________________
ImportError while importing test module '/builddir/python3-aiosignal-1.3.1/tests/test_signals.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.12/importlib/__init__.py:90: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_signals.py:6: in <module>
from aiosignal import Signal
aiosignal/__init__.py:1: in <module>
from frozenlist import FrozenList
E ModuleNotFoundError: No module named 'frozenlist'
```
Could this have anything to do with the move to Python 3.12?
next prev parent reply other threads:[~2023-10-16 22:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 13:48 [PR PATCH] " ar-jan
2023-10-02 13:54 ` [PR PATCH] [Updated] " ar-jan
2023-10-02 13:57 ` ar-jan
2023-10-02 14:17 ` ar-jan
2023-10-02 14:30 ` [PR PATCH] [Updated] " ar-jan
2023-10-02 14:46 ` ar-jan
2023-10-02 15:03 ` ar-jan
2023-10-02 15:38 ` ar-jan
2023-10-03 8:43 ` ar-jan
2023-10-03 16:21 ` ar-jan
2023-10-10 18:33 ` ar-jan
2023-10-14 15:30 ` ahesford
2023-10-16 22:18 ` ar-jan [this message]
2023-11-13 15:11 ` [PR PATCH] [Updated] python3-aiohttp_socks: update to 0.8.4 " ar-jan
2023-11-13 15:18 ` ar-jan
2023-11-13 15:24 ` ar-jan
2023-11-13 16:45 ` [PR REVIEW] " ahesford
2023-11-13 16:45 ` ahesford
2023-11-13 17:32 ` [PR PATCH] [Updated] " ar-jan
2023-11-13 17:35 ` ar-jan
2023-11-15 13:37 ` ar-jan
2023-11-15 14:17 ` ar-jan
2023-11-15 21:04 ` [PR PATCH] [Updated] " ar-jan
2023-11-15 21:32 ` ar-jan
2023-11-18 10:36 ` [PR PATCH] [Updated] Update python3-aiohttp_socks, python3-aiohttp, python3-async-timeout; add dependencies ar-jan
2023-11-26 20:47 ` ar-jan
2023-11-26 20:55 ` ar-jan
2023-11-26 21:17 ` [PR PATCH] [Merged]: " ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231016221833.iRkb-JUufHSq1FYHlQW3_1ZxncX3WekU5-5OlV4Tm98@z \
--to=ar-jan@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).