φ
whats the best practice for making a python progran nowadays ? just use uv ? ive never used it before but ive seen it shilled so i assume its good ?
Mar 6 at 1:52pmWeb
Show threadroseMar 6
don't use uv please, it unnecessarily introduces rust into a python codebase
honestly i just use a setuptools pyproject.toml
Show threadφMar 6
i see , tbh i probably wont even end up needing dependencies , so maybe i should just not use anything like that . but thanks your insight is always appreciated ^^
Show threadroseMar 6
even if you dont need dependencies i'd recommend using pyproject.toml so that its easier to install
Show threadφMar 6
does that just help you with keeping it PEP517 compliant ?
Show threadroseMar 6
Essentially yes, you can 'hardcode' a build system but afaik the general goal is to be able to replace the buildsystem configured with something else and still have it work

Show threadφMar 6
oh amazing thanks ill do that

why do ppl use uv then ? does it do anything other than providing a cargo-like cli for pypi?
Show threadroseMar 6
not really lol
its kinda just for people who just cant work without a package manager for programming languages
id call it packageslop but that makes it sound like an llm thing
Show threadmax ✦Mar 6
@fiore you dont fiore
Show threadSteffoMar 6

@fiore as long as you make it a module with pyproject.toml, there really isn't a best practice as far as package managers go

use pip, poetry, flit, uv, whatever you like more

Show threadCatpucchino Mar 6

@fiore uv manages python dependencies, versions and environments. It is like an all in one solution that works fast but it depends really on what you want to do. PEP8 is still relevant, black does a nice job as a formatter and you can tweak it as you please: https://github.com/psf/black

Pydantic is also nice to check out:
https://pydantic.com.cn/en/

Show threadφMar 6
im talking about build systems , i think ill just be normal and use setuptools
Show threadCatpucchino Mar 6
@fiore oh, my bad then