Robert Sachunsky

Duplicate of #473.

Does anyone know if [pyproject.toml](https://snarky.ca/what-the-heck-is-pyproject-toml) (replacing setup.py) could help us, or is this really a wheel-building issue?

> I'm no Python packaging expert, but It seems like the wheel was made in an environment where `opencv-python` was installed so it made its way into the wheel dependencies....

> * re-upload the wheel, making sure that the correct library (`opencv-python-headless`) is referenced in it IINM, that could be as simple as: pip download imgaug wheel unpack imgaug*.whl sed...

> I tried to use this PR for a single-class instance segmentation task, but the trained model produced more false positives. > > I looked up mrcnn_class_loss_graph and noticed that...

I am not sure if this is related: When I ignore the above errors and continue with detection, I see these: ``` >>> import layoutparser as lp ** fvcore version...

Tried with the [last stable release](https://github.com/facebookresearch/detectron2/releases/latest), i.e. `detectron2==0.3`, but still the same result.

`0.2.1` (on `torch==0.1.6`) is also the same. Note, one cannot just ignore detectron2's fvcore requirement, since it is enforced: ``` assert get_version(fvcore, 3) >= (0, 1, 2), "Requires fvcore>=0.1.2" AssertionError:...

> And `layout` is empty. That might be a specific problem of the `lp://PubLayNet/mask_rcnn_X_101_32x8d_FPN_3x/config` model. I do get non-empty results for all the other models (including ResNet-50 based PubLayNet models)...

Many thanks for your fast response! Good to know you are already onto these dependency conflicts. So am I correct in inferring these warnings don't actually do any harm? >...