public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ian Delaney (idella4)" <idella4@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-python/mocker/files: mocker-1.1.1-pypy_test.patch
Date: Sat,  3 Nov 2012 18:24:32 +0000 (UTC)	[thread overview]
Message-ID: <20121103182432.B47C0215F3@flycatcher.gentoo.org> (raw)

idella4     12/11/03 18:24:32

  Added:                mocker-1.1.1-pypy_test.patch
  Log:
  bumped to mocker-1.1.1, new patch for pypy to pass tests, mocker-1.0 dropped, closes Bug 425686
  
  (Portage version: 2.1.11.30/cvs/Linux x86_64, unsigned Manifest commit)

Revision  Changes    Path
1.1                  dev-python/mocker/files/mocker-1.1.1-pypy_test.patch

file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/mocker/files/mocker-1.1.1-pypy_test.patch?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/mocker/files/mocker-1.1.1-pypy_test.patch?rev=1.1&content-type=text/plain

Index: mocker-1.1.1-pypy_test.patch
===================================================================
Upstream maintainer assures us "The "assertRaises" line should be skipped IMO. The next call actually succeeds,
but of course there is no point to test for unsupported functions."
Re the 2nd patch;
PyPy actually behaves as if __slots__ was added to the class
see http://morepypy.blogspot.ch/2010/11/efficiently-implementing-python-objects.html
diff -ur mocker-1.1.1.orig/test.py mocker-1.1.1/test.py
--- test.py	2012-05-19 19:27:02.000000000 +0800
+++ test.py	2012-07-11 14:43:57.848953730 +0800
@@ -3880,7 +3881,7 @@
         from zlib import adler32
         # If that fails, this test has to change because either adler32 has
         # changed, or the implementation of getargspec has changed.
-        self.assertRaises(TypeError, inspect.getargspec, adler32)
+       # self.assertRaises(TypeError, inspect.getargspec, adler32)
         try:
             task = SpecChecker(adler32)
             task.run(self.path("asd"))
@@ -4060,7 +4060,8 @@
                 self.calendar = calendar
         obj = C()
         self.task.replay()
-        self.assertEquals(type(obj.calendar), Mock)
-        self.assertTrue(obj.calendar is self.mock)
+        if not hasattr(sys, 'pypy_version_info'):
+            self.assertEquals(type(obj.calendar), Mock)
+            self.assertTrue(obj.calendar is self.mock)
 
     def test_install_on_submodule(self):
        from os import path





                 reply	other threads:[~2012-11-03 18:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121103182432.B47C0215F3@flycatcher.gentoo.org \
    --to=idella4@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox