Python Best Practices for a New Project in 2021

Re:Python Best Practices for a New Project in 2021 by thundergolfer on Monday July 05, 2021 @08:14AM (#27737149)

The lack of discussion of lock files is a big omission in any 'best practices' page. "Lock" only appears in a log output of Poetry.

Even if the answer is "Poetry handles it" you certainly want to explain why they're important just like is being done in the rest of the "Why use..." sections.

[ Parent | on HN ]

Re:Python Best Practices for a New Project in 2021 by nerdponx on Monday July 05, 2021 @08:46AM (#27737391)

For a generic lockfile, use the pip-compile tool from https://pypi.org/project/pip-tools

[ Parent | on HN ]

Re:Python Best Practices for a New Project in 2021 by beaugunderson on Tuesday July 06, 2021 @02:31AM (#27744862)

Huge +1 for this; pip-compile is so much faster and less surprising than poetry. Poetry's #1 footgun is that it updates the version of unrelated dependencies when you add a new dependency. No thanks.

[ Parent | on HN ]

Re:Python Best Practices for a New Project in 2021 by pmkiwi on Tuesday July 06, 2021 @07:01PM (#27755454)

Yeap I am using pip-compile too because I always managed to mess up my environment when using poetry!

[ Parent | on HN ]

Re:Python Best Practices for a New Project in 2021 by 0x008 on Monday July 05, 2021 @05:13PM (#27741864)

Yes! Lockfiles are basically the only reason to use poetry over pip+venv or am I missing something?

[ Parent | on HN ]