-
Notifications
You must be signed in to change notification settings - Fork 1k
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
What are the Maintaners' intentions with Guidance? #395
Comments
Thank you for the suggestion of other alternatives, i was wondering the same thing about the repository status. |
Not dead - we have been working on a release with lots of big changes (it's taking longer than expected). |
@marcotcr Thanks for the reply! I really did prefer this project over alternatives, but then bugs went uninspected, and PRs unmerged. Could you tell us about the |
Yes, sorry, a lot has happened. Me and @slundberg switched employers, and Microsoft moved the project out to The switch took a while, and we let the project lapse in the meantime. Since we picked it back up, me and Scott have been working on this branch, and more recently on this one with what we thought would be a quick change, but proved to result in a larger refactor that obviates many of the current issues. I think we're close to being ready to release (as in... in a couple of weeks), at which point our plan is to write a blog post, revamp README, examples, etc, and go through all issues that are still relevant. The new version should be way better, but we'll see how the community responds :) |
❤️ Thanks for the update! ❤️ |
@marcotcr - really appreciate hearing the update. We have a Ruby wrapping of Guidance (and some more fun stuff coming) at https://github.com/Unsupervisedcom/guidance and would love to contribute to some of the newer efforts too. |
Fantastic to hear this is still in development. There's nothing I found that quite gives me the control over the results of prompt chaining than guidance. Excited to see the update when it comes out. Syntax highlighting would be a gamechanger so hoping that's on the roadmap. 🙏 |
How about LMQL? I've been thinking about using it instead of guidance but I don't know if anyone has tried both to give an unbiased comparison of them. |
Wasn't aware of this package yet, thanks for pointing it out. From what I can see LMQL is limited to completion endpoints/model which would make it less versatile than guidance. There are some interesting ideas there though so I'll definitely check it out. |
@Nick-tenBroeke guidance works on fill-in-the-middle models? I wasn't aware. I truly wish this project would revive. Last I tried it it was broken for all my use cases, and relevant issues from other users were ignored :( |
Hey @freckletonj, thanks for all your interest and passion about Guidance! As Marco mentioned above, we've been focused on completely revamping guidance in the branch here: https://github.com/guidance-ai/guidance/tree/pythonic2, though these changes are still stabilizing (and therefore not ready to pull into main just yet). Lots of progress being made, just not on the default GH homepage view :) |
Hey, I would love to use the version on the branch. Even if it is not stabilised, can we still test it? Do you have a small example of the new default python file using OpenAI and not LLama? |
Thank you. I was developing guidance from the very beginning, just hadn't joined the board :) We finally have a new release, sorry it took us so long :) |
This was my favorite "constrained generation" library, but I'm afraid it's dead. I would like to be wrong.
It's Oct 5, the last commit was >2mo ago, and maintainers have not been involved in replies, vetting Issues nor PRs, nor adding models, nor fixing bugs.
Would you please give a status report of your intentions, or archive this project?
If not, the community should direct their attention at a fork that isn't dead, although I don't know if those maintainers would be serious about carrying the torch. 2 forks have novel commits, and several github stars:
If not, some similar players in this space are actively maintained:
The text was updated successfully, but these errors were encountered: