Changes by Alex James :
--
components: +Library (Lib) -Documentation, Extension Modules, Windows
___
Python tracker
<http://bugs.python.org/issue6290>
___
___
Alex James added the comment:
Your test prints:
'(1p1\nF1.#INF\naF-1.#INF\naF-1.IND\na.'
[inf, -inf, nan]
My installation is Python 2.6.2 as currently distributed.
Specifying protocol 1 or 2 does circumvent the error.
Thank you.
--
components: +Documentation, Extensi
Alex James added the comment:
I have now pinpointed the error to a list of infinities (see attached).
When using pickle.py to read the cPickle'd data we get a different, and
more, informative error:
ValueError: invalid literal for float(): 1.#INF
--
Added file: http://bugs.pytho
New submission from Alex James :
When using cPickle to pickle / unpickle an object instance whose
__dict__ contains a dictionary of NumPy Arrays (on a windows32 system),
some of the array elements have the wrong type raising a ValueError:
could not convert string to float.
On UNIX platform
Alex James added the comment:
Ok Jesse, that did stop the bomb problem.
Unfortunately the real code belongs in a scientific research
distributable module that is called by another function in the module
where both have been imported into the script that is run. So it isn't
being call
New submission from Alex James :
When calling multithreading.Pool().map() to distribute computational
load I've recently got system crashes.
The attached minimalist script exhibits this issue.
On a Windows Vista home premium sp1 running Python 2.6.2 on a dual-core
laptop, the script
Alex James added the comment:
Um, nevermind.
I completely missed cwd=os.path.split(sys.argv[0])[0] so the shell
command wasn't operating in the same relative path as the script.
And that never mattered on Unix because we always ran from commandline,
not IDLE, so the shell inherite
Alex James added the comment:
>>> import subprocess
>>> fileName = 'test_a5.py.out'
>>> locator = 'step 5200 '
>>> p = subprocess.Popen('findstr /O /B /C:"' + locator + '" '+
fileName, stdout=subprocess.PI
New submission from Alex James :
When calling p=subprocess.Popen(findstr "string" filename, stdout=PIPE)
both p.stdout.read() and p.communicate()[0] are returning None even when
the shell process has output (ie string was found in filename).
Further, redirecting stdout to a file wil
Changes by Alex James :
--
components: IO, Windows
nosy: ac.james
severity: normal
status: open
title: Pipes fail to return subprocess output on Windows
type: behavior
versions: Python 2.6
___
Python tracker
<http://bugs.python.org/issue6
10 matches
Mail list logo
