To support embedded use and other situations where the use of python is not desired, do whatever it takes to allow "pure C++" GNU Radio applications to be developed. When complete, there shall be no duplication of code. Rather there should be a C++ implementation of whatever primitives are required, and those primitives shall have SWIG'd python bindings available.

With regard to hierarchical blocks coded in Python, it is expected that they will remain in Python until somebody who cares recodes them in C++. At that point, there will be only a single implementation, the C++ one, with SWIG'd python bindings. The basic idea is to make this transition without multiplying the amount of code that needs to be maintained. Thus the requirement that there be only a single implementation of any given piece of functionality.