[TIP] "disable" in patch
fuzzyman at voidspace.org.uk
Mon Dec 13 17:17:17 PST 2010
On 12/12/2010 02:23, Alexandre Conrad wrote:
> Hey there,
> I have created an issue on Google Code for a feature enhancement.
> Although I have learned about this mailing list *after* I created the
> issue and I wish I could have exposed my idea before.
> Nevertheless, I wanted to know how this idea would be accepted by the
> python mock community. The details are here:
So effectively calling patch with disable=True would be the same as not
I think there are better ways of switching between test environments.
All the best,
> Alex | twitter.com/alexconrad <http://twitter.com/alexconrad>
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
READ CAREFULLY. By accepting and reading this email you agree,
on behalf of your employer, to release me from all obligations
and waivers arising from any and all NON-NEGOTIATED agreements,
licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap,
confidentiality, non-disclosure, non-compete and acceptable use
policies (”BOGUS AGREEMENTS”) that I have entered into with your
employer, its partners, licensors, agents and assigns, in
perpetuity, without prejudice to my ongoing rights and privileges.
You further represent that you have the authority to release me
from any BOGUS AGREEMENTS on behalf of your employer.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python