Should installing a blueprint require importing blueprint.py?

[eyeseast]

Installing a new blueprint, and this happens:

$ tarbell install-blueprint git@github.com:frontlinepbs/fl-base-blueprint.git

Installing git@github.com:frontlinepbs/fl-base-blueprint.git

- Cloning repo
Cloning into '.'...

Requirements file found at /var/folders/cm/yyzsx0y146q8mpj8k2nq558sklvvz7/T/tmpLxqaf6/requirements.txt
Install requirements now with pip install -r requirements.txt? [Y/n] n
Not installing requirements. This may break everything! Vaya con dios.

- Found _blueprint/blueprint.py

- Name specified in blueprint.py: FRONTLINE base

+ Added new project template: FRONTLINE base

The blueprint repo gets cloned (into a temp dir). Tarbell finds requirements.txt and asks whether to install it. (I say no.) Tarbell imports blueprint.py as a module.

I think this is all so it can look up blueprint.NAME. Would it be easier to pass the blueprint name as an argument, and prompt if it's missing? Would that save many people much heartache?