Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: Andreas Tille <andreas@an3as.eu>
Newsgroups: linux.debian.maint.python
Subject: Re: Help for Python mock test suite needed
Date: Wed, 17 Aug 2016 14:00:02 +0200
Message-ID: <s77FM-wB-7@gated-at.bofh.it>
References: <s5AVz-5B0-3@gated-at.bofh.it> <s5AVz-5B0-1@gated-at.bofh.it> <s5Kid-3N8-7@gated-at.bofh.it> <s5PBf-7sM-3@gated-at.bofh.it> <s5RMJ-mo-3@gated-at.bofh.it> <s5WW6-45C-1@gated-at.bofh.it> <s68Xg-3DL-19@gated-at.bofh.it> <s6mQx-3Wz-5@gated-at.bofh.it> <s6wGd-1PM-15@gated-at.bofh.it>
X-Original-To: debian-python@lists.debian.org
X-Mailbox-Line: From debian-python-request@lists.debian.org  Wed Aug 17 11:58:20 2016
Old-Return-Path: <andreas@an3as.eu>
X-Amavis-Spam-Status: No, score=-8.287 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate: -6.1
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/14119
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/20160817115804.GR4482@an3as.eu
Approved: robomod@news.nic.it
Lines: 28
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Wed, 17 Aug 2016 13:58:04 +0200
X-Original-Message-ID: <20160817115804.GR4482@an3as.eu>
X-Original-References: <20160809213240.GA22935@an3as.eu> <20160813064034.GA22254@an3as.eu> <2201782.mV6MicLdnE@kitterma-e6430> <20160813222229.GI22254@an3as.eu> <85oa4wyyie.fsf@benfinney.id.au> <20160814061201.GL22254@an3as.eu> <85bn0vyy3f.fsf@benfinney.id.au> <20160815095545.GS22254@an3as.eu> <8537m5zsq8.fsf@benfinney.id.au>
Xref: csiph.com linux.debian.maint.python:8778

On Tue, Aug 16, 2016 at 06:23:43AM +1000, Ben Finney wrote:
> Andreas Tille <andreas@an3as.eu> writes:
> 
> > Yes, this is what I guessed from the log.  However, how can I find out
> > why exactly the command is not called?
> 
> That seems to be a question to take up with the upstream developer,

Yes.

> or just normal Python debugging.

This exactly was my question:  Is there any advise how to inject
sensible debugging code or any other strategies to find out what might
be the problem.

> So you can use the full power of your development environment to hunt
> the problem: an interactive debugging session, etc. Use your Python
> skills :-)

I'm afraid at first I need to enhance my Python skills ...

Kind regards

        Andreas.

-- 
http://fam-tille.de