New submission from Silverback Networks:
sample.py:
import sys, pdb
infile = sys.stdin.buffer
pdb.set_trace()
command line:
python -m pdb sample.py binary.exe
output:
c:\users\me\dropbox\sample.py(1)module()
- import sys, pdb
(Pdb) Traceback (most recent call last):
File C:\dev\Python\x86
Silverback Networks added the comment:
Just verified the problem on 3.4.1 as well.
--
title: pdb.set_trace() crashes when binary data is input via stdin -
pdb.set_trace() crashes with UnicodeDecodeError when binary data is input via
stdin
Silverback Networks added the comment:
OK, now that I've screwed my thinking cap back on, it's obvious that pdb in the
example is pulling from stdin. However, that isn't be the case in my original
problem, so modify the example to:
sample.py:
import sys, pdb
infile = sys.stdin.buffer.read
Changes by Silverback Networks silverback...@gmail.com:
--
nosy: +silverbacknet
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17011
___
___
Python
New submission from Silverback Networks:
ET reads a default-namespaced (xmnls=whatever) file correctly but won't write
it back out.
The error given is:
ValueError: cannot use non-qualified names with default_namespace option
The XML reference is reasonably clear on this:
http://www.w3.org/TR
Silverback Networks added the comment:
Boy, do I feel like an idiot now. An update to VC 2010 Express SP1 had
clobbered by x64 build capabilities completely, and even reinstalling the SDK
did nothing. It turns out that there's a specific hotfix you have to install to
get x64 builds working
New submission from Silverback Networks:
Once I got my broken environment fixed, this was the only thing that didn't
work. The bug is that VS 2010 no longer creates a manifest by default, despite
the documentation, and there are confirmation posts around the internet.
/Manifest has
Silverback Networks added the comment:
oops, add _debug on the second part of the patch.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16296
Silverback Networks added the comment:
Sure. I got this patch from Mercurial, just in case, but it looks the same.
--
keywords: +patch
Added file: http://bugs.python.org/file27648/msvc9manifest.diff
___
Python tracker rep...@bugs.python.org
http
Silverback Networks added the comment:
Same errors in 3.3. Some names are decorated, some aren't, seemingly at random.
For instance, python32.lib contains:
35B20 _PyObject_Dump
35B20 __imp__PyObject_Dump
and just below that,
2924A PyObject_Free
2924A __imp_PyObject_Free
Changes by Silverback Networks silverback...@gmail.com:
--
versions: +Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15772
Silverback Networks silverback...@gmail.com added the comment:
I feel like a 'tard now, it was because I was trying to print() it at the same
time I decoded it, which is what threw up. Well, sorry about that, next time
I'll be a little more careful to separate every step before I go reporting
New submission from Silverback Networks silverback...@gmail.com:
I've searched high and low to find a way to make Python accept Apple's iOS
characters, but it looks like Python is not supporting greater than 16-bit
characters correctly. If you look at the leading character of each group, it's
Changes by Silverback Networks silverback...@gmail.com:
--
title: bytes.deocde() UnicodeEncodeError on Apple iOS characters -
bytes.decode() UnicodeEncodeError on Apple iOS (16-bit) characters
___
Python tracker rep...@bugs.python.org
http
14 matches
Mail list logo
