Path: csiph.com!2.eu.feeder.erje.net!feeder.erje.net!1.eu.feeder.erje.net!newsfeed.datemas.de!weretis.net!feeder4.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Ben Finney Newsgroups: linux.debian.maint.python Subject: Re: Help for Python mock test suite needed Date: Mon, 15 Aug 2016 22:30:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Aug 15 20:24:06 2016 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.206 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, RDNS_NONE=0.793] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -6.1 X-Injected-Via-Gmane: http://gmane.org/ Lines: 21 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) X-Public-Key-ID: 0xAC128405 X-Public-Key-Fingerprint: 517C F14B B2F3 98B0 CB35 4855 B8B2 4C06 AC12 8405 X-Public-Key-URL: http://www.benfinney.id.au/contact/bfinney-pubkey.asc X-Post-From: Ben Finney Cancel-Lock: sha1:APUxjhnb9xOuiboLm8WWOIc6lm0= X-Mailing-List: archive/latest/14114 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/8537m5zsq8.fsf@benfinney.id.au Approved: robomod@news.nic.it Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 16 Aug 2016 06:23:43 +1000 X-Original-Message-ID: <8537m5zsq8.fsf@benfinney.id.au> 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> X-Original-X-Complaints-To: usenet@blaine.gmane.org Xref: csiph.com linux.debian.maint.python:8773 Andreas Tille 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, or just normal Python debugging. Unless I'm misunderstanding, this doesn't appear to be a problem specific to a Debian build environment, so I would guess it fails even when simply running the test suite in a normal development environment. So you can use the full power of your development environment to hunt the problem: an interactive debugging session, etc. Use your Python skills :-) -- \ “Broken promises don't upset me. I just think, why did they | `\ believe me?” —Jack Handey | _o__) | Ben Finney