Removes the FORCE_BILLIARD_LOGGING setting, as it is no longer useful

celery/app/defaults.py

@@ -100,7 +100,6 @@ NAMESPACES = {
         'ACKS_LATE': Option(False, type='bool'),
         'ALWAYS_EAGER': Option(False, type='bool'),
         'ANNOTATIONS': Option(type='any'),
-        'FORCE_BILLIARD_LOGGING': Option(True, type='bool'),
         'BROADCAST_QUEUE': Option('celeryctl'),
         'BROADCAST_EXCHANGE': Option('celeryctl'),
         'BROADCAST_EXCHANGE_TYPE': Option('fanout'),

celery/tests/app/test_app.py

@@ -190,7 +190,6 @@ class test_App(AppCase):
         self.assertTrue(loads(dumps(self.app)))
 
     def test_autodiscover_tasks_force(self):
-        self.app.conf.CELERY_FORCE_BILLIARD_LOGGING = True
         self.app.loader.autodiscover_tasks = Mock()
         self.app.autodiscover_tasks(['proj.A', 'proj.B'], force=True)
         self.app.loader.autodiscover_tasks.assert_called_with(

docs/configuration.rst

@@ -1652,23 +1652,6 @@ Can be one of :const:`DEBUG`, :const:`INFO`, :const:`WARNING`,
 
 Default is :const:`WARNING`.
 
-.. setting:: CELERY_FORCE_BILLIARD_LOGGING
-
-CELERY_FORCE_BILLIARD_LOGGING
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. versionadded:: 3.1
-
-Celery uses :mod:`multiprocessing`'s fork called `billiard` as a pool
-implementation. Python assumes we use :mod:`multiprocessing` when trying
-to log `processName` though. By default this option forces Celery to modify
-the logger class as early as possible in order to provide correct process
-name in log messages. If you are going to use :mod:`multiprocessing` along
-with Celery, you can disable this behavior by setting
-`CELERY_FORCE_BILLIARD_LOGGING = False`.
-
-Default is :const:`True`.
-
 .. _conf-security:
 
 Security