https://bugzilla.redhat.com/show_bug.cgi?id=1572928
--- Comment #3 from Athmane Madjoudj <[email protected]> --- (In reply to Miro Hrončok from comment #1) 1,2,5 => done (will post update shortly) 3. Sorry for confusion, that bit was residue from testing with python2 4. The test-suite is inherited from upstream fabric, upstream preferred to plan a switch to mock instead of updating to fudge 1.x (didn't happen yet) since fudge is no longer maintained [1][2] [1] https://bitbucket.org/kumar303/fudge/issues/27/test-failures-with-python-3 [2] https://github.com/fabric/fabric/issues/203 Quote from [1]: "Hi, thanks for the report. I don't use fudge anymore because Mock has surpassed it in features, stability, and Python support. I'd be happy to merge in any patches but it would probably be easier if we switch everything to a github project. If anyone has time to do that I'd greatly appreciate it." Quote from [2]: "I should actually close this - I've been using mock on my newer projects and find it a bit more usable than Fudge (even Fudge 1.x). Fabric 1.x is nearing EOL so updating its dependencies isn't really a priority anymore." -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected]
