From owner-freebsd-questions@FreeBSD.ORG Thu Jan 10 15:31:33 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52C2516A417 for ; Thu, 10 Jan 2008 15:31:33 +0000 (UTC) (envelope-from stapleton.41@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by mx1.freebsd.org (Postfix) with ESMTP id 27F7A13C45D for ; Thu, 10 Jan 2008 15:31:32 +0000 (UTC) (envelope-from stapleton.41@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1236579waf.3 for ; Thu, 10 Jan 2008 07:31:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=IjdNqnTmpvOiFWORT5wzHtP686UdBP9cyoTXGVUIDWs=; b=lOQ0xoJiN43N9D2lmfTUxS3d/LzhYZBxZdalAKd8+ilIF8v0bH8BgnogiWW7tpvXONXLhHBWpumXRuLbZUDIM1df9NzqqQCTadA4ckNzqcHNtEh5a6oub6XpsYqq7psvObKATI4k6OZgnkODQaeE/A/kDxp246VWKPj7Q3XNoUM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=xm7Kmq2h0aTC5Qugh50sm5PhI0mPPbmBw+kq3QZDgOt4jy6M4ppWkS8w6sXQxg99P2ohhF+6CYWVTLzMFT39mTltB/51DOkMTxfq3DgoaHB4q6oJc0ImEUaV0zzCL3YSU9fAgywfTCTkVQn2VyDJ+2o41X1m8h1H2MHOKvlVRW0= Received: by 10.114.81.1 with SMTP id e1mr2431321wab.11.1199979090538; Thu, 10 Jan 2008 07:31:30 -0800 (PST) Received: by 10.114.240.16 with HTTP; Thu, 10 Jan 2008 07:31:30 -0800 (PST) Message-ID: <80f4f2b20801100731s7ed6b909h774c5ea783c1c664@mail.gmail.com> Date: Thu, 10 Jan 2008 10:31:30 -0500 From: "Jim Stapleton" To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: RE: Python threading - some ports depend on it, others break with it X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jan 2008 15:31:33 -0000 > I'm having so much trouble with this. I'm hosting a trac based project > which is implemented in python and uses an sqlite db backend along with > its python bindings. Now it turns out that pysqlite breaks badly > (compiles and installs fine but chokes on import, see > http://lists.initd.org/pipermail/pysqlite/2006-May/000553.html) if > python itself is compiled *without threading* support. > > However, on the same box I run a postgresql development and testing > database and we have some triggers and other functions implemented in > pl/python. Guess what? The compile of postgresql-plpython chokes upon > configure if python is built *with threading* support. Running it seems > to work fine, but there's a reason upstream put this check into > configure because supposedly this is known to break things. ... > I need both of these ports on one box and I'm not sure what to do to > sort out this mess properly. Any ideas? What's up with Python's > threading support on FreeBSD in any case, why is is broken? I would suggest framing either some of the programs/libraries with a few counts of 1st degree murder, and sending it to jail for life, where it can run for life in a nice little cell with it's own pet python. Would that work? It's probably a bit more work than a desirable solution, but if you don't need them running in the same "space", it should work. Or have I completely missed the point (very likely given me). -Jim Stapleton