You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Build definitions VSCode-Python-CI and VSCode-Python-Rolling-CI are updated. I removed the --pre flag from the place I install PTVSD from in those definitions.
Do we want to pin PTVSD to a specific version?
I have left the VSCode-Python-ptvsd_master-CI build alone, it runs nightly whenever there is a change to PTVSD. It is triggered by the PTVSD-DependencyChain CI build, which triggers on a schedule every night, IFF the PTVSD:master sources have changed.
Do we want to continue to build ptvsd_master against the extension in this way?
d3r3kk
added a commit
to d3r3kk/vscode-python
that referenced
this issue
Aug 22, 2018
With ptvsd 4.1.1 now released, we should make sure we are always using the latest stable release and not any
--pre
releases.The text was updated successfully, but these errors were encountered: