Asadullah Shaikh
Asadullah Shaikh
There's a workaround by adding this to `.zshrc` [Warp#2684](https://github.com/warpdotdev/Warp/issues/2684) `export PYENV_VIRTUALENV_DISABLE_PROMPT=1` This will get rid of the preceding venv prompt by disabling the venv prompt shown by pyenv
Related [#21678](https://github.com/zed-industries/zed/issues/21678) (I think) @ConradIrwin
nvm use [uv](https://github.com/astral-sh/uv)
After reading the opinions on the discussion, here's what I would recommend: - @\matchai wants a single path [in the docs], to keep things simple for non-technical users, let this...
[#6690](https://github.com/starship/starship/pull/6690)
> A more reasonable critique would be to say that this should be opt-in rather than opt-out. This (reading `.env` file) is a great feature, but not a sensible default....
for some reason smoke test pi4 is queued perennially, even before I force pushed anything
these class-level constants provide simple one-to-one aliases to constants that can be accessed at the top-level of a std-lib module - totally redundant. plus they don't belong to a class...
Since we're in beta I didn't add a deprecation warning. Do we have a formal deprecation policy? If you think this is a good idea, I can add it.
I already added backwards compatibility to the deprecation of `show_preview=True` (and `False`) yesterday But I don't see a meaningful way to "deprecate" the change in behaviour of `show_preview=None` (and `False`)...