Path: csiph.com!weretis.net!feeder9.news.weretis.net!newsfeed.endofthelinebbs.com!news.corradoroberto.it!gothmog.csi.it!bofh.it!news.nic.it!robomod
From: c.buhtz@posteo.jp
Newsgroups: linux.debian.maint.python
Subject: Re: [Help] New package python-loky build time test times out
Date: Thu, 26 Dec 2024 09:50:01 +0100
Message-ID: <JXRJ7-2MBb-1@gated-at.bofh.it>
References: <JXDG9-2vjp-3@gated-at.bofh.it> <JXFoB-2wTN-1@gated-at.bofh.it> <JXFHY-2x9n-5@gated-at.bofh.it>
X-Original-To: Debian python <debian-python@lists.debian.org>
X-Mailbox-Line: From debian-python-request@lists.debian.org  Thu Dec 26 08:49:10 2024
Old-Return-Path: <c.buhtz@posteo.jp>
X-Amavis-Spam-Status: No, score=-9.399 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate: -5.5
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/22724
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/be7651e4ec6d71e23bb0c8a5fd7426c0@posteo.de
Approved: robomod@news.nic.it
Lines: 20
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Thu, 26 Dec 2024 08:48:54 +0000
X-Original-Message-ID: <be7651e4ec6d71e23bb0c8a5fd7426c0@posteo.de>
X-Original-References: <Z2xFFbq2vXFRtB0N@an3as.eu> <4226e68c154e1fdf36e291b5d95d95fd@posteo.de> <Z2xjZfWQL_D-BuIP@belkar.wrar.name>
Xref: csiph.com linux.debian.maint.python:16630

Dear Andrey,

Am 25.12.2024 20:56 schrieb Andrey Rakhmatullin:
> https://github.com/search?q=repo%3Acogent3%2Fcogent3%20loky&type=code

Sending URLs only is quit annoying to all other list members and not an 
answer.

I know the details and that there are reasons why this package depend on 
the other. But IMHO the reasons are not heavy enough to burn resources 
of Debian packagers.
As upstream I would just integrate that codebase into my own, or open a 
ticket at Jupyter to get rid of that restriction causing that 
dependency.

I think of Debian GNU/Linux as a big project and I am worried about its 
resources. That's all.

Regards,
Christian