F-G Fernandez

I just checked and weasyprint does have a conda build now :raised_hands: https://anaconda.org/conda-forge/weasyprint (But I still think we should move it to extra builds)

Thanks for reporting this! I'm not sure which way would be the best, but here are some ideas to handle this: - **Batch post-processing**: NMS to perform with a looser...

@charlesmindee Thanks for the suggestion! However when I suggested an NMS, I thinking about the iterative merging implementation of it So I fully agree that pure filtering won't be enough....

Coming back to this issue, I suggest the following: - Investigate the heatmap of the text detection module to assess whether this comes from the segmentation or box conversion part...

Thanks for reporting it! If M1 MacOS users are getting more common, we indeed have to handle this. However if this is correct, it seems the issue is due to...

Thanks for investigating @fharper :pray: We'll have to think about a way to counter this, the quick fix of adding constraints on the python version is quite heavy on other...

Thanks @fharper :pray: Have you followed some tutorials or guidelines from a specific resource? If not, is keras preprocessing required to build TF?

I've checked online, and here is what I found about DL framework support on M1 chips: - TensorFlow: https://towardsdatascience.com/installing-tensorflow-on-the-m1-mac-410bb36b776, https://betterprogramming.pub/installing-tensorflow-on-apple-m1-with-new-metal-plugin-6d3cb9cb00ca - PyTorch: https://github.com/pytorch/pytorch/issues/47702#issuecomment-965625139

Oh yeah, it's more for tracking purposes :+1: Considering the efforts that people have to put into this to make it work on M1 chips, I wouldn't advise jumping back...

Hi @fharper :wave: I think that with #749, you might be able to install everything smoothly! When you have some time, could you try? That would help us close this...