open-compass / open-compass/VLMEvalKit

Confirm whether Polygon3 is still required

Open Beginner friendly
#1,528 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
4.4k
Forks
768
Avg merge
1d 10h
Merged PRs (30d)
17

Description

Hi VLMEvalKit maintainers,

I noticed that Polygon3 is currently listed as a dependency in:

  • requirements.txt
  • vlmeval/dataset/utils/Ocrbench_v2/requirements.txt

Polygon3 includes the General Polygon Clipper (GPC) component. Its PyPI metadata lists the license as LGPL for Polygon, other for gpc and includes Other/Proprietary License, which can create issues for commercial users because GPC has separate licensing terms.

I searched the current codebase and did not find any imports or direct usage of Polygon3, polygon3, or GPC outside those requirement files. Could you confirm whether this dependency is still required?

If it is unused, I would be happy to submit a PR removing it from the requirements files. If it is only needed for a specific benchmark path, another option may be to move it out of the default install path and document it as an optional benchmark-specific dependency.

Thanks.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing requirements.txt and vlmeval/dataset/utils/Ocrbench_v2/requirements.txt, then search the repository for Polygon3, polygon3, and GPC references. Confirm whether any benchmark path depends on it; done means determining whether it can be removed from the default requirements or needs to remain documented as an optional dependency.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Refactor
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.