We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, we use the multiprocessing-logging package; see multiprocessing-logging on github. The package is initialized at the time django_elastic_migrations.utils.django_elastic_migrations_log is imported. This is a bug; we shouldn't initialize multiprocessing-logging until we are actually using multiprocessing.
multiprocessing-logging
django_elastic_migrations.utils.django_elastic_migrations_log
Initialization should be moved to DjangoMultiProcess.enter, so that when the context manager for multiprocessing opens, multiprocessing logging is started.
DjangoMultiProcess.enter
The text was updated successfully, but these errors were encountered:
#35 open multiprocessing log in context handler
3d4f449
bump 0.7.4 --> 0.7.5
781c962
* update changelog * add test stub for django elastic migrations log #35 open multiprocessing log in context handler
add basic test for multiprocessing_utils so pr coverage does not go down
fdcf226
update basic multiprocessing logging test
edfee88
1e4d4ad
codekiln
No branches or pull requests
Currently, we use the
multiprocessing-logging
package; see multiprocessing-logging on github. The package is initialized at the timedjango_elastic_migrations.utils.django_elastic_migrations_log
is imported. This is a bug; we shouldn't initializemultiprocessing-logging
until we are actually using multiprocessing.Initialization should be moved to
DjangoMultiProcess.enter
, so that when the context manager for multiprocessing opens, multiprocessing logging is started.The text was updated successfully, but these errors were encountered: