Pyuavcan -> Nunavut migration?

[pavel.kirienko]

@scottdixon

I suppose we could move this into Nunavut and add a concept of “supporting source” that isn’t generated.

Makes sense (but see below). Surely we’re going to need something equivalent for C++ and friends as well.

@scottdixon

We’d also want to provide a packaging concept that would allow generation of python eggs or wheels, and c++ tar.bz or (perhaps) deb files.

I don’t quite follow why though. Why would one need to package autogenerated code when it can be just re-generated on-demand instead? High-DAL software comes to mind, but it is unlikely to benefit from pre-packaged units either way.

@scottdixon

if we start adding more languages the polyglot nature of this project may become unwieldy.

Yeah. Perhaps we could consider this alternative I mentioned earlier:

@pavel.kirienko

So maybe instead of templates we could ship dedicated Python modules that can be also run as CLI tools, one per target language? nnvg-python , nnvg-cpp , etc.