Adds support for the Assistants API #192
Conversation
|
Excited for this one to be merged as it is needed for reading uploaded files. @georgegkonis how has it been working for you? |
|
When shall we expect the merge of this pull request? Is there a work around dealing with assistants and files for now? Thank you! |
|
I haven't gotten any feedback from the author and it's been months since I've opened the PR so I'd say chances of it being merged are slim to none. From a quick look, I see there's no activity on all new issues, so maybe it is that the project isn't being actively worked on for the time being. I've since migrated to Azure's library for my needs, as new features are being implemented much faster. It's a shame, as I much preferred the approach this solution took, but it is what it is. To answer your question, @Tronald, the solution was working well for me, though I didn't have the opportunity to test it extensively across multiple scenarios—just the specific ones I needed. |
|
@georgegkonis thanks for the heads up. I really like this library, but as with many open source projects, there comes the risk that those running it have to attend to higher priorities. I suppose I will look into the Azure solutions as well, though they seem a bit convoluted in comparison sadly. |
|
@georgegkonis looks like this commit supports Assistant v1, would it work with v2 as well? Edit: Doesn't look like it would. This commit still uses v1 objects, and doesn't fit the descriptions of this Migration Guide: |
Added support for the Assistants API.
Tried to integrate it as best as I could without making any changes to the other parts of the code. Still WiP as I haven't had the time to write any tests yet, and a couple result classes are missing and are simply "object" for now. Open to feedback.