Does anyone really dislike the __call__ syntax?

[goodboy]

I remember way back when first writing this we had an internal debate about .run() versus __call__() and can't remember why we settled on the latter.

In hindsight, after more years of codezing, I think the .run() is more clear and pythonic maybe?

Does anyone have opinions on this?

[kontsaki]

i agree that .run() is more explicit

do you lean on deprecating the scenario object being a callable?

[goodboy]

@kontsaki yeah, it use of __call__() was from a different "way" of design in younger years.

I wonder if Scenario.run() is just more simple and intuitive.

[kontsaki]

yes it feels like it, since there is a .finalize() coming as well.

[kontsaki]

hey @goodboy , what is the current way of running a single specific xml scenario?
i used to work with client/server agents and set the scen_file attribute but apparently that was incorrect cause now it blows up with Internal error, main_scenario already set which i guess makes sense.

[kontsaki]

does it make sense to expose ua like client and server ?
edit: just realized i can just pass the scen_file as argument to client/server agents
btw what is the difference between a client and server agent in the context of pysipp ?