Result for 1065CFCFCFF434B074C119AAC2E9DCD8D0B713F3

Query result

Key Value
FileName./usr/share/doc/packages/python3-fudge/html/search.html
FileSize3454
MD5E5EA874C9BF07F479F75B5F51F2329F8
SHA-11065CFCFCFF434B074C119AAC2E9DCD8D0B713F3
SHA-256E582783F0F262CE6354654D4B1535BCA4973181476C5210490023C6F9867386F
SSDEEP48:4Vm3pQoTffFzl5lDmHM9C5x2D9N4v6LLq0kW6Zv+djUrPq5x2Du4vX4n1:qoTffFBDms9C2D9Wv6CnW6Za8C2Dlv0
TLSHT1766140169CF2D813C07286D7E5F6E9166E82D10B8609A80871CC966D2FD2F884E5FB8D
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD55B8785CBEEF93AF07A9448E5816373BA
PackageArchnoarch
PackageDescriptionComplete documentation is available at http://farmdev.com/projects/fudge/ Fudge is a Python module for using fake objects (mocks and stubs) to test real ones. In readable Python code, you declare what methods are available on your fake and how they should be called. Then you inject that into your application and start testing. This declarative approach means you don't have to record and playback actions and you don't have to inspect your fakes after running code. If the fake object was used incorrectly then you'll see an informative exception message with a traceback that points to the culprit. Here is a quick preview of how you can test code that sends email without actually sending email:: @fudge.patch('smtplib.SMTP') def test_mailer(FakeSMTP): (FakeSMTP.expects_call() .expects('connect') .expects('sendmail').with_arg_count(3)) send_mail()
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython2-fudge
PackageReleaselp150.2.3
PackageVersion1.1.0
SHA-160DC069A7E153DB3A9A044E2B44D3BFC28881AAF
SHA-2563BF09D5211E6497B12EA7F1A764E47AE156FA6706799D8897E1C715D063D6597
Key Value
MD5E8EC2EB8384953FCACCA767DC090C966
PackageArchnoarch
PackageDescriptionComplete documentation is available at http://farmdev.com/projects/fudge/ Fudge is a Python module for using fake objects (mocks and stubs) to test real ones. In readable Python code, you declare what methods are available on your fake and how they should be called. Then you inject that into your application and start testing. This declarative approach means you don't have to record and playback actions and you don't have to inspect your fakes after running code. If the fake object was used incorrectly then you'll see an informative exception message with a traceback that points to the culprit. Here is a quick preview of how you can test code that sends email without actually sending email:: @fudge.patch('smtplib.SMTP') def test_mailer(FakeSMTP): (FakeSMTP.expects_call() .expects('connect') .expects('sendmail').with_arg_count(3)) send_mail()
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython3-fudge
PackageReleaselp150.2.3
PackageVersion1.1.0
SHA-17D07BA05C9B6062E440AA47BC15FD79A3F3A9998
SHA-256A4EC66DB5E1F3F6D77589FA9604A7BF2E66DDBC051F8D3C867D50CFDDC122A73