Conversation
|
@MaksymTkachuk Looks like there is a failing test in here - @julian-smith-artifex-com might have some ideas |
|
@jamie-lemon |
|
julian-smith-artifex-com
left a comment
There was a problem hiding this comment.
Also please see my comments on the main page.
setup.py
Outdated
| zip_safe=False, | ||
| install_requires=load_requirements("requirements.txt"), | ||
| python_requires=">=3.6", | ||
| python_requires=">=3.14", |
There was a problem hiding this comment.
Is this right? Current supported python versions are 3.10-3.14 so i would have expected >=3.10 ?
There was a problem hiding this comment.
Currently, I am using 3.11. Is it ok?
There was a problem hiding this comment.
Ok. I updated it from 3.11 to 3.10.
|
Hi @jamie-lemon @julian-smith-artifex-com
|
julian-smith-artifex-com
left a comment
There was a problem hiding this comment.
What do you think about points 2 and 5 in my earlier message? (About the added+removed test_extract_tables_issue_358_err_table() test, and the seemingly missing input file test/samples/issue-358-err_table.pdf.)
.github/workflows/test.yml
Outdated
| python-version: ["3.8", "3.9", "3.10"] | ||
| python-version: ["3.10", "3.11", "3.12"] |
There was a problem hiding this comment.
We should probably test on all supported python versions, currently 3.10-3.14.
There was a problem hiding this comment.
I added python versions.
["3.10", "3.11", "3.12"] -> ["3.10", "3.11", "3.12", "3.13", "3.14"]
I added test_extract_tables_issue_358_err_table() into unit-test. it's working now. |
e831e40 to
d570be7
Compare
- Update GitHub Actions workflows to use Python 3.10+ (required for PyMuPDF 1.26.7) - Add setuptools/wheel installation in test workflow - Fix artifact naming conflict by including Python version in artifact names - Update PyPI publish action to use stable release/v1 tag - Fixed bug when extracting tables with empty cells, see test_extract_tables_empty_cell(). - Update requirements.txt to use PyMuPDF>=1.26.7 - Update setup.py python_requires to >=3.10
d570be7 to
33a6ded
Compare
#358
While testing with the document from issue #358 using this code, I encountered an error. I’ve added some fixes to address it.