Project

General

Profile

Bug #896

MapPyGroup birth and death

Added by Jackson, Mike over 12 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
common_py
Target version:
Start date:
07 February 2012
Due date:
% Done:

100%

Estimated time:
Workflow:
Closed

Description

A possible issue?

At present MapPyGroup.death does:

        try:
            for worker in self._workers:
                assert worker.death()
        except: # pylint:disable = W0702
            return False
        return True

This means that if death of one sub-worker fails, then death won't be called on subsequent workers? Is this an issue? Will it matter that the subsequent ones won't be @death@d and possibly do their clean-up?

Also available in: Atom PDF