Visual Studio does not use current PTVSD version
up vote
0
down vote
favorite
Setup
I use Visual Studio 2017 (V15.8.9) with python tools. When I try to remote debug using ptvsd I see different versions depending where I import ptvsd.
When opening a python console in visual studio in my current environment and import ptvsd, i allways get version 3.2.1.0 which is installed in %ProgramFiles(x86)%microsoft visual studio2017communitycommon7ideextensionsmicrosoftpythoncoreptvsd.
If I install ptvsd in the python environment, the current version 4.2.0 is correctly installed. But when I repeat the above import statement I still see Version 3.2.1.0. The packet version installed in the core seems to override the newer package installed in the environment.
On the remote machine the current version of PTVSD is installed and used. This leads to a version mismatch.
Problem
When using PTVSD 3.2.1 on both machines, visual studio complains when starting the debug that there would be a never version (4.1.1a9) installed on the local machine.
Questions
- What do I need to do to use the current version of PTVSD?
- Is downgrading the only option?
python visual-studio-2017 remote-debugging
asked 23 hours ago
Georg W.
683417
add a comment |
up vote
0
down vote
favorite
Setup
I use Visual Studio 2017 (V15.8.9) with python tools. When I try to remote debug using ptvsd I see different versions depending where I import ptvsd.
When opening a python console in visual studio in my current environment and import ptvsd, i allways get version 3.2.1.0 which is installed in %ProgramFiles(x86)%microsoft visual studio2017communitycommon7ideextensionsmicrosoftpythoncoreptvsd.
If I install ptvsd in the python environment, the current version 4.2.0 is correctly installed. But when I repeat the above import statement I still see Version 3.2.1.0. The packet version installed in the core seems to override the newer package installed in the environment.
On the remote machine the current version of PTVSD is installed and used. This leads to a version mismatch.
Problem
When using PTVSD 3.2.1 on both machines, visual studio complains when starting the debug that there would be a never version (4.1.1a9) installed on the local machine.
Questions
- What do I need to do to use the current version of PTVSD?
- Is downgrading the only option?
python visual-studio-2017 remote-debugging
asked 23 hours ago
Georg W.
683417
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Setup
I use Visual Studio 2017 (V15.8.9) with python tools. When I try to remote debug using ptvsd I see different versions depending where I import ptvsd.
When opening a python console in visual studio in my current environment and import ptvsd, i allways get version 3.2.1.0 which is installed in %ProgramFiles(x86)%microsoft visual studio2017communitycommon7ideextensionsmicrosoftpythoncoreptvsd.
If I install ptvsd in the python environment, the current version 4.2.0 is correctly installed. But when I repeat the above import statement I still see Version 3.2.1.0. The packet version installed in the core seems to override the newer package installed in the environment.
On the remote machine the current version of PTVSD is installed and used. This leads to a version mismatch.
Problem
When using PTVSD 3.2.1 on both machines, visual studio complains when starting the debug that there would be a never version (4.1.1a9) installed on the local machine.
Questions
- What do I need to do to use the current version of PTVSD?
- Is downgrading the only option?
python visual-studio-2017 remote-debugging
asked 23 hours ago
Georg W.
683417
Setup
I use Visual Studio 2017 (V15.8.9) with python tools. When I try to remote debug using ptvsd I see different versions depending where I import ptvsd.
When opening a python console in visual studio in my current environment and import ptvsd, i allways get version 3.2.1.0 which is installed in %ProgramFiles(x86)%microsoft visual studio2017communitycommon7ideextensionsmicrosoftpythoncoreptvsd.
If I install ptvsd in the python environment, the current version 4.2.0 is correctly installed. But when I repeat the above import statement I still see Version 3.2.1.0. The packet version installed in the core seems to override the newer package installed in the environment.
On the remote machine the current version of PTVSD is installed and used. This leads to a version mismatch.
Problem
When using PTVSD 3.2.1 on both machines, visual studio complains when starting the debug that there would be a never version (4.1.1a9) installed on the local machine.
Questions
- What do I need to do to use the current version of PTVSD?
- Is downgrading the only option?
python visual-studio-2017 remote-debugging
python visual-studio-2017 remote-debugging
asked 23 hours ago
Georg W.
683417
asked 23 hours ago
Georg W.
683417
edited 22 hours ago
asked 23 hours ago
Georg W.
683417
asked 23 hours ago
Georg W.
683417
asked 23 hours ago
Georg W.
683417
683417
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53265346%2fvisual-studio-does-not-use-current-ptvsd-version%23new-answer', 'question_page');
}
);
Post as a guest
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
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
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
