I’m afraid you missed a bit the mark :(
This is the equivalent of LSP but for coding agents. So any editor does not have to rebuild an interface to support each and every new one.
HN user
I’m afraid you missed a bit the mark :(
This is the equivalent of LSP but for coding agents. So any editor does not have to rebuild an interface to support each and every new one.
Really hope for this to get traction so I’m not bound to the usual IDE
i think it's good to let them experiment! cargo (and go?) offers this already, so why not.
uv ruffy sounds funny
Wow I never realized how much mistral was “disconnected” from the ecosystem
How’s this different from xml?
Yeah. The docs tell you that you should build it yourself, but…
Litestar is really underrated but deserves much more usage! I’ve been meaning to try it for at least a year now, but always felt a bit scary to tell the team “hey let’s deviate from our stack”
Yeah they might be good but the marketing is really bold and, to a certain extent, arrogant if not outright disgusting.
BasedPyright is much better than pyright! Must use.
That’s not true, they have been developing it as red knot for a good while :)
You basically pay databricks a “fee” to choose the more appropriate and modern stack for you to build on, and keep it up to date. Never used it, but it handles with lots of the administrative bs (compliance, SLAs, idk) for you so you can just ship.
This looks so dope!
sqlalchemy doesn’t really accepts strings - if you do, you need to pass them into a “conn.execute(text(…))”, so end users should not face a breaking change.
Type checkers to the rescue ahaha I think db.get could also raise if the type does not match?
OpenAI coping so hard
he's coping so hard.
Oh you maintain PyTorch right?
Absolutely. No second thoughts.
also a whole bunch of new features (--script mode), speed of development, a stacked team.
Yes but only for linting (the flake8 rules etc). The end goal is to have proper type checking and, I think, proper LSP refactoring capabilities.
they are working on it! the internal name is currently red-knot (you can see it in their GH History and in the discord). First thing is a type checker, I think, then the renaming capabilities and such.
Super interested. Do you have an equivalent of vLLM? Did you have to rewrite batching, paged attention…?
Uuuh can you tell a bit more about wasabi, the Python LSP? Saw a post years ago and been eager to see whether it’d be open sourced (or why it wouldn’t).
Have you seen two “prototypes” of standard for LLM telemetry? One is openllmetry, maintained by the folks at TraceLoop. Seems the more popular. The other one is openinference IIRC, by Arize AI.
I wouldn't say it's an escape hatch: pip and poetry/pdm/uv serve different purposes. I am not sure what you refer to with `Pipfile`. As per the "command converter": you mean something like from `uv pip` to `uv add`?
BTW, there is a proposal to standardise the lockfile format in Python: https://discuss.python.org/t/pep-751-lock-files-again/59173/...
There's an issue about pytorch (I think you might already have seen it since you encountered this). This is still due to lack of support for pinning a package to a third party index (see https://github.com/astral-sh/uv/issues/171).
I am not sure I totally understand what you mean: yes, the lockfile might be messed up, but is the environment working? I'm a bit blessed because I don't have CUDA on my machine so I save myself a lot of hassle.
I am trying to submit an improvement to the docs about this. https://github.com/astral-sh/uv/pull/6523 I'd love to hear your feedback.
You are correct - I should've been more specific. Binding a package(s) to a third party index is currently unsupported (see issue: https://github.com/astral-sh/uv/issues/171) as it is something that pip itself does not support. PDM/Poetry implemented this on their own - though this it's an important feature and as far as I can tell it's coming.
it's an absolute beast.
They need to add a couple minor painful paths that people usually use package managers with (private indexes, binding packages to third party indexes...) but if you don't need fancy corner cases, it's the best thing ever.
Interesting! Too bad it’s just about two of them.