Double initialization

[adrienbanse]

• Implementation of double intialization discussion in Decorator mode vs client wrapper #8 (in the end I raised an exception to avoid any bad user implementation)
• Unit test

[adrienbanse]

I'm not sure if there is a workaround that allows not to export TracerInitializationError in __init__.py to use it in the tests
We can also just check if it raises an Exception

[samuelrince]

Looks great!

I'm not sure if there is a workaround that allows not to export TracerInitializationError in __init__.py to use it in the tests We can also just check if it raises an Exception

Can't you just import it with from genai_impact.tracer import TracerInitializationError?

Also, not mandatory, but I find it to be a good practice to centralize the possible exceptions of the package in a separate module called exceptions.py. And have a global exception GenAIImpactError that is inherited by all the other exceptions.

PS: I can't wait to change the name, it makes my eyes bleed to see GenAIImpact in the class names!

[adrienbanse]

@samuelrince Right! Yes it's not the optimal naming haha
It's implemented