Closed Don-Yin closed 2 years ago
Thanks a lot for reporting this! Indeed, it is due to the bug that you pointed out. I am quite puzzled why this bug has "manifested" only now, I would have excepted this situation to occur more often. Maybe I accidentally created it in the last version....
I fixed the bug by making sure that the functions extract_doi_from_text
and extract_arxivID_from_text
return an empty list instead of None when nothing is found. I also fixed the deprecates sintaxes that you pointed out. Thanks again!
I released the version 1.2rc1 on pypi, would you mind testing it on this pdf file again?
pip install pdf2doi==1.2rc1
Thank you for responding! It is now operational! Well done! Thank you for this fantastic project.
same problem
same problem
alexmaehon, do you still get this error after upgrading to version 1.2rc1? If yes, can you send me the PDF file and the full traceback?
Thank you for responding! It is now operational! Well done! Thank you for this fantastic project.
Excellent, thanks for your help! I will release the 1.2 version later today, then.
This bug was fixed with version 1.2
There appears to be a type error in "finder.py" that only emerges on certain PDF files. This one, for example: paper12.2009_unknown_040916_440842.pdf
A miniumn code snippet for reproducing this error:
Where the PDF is placed in the example folder.
Here is the error message:
I thought I fixed this error by adding:
at line 286 of your "finder.py", so that it becomes:
But this was a bit hacky and not the proper solution. You'd undoubtedly know more about what's going on, so I thought I'd let you know about this.
And by the way, there are some deprecated syntax that you might want to address:
cheers, Don