Bryan Hunt

@ceejatec @hmaarrfk - Yes this does seem to be the result of core difference between the way conda handles optional dependencies versus pip. The exclude option simply doesn't work to...

@jakirkham @moorepants Redirecting from the conversation that started at https://github.com/conda-forge/libtiff-feedstock/issues/74 After putting some more thought into this ``` I agree that is unreasonable to audit everything - but from a...

> > If the package license is already GPL then do no work otherwise the following: > > That should be, "If the package license is GPL compatible then do...

> That's not correct. You are free to distribute your own code under any license you want. It doesn't include any GPL code, so there's no problem. > > When...

This should have been originally resolved in cryptoauthlib==20221018

It would have to be tested - there are a couple of usecases for the uart usage. Kit protocol (which is basic ascii frames) and SWI which is more complicated...

Thanks for the additional details. This does make sense to modify given the SWI usecase generally revolves around removable components.

I am not sure what the error is coming from so that does requires additional investigation. The device however is properly initialized at the end. All private keys must have...

So we ended up locating the root cause for this issue so I'm updating the ticket with the findings so those that may encounter will see this comment. The basic...

We're still working on integrating toolchains so for this one I think the best path for you will be to check out the recent [AVR IoT](https://avr-iot.com/) project. [Start Examples](http://start.atmel.com/#examples) ->...