-
Notifications
You must be signed in to change notification settings - Fork 4
Remodernisation of AutoDDG #4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remodernisation of AutoDDG #4
Conversation
e6b4e9b to
d90a560
Compare
d90a560 to
f8c3f35
Compare
f8c3f35 to
6cd4df3
Compare
|
Hi @roquelopez just so you know, I've successfully rebased this current PR's branch with Take care |
|
Hi @roquelopez hope all is well 🙏 Maybe we can try to pre-review the PR with someone else from the team? E.g. someone Juliana cc-ed in the email a couple of days ago, if you are too busy at the moment? (Please do not answer over the weekend nothing very very urgent anyway ^^ I just thought about this PR in between two rides in London!) Cheers |
|
UP Friendly Reminder 🫡 @roquelopez |
|
Thanks, @simonprovost, for implementing this, it looks great to me! |
Thanks so much for your time Roque ! ✅ |
Hi @roquelopez and team!
Hope you’re well! Happy to propose a complete restructure of the library to be more (i) modern Python, (ii) highly typed and checked during runtime with a O(1) overhead, (iii) with one and only one entrypoint, (iv) hard-coded data/prompts fully YAML-transformed for easier maintenance, and(v) fully-lightweight docstringed 🥳
Next step I believe would be to someone to create a workflow to make
AutoDDGavailable on PyPI so we can focus on an MCP with MCPStack. What do you think? I hope it wasn’t too much to ask for such a significant change, but trust me necessary to modernise it and make it easier to build an MCP on top of it.Here’s a video showing some visuals (e.g. Readme, the quick start running, etc.)
VideoPRCompressed.mp4
Caution
This PR should not be merge prior #3 please, let me rebase before whenever this #3 is merged!
Cheers