Andy

joined 2 years ago
MODERATOR OF
 

As usual, not my own post here.

Discussion on reddit

 

I really don't know what to make of this.

Recent post on lobsters: https://lobste.rs/s/ctzngb/cosy

 

This popped up on Hacker News

https://news.ycombinator.com/item?id=43503897

 

Not my project, just sharing it.

demo

[–] Andy@programming.dev 1 points 1 year ago (2 children)

So it looks like a totally different data flow style, and (I think) geared toward writing then running programs, whereas Stacker is more for interactive stack-oriented calculator tasks.

[–] Andy@programming.dev 1 points 1 year ago (4 children)

I've never used Hy. Does it offer any concatenative-style interaction?

[–] Andy@programming.dev 6 points 1 year ago

I suggest trying this one for Zsh, over the more common one: https://github.com/zdharma-continuum/fast-syntax-highlighting

[–] Andy@programming.dev 1 points 1 year ago

As someone else said, setting less' jump value is helpful.

Another tool I use, mostly for the zshall manpage, is https://github.com/kristopolous/mansnip

[–] Andy@programming.dev 2 points 1 year ago (5 children)

Thanks, yes, I use nox and github actions for automated environments and testing in my own projects, and tox instead of nox when it's someone else's project. But for ad hoc, local and interactive multiple environments, I don't.

[–] Andy@programming.dev 1 points 1 year ago

If it didn’t bring something more to the table, besides speed, no one would care

I'm literally saying its speed in certain operations makes an appreciable difference in my workflows, especially when operating on tens of venvs at a time. I don't know why you want to fight me on my own experience.

I'm not telling anyone who doesn't want to use uv to do so. Someone asked about motivation, and I shared mine.

[–] Andy@programming.dev 2 points 1 year ago (7 children)

The convention

That's one convention. I don't like it, I prefer to keep my venvs elsewhere. One reason is that it makes it simpler to maintain multiple venvs for a single project, using a different Python version for each, if I ever want to. It shouldn't matter to anyone else, as it's my environment, not some aspect of the shared repo. If I ever needed it there for some reason, I could always ln -s $VIRTUAL_ENV .venv.

Learn pyenv

I have used pyenv. It's fine. These days I use mise instead, which I prefer. But neither of them dictate how I create and store venvs.

Shell scripts within Python packages is depreciated

I don't understand if what you're referencing relates to my comment.

[–] Andy@programming.dev 1 points 1 year ago (2 children)

I have a pip-tools wrapper thing that now optionally uses uv instead. Aside from doing the pip-tools things faster, the main advantage I've found, and what really motivated me to support and recommend uv with it, is that uv creates new venvs MUCH faster than python's venv module, which is really annoyingly slow for that operation.

[–] Andy@programming.dev 2 points 1 year ago (9 children)

I use my own Zsh project (zpy) to manage venvs stored like ~/.local/share/venvs/HASH-OF-PROJECT-PATH/venv, so use zpy's vpy function to launch a script with its associated Python executable ad-hoc, or add a full path shebang to the script with zpy's vpyshebang function.

vpy and vpyshebang in the docs

If anyone else is a Zsh fan and has any questions, I'm more than happy to answer or demo.

[–] Andy@programming.dev 1 points 1 year ago

From the author, on reddit:

Made a little mistake in there: you can create FDs with higher numbers using eg. exec {fd}<>pipe and they'll generate numbers above 10, plus the variables'll be better for scripting.

[–] Andy@programming.dev 7 points 1 year ago (1 children)

CLI flow: run command, print output below

TUI flow: navigate and interact with a layout that updates in place

view more: ‹ prev next ›