[issue6546] [Distutils][PATCH] Add bdist_rpm option to select the name of the resulting package

OG7 ony...@users.sourceforge.net added the comment: In most cases, a distribution named foo becomes and rpm named python-foo, so it can't be the same name for both. I'm using bdist_rpm to generate rpms from eggs I didn't write myself, so an option to give external control works best

[issue6615] multiprocessing logging support test

New submission from OG7 ony...@users.sourceforge.net: There is an additional test for multiprocessing's logging support here: http://code.google.com/p/python-multiprocessing/issues/detail?id=18 (disregard the fix, it is only needed for the backport). -- components: Library (Lib

[issue6546] [Distutils][PATCH] Add bdist_rpm option to select the name of the resulting package

New submission from OG7 ony...@users.sourceforge.net: This simple Distutils patch allows choosing the name of the rpm built by bdist_rpm. It leaves the name of the source tarball alone, and changes the name of the resulting spec file and rpm. It was tested with distutils nightlies, and applies

[issue5870] subprocess.DEVNULL

Changes by OG7 ony...@users.sourceforge.net: -- nosy: +OG7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5870 ___ ___ Python-bugs-list mailing

[issue6445] Add check parameter to subprocess.Popen.communicate

New submission from OG7 ony...@users.sourceforge.net: communicate is often used in one-liners, but becomes a four-liner if you want to check the process exit status. Adding a check parameter would make it more convenient to get things right and write non-buggy code. The CalledProcessError

[issue5313] multiprocessing.process using os.close(sys.stdin.fileno) instead of sys.stdin.close()

OG7 ony...@users.sourceforge.net added the comment: Please do this: --- a/multiprocessing/process.py +++ b/multiprocessing/process.py @@ -225,7 +225,8 @@ class Process(object): self._children = set() self._counter = itertools.count(1) try

[issue5331] multiprocessing hangs when Pool used within Process

OG7 ony...@users.sourceforge.net added the comment: It seems the root cause is at http://bugs.python.org/issue5155 . A workaround is to use a duplex Pipe in SimpleQueue. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5331

[issue5313] multiprocessing.process using os.close(sys.stdin.fileno) instead of sys.stdin.close()

OG7 ony...@users.sourceforge.net added the comment: Using sys.stdin.close() fixes issues 5155 and 5331. -- nosy: +OG7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5313

[issue5155] Multiprocessing.Queue created by sub-process fails when used in sub-sub-process (bad file descriptor in q.get())

OG7 ony...@users.sourceforge.net added the comment: Issue 5313 seems to be the culprit. -- nosy: +OG7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5155

[issue5313] multiprocessing.process using os.close(sys.stdin.fileno) instead of sys.stdin.close()

OG7 ony...@users.sourceforge.net added the comment: Closing the stdin fd without closing the stdin file is very dangerous. It means that stdin will now access some random resource, for example, a pipe created with os.pipe(). Closing stdin is useful to let the parent be alone in reading from