Task #1475 (closed)
Opened 10 years ago
Closed 8 years ago
OmeroPy threads should not be called "dummy"
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | OMERO-4.4 |
| Component: | General | Version: | 3.0-M1 |
| Keywords: | n.a. | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
For some reason, Ice initializes the thread pool under Python to "dummy-".
Change History (2)
comment:1 Changed 10 years ago by jmoore
- Milestone changed from OMERO-Beta4.2 to Unscheduled
comment:2 Changed 8 years ago by jmoore
- Milestone changed from Unscheduled to OMERO-Beta4.4
- Resolution set to wontfix
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
This isn't an Ice issue, but is hard-coded in threading.py:
# Dummy thread class to represent threads not started here. # These aren't garbage collected when they die, nor can they be waited for. # If they invoke anything in threading.py that calls current_thread(), they # leave an entry in the _active dict forever after. # Their purpose is to return *something* from current_thread(). # They are marked as daemon threads so we won't wait for them # when we exit (conform previous semantics). class _DummyThread(Thread): def __init__(self): Thread.__init__(self, name=_newname("Dummy-%d"))