ragflow/deepdoc/vision
Mathias Panzenböck 1a367664f1
Remove usage of eval() from postprocess.py (#4571)
Remove usage of `eval()` from postprocess.py

### What problem does this PR solve?

The use of `eval()` is a potential security risk. While the use of
`eval()` is guarded and thus not a security risk normally, `assert`s
aren't run if `-O` or `-OO` is passed to the interpreter, and as such
then the guard would not apply. In any case there is no reason to use
`eval()` here at all.

### Type of change

- [x] Bug Fix (non-breaking change which fixes an issue)
- [x] Other (please describe):

Potential security fix if somehow the passed `modul_name` could be user
controlled.
2025-01-22 19:37:24 +08:00
..
__init__.py Update comments (#4569) 2025-01-21 20:52:28 +08:00
layout_recognizer.py Update comments (#4569) 2025-01-21 20:52:28 +08:00
ocr.py Update comments (#4569) 2025-01-21 20:52:28 +08:00
ocr.res Format file format from Windows/dos to Unix (#1949) 2024-08-15 09:17:36 +08:00
operators.py Upgrades Document Layout Analysis model. (#4054) 2024-12-17 11:27:19 +08:00
postprocess.py Remove usage of eval() from postprocess.py (#4571) 2025-01-22 19:37:24 +08:00
recognizer.py Update comments (#4569) 2025-01-21 20:52:28 +08:00
seeit.py Update comments (#4569) 2025-01-21 20:52:28 +08:00
t_ocr.py Update comments (#4569) 2025-01-21 20:52:28 +08:00
t_recognizer.py Update comments (#4569) 2025-01-21 20:52:28 +08:00
table_structure_recognizer.py Update comments (#4569) 2025-01-21 20:52:28 +08:00