From owner-freebsd-python@FreeBSD.ORG Thu Jun 10 01:35:46 2004 Return-Path: <owner-freebsd-python@FreeBSD.ORG> Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25C1616A4CE for <freebsd-python@freebsd.org>; Thu, 10 Jun 2004 01:35:46 +0000 (GMT) Received: from smtp.sw.oz.au (alt.aurema.com [203.217.18.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02FC843D4C for <freebsd-python@freebsd.org>; Thu, 10 Jun 2004 01:35:45 +0000 (GMT) (envelope-from vance@aurema.com) Received: from smtp.sw.oz.au (localhost [127.0.0.1]) by smtp.sw.oz.au with ESMTP id i5A1ZRDZ015753; Thu, 10 Jun 2004 11:35:27 +1000 (EST) Received: (from vance@localhost) by smtp.sw.oz.au id i5A1ZRG8015751; Thu, 10 Jun 2004 11:35:27 +1000 (EST) Date: Thu, 10 Jun 2004 11:35:27 +1000 From: Christopher Vance <vance@aurema.com> To: freebsd-python@freebsd.org Message-ID: <20040610013527.GC19601@aurema.com> Mail-Followup-To: Christopher Vance <vance@aurema.com>, freebsd-python@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Scanned-By: MIMEDefang 2.43 cc: vance@aurema.com Subject: python2 2.3.4 threads on 4.10-stable X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>, <mailto:freebsd-python-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python> List-Post: <mailto:freebsd-python@freebsd.org> List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>, <mailto:freebsd-python-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 10 Jun 2004 01:35:46 -0000 I'm running -STABLE and keep my ports updated with portupgrade. I have used a home-grown python tkinter script on this machine (and also on Red Hat) for quite a while for time tracking. It which includes a single use of thread.start_new_thread running a function which does very little, mostly time.sleep. The script uses menus. I have found that the script now hangs, sometimes before it even finishes showing the original window, unless I comment out the thread invocation. Perhaps the sleep is blocking the initial thread as well as the subsidiary one? This would be despite the thread doc which says that time.sleep should work. This occurs in both kde and gnome, so I don't think this error message is relevant - but included in case: Jun 10 09:57:09 fred bonobo-activation-server (vance-45830): invalid character '#' in iid 'OAFIID:This#!!%$iid%^$%_|~!OAFIID_ContainsBadChars' Several possible causes change in threading in Python 2.3.4 vs 2.3.3 change in threading in 4.10-S vs older window manager Any suggestions? -- Christopher Vance From owner-freebsd-python@FreeBSD.ORG Thu Jun 10 12:25:14 2004 Return-Path: <owner-freebsd-python@FreeBSD.ORG> Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B42DA16A4D0 for <freebsd-python@freebsd.org>; Thu, 10 Jun 2004 12:25:14 +0000 (GMT) Received: from smtp.sw.oz.au (alt.aurema.com [203.217.18.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC98A43D1F for <freebsd-python@freebsd.org>; Thu, 10 Jun 2004 12:25:13 +0000 (GMT) (envelope-from vance@aurema.com) Received: from smtp.sw.oz.au (localhost [127.0.0.1]) by smtp.sw.oz.au with ESMTP id i5ACOnDZ026867 for <freebsd-python@freebsd.org>; Thu, 10 Jun 2004 22:24:50 +1000 (EST) Received: (from vance@localhost) by smtp.sw.oz.au id i5ACOn4i026865 for freebsd-python@freebsd.org; Thu, 10 Jun 2004 22:24:49 +1000 (EST) Date: Thu, 10 Jun 2004 22:24:49 +1000 From: Christopher Vance <vance@aurema.com> To: freebsd-python@freebsd.org Message-ID: <20040610122449.GP19601@aurema.com> Mail-Followup-To: Christopher Vance <vance@aurema.com>, freebsd-python@freebsd.org References: <20040610013527.GC19601@aurema.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20040610013527.GC19601@aurema.com> User-Agent: Mutt/1.4.2.1i X-Scanned-By: MIMEDefang 2.43 Subject: Re: python2 2.3.4 threads on 4.10-stable X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>, <mailto:freebsd-python-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python> List-Post: <mailto:freebsd-python@freebsd.org> List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>, <mailto:freebsd-python-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 10 Jun 2004 12:25:14 -0000 On Thu, Jun 10, 2004 at 11:35:27AM +1000, I wrote: >Several possible causes > change in threading in Python 2.3.4 vs 2.3.3 > change in threading in 4.10-S vs older > window manager Thanks for the response I received. I found tcl 8.4.6, tk 8.4.6 and python 2.3.4 all understand WITH_THREADS, which I had not specified. (Everything worked before, without it set.) Recompiling tcl and python with that set in /etc/make.conf seems to have fixed the problem. I'm not sure which pkg was the real problem. But tk is broken, in that it won't compile WITH_THREADS, barfing on -pthread. I'll check for PRs, and raise one if necessary. -- Christopher Vance