-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors while importing ParsingExceptions from megaparse.exceptions.base #217
Comments
bryanhughes
changed the title
Errors while ParsingExceptions from megaparse.exceptions.base
Errors while importing ParsingExceptions from megaparse.exceptions.base
Jan 10, 2025
Hi Bryan, Thank you for creating this issue, I found the reason why and solved it in #218 which will be merged and released soon ! |
Merged
Hi!
I used the PyPi package. Here are the versions:
pip list | grep megaparse
megaparse 0.0.52
megaparse-sdk 0.1.10
I am not sure what other steps I can take help debug, but please let me
know. How I am capturing everything is that I set a debug point on the
import statement and then step over it. I am using Pycharm Professional
24.3.1.1.
If there are more steps to help, please let me know.
Cheers,
Bryan
On January 13, 2025 at 7:17:01 AM, Chloé Daems ***@***.***) wrote:
Hi Bryan, Thank you for creating this issue, I cannot manage to replicate
this error, are you using the PyPi package megaparse of did you clone the
repository ?
On my hand the two seem to not throw the same error as you when running from
megaparse.exceptions.base import ParsingException.
Could you give me the version of megaparse you are using ?
—
Reply to this email directly, view it on GitHub
<#217 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAFFXXX5JQ5XXVMSUM7XB32KPKG3AVCNFSM6AAAAABU5ORQHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBXGM4TCNRRGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
No worries, it is a logging error, I fixed it in the new PR and it should be solved in the next release (end of the week). In the meantime you can just remove |
Wow. Thank you for the prompt fix!!! So far I am loving Megaparse. Great
work - very solid.
On January 13, 2025 at 8:25:15 AM, Chloé Daems ***@***.***) wrote:
No worries, it is a logging error, I fixed it in the new PR and it should
be solved in the next release (end of the week). In the meantime you can
just remove logger.info("Available providers:", prov) in doctr_parser.py
file in the lib folder :)
—
Reply to this email directly, view it on GitHub
<#217 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAFFXVT26MGNRBXIU26IOL2KPSGXAVCNFSM6AAAAABU5ORQHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBXGU4DKNBUGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just loading my module is producing all these issues:
The text was updated successfully, but these errors were encountered: