[issue2156] TestCase.tmpdir(), TestCase.mock()

Changes by Jesús Cea Avión [EMAIL PROTECTED]: -- nosy: +jcea __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2156 __ ___ Python-bugs-list mailing list Unsubscribe:

[issue2156] TestCase.tmpdir(), TestCase.mock()

New submission from Virgil Dupras: I've been using unittest for quite a while. One thing I got tired with is the code duplication for file management and mocking. A few months ago I created this nifty little TestCase subclass and I've been using it ever since. It works quite well. Am I the

[issue2156] TestCase.tmpdir(), TestCase.mock()

Benjamin Peterson added the comment: The Path class of hs.path is, I assume, a nice wrapper around a file or directory. However, Python does not have something like this, so it's probably more useful to just return the raw path. __ Tracker [EMAIL PROTECTED]

[issue2156] TestCase.tmpdir(), TestCase.mock()

Benjamin Peterson added the comment: First, is hs a company package? You'll most likely want to remove it. Otherwise, this looks useful. I wonder if this is something we could use in test.test_support. I'd like it for some of Python's regression tests. Brett, what do you think about that?

[issue2156] TestCase.tmpdir(), TestCase.mock()

Virgil Dupras added the comment: Oh, you meant hs.path? ah yeah, it's just for tmppath(), which is of no use except in my own stuff. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2156 __

[issue2156] TestCase.tmpdir(), TestCase.mock()

Virgil Dupras added the comment: Well, yeah, but I'm the owner, it's not like if the copyright was a problem. I'd gladly release it (and the test unit that goes with it) under BSD. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2156

[issue2156] TestCase.tmpdir(), TestCase.mock()

Raymond Hettinger added the comment: -1 on adding these to unittest. The module is already too complex. Mock objects have been rejected previously and the rationale still holds. There is no standardized approach that meets everyone's needs. It doesn't make sense to lock in one of the many ways

[issue2156] TestCase.tmpdir(), TestCase.mock()

Steve Purcell added the comment: I agree with Raymond: -1 from me. There isn't a consensus on what mock object means*, and trying to provide a standardised mock object facility is a quagmire*, hence the prior rejections to which Raymond refers. It's easy to roll your own simple mock objects

[issue2156] TestCase.tmpdir(), TestCase.mock()

Changes by Steve Purcell: -- status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2156 __ ___ Python-bugs-list mailing list Unsubscribe: