Thanks for the note - can someone with build 213 for Python 3.0
installed check if they have the same problem or not (ie, if it is a
regression or just the first report of a problem existing for a few months)?
Ideally an issue should be opened at sourceforge too - I'm busy at the
moment, so may end up forgetting about then when I next find pywin32 time...
Thanks,
Mark
On 8/07/2009 5:41 PM, Elias Fotinis wrote:
From: "Mark Hammond"
I'm happy to announce the release of pywin32 build 214.
Thanks, Mark.
Last night I wanted to try Python 3.1 and was wondering when PythonWin
will come out. Nice timing!
By the way, there's a bug (causing a triple exception) in the display of
syntax errors in the interactive prompt. Seems to be a bytes/str
mismatch in winout.py (only in Python 3.x of course; the 2.x version
works fine).
Here's an example while trying to eval u'' (some paths trimmed for
brevity):
==========
PythonWin 3.1 (r31:73574, Jun 26 2009, 17:50:52) [MSC v.1500 64 bit
(AMD64)] on win32.
Portions Copyright 1994-2008 Mark Hammond - see 'Help/About PythonWin'
for further copyright information.
u''
Firing event 'ProcessEnter' failed.
Traceback (most recent call last):
File "...\Python31\lib\code.py", line 63, in runsource
code = self.compile(source, filename, symbol)
File "...\Python31\lib\codeop.py", line 168, in __call__
return _maybe_compile(self.compiler, source, filename, symbol)
File "...\Python31\lib\codeop.py", line 99, in _maybe_compile
raise SyntaxError(err1)
File "<string>", line None
SyntaxError: invalid syntax (<interactive input>, line 1)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "...\pywin\framework\interact.py", line 485, in ProcessEnterEvent
if self.interp.runsource(source, "<interactive input>"): # Need more input!
File "...\Python31\lib\code.py", line 66, in runsource
self.showsyntaxerror(filename)
File "...\pywin\framework\interact.py", line 261, in showsyntaxerror
sys.stderr.write(tracebackHeader) # So the color syntaxer recognises it.
File "...\pywin\framework\winout.py", line 177, in write
return self.template.write(msg)
File "...\pywin\framework\winout.py", line 487, in write
self.HandleOutput(message)
File "...\pywin\framework\winout.py", line 465, in HandleOutput
pos = message.rfind('\n')
TypeError: expected an object with the buffer interface
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "...\pywin\scintilla\bindings.py", line 142, in fire
rc = binding.handler(*args)
File "...\pywin\framework\interact.py", line 495, in ProcessEnterEvent
self.OutputRelease()
File "...\pywin\framework\interact.py", line 435, in OutputRelease
self.flush()
File "...\pywin\framework\winout.py", line 182, in flush
self.template.flush()
File "...\pywin\framework\winout.py", line 490, in flush
self.QueueFlush()
File "...\pywin\framework\winout.py", line 455, in QueueFlush
self.currentView.dowrite(''.join(items))
TypeError: sequence item 0: expected str instance, bytes found
==========
_______________________________________________
python-win32 mailing list
python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
_______________________________________________
python-win32 mailing list
python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
