a66ey, 3 months ago to python

About half a year ago I wrote myself a little #python script to automate #wikipedia #translation via #deepl.

Tried to use it on my second 💻 today, to no avail and much grinding of teeth.

I'm not setting up any more #venv . I'm fed up. I'm bloody rewriting everything, even libraries in #perl so it works proper on #unix damn it. And maybe throw a look at some #zig porting while at it.

villares, 4 months ago to python Portuguese

Será que é hoje que eu vou aprender a usar um "ambiente virtual levinho" feito com o módulo #venv do #Python?

• docs: https://docs.python.org/3/library/venv.html
• para criar: python -m venv <path_do_venv>
• para ativar, no Linux pelo menos: source <path_do_ven>
• para desativar: deactivate
• para por nos scripts .py ("shebang"):#! <path_do_env>/bin/python

alatitude77, 6 months ago to python

An unbiased evaluation of environment management and packaging tools | #dev #python #tooling #package #venv #virtualenv #pipenv #conda #pdm #poetry #hatch #rye #pyflow https://alpopkes.com/posts/python/packaging_tools/

publicvoit, 9 months ago to NixOS

TIL: #NixOS isn't compatible with my usual #Python #venv process: https://www.reddit.com/r/NixOS/comments/16bpe89/how_to_deal_with_python_venv_and_their_hardcoded/ 😩

All sorts of workarounds that either sound very dirty or require much more complexity such as docker images for simple Python scripts.

I guess I'll stick with a hard-coded Python version for now so that the path won't change. Let's learn how to accomplish that ... 🙄

#Yakshaving

Edent, 10 months ago to python

Grrr. I have a stupid #Python problem.

I use cron to trigger a script in a #venv - like so:

5 * * * * /path/to/script/bin/python /path/to/script/example.py

That works. But when the script tries to read or write a file, it uses my home directory.

Is that normal? I would have thought it would use the directory the file is in. But it appears to use the home of the user running cron.

Is there a sensible way to fix this?

setebos, 10 months ago to python

You usually want a separate virtual environment for your #python project. And it is quite annoying to activate it whenever you start your work on it.
Here is an example of how you can #automate the activation of your env with Makefile. This makes it possible to just run make go to start your project in your #venv automagically. You can also add a similar test target to run tests in the env you want by just running make tests. #makefile #development #automation #coding

djpeacher, 1 year ago (edited 1 year ago) to random

Nice, spent the last two hours #debugging an upstream #dependency issue, only for the issue to be “yanked” upstream. Thankful, but dang does my head hurt!