-
Notifications
You must be signed in to change notification settings - Fork 5
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
Merge the gilt and go-gilt projects #107
Comments
Yeah, it's been done for Taskfile as well. @0xDEC0DE it looks like ruff uses maturin which seems magical. Do you know if there is anything similar for golang? I don't think it's as easy as embedding various go binaries in the pip package, and go-task-bin looks to build the binary on install. |
Agree... I should have just merged them originally, but at the time I didn't think I would deprecate the python version. |
How on earth did I miss this comment? No, I really don't know how it's done. But looking at the wheel package format, it appears that it's really is simply a matter of putting your built binaries in specifically-named directories, and they'll land in the venv where they need to. Getting the metadata, etc., right seems to be the REAL trick. I've gone all-in on Hatch for Python packaging lately, but this kind of thing seems "challenging" to do with that toolchain. The Or not. I don't know. 😆 |
Maybe we could create a new issue for this specific ask? However, I could probably use your help with this. |
That's what the original issue was about! 😆 |
Yeah, I had looked at the title yesterday and had forgotten about all the original request, sorry about that. |
Tools like ruff have shown that it is possible to have non-Python tools that leverage the Python ecosystem (installation via
pip
, automatic hash checking, etc.), and can even become wildly popular in doing so.Gilt should attempt to take a page from that playbook, and as a side-effect, unify the schism between implementations.
I'd advocate for putting everything in the "other" repo and retiring this one, but Your House, Your Rules™.
The text was updated successfully, but these errors were encountered: