Salvador E. Tropea

> The default approach, which works for many (but not all) macros, is to just not care about this in the macro implementation, and let MacroPy fix up (as a...

> Is there any material on `mcpy`, e.g. a user manual or similar? I have a ton of questions, but I don't want to derail the discussion here further. :)...

Just for the records: `mcpyrate` solves the problems in a clean way. The needed extra nodes are added automatically in a consistent way. You just need to manually add line...

Hi @Technologicat ! For my use `mcpyrate` is working with `Coverage.py`. The only annoying thing I have is with `pytest`, some times I need to do a `touch *.py` of...

> I agree. It would be best if this could be implemented without adding a lot of new code since this is not a very important feature. Maybe logic can...

IMHO is OK not to propagate it. Propagation of values is a hack for lazy people. You should have libraries where components has all the needed fields, and not rely...

Hi @hildogjr ! I agree with marking it as "wont fix". And I agree this issue can remain open for discussion. Maybe it could be labeled as enhancement, like you...

Hi @craigarno ! >kicost -w -i "USB-C PWR.xml" --eda kicad --include digikey --debug 8 ... DEBUG:Digi-Key API not available (kicost.distributors - log.py:115) ... This is a problem importing the Digi-Key...

Hi @craigarno ! I have no idea about this dependency problem. And this is why I kept the Digi-Key plug-in separated from KiCost: too much dependencies. Try upgrading (or reinstalling)...

Hi @craigarno ! I never tried WSL myself, but I know some KiBot users are using it. KiCost is just one of the many tools used by KiBot, so I...