Skip to content

Conversation

@hoangduytran
Copy link

maintenance and also speed up the parsing using multiprocessing option, including debugging, abort if invalid in multiprocessing as well as in linear processing mode, plus custom hook to system's exception handling to not show the frame stacks tracing. User now can just use

load_po(filename, debug=True, multiprocessing=True, hookexcept=True, batch_size_division=3 ...)

Please read the documentation of poparse.load_po() for further details.

…ntenance and also speed up the parsing using multiprocessing option, including debugging, abort if invalid in multiprocessing as well as in linear processing mode, plus custom hook to system's exception handling to not show the frame stacks tracing. User now can just use

load_po(filename, debug=True, multiprocessing=True, hookexcept=True, batch_size_division=3 ...)

Please read the documentation of poparse.load_po() for further details.
@rffontenelle
Copy link
Contributor

Logs show: ImportError: cannot import name 'poparse' from 'babel.messages'

I don't see any track of a "poparse" among babel's source code. Neither load_po. Can you explain this?

@rffontenelle
Copy link
Contributor

Ok, I found your PR python-babel/babel#1199 adding implementation of babel.messages.poparse, which seems to have been closed without a merge. If this is not going to enter babel's source code, then I guess this PR can be closed?

@shimizukawa shimizukawa linked an issue Aug 2, 2025 that may be closed by this pull request
@shimizukawa
Copy link
Member

I closed #118, so I will close this one as well.

@shimizukawa shimizukawa closed this Aug 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

babel pull 1199 failed and rejected

3 participants