【疑难解决】PaddleOCR依赖治理 #13056
【疑难解决】PaddleOCR依赖治理
#13056
Replies: 5 comments
-
Beta Was this translation helpful? Give feedback.
0 replies
-
minAreaRect 实现好像比较复杂 |
Beta Was this translation helpful? Give feedback.
0 replies
-
我觉得第四类里面的,只要没有冲突,都可以暂时不动 |
Beta Was this translation helpful? Give feedback.
0 replies
-
当前日志系统还有wandb,可以把visualdl也做成可选的 |
Beta Was this translation helpful? Give feedback.
0 replies
-
可以先对,1 待移除的包 和 2 需要移动到structure的包,动手。 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
现状
PaddleOCR依赖了两个requirements.txt,分别是根目录下的 requirement.txt 和 ppstructure/recovery/requirements.txt,过多未标明版本的依赖项会导致依赖混乱。本ISSUE以Paddle v2.6和 requirement.txt 中的信息,对PaddleOCR当前的依赖情况进行梳理,并给出优化建议。
更多相关信息参考 PaddleOCR疑难解决。
依赖信息
总结
综上,对于当前依赖的包可以进行如下分类:
其中,前三类可以优先处理。
此外,paddle框架限制numpy>=1.13, <2.0,可以发起对paddle框架进行numpy>2.0支持的活动。
Beta Was this translation helpful? Give feedback.
All reactions