74
you are viewing a single comment's thread
view the rest of the comments
[-] richieadler@lemmy.myserv.one 6 points 4 months ago

... except for the part where the dependency definition doesn't follow the latest approved PEP, and the default constraint with ^ add an upper limit that causes problems.

I moved to PDM.

[-] sugar_in_your_tea@sh.itjust.works 5 points 4 months ago

Eh, by the time I get everyone on board and convert all of our repos, poetry will probably have support for the latest PEP.

[-] richieadler@lemmy.myserv.one 2 points 4 months ago

Given the glacial pace I've been seeing, I would't be so sure... But understandable if you have many repos and need to reach consensus.

You can reduce some impacts adding explicit >= constraints instead of ^.

[-] sugar_in_your_tea@sh.itjust.works 2 points 4 months ago

The thing is, things are working reasonably well right now, so updating to be in sync with the latest PEP isn't super impactful, whereas switching from requirements.txt -> poetry and pyproject.toml was a big change. So we'll probably switch eventually, but since we have over a dozen repos and several teams across timezones, it isn't a priority.

I'll certainly take a look though.

this post was submitted on 08 Jul 2024
74 points (93.0% liked)

Python

6400 readers
12 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