|
|
|
|
|
by idoubtit
1260 days ago
|
|
From the sibling thread about packaging and deploying a single script, there was no consensus. There was disagreement on the best way to package, and doubts about the mid term future of some suggested solutions. The following alternatives were suggested: - package with a `pyproject.toml` file configured to use modern tooling - package with a `pyproject.toml` file configured to use traditional `setup.py` tooling - package with traditional `setup.py` tooling - package with poetry - package with whatever, deploy with nuikta or pipx - skip the packaging and deploy with Pyinstaller - skip the packaging and deploy with nikta Note that, unless the Python world has radically changed while I was looking away, the packaging does not ensure a simple way to deploy the package and its single script. I remember vividly `pipenv` crashing on me, so switching to venv+pip (or was it virtualenv+pip?) then setting up a bash wrapper to call the Python script with the right venv... |
|