this post was submitted on 02 Oct 2023
108 points (99.1% liked)

Python

6413 readers
4 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

πŸ“… Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

🐍 Python project:
πŸ’“ Python Community:
✨ Python Ecosystem:
🌌 Fediverse
Communities
Projects
Feeds

founded 1 year ago
MODERATORS
top 15 comments
sorted by: hot top controversial new old
[–] [email protected] 15 points 1 year ago

itertools.batched() is pretty neat.

[–] Pyro 13 points 1 year ago
[–] [email protected] 8 points 1 year ago

This update just makes me thirstier for the next level optimizer currently in work. I think it's supposed to come out with 3.13.

[–] [email protected] 4 points 1 year ago (5 children)

How do you guys update python versions and all the libraries you have installed? I have multiple like

  • pygame
  • ptpython
  • pandas
  • Pillow
  • icecream
  • ... is it not a massive hassle to have to reinstall all of this with every new version and fight the old version on ubuntu?
[–] [email protected] 21 points 1 year ago (1 children)

Pyenv! Let the OS have its own version and work on whatever version you want, whenever.

[–] [email protected] 8 points 1 year ago* (last edited 1 year ago)

Also pipx for cli tools. It creates isolated environments for every tool you install. And upgrading is one command away pipx reinstall-all --python (your pyenv).

[–] [email protected] 9 points 1 year ago

You are 100% right, that's why we use virtual environments. Specifically we use poetry, which is fine.

[–] [email protected] 4 points 1 year ago

Conda is, to the alternative already mentioned, a great way to keep different versions of python and it's packages for each project!

[–] [email protected] 3 points 1 year ago

On Linux, I'd just build my own Python binaries and make them available. But you can also use pyenv for the same thing if you're ok with it.

Then, using poetry, I have different projects with isolated environments.

[–] [email protected] 1 points 1 year ago

The deadsnakes ppa is quite awesome

[–] [email protected] 3 points 1 year ago (1 children)

PEP 688 sounds useful. Might have to have a play.

[–] [email protected] 2 points 8 months ago (1 children)

This broke Pytest for us, not sure if it's an us problem, pytest problem, or Python 3.12 problem. Basically, it uses a ton of RAM until it gets killed by the OOM (I'm running in a Docker container w/ 3GB max RAM limit).

I'll post back when I get it working, but that's blocking our upgrade for now. Will probably revisit in a couple months after we get some projects shipped so we don't fall too far behind.

[–] [email protected] 1 points 6 months ago (1 children)

How is it going ? Did you solve it, or find the cause yet ?

[–] [email protected] 2 points 6 months ago

No, but we haven't really been trying.

Our tests are written in unittest style, but run with unit test. Unfortunately, a large number of our tests rely on fixtures, as in loading a ton of data into a SQLite database and then running code against that. That's because we have DB queries all throughout our service logic, so it's quite a bit of spaghetti to try to mock the DB logic.

So instead of trying to fix the memory issues in pytest, we're refactoring our app to separate the DB calls from our service logic, which should let us easily mock the repository in our tests.

So short answer: no. Longer answer: I might be able to tell you in a few months if this approach fixes the issue.