When generating local console scripts, should give user a option to decide whether add –O to ‘executable’, such as /usr/bin/python -O

Currently, after installing openstack, such as openstack/cinder, all console scripts under /usr/bin have the top one line like “#!/usr/bin/python”. This will result to a problem if only .pyo left.
Below I will take a example using cinder.
Steps to reproduce:
1. compile cinder project to pyo
# python -O -m compileall /usr/lib/python2.7/site-packages/cinder
2. rm all .py
#rm –fr `find /usr/lib/python2.7/site-packages/cinder –name “*.py”`
3. restart all cinder services

Excepted result:
4. All cinder services restart successfully
Actual result
3.All cinder services restart failed

If changing ‘/usr/bin/python’ to ‘/usr/bin/python -O’ in all cinder console scripts, then all cinder services will restart successfully.
So, I think when generating console script by pbr, It should give user a option to decide whether to add –O option in ‘executable’.