Updating add-on requires Orange3 re-install
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
add a comment |
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
add a comment |
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
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
python python-3.x orange
edited Nov 12 at 14:29
Primoz
4301621
4301621
asked Nov 8 at 15:34
Ralph
456
456
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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.
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 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 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 at 10:02
add a comment |
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
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.
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 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 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 at 10:02
add a comment |
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.
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 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 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 at 10:02
add a comment |
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.
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.
answered Nov 12 at 13:53
Primoz
4301621
4301621
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 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 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 at 10:02
add a comment |
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 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 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 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 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 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 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 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 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 at 10:02
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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