You're a fan of fewest source lines I think, but your DIRs add 2 lines, or am I mistaken?
I do not subscribe to the "fewest lines automatically wins" philosophy but I do love to be concise in my code thus my love for "ten lines or less".
- Code is more often read than written so... "Readability counts"
- Don't Repeat Yourself (DRY)
- The more concise your code is, the easier it is to understand and to debug but it must be readable
- Having clean lines is just as important as having few lines.
- Breaking your work into functions and methods will makes your code more understand and reusable.
So "wasting a few lines" to calculate DOCS_DIR and SITE_DIR up front will make the code easier to read, easier to debug, more concise and more efficient (DRY). This is all goodness in alignment with the Zen of Python.
Plist and XML ... well use what you know for one thing, but just 3 source lines to get the URL isn't pretty neat?
My favorite friends are the ones that push learn new things ;-) I think @dgelessus is trying to do that above. His idea about putting your data file on GitHub is a good one.
I don't know yaml or json... by comparison, how many source lines to do it in them? You'd have to give an example to convince me.
@dgelessus has started this above but if put your code in a GitHub repo, we can submit pull requests for you to consider.
How more human friendly are they?
A ton more human friendly (and more efficient for computers to parse too). When I worked at Sun Microsystems, I met Jon Bosak the "Father of XML" a few times and I have the utmost respect for his work. XML and its decedents have had a tremendous positive effect on computing over the years but today for these kind of projects we have better tools than XML.
Does it matter much when the user doesn't see it?
Oh yes it does!! If your goal is to build systems that last then take the time to make your work easy for yourself, your maintainer and your system administrator, as well as for your end user.