Result for 121C0D9D557ADF23E14BAE6681B6EF389768F773

Query result

Key Value
FileName./usr/lib/python3.6/site-packages/fudge/tests/support/__pycache__/_for_patch.cpython-36.pyc
FileSize437
MD590B09854D4B09896AFA6B50D51F224BB
SHA-1121C0D9D557ADF23E14BAE6681B6EF389768F773
SHA-2567C9D9753A383F070A3C3F27E016CFA404D54FD219E46347F44071E476F8BA436
SSDEEP12:XPv3cg/1/y4BYGjetuGyRXtbTNBZ4bU8SskJ:fvcg1yxGIuGy/T6bU8SfJ
TLSHT19BE02284CE81CA92F829F6B2213616297CAA4AFB423DA286171CB0C2980DFE00CA1405
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
MD592853F165708E5D7EECA14B7D8541083
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
PackageReleaselp151.3.3
PackageVersion1.1.0
SHA-16287D59D3391A74BCF35726C076AAE260C355BB6
SHA-25628902D830074136F2097629534F0F255D84C84768DFF169B619EDDB1EA3CDC46
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