@@ -69,15 +69,15 @@ import { ITestCodeNavigatorCommandHandler, ITestExplorerCommandHandler } from '.
69
69
import { registerTypes as unitTestsRegisterTypes } from './testing/serviceRegistry' ;
70
70
71
71
// components
72
- import * as pythonEnvironments from './pythonEnvironments' ;
72
+ // import * as pythonEnvironments from './pythonEnvironments';
73
73
74
74
import { ActivationResult , ExtensionState } from './components' ;
75
75
import { Components } from './extensionInit' ;
76
76
77
77
export async function activateComponents (
78
78
// `ext` is passed to any extra activation funcs.
79
79
ext : ExtensionState ,
80
- components : Components
80
+ _components : Components
81
81
) : Promise < ActivationResult [ ] > {
82
82
// Note that each activation returns a promise that resolves
83
83
// when that activation completes. However, it might have started
@@ -89,7 +89,13 @@ export async function activateComponents(
89
89
// activation resolves `ActivationResult`, which can safely wrap
90
90
// the "inner" promise.
91
91
const promises : Promise < ActivationResult > [ ] = [
92
- pythonEnvironments . activate ( components . pythonEnvs ) ,
92
+ // tslint:disable-next-line:no-suspicious-comment
93
+ // TODO: For now the extension should only interact with the component via the component adapter,
94
+ // which takes care of putting the component behind the experiment flag. It already activates the
95
+ // component among other things, hence the following is not needed.
96
+ // pythonEnvironments.activate(components.pythonEnvs),
97
+ // If we need to activate, we need to use the adapter:
98
+ // https://github.com/microsoft/vscode-python/issues/14984
93
99
// These will go away eventually.
94
100
activateLegacy ( ext )
95
101
] ;
0 commit comments