#Flat project layout

1 messages · Page 1 of 1 (latest)

harsh parrot
#

It's a local PoC. Do you have thoughts?

wintry birch
#

Well, I've just started exploring dagger. We're evaluating if it can be a good replacement of our jenkins shared library that got quite complex and unmaintainable. If this would be a new and/or better way to structure things, it would be nice to use it from the start as you mention that it might be hard to "downscale" to a single script

harsh parrot
#

It's not hard at all to change, it's just that for Python newcomers not used to the ecosystem, it can get overwhelming if they need to troubleshoot. It can be documented but if people deviate a little bit from our default and aren't familiar with Python it can create friction.

#

Also, I wouldn't say the flat layout is the better way to structure the module. It seems simpler and better but has a number of issues. I've resisted that because the general best practice in Python is a src/ layout, although there's still some debate on this, especially for some specific use cases, if you know what you're doing. Since we're running in a controlled environment it can be a good fit.

Packaging a python library - Thoughts on packaging python libraries

Thoughts on packaging python libraries — Note This is about packaging libraries, not applications. ⸻ All the advice here is implemented in a project template (with full support for C...

#

Now that uv supports scripts through PEP 723 though, I figured we can support that more specifically for simpler use cases.

Python Enhancement Proposals (PEPs)
PEP 723 – Inline script metadata | peps.python.org

This PEP specifies a metadata format that can be embedded in single-file Python scripts to assist launchers, IDEs and other external tools which may need to interact with such scripts.