Blueprint view with same name will be override

[steelywing]

Reproduce:

• clone https://github.com/SteelyWing/flask-blueprint-test.git
• run index.py
• open http://localhost:5000/bp-0/ , display blueprint 0 (Correct)
• open http://localhost:5000/bp-1/ , display blueprint 0 (Incorrect)
• close index.py

---

• run index.py
• open http://localhost:5000/bp-1/ , display blueprint 1 (Correct)
• open http://localhost:5000/bp-0/ , display blueprint 1 (Incorrect)
• close index.py

---

Is it the cache issue ? I tried if rename blueprint_0/index.html to blueprint_0/bp_0.html, and blueprint_1/index.html to blueprint_1/bp_1.html, all work. I also add a test of this, please have a see of THIS

[mitsuhiko]

This is documented behavior. Blueprints resolve template names globally. Their template folder should contain another level which for instance could be the name of the blueprint.

This is done so that one blueprint can provide templates for another blueprint.

[steelywing]

@mitsuhiko Thanks for reply, this pull will not break the original behavior (blueprint can provide templates for another blueprint), it only prefer to use their template, would you consider again ? =)

[mitsuhiko]

No. We had something like this originally in Flask 0.7 (before blueprints) or so and it caused problems which is why it was changed.