Wouter Vanden Hove

> ignore all possible forms of the "export" directives ÌMHO, only needed is to skip/ignore lines starting with : ``` set -o ... set +o ... ``` no?

for now: ``` poetry export > requirements.txt uv venv uv pip install -r requirements poetry install ```

Reading this issue made me just add to my bashrc/zshrc: ``` alias uve="uv venv" alias uvp="uv pip" ``` IMHO the pip subcommand is fine, as long as a big enough...

By default, usually subcommands show help: ``` > uv pip Resolve and install Python packages Usage: uv pip [OPTIONS] Commands: compile Compile a `requirements.in` file to a `requirements.txt` file sync...

@zanieb created https://github.com/astral-sh/uv/issues/1674

for me not working at all, using doc8 v1.1.1 python 3.11.5

When not developing a python project (where the venv is managed by tools like poetry), "." is probably the most common directory I use when manually creating a venv (usually...

Can we have a solution on this please? You can move the repo to a organisation-repo and have multiple maintainers. So there is no need to grant write-access into your...

A direct git clone via ssh on the same ssh-glone url works. I use an ssh-agent running, and use named ssh-sessions like this: ``` Host gitlab.com AddKeysToAgent yes HostName gitlab.com...

This is very frustating, no verbose mode, nothing works. I can get a list of remote repos, but I cannot do anything with it, Something is missing in the docs....