Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eweka.nl!lightspeed.eweka.nl!193.141.40.65.MISMATCH!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path: <rosuav@gmail.com>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.048
X-Spam-Evidence: '*H*': 0.91; '*S*': 0.00; 'lines,': 0.07; 'python': 0.11; '2:28': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'reload': 0.16; 'wrote:': 0.18; 'bit': 0.19; 'module': 0.19; '(by': 0.24; 'header:In-Reply-To:1': 0.27; 'function': 0.29; 'am,': 0.29; 'message-id:@mail.gmail.com': 0.30; 'easier': 0.31; 'sep': 0.31; 'figure': 0.32; 'supposed': 0.32; 'received:google.com': 0.35; 'two': 0.37; 'to:addr:python-list': 0.38; 'to:addr:python.org': 0.39; 'problems.': 0.60; 'first': 0.61; 'times': 0.62; "it'd": 0.84; '2013': 0.98
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=0Gwak+uzkxCvf817wsqBRVryAdr8oVqbYGlLK0riDJ4=; b=w/RDeATHllnJOmvM/GGqdfnkhZK080geg4hfe03itA/acM6hVulncnl9OuVpGVcHYr YeRF9fQrL0BkOLRnLOTeVsxm1fSp4KagxjyPLtwgI+hmhplFKh5X4oFyDSWJkpLR0n3v Pp7ECaBdeW6Lbo+C2vuhG3TtfnpGoaxfBNyT5tgJeTZpjPtrA0a0VRH1a8h2qDFPeSjS ExoSHTNhoW6anp/TgYtbp4a7Vhvh7g7wZvbvY/bp/KW9PJbpRc7fNGVApiO6NIhJo8PD 90+6b2q/M5ftvGAwJzgFhYgREHpkBIeTP4nN1W4I/ElZZy/exHtb8wIWIuVIAIroGU9+ dTNQ==
MIME-Version: 1.0
X-Received: by 10.52.64.143 with SMTP id o15mr24620163vds.16.1379370848428; Mon, 16 Sep 2013 15:34:08 -0700 (PDT)
In-Reply-To: <l17bj9$1qs$1@dont-email.me>
References: <l17bj9$1qs$1@dont-email.me>
Date: Tue, 17 Sep 2013 08:34:08 +1000
Subject: Re: Weird ttk behaviour
From: Chris Angelico <rosuav@gmail.com>
To: python-list@python.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.39.1379370869.18130.python-list@python.org>
Lines: 12
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1379370869 news.xs4all.nl 15961 [2001:888:2000:d::a6]:44654
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:54250

On Tue, Sep 17, 2013 at 2:28 AM, Rotwang <sg552@hotmail.co.uk> wrote:
> If I then uncomment those two lines, reload the module and call f() again
> (by entering tkderp.reload(tkderp).f()), the function works like it was
> supposed to in the first place: two warnings, no exceptions. I can reload
> the module as many times as I like and f() will continue to work without any
> problems.

Reloading modules in Python is a bit messy. Are you able to tinker
with it and make it work in some way without reloading? It'd be easier
to figure out what's going on that way.

ChrisA