Well, at least I feel very proud to have discovered a bug. I guess someone else might have step with it before.
Sent from Samsung Mobile <div>-------- Original message --------</div><div>From: Tim Roberts <t...@probo.com> </div><div>Date:05-19-2015 12:31 PM (GMT-05:00) </div><div>To: Python-Win32 List <python-win32@python.org> </div><div>Subject: Re: [python-win32] Issues with tkinter, COM servers and Python 3.x </div><div> </div>Diego Vélez Torres wrote: > > The VALUES were an empty string and an empty bytes respectively. > > Before applying your advise, I put some 'prints' in order to > understand what is happening to 'baseName' variable. What I found was > that when I initiate an instance of tkinter app: app = tkinter.Tk() > outside a COM object (eg. directly from the interactive window), the > value was '' (I mean an empty string). The same code, but called from > a COM the value was a b'' (an empty variable of the type bytes). I > don't know if I'm answering your question. I hope I do. Absolutely, yes. Thanks. I have to think this is a bug in the Python COM interface layer, injecting a value into sys.argv without implementing the Python 3 string changes. I don't see the problem in 5 minutes of perusal, but we should get this on a bug list. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. _______________________________________________ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
_______________________________________________ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
