Use zargs to parallelize all pip-compile operations, and any project-isolated pip-sync operations. Maybe some other things like pipcheckold, if the output is or can be made human friendly.

Hi, and thanks for the great project- the guiding ideas really resonate with me.

In a better world, I would be able to only use pip to manage dependencies in Python projects, however sometimes conda is useful, either because it can handle stuff pip can't (notably different python versions per env), or because the conda packaging has better support from from the package's author (if the pip's package has exists at all).

In practice, for my projects I usually use a minimal environment.yml file:

name: myenv
channels:
  - conda-forge
  - defaults
dependencies:
  - python=3.8
  - pip
  - pip:
    - -r requirements.txt
    - -r requirements-dev.txt

If all the dependencies I need are available from pip (the best situation), they can all be managed with pip-compile. If not, I can add more dependencies to the conda file.

Is there a way to use zpy so that it integrates well with conda?
For example, in my setup conda stores envs in ~/.local/pkg/conda/envs, so zpy would need to use that, and with the name of the env, not the current hash (AFAIK conda finds myenv by checking ~/.local/pkg/conda/envs/myenv).

And use a proper framework, possibly avocado.

May be able to use the zpy function to add documentation messages to the completion functions as well.

Maybe use pelican and m.css

See pip-tools #759. Fix here will depend on how that's resolved in pip-tools.

Create with buildah, base on alpine, include python, zsh, pcregrep, fzf, micro, git, highlight, and a friendly zsh environment (maybe zulu for the simplicity/size; need to compare to prezto or others). Ensure completions and decent prompt info.

Push to dockerhub.

Consider default volume mounting.

Will allow users to quickly try the project out, either totally inside or interacting with their local system. Also will be used for better demo videos/screenshots/asciicasts.

Maybe use same container for tests.

To find candidates for changing, try rg '\(<\$'

e.g. pipz upgrade --all -- --pre where --pre is passed along to pip-compile.

• pipz upgrade
• pipz install
• pipz inject
• pipz reinstall

I'm not sure about adding it for pipz runpkg, as it might conflict with the cmd being run.

Would it make sense to make the different commands subcommands of zpy, while making the separate commands opt-out/opt-in?
My reasons are:

1. zpy <subcmd> improves discoverability of the different commands. Right now zpy subcmd has good autocomplete but prints the docs, so these will need to be moved to a new help subcommand or something (so zpy help pypc instead of zpy pypc).
2. I don't like polluting the global commands namespace, and prefer to define my own aliases for what I use most often. The current implementation forces these commands into the global namespace.

Thanks!

Currently supported backends for documentation functions:

• zsh built with --enable-pcre
• rg (ripgrep)
• pcre2grep (pcre2/pcre2-tools)
• pcregrep (pcre/pcre-tools)

ugrep is probably good enough to work as well, so I'll have a look.

My default pip-compile command is something like pip-compile --generate-hashes --allow-unsafe .... --generate-hashes guarantees that hosted versions don't change unexpectedly. --allow-unsafe, despite its name, seems to actually be the preferred way: jazzband/pip-tools#989

I just saw this update notice for the Sublime Text LSP package:

For developers working on LSP-* packages and using LSP-pyright for type-checking, it's now necessary
to tell pyright explicitly which version of Python to check against.
Do that by adding a pyrightconfig.json configuration file in the root of the LSP-* package:

{
    "pythonVersion": "3.11"
}

So it may be appropriate to set the corresponding version when calling vpypyright

Create table with comparable commands, timed, for zpy, pipenv, poetry, pipx. Pipx may need its own table.

Use data to target performance improvements.

Create:

• arch pkgbuild
• brew formula

Maybe:

• alpine abuild
• zsh plugin
• pypi distribution
• one of those awful curl-pipe options that some people actually like

Depends on #5

Related: jazzband/pip-tools#1107