Dev scripts

[kotleni]

Do we really need to use minishell for such a simple scripts?

Out of the box I even can't use them:

kotleni@archpc-kotleni  ~/Projects/web   feat/standalone-docker  ./scripts/branch dev
Traceback (most recent call last):
  File "/home/kotleni/Projects/web/./scripts/branch", line 2, in <module>
    from minishell import shell
ModuleNotFoundError: No module named 'minishell'

Also on modern Linux distros you can't just install package from pip system-wide without venv.

kotleni@archpc-kotleni  ~/Projects/web   feat/standalone-docker  pip3 install minishell     
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try 'pacman -S
    python-xyz', where xyz is the package you are trying to
    install.
    
    If you wish to install a non-Arch-packaged Python package,
    create a virtual environment using 'python -m venv path/to/venv'.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip.
    
    If you wish to install a non-Arch packaged Python application,
    it may be easiest to use 'pipx install xyz', which will manage a
    virtual environment for you. Make sure you have python-pipx
    installed via pacman.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

[kotleni]

I understand why you prefer to use this, but I don't think that its convenient to use for other developers (strangers).

[y9san9]

The thing is that I don't understand how it's getting in the way being version controlled. If it does, I can move them to my local .nvim folder that I have for each project and that is gitignored.

These scripts are usually convenient for people who are used to CLI dev and it's fine you are not one of them. On some other (private) projects I share these scripts and several people use them, I use their scripts.

So it's a good extension for people who are used to CLI and want to follow our workflow processes. If regular people prefer to do things by hand, it's also fine but does these scripts there hurt someone?

[kotleni]

The thing is that I don't understand how it's getting in the way being version controlled. If it does, I can move them to my local .nvim folder that I have for each project and that is gitignored.

These scripts are usually convenient for people who are used to CLI dev and it's fine you are not one of them. On some other (private) projects I share these scripts and several people use them, I use their scripts.

So it's a good extension for people who are used to CLI and want to follow our workflow processes. If regular people prefer to do things by hand, it's also fine but does these scripts there hurt someone?

You misunderstood me. I am not against these scripts, I live in a CLI environment >80% of my time spend at the computer xD
I was just complaining about using python with a external dependency in such a small scripts.

Just a joke:

NixOS users may find `--break-system-packages` offensive.

[kotleni]

@y9san9 :c

[y9san9]

@kotleni people familiar with python ecosystem will be able to use it easily.

To install that package you don't need to create any global environments. Instead you need to use pip3 install --break-system-packages --user minishell. This will not break system packages as minishell is not uploaded to any other package manager than PIP.

This warning was introduced because people started (ab)using pip3 to upload their executables there. minishell is not one and it is a Python library that is needed to be installed globally like this. Exception to that rule. After you run the command above, you can launch scripts via

scripts/push without any python scripts/push or so (like other bash scripts).