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 purcell
Recipients
Date 2004-01-22.15:37:19
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=21477

Hi Matthew and Raymond,

Even though I'm a regular mock user, I'm currently not keen
to add Mock classes to unittest.py. I much prefer that
unittest.py should concentrate solely on providing
test/test-runner infrastructure; there are a number of mock
packages out there, and Python users can choose between
them. Additionally, it is pretty straightforward to write
code from scratch to mock out methods and instances.

Opinions in the XP community of mocking techniques and their
merits are varied enough that even java folk are writing new
mock frameworks, and by incorporating mock support into
unittest.py there is a danger of freezing a moving target,
then being bound to support it and maintain backward
compatibility.

Regards,
-Steve

(Apologies for the delays in processing these SF issues.
They are due to extensive and ongoing work and personal
commitments.)
History
Date User Action Args
2007-08-23 16:06:32adminlinkissue708125 messages
2007-08-23 16:06:32admincreate