Another option for mocking would be a class that would inherit from cgi
and then overload the functions you want to manipulate.
meaning :
class mycgi(cgi):
def get_params(self):
doMyOwnMagic()
Using mycgi will probebly be transparent to any component which is using
cgi...
you just switch
On 17 Jul, 2005, at 9:58, Lior Kesos wrote:
Another option for mocking would be a class that would inherit from
cgi and then overload the functions you want to manipulate.
meaning :
class mycgi(cgi):
def get_params(self):
doMyOwnMagic()
You can't subclass a module.
>>> import cgi
>>>
Hi guys...
Although I haven't participated in the meeting due to a mixture of
family/work/kids I'm happy the meetings have started although I do not
have the resources to be one of the driving members.
Anyway Chen told me about the search for a place to pass lectures so
I've ok'ed the meetings
Sorry -my bad - I meant the class (probably fieldStorage in Shlomi's case).
I just tried to emphasize overloading as a standard way of "hooking"
functions to modify the behavior.
Lior.
Nir Soffer wrote:
On 17 Jul, 2005, at 9:58, Lior Kesos wrote:
Another option for mocking would be a class th
Don't know I just announced that it can take place in my company.
Most of the meetings are announced here...
http://www.python.org.il/mediawiki/index.php/Events
[EMAIL PROTECTED] wrote:
Hi lior,
whzz up?
great.
when the next meeting suppose to be?
is there a list of the PPT
