Software development suggestions

[enahwe]

I think aisuite has a lot of potential. However, I didn't find any logic from an integration and generalization point of view for teams of developers within an IT.

The aisuite code seems to be selfishly centered from a "developer who acts alone in his corner" point of view...

For example, forcing the Python version to at least 3.10 is really a shame because in the real business world there are many Python projects (not too old) that use versions 3.7.x, 3.8.x, 3.9.x and more.
And some of these projects could evolve very quickly by integrating aisuite, but the fact that aisuite requires at least 3.10 does not allow it.

It is also difficult to find a way around the organization of aisuite's system files, it lacks logic. For example, there is no configuration file centralizing the URLs for each provider. If I integrate an Ollama service into my IT, I don't know which configuration file to use to configure the URL of my Ollama!

[chrismstokes-qs]

You can check the source for each provider in aisuite/provider/<provider_name>_provider.py to see exactly where config parameters are read from. For example, the ollama provider __init__() tells us the ollama URL can be configured through setting the OLLAMA_API_URL environment variable.

aisuite/aisuite/providers/ollama_provider.py

Line 23 in 7eecd6d

"OLLAMA_API_URL", "http://localhost:11434"

[ksolo]

@enahwe I can check compatibility to 3.9 but versions below that are EOL and will not be supported (https://devguide.python.org/versions/). If you are using anything older than that I highly recommend you upgrade your versions.

The client can also accept a dict with provider specific configuration if needed. It's outlined in the doc string (https://github.com/andrewyng/aisuite/blob/main/aisuite/client.py#L5-L27). I would agree we can add more documentation on this to highlight it.