New submission from Harsh Patel :
We have a long-running process, which uses thread pool to get tasks and these
threads then schedule the tasks and send them to multiprocessing.Pool (with
maxtasksperchild limit set) using apply function. The original codebase is
large but I have extracted
Change by Harsh Patel :
--
title: Incorrect heapq heapify naming -> Add clarification in documentation for
incorrect heapq heapify naming
___
Python tracker
<https://bugs.python.org/issu
Harsh Patel added the comment:
This ticket is not intended to rename heapify method in the stdlib (its too
late for that). This is to merely add a clarification in the docs to state
that heapify here has a different connotation than what's used in standard
algorithmic literature
New submission from Harsh Patel :
heapify method is a misnomer in that it is actually the make-heap or build-heap
procedure from textbooks
--
components: Library (Lib)
messages: 361996
nosy: hp685
priority: normal
pull_requests: 17888
severity: normal
status: open
title: Incorrect
Harsh Patel added the comment:
I know this has been closed as "Not a bug" but it would have been convenient if
the message was broken down into multiple packets and transmitted, should it
exceed the packet limit.
Raising an exception [Errno 40 or Errno 90] or silently ignoring the