This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author cjw296
Recipients cjw296, ezio.melotti, michael.foord, pitrou, python-dev, serhiy.storchaka, vajrasky
Date 2014-06-20.11:57:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403265434.42.0.0991378594395.issue18996@psf.upfronthosting.co.za>
In-reply-to
Content
So, this appears to be the source of some degraded behaviour for me with Python 3.4 versus Python 3.3.

This code, prior to 3.4:

from testfixtures import Comparison as C

class AClass:
    def __init__(self,x,y=None):
        self.x = x
        if y:
            self.y = y
    def __repr__(self):
        return '<'+self.__class__.__name__+'>'

...

self.assertEqual(
    C('testfixtures.tests.test_comparison.AClass',
      y=5, z='missing'),
      AClass(1, 2))

Would give the following output in the failure message:

"""
<C(failed):testfixtures.tests.test_comparison.AClass>
  x:1 not in Comparison
  y:5 != 2
  z:'missing' not in other
</C> != <AClass>"
"""

Now, in 3.4, you get the (rather unhelpful):

"""
<C(failed):testfixtures.tests.test_com[79 chars] </C> != <AClass>
"""

It's particularly disappointing that there's no API (class attribute, etc) to control whether or not this new behaviour is enabled.

What's the process I should tackle for getting this sorted out?
History
Date User Action Args
2014-06-20 11:57:14cjw296setrecipients: + cjw296, pitrou, ezio.melotti, michael.foord, python-dev, serhiy.storchaka, vajrasky
2014-06-20 11:57:14cjw296setmessageid: <1403265434.42.0.0991378594395.issue18996@psf.upfronthosting.co.za>
2014-06-20 11:57:14cjw296linkissue18996 messages
2014-06-20 11:57:14cjw296create