On Wednesday, December 14, 2011 02:27:50 PM Daniel Hyams wrote:
> On Wed, Dec 14, 2011 at 2:13 AM, Sebastian Hilbert <
> 
> [email protected]> wrote:
> > On Wednesday, December 14, 2011 02:40:44 AM Daniel Hyams wrote:
> > 
> > HI Daniel,
> > 
> > > And as far as converting to api v3, also change any 'topic' keywords to
> > > 'topicName'.
> > 
> > I agree with your summary of findings.
> > For me that would mean we would need to get pure setupv1 api working with
> > pyinstaller.
> > 
> > I have created a test case for it and here is the output after having
> > been frozen.
> > ==========================================
> > 
> > import wx._gdi_ # dynamically loaded from C:
> > \Temp\pubsub\dist\test_wxpubsub_setu
> > pv1\wx._gdi_.pyd
> > import wx._windows_ # dynamically loaded from C:
> > \Temp\pubsub\dist\test_wxpubsub_
> > setupv1\wx._windows_.pyd
> > import wx._controls_ # dynamically loaded from C:
> > \Temp\pubsub\dist\test_wxpubsub
> > _setupv1\wx._controls_.pyd
> > import wx._misc_ # dynamically loaded from C:
> > \Temp\pubsub\dist\test_wxpubsub_set
> > upv1\wx._misc_.pyd
> > 
> > Traceback (most recent call last):
> >  File "<string>", line 5, in <module>
> >  File "C:\workplace\pyinstaller-1.5.1\iu.py", line 477, in importHook
> >  
> >    mod = self.doimport(nm, ctx, ctx+'.'+nm)
> >  
> >  File "C:\workplace\pyinstaller-1.5.1\iu.py", line 521, in doimport
> >  
> >    exec co in mod.__dict__
> >  
> >  File "c:
> > \Temp\pubsub\build\pyi.win32\test_wxpubsub_setupv1\outPYZ1.pyz/wx.lib.
> > pubsub.setupv1", line 16, in <module>
> > 
> >  File "c:
> > \Temp\pubsub\build\pyi.win32\test_wxpubsub_setupv1\outPYZ1.pyz/wx.lib.
> > pubsub.pubsubconf", line 16, in setVersion
> > 
> >  File "c:
> > \Temp\pubsub\build\pyi.win32\test_wxpubsub_setupv1\outPYZ1.pyz/wx.lib.
> > pubsub.pubsubconf", line 51, in setVersion
> > AssertionError
> > RC: -1 from test_wxpubsub_setupv1
> > OK.
> > 
> > ===========================================
> > 
> > Interestingly (but that really is another problem) when I use the arg1
> > api in
> > unfrozen state it works just fine for GNUmed. However when using arg1 in
> > frozen
> > mode it freezes ok but does not run properly due to complaints about the
> > syntax in subscribe() statements.
> 
> Can you post what syntax error you are getting there?

something about invalid listener. function 
_signal_debugging_monitor_pubsub(self, mssg):

cannot take any arguments , got mssg.


The strange thing about it is that I have no clue why this happens. i have 
another listener in there which listens for topic 'statustext' and it is 
working just find.

code in question

#----------------------------------------------
        def _signal_debugging_monitor_pubsub(self, mssg):
                print "wx.lib.pubsub message:"
                print mssg.topic
                print mssg.data

Here is the call to the listener

if _cfg.get(option = 'debug'):
                        gmDispatcher.connect(receiver = 
self._signal_debugging_monitor)
                        _log.debug('connected old signal monitor')
                        #wx.lib.pubsub.Publisher().subscribe(listener = 
self._signal_debugging_monitor_pubsub) # this was v1 api
                        
Publisher.subscribe(self._signal_debugging_monitor_pubsub, 
Publisher.ALL_TOPICS)
                        
I commented out v1 api and replaced it by the line below.

I wonder which message is actually caught by ALL_TOPICS. I have a feeling that 
this has something to do with

http://pubsub.sourceforge.net/apidocs/more_advanced_use.html#message-data-
specification-mds

If I run GNUmed without 'debug' enabled it will not initiate the listener for 
'ALL_TOPICS' and run just fine.

I am trying to find out what exactly is happening in the listener for 
ALL_TOPICS and why it seems to be invalid.

Next step will be to create a small example.

Sebastian

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pyinstaller?hl=en.

Reply via email to