Delivery: compute publishedBasename before destination path validation

[jakubjezek001]

Changelog Description

Delivery now computes the publishedBasename template key (via pathlib.Path) before validating the destination path, instead of after. Previously, destination validation ran before publishedBasename was set, so templates relying on that key always failed the check.

Additional info

• Sequences: basename is derived from the first source file with the frame number and trailing separators stripped.
• Single files: basename is used as-is.

Testing notes:

1. Deliver a sequence representation using a template containing {publishedBasename} and confirm the destination path resolves and validates correctly.
2. Deliver a single-file representation using a template containing {publishedBasename} and confirm the same.

Dependency

Close #1934
YN-0905

[BigRoy]

I actually my doubts about still manipulating the publishedBasename like stripping of the frame numer.

First replace(first_frame, "") is a wrong assumption.

If my shot is 1100 and the first frame happens to be 1100 then suddenly I'm also removing the shot name from the shot.

What's the reason we can't just have publishedFilename be the full source filename?

So essentially:

published_filename = os.path.basename(source)

And that's it. It doesn't make much sense to use {publishedFilename} with any other tokens (unless you want to prefix it perhaps) but at least it's very clear what it does, it's the full filename of the file we're copying over?

[jakubjezek001]

but how do you deal with frames and what if you want to renumber frames?

[BigRoy]

In that scenario you wouldn't renumber frames - you'd get the exact filename that lives in the publish directory essentially.

@iLLiCiTiT thoughts? am I oversimplifying?