wxpython pubsub fails after loading from dill










0















I use wxpython (phoenix) as frontend and wx.lib.pubsub to manage the inter-module (and inter-package) messaging in my program. I currently use the module dill to save and load the program state.



I only use the sendMessage and the subscribe methods, no fancy tricking here.



If I stay in the same session, that is, I build the model and modify it without saving and reloading the model, all works fine.
However, when restarting the GUI and starting a session from a saved file, part of the messaging that worked previously OK, fails: the messages are sent, but the receiver does not get them.
When directly calling the methods that should have been called on the receiver side, all works great, regardless of the session.



Due to the complexity of the problem I can't really provide an example, but would appreciate any effort for clarification or shared similar experiences.










share|improve this question


























    0















    I use wxpython (phoenix) as frontend and wx.lib.pubsub to manage the inter-module (and inter-package) messaging in my program. I currently use the module dill to save and load the program state.



    I only use the sendMessage and the subscribe methods, no fancy tricking here.



    If I stay in the same session, that is, I build the model and modify it without saving and reloading the model, all works fine.
    However, when restarting the GUI and starting a session from a saved file, part of the messaging that worked previously OK, fails: the messages are sent, but the receiver does not get them.
    When directly calling the methods that should have been called on the receiver side, all works great, regardless of the session.



    Due to the complexity of the problem I can't really provide an example, but would appreciate any effort for clarification or shared similar experiences.










    share|improve this question
























      0












      0








      0








      I use wxpython (phoenix) as frontend and wx.lib.pubsub to manage the inter-module (and inter-package) messaging in my program. I currently use the module dill to save and load the program state.



      I only use the sendMessage and the subscribe methods, no fancy tricking here.



      If I stay in the same session, that is, I build the model and modify it without saving and reloading the model, all works fine.
      However, when restarting the GUI and starting a session from a saved file, part of the messaging that worked previously OK, fails: the messages are sent, but the receiver does not get them.
      When directly calling the methods that should have been called on the receiver side, all works great, regardless of the session.



      Due to the complexity of the problem I can't really provide an example, but would appreciate any effort for clarification or shared similar experiences.










      share|improve this question














      I use wxpython (phoenix) as frontend and wx.lib.pubsub to manage the inter-module (and inter-package) messaging in my program. I currently use the module dill to save and load the program state.



      I only use the sendMessage and the subscribe methods, no fancy tricking here.



      If I stay in the same session, that is, I build the model and modify it without saving and reloading the model, all works fine.
      However, when restarting the GUI and starting a session from a saved file, part of the messaging that worked previously OK, fails: the messages are sent, but the receiver does not get them.
      When directly calling the methods that should have been called on the receiver side, all works great, regardless of the session.



      Due to the complexity of the problem I can't really provide an example, but would appreciate any effort for clarification or shared similar experiences.







      python-3.x dill wxpython-phoenix






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 11 '18 at 8:10









      jake77jake77

      491516




      491516






















          1 Answer
          1






          active

          oldest

          votes


















          0














          To kind of answer my own question: after trying to reproduce the issue in toy problems unsuccesfully followed by lenghty debugging the source of the problem was found to be the way certain properties were set, namely using property.setters. These have been replaced by set_ methods and the issue was resolved.



          I know this question and also the answer are well below the expected SO standard, feel free to downvote.






          share|improve this answer






















            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "1"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53246911%2fwxpython-pubsub-fails-after-loading-from-dill%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            To kind of answer my own question: after trying to reproduce the issue in toy problems unsuccesfully followed by lenghty debugging the source of the problem was found to be the way certain properties were set, namely using property.setters. These have been replaced by set_ methods and the issue was resolved.



            I know this question and also the answer are well below the expected SO standard, feel free to downvote.






            share|improve this answer



























              0














              To kind of answer my own question: after trying to reproduce the issue in toy problems unsuccesfully followed by lenghty debugging the source of the problem was found to be the way certain properties were set, namely using property.setters. These have been replaced by set_ methods and the issue was resolved.



              I know this question and also the answer are well below the expected SO standard, feel free to downvote.






              share|improve this answer

























                0












                0








                0







                To kind of answer my own question: after trying to reproduce the issue in toy problems unsuccesfully followed by lenghty debugging the source of the problem was found to be the way certain properties were set, namely using property.setters. These have been replaced by set_ methods and the issue was resolved.



                I know this question and also the answer are well below the expected SO standard, feel free to downvote.






                share|improve this answer













                To kind of answer my own question: after trying to reproduce the issue in toy problems unsuccesfully followed by lenghty debugging the source of the problem was found to be the way certain properties were set, namely using property.setters. These have been replaced by set_ methods and the issue was resolved.



                I know this question and also the answer are well below the expected SO standard, feel free to downvote.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 13 '18 at 14:22









                jake77jake77

                491516




                491516



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53246911%2fwxpython-pubsub-fails-after-loading-from-dill%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    𛂒𛀶,𛀽𛀑𛂀𛃧𛂓𛀙𛃆𛃑𛃷𛂟𛁡𛀢𛀟𛁤𛂽𛁕𛁪𛂟𛂯,𛁞𛂧𛀴𛁄𛁠𛁼𛂿𛀤 𛂘,𛁺𛂾𛃭𛃭𛃵𛀺,𛂣𛃍𛂖𛃶 𛀸𛃀𛂖𛁶𛁏𛁚 𛂢𛂞 𛁰𛂆𛀔,𛁸𛀽𛁓𛃋𛂇𛃧𛀧𛃣𛂐𛃇,𛂂𛃻𛃲𛁬𛃞𛀧𛃃𛀅 𛂭𛁠𛁡𛃇𛀷𛃓𛁥,𛁙𛁘𛁞𛃸𛁸𛃣𛁜,𛂛,𛃿,𛁯𛂘𛂌𛃛𛁱𛃌𛂈𛂇 𛁊𛃲,𛀕𛃴𛀜 𛀶𛂆𛀶𛃟𛂉𛀣,𛂐𛁞𛁾 𛁷𛂑𛁳𛂯𛀬𛃅,𛃶𛁼

                    Edmonton

                    Crossroads (UK TV series)