Conditionally abort on conflicting article paths?

[abg]

Right now it seems that if I accidentally define the same slug, one of the articles arbitrarily wins and may (depending on my ARTICLE_* settings) overwrite some other article. Ideally I would like the ability to see an error in that case as a safety check to avoid accidentally blowing away content when I publish.

Currently there's a warning for overlapping slugs in utils.process_translations, but I would like the ability for an error and non-zero exit status when overwriting other content to handle aborting in an automated publish script more easily.

[almet]

Yep, this makes sense. Including for 3.1 release.

[Rogdham]

I've started working on that: #848.

Two different things implemented:

• if several posts have the same slug and the same language, a warning is displayed to the user (before it was only for non-translation posts)
• if two templates generating files which would override a previously generated one, a critical error is displayed to the user, and pelican exits with non-zero status code

It needs more testing, in particular to know the impact on performances.

[Rogdham]

@justinmayer gave me a setting with 1419 posts to measure performances.

Before: make html 89.01s user 1.29s system 87% cpu 1:43.53 total
After: make html 89.68s user 1.26s system 90% cpu 1:41.02 total

I can conclude that it does not have bad impact on performances.