I saw a repo the other day that had these files in it. ``` requirements.txt requirements-in.txt dev-requirements.txt dev-requirements-in.txt ``` It threw me off.

Vincent D. Warmerdam

Python projects should name development requirements files as 'requirements-dev.txt' instead of 'dev-requirements.txt' to maintain visual grouping with production requirements files. This naming convention keeps related dependency files together in directory listings, making them easier to spot and manage. While functionally identical, proper naming improves code organization and reduces the risk of overlooking development dependencies.

dev-requirements.txt is bad

Python should move to toml and standardize uv practices

I know people who took this to the extreme with prefixing every file with numbers.
<pre><code>00-index.html
10-styles.css
</code></pre>
I generally agree with the notion of the post but i also think that focussing too much on these “sidetopics” of a project can lead to more complexity and not less.
Nobody is going pay you for having the right order of files 😅.

Good one thank you for sharing 😊

Also storing dependencies in txt is a things that bothers me a little bit in python, what is your take on this?