Updating add-on requires Orange3 re-install










2















I created an add-on on PyPI.org and can successfully import it in Orange 3.17 for Mac OSX. However, when I make a small change to the code I cannot get Orange3 to pick up the changes. It keeps referring to some cached version of the add-on.



Even when you select "Reset Widget settings" in the "Options" menu or even physically delete the ~/Library/Caches/Orange3 files, the old version keeps popping up. I uninstalled the previous add-on, then re-installed the latest version, all the while restarting Orange3. I tried many different combinations to get Orange3 to see the changes. But to no avail.



The only thing that seems to work is to completely remove Orange3 from my PC and re-install it completely. If I load the add-on then, I get the latest version with the updated code.



Is there an explanation for this behaviour? If I'm testing my add-on it's bit cumbersome to have to re-install Orange3 all the time.



Any help would be very much appreciated!



Cheers










share|improve this question




























    2















    I created an add-on on PyPI.org and can successfully import it in Orange 3.17 for Mac OSX. However, when I make a small change to the code I cannot get Orange3 to pick up the changes. It keeps referring to some cached version of the add-on.



    Even when you select "Reset Widget settings" in the "Options" menu or even physically delete the ~/Library/Caches/Orange3 files, the old version keeps popping up. I uninstalled the previous add-on, then re-installed the latest version, all the while restarting Orange3. I tried many different combinations to get Orange3 to see the changes. But to no avail.



    The only thing that seems to work is to completely remove Orange3 from my PC and re-install it completely. If I load the add-on then, I get the latest version with the updated code.



    Is there an explanation for this behaviour? If I'm testing my add-on it's bit cumbersome to have to re-install Orange3 all the time.



    Any help would be very much appreciated!



    Cheers










    share|improve this question


























      2












      2








      2








      I created an add-on on PyPI.org and can successfully import it in Orange 3.17 for Mac OSX. However, when I make a small change to the code I cannot get Orange3 to pick up the changes. It keeps referring to some cached version of the add-on.



      Even when you select "Reset Widget settings" in the "Options" menu or even physically delete the ~/Library/Caches/Orange3 files, the old version keeps popping up. I uninstalled the previous add-on, then re-installed the latest version, all the while restarting Orange3. I tried many different combinations to get Orange3 to see the changes. But to no avail.



      The only thing that seems to work is to completely remove Orange3 from my PC and re-install it completely. If I load the add-on then, I get the latest version with the updated code.



      Is there an explanation for this behaviour? If I'm testing my add-on it's bit cumbersome to have to re-install Orange3 all the time.



      Any help would be very much appreciated!



      Cheers










      share|improve this question
















      I created an add-on on PyPI.org and can successfully import it in Orange 3.17 for Mac OSX. However, when I make a small change to the code I cannot get Orange3 to pick up the changes. It keeps referring to some cached version of the add-on.



      Even when you select "Reset Widget settings" in the "Options" menu or even physically delete the ~/Library/Caches/Orange3 files, the old version keeps popping up. I uninstalled the previous add-on, then re-installed the latest version, all the while restarting Orange3. I tried many different combinations to get Orange3 to see the changes. But to no avail.



      The only thing that seems to work is to completely remove Orange3 from my PC and re-install it completely. If I load the add-on then, I get the latest version with the updated code.



      Is there an explanation for this behaviour? If I'm testing my add-on it's bit cumbersome to have to re-install Orange3 all the time.



      Any help would be very much appreciated!



      Cheers







      python python-3.x orange






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 12 '18 at 14:29









      Primoz

      5381624




      5381624










      asked Nov 8 '18 at 15:34









      RalphRalph

      456




      456






















          1 Answer
          1






          active

          oldest

          votes


















          2














          When you install your add-on with pip it normally copies the source code somewhere else in the environment that Orange is using. If you want to develop add-on and see the changes directly in Orange you can register your addon with the following command:



          pip install -e .


          while standing in the root directory of the addon. You must have the Orange's virtual environment activated. -e option will tell pip not to copy the source but to use the code from the directory where you are developing the add-on.



          When changes are pushed to PyPI you can update the add-on from the Orange's Add-ons dialog (Options>Add-ons) with checking the add-on which is updated or you can use the pip command:



          pip install --upgrade <add-on name>


          You must have Orange's virtual environment activated.



          For development, I am suggesting to use the version of Orange from GitHub. You can install it following to instructions.






          share|improve this answer























          • Thanks for the suggestion. Unfortunately, my users do not have the option (nor skills) to run anything from the command-line and I'd like to test the add-on in Orange3 just like they would use it.

            – Ralph
            Nov 13 '18 at 17:16











          • When you are developing you can use suggested way but yes when you test the add-on for users you upload a new version to PyPI and then you and users can install it from the menu.

            – Primoz
            Nov 14 '18 at 15:44











          • Just as a follow-up: when you try to simply update the add-on by clicking the minus sign to the left of it, it says "Update" but actually doing that (and restarting) does not have any effect. When you check the add-ons again, the add-on is still highlighted for updating, e.g., 0.0.8 < 0.0.9. This smells like a bug to me...

            – Ralph
            Nov 15 '18 at 10:02










          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%2f53211063%2fupdating-add-on-requires-orange3-re-install%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









          2














          When you install your add-on with pip it normally copies the source code somewhere else in the environment that Orange is using. If you want to develop add-on and see the changes directly in Orange you can register your addon with the following command:



          pip install -e .


          while standing in the root directory of the addon. You must have the Orange's virtual environment activated. -e option will tell pip not to copy the source but to use the code from the directory where you are developing the add-on.



          When changes are pushed to PyPI you can update the add-on from the Orange's Add-ons dialog (Options>Add-ons) with checking the add-on which is updated or you can use the pip command:



          pip install --upgrade <add-on name>


          You must have Orange's virtual environment activated.



          For development, I am suggesting to use the version of Orange from GitHub. You can install it following to instructions.






          share|improve this answer























          • Thanks for the suggestion. Unfortunately, my users do not have the option (nor skills) to run anything from the command-line and I'd like to test the add-on in Orange3 just like they would use it.

            – Ralph
            Nov 13 '18 at 17:16











          • When you are developing you can use suggested way but yes when you test the add-on for users you upload a new version to PyPI and then you and users can install it from the menu.

            – Primoz
            Nov 14 '18 at 15:44











          • Just as a follow-up: when you try to simply update the add-on by clicking the minus sign to the left of it, it says "Update" but actually doing that (and restarting) does not have any effect. When you check the add-ons again, the add-on is still highlighted for updating, e.g., 0.0.8 < 0.0.9. This smells like a bug to me...

            – Ralph
            Nov 15 '18 at 10:02















          2














          When you install your add-on with pip it normally copies the source code somewhere else in the environment that Orange is using. If you want to develop add-on and see the changes directly in Orange you can register your addon with the following command:



          pip install -e .


          while standing in the root directory of the addon. You must have the Orange's virtual environment activated. -e option will tell pip not to copy the source but to use the code from the directory where you are developing the add-on.



          When changes are pushed to PyPI you can update the add-on from the Orange's Add-ons dialog (Options>Add-ons) with checking the add-on which is updated or you can use the pip command:



          pip install --upgrade <add-on name>


          You must have Orange's virtual environment activated.



          For development, I am suggesting to use the version of Orange from GitHub. You can install it following to instructions.






          share|improve this answer























          • Thanks for the suggestion. Unfortunately, my users do not have the option (nor skills) to run anything from the command-line and I'd like to test the add-on in Orange3 just like they would use it.

            – Ralph
            Nov 13 '18 at 17:16











          • When you are developing you can use suggested way but yes when you test the add-on for users you upload a new version to PyPI and then you and users can install it from the menu.

            – Primoz
            Nov 14 '18 at 15:44











          • Just as a follow-up: when you try to simply update the add-on by clicking the minus sign to the left of it, it says "Update" but actually doing that (and restarting) does not have any effect. When you check the add-ons again, the add-on is still highlighted for updating, e.g., 0.0.8 < 0.0.9. This smells like a bug to me...

            – Ralph
            Nov 15 '18 at 10:02













          2












          2








          2







          When you install your add-on with pip it normally copies the source code somewhere else in the environment that Orange is using. If you want to develop add-on and see the changes directly in Orange you can register your addon with the following command:



          pip install -e .


          while standing in the root directory of the addon. You must have the Orange's virtual environment activated. -e option will tell pip not to copy the source but to use the code from the directory where you are developing the add-on.



          When changes are pushed to PyPI you can update the add-on from the Orange's Add-ons dialog (Options>Add-ons) with checking the add-on which is updated or you can use the pip command:



          pip install --upgrade <add-on name>


          You must have Orange's virtual environment activated.



          For development, I am suggesting to use the version of Orange from GitHub. You can install it following to instructions.






          share|improve this answer













          When you install your add-on with pip it normally copies the source code somewhere else in the environment that Orange is using. If you want to develop add-on and see the changes directly in Orange you can register your addon with the following command:



          pip install -e .


          while standing in the root directory of the addon. You must have the Orange's virtual environment activated. -e option will tell pip not to copy the source but to use the code from the directory where you are developing the add-on.



          When changes are pushed to PyPI you can update the add-on from the Orange's Add-ons dialog (Options>Add-ons) with checking the add-on which is updated or you can use the pip command:



          pip install --upgrade <add-on name>


          You must have Orange's virtual environment activated.



          For development, I am suggesting to use the version of Orange from GitHub. You can install it following to instructions.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 12 '18 at 13:53









          PrimozPrimoz

          5381624




          5381624












          • Thanks for the suggestion. Unfortunately, my users do not have the option (nor skills) to run anything from the command-line and I'd like to test the add-on in Orange3 just like they would use it.

            – Ralph
            Nov 13 '18 at 17:16











          • When you are developing you can use suggested way but yes when you test the add-on for users you upload a new version to PyPI and then you and users can install it from the menu.

            – Primoz
            Nov 14 '18 at 15:44











          • Just as a follow-up: when you try to simply update the add-on by clicking the minus sign to the left of it, it says "Update" but actually doing that (and restarting) does not have any effect. When you check the add-ons again, the add-on is still highlighted for updating, e.g., 0.0.8 < 0.0.9. This smells like a bug to me...

            – Ralph
            Nov 15 '18 at 10:02

















          • Thanks for the suggestion. Unfortunately, my users do not have the option (nor skills) to run anything from the command-line and I'd like to test the add-on in Orange3 just like they would use it.

            – Ralph
            Nov 13 '18 at 17:16











          • When you are developing you can use suggested way but yes when you test the add-on for users you upload a new version to PyPI and then you and users can install it from the menu.

            – Primoz
            Nov 14 '18 at 15:44











          • Just as a follow-up: when you try to simply update the add-on by clicking the minus sign to the left of it, it says "Update" but actually doing that (and restarting) does not have any effect. When you check the add-ons again, the add-on is still highlighted for updating, e.g., 0.0.8 < 0.0.9. This smells like a bug to me...

            – Ralph
            Nov 15 '18 at 10:02
















          Thanks for the suggestion. Unfortunately, my users do not have the option (nor skills) to run anything from the command-line and I'd like to test the add-on in Orange3 just like they would use it.

          – Ralph
          Nov 13 '18 at 17:16





          Thanks for the suggestion. Unfortunately, my users do not have the option (nor skills) to run anything from the command-line and I'd like to test the add-on in Orange3 just like they would use it.

          – Ralph
          Nov 13 '18 at 17:16













          When you are developing you can use suggested way but yes when you test the add-on for users you upload a new version to PyPI and then you and users can install it from the menu.

          – Primoz
          Nov 14 '18 at 15:44





          When you are developing you can use suggested way but yes when you test the add-on for users you upload a new version to PyPI and then you and users can install it from the menu.

          – Primoz
          Nov 14 '18 at 15:44













          Just as a follow-up: when you try to simply update the add-on by clicking the minus sign to the left of it, it says "Update" but actually doing that (and restarting) does not have any effect. When you check the add-ons again, the add-on is still highlighted for updating, e.g., 0.0.8 < 0.0.9. This smells like a bug to me...

          – Ralph
          Nov 15 '18 at 10:02





          Just as a follow-up: when you try to simply update the add-on by clicking the minus sign to the left of it, it says "Update" but actually doing that (and restarting) does not have any effect. When you check the add-ons again, the add-on is still highlighted for updating, e.g., 0.0.8 < 0.0.9. This smells like a bug to me...

          – Ralph
          Nov 15 '18 at 10:02



















          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%2f53211063%2fupdating-add-on-requires-orange3-re-install%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

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

          Crossroads (UK TV series)

          ữḛḳṊẴ ẋ,Ẩṙ,ỹḛẪẠứụỿṞṦ,Ṉẍừ,ứ Ị,Ḵ,ṏ ṇỪḎḰṰọửḊ ṾḨḮữẑỶṑỗḮṣṉẃ Ữẩụ,ṓ,ḹẕḪḫỞṿḭ ỒṱṨẁṋṜ ḅẈ ṉ ứṀḱṑỒḵ,ḏ,ḊḖỹẊ Ẻḷổ,ṥ ẔḲẪụḣể Ṱ ḭỏựẶ Ồ Ṩ,ẂḿṡḾồ ỗṗṡịṞẤḵṽẃ ṸḒẄẘ,ủẞẵṦṟầṓế