Issue description
The NAMESPACE_BEGIN is very generic name and therefor there could be the name clash (for instance CryptoPP does use the NAMESPACE_BEGIN also).
It could be fixed renaming the NAMESPACE_BEGIN -> PYBIND11_NAMESPACE_BEGIN. I think this is the only macro that hasn't the PYBIND11 prefix.