From owner-freebsd-questions@FreeBSD.ORG Wed Jan 9 19:07:37 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 B48EA16A41A for ; Wed, 9 Jan 2008 19:07:37 +0000 (UTC) (envelope-from gunther.mayer@googlemail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id 4829113C46A for ; Wed, 9 Jan 2008 19:07:37 +0000 (UTC) (envelope-from gunther.mayer@googlemail.com) Received: by ug-out-1314.google.com with SMTP id y2so171408uge.37 for ; Wed, 09 Jan 2008 11:07:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:user-agent:mime-version:to:subject:content-type:content-transfer-encoding:from; bh=NLz6+zXWGraZsrMBRbOt8LkoQBIyU90dnX5tlq2HNfI=; b=SSGBOy8N4/Q2Zn/bvkjPzKVBIlcIGJtoXdXX2upsRFNrZh3oEjZMz5efVmSG5AASBatOWrUXJjtObDrDhyT9k0bGtqU7rmu935eaYXiqIdcjRgtecmFenrDYdwnGlC1fwx1VJf2PC+TtBM2t8KCD2TH1qkwgsIsLPLuIbtYiWUk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:user-agent:mime-version:to:subject:content-type:content-transfer-encoding:from; b=Ph5Sn6T5dqg6/p+AGDxP7b9pLmc9Tm7I51I+B3UlZWjORgZwqh8022MebCb3TuGEYeTNMiuuPu0J7UG40IEPn5huQXxYB3VIq99UrY1GV4RyoJ/cTYVK4puAT9YhN5GfQOpaD9LY6NqwLlSE9z7Q6+yDqV7de+ZELDMobQv9h40= Received: by 10.67.116.2 with SMTP id t2mr2542588ugm.62.1199904010061; Wed, 09 Jan 2008 10:40:10 -0800 (PST) Received: from ?172.25.0.18? ( [196.7.14.186]) by mx.google.com with ESMTPS id i30sm1977147ugd.38.2008.01.09.10.40.07 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 09 Jan 2008 10:40:09 -0800 (PST) Message-ID: <47851504.8090006@gmail.com> Date: Wed, 09 Jan 2008 20:40:04 +0200 User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit From: Gunther Mayer Subject: 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: Wed, 09 Jan 2008 19:07:37 -0000 Hi guys, 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. Chicken and egg - one of my ports insists on python with threads enabled, the other port insists I use python without thread support. My workaround is to compile python without threading, install(or upgrade) postgresql-plpython, then recompile python with threading, install(or upgrade) trac and pray that plpython won't eat my dog when I use it. A really painful and error prone exercise, especially when an upgrade comes along (security or otherwise). 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? To get you an idea of what versions I'm running, the affected postgresql ports are postgresql-plpython-8.2.6 postgresql-server-8.2.6 for the trac dependencies the involved culprits are: py25-pysqlite-2.0.7_1 python25-2.5.1_1 python-2.5,2 sqlite-3.3.8 # peripheral I remember with python 2.4 I had the same endless issues over a year ago so it's not 2.5's fault. Oh, and btw, I'm running 6.2-RELEASE-p9 i386. Gunther