From owner-freebsd-python@FreeBSD.ORG Tue Jul 8 13:29:24 2008 Return-Path: Delivered-To: python@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02F3F1065680; Tue, 8 Jul 2008 13:29:24 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4E93A8FC3D; Tue, 8 Jul 2008 13:29:22 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <48736BB5.3080703@FreeBSD.org> Date: Tue, 08 Jul 2008 15:29:25 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Andrew MacIntyre References: <48711120.1000209@FreeBSD.org> <48734D3F.5070008@bullseye.andymac.org> In-Reply-To: <48734D3F.5070008@bullseye.andymac.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: neal@nelson.name, wxs@FreeBSD.org, python@FreeBSD.org Subject: Re: py-bittorrent/twistedCore broken on 8.0? X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 13:29:24 -0000 Andrew MacIntyre wrote: >> i.e. just it is getting exceptions when doing nothing at all, so it >> seems to be completely broken. >> >> Have you tried this, or do you know where to begin looking at what >> might be wrong? > > I know very little about Twisted, but I seem to recall that it offers > a range of different reactors; if you can find where in bittorrent its > deciding to use the kqreactor, you might be able to force it to use an > alternate reactor (such as one based on select() or poll()). > > If you can change the reactor and get something that works, that would > suggest some issue with the kqreactor, at least on 8.x. > Yeah, I tried the poll reactor, which doesn't throw exceptions but appears still not to work properly (the bittorrent tracker doesn't seem to be getting events delivered). I am trying to track down further what might be wrong. Kris