Alexander Condello
Alexander Condello
Hi @ZeroDesigner, can you provide an example of the code you wish to measure?
Not at all a blocker, but worth mentioning that I don't believe any of our dependencies have `musllinux` wheels (e.g. [numpy](https://pypi.org/project/numpy/#files)). I imagine they build from source though. Edit: relevant...
Hi @henryiii , I do think that's a cool package, and we may use it in the future. However, we do currently [test](https://github.com/dwavesystems/dwave-preprocessing/blob/be12b72b1e9c8ef450f83e93b844801df641e7bd/.circleci/config.yml#L416) our [supported NumPy range](https://github.com/dwavesystems/dwave-preprocessing/blob/be12b72b1e9c8ef450f83e93b844801df641e7bd/setup.py#L63) to ensure that...
> I think you mean patch, not minor. I did mean minor. Though I agree/know that in general one needs to treat minor changes as breaking, my point was that...
I am going to transfer this issue over to our sdk, so that we can track changes across all of Ocean
Interesting. Thanks for the request! We'll look into it.
While we're making changes to CONTRIBUTING, it also currently says that all code should be python 2 and 3 compatible.
I think you're just missing `wheel`, https://pypi.org/project/wheel/
Current test failures seem to be from an interaction between https://github.com/dwavesystems/dwave-neal/pull/91 and dwave-hybrid. Can look into it next week.
> Looks good, it's just not clear to me why are we adding docs manually here, instead of using Neal's docs (with deprecation note added there)? We talked about this...