Two different Amplitude instances send event to the same project

[hurlenko]

Consider this sample code:

client_a = Amplitude(PROJECT_A)
client_b = Amplitude(PROJECT_B)

client_a.track(...)  # sends event to PROJECT_B

Expected Behavior

client_a.track(...) sends the event to PROJECT_A

Current Behavior

client_a.track(...) sends the event to PROJECT_B

Possible Solution

Don't use mutable defaults in function arguments as they are shared across all class instances:

Amplitude-Python/src/amplitude/client.py

Line 40 in ec79070

def __init__(self, api_key: str, configuration: Config = Config()):

Amplitude-Python/src/amplitude/client.py

Lines 48 to 49 in ec79070

	self.configuration: Config = configuration
	self.configuration.api_key = api_key

Can be replaced with something like:

def __init__(self, api_key: str, configuration: Optional[Config] = None):
    self.configuration = configuration or Config()

Possible workaround for now is to specify different config instances explicitly:

client_a = Amplitude(PROJECT_A, configuration=Config())
client_b = Amplitude(PROJECT_B, configuration=Config())

Another possible bug with this scenario might be here (didn't check):

Amplitude-Python/src/amplitude/config.py

Line 58 in ec79070

storage_provider: StorageProvider = InMemoryStorageProvider(),

Environment

• SDK Version: amplitude-analytics==1.1.0
• Python Version: 3.9.16
• OS Info: macOS 13.2

[Mercy811]

Hi @hurlenko, thanks for creating this issue. It should be fixed in 1.1.2. Please upgrade to the latest version.