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
{{ message }}
Repository navigation
Setting python.experiments.optInto gives confusing hover information #15635
Overal, it's confusing whether it's possible to opt in/out of experiments, and if experiments set with that setting are deprecated, that hover message should probably be updated to show this information.
Extension version: 2021.2.636928669
VS Code version: Code 1.54.1 (f30a9b73e8ffc278e71575118b6bf568f04587c8, 2021-03-04T22:38:50.094Z)
OS version: Linux x64 5.10.19-1-lts
The problem is that we change the experiments often enough that it would be hard to manually maintain the list of the active experiments. The idea is that the auto completions in the settings.json file should help with knowing which values are accepted or not.
The new page you linked is definitely better. I'm not sure I understand your second paragraph - do you mean that it's hard to update the wiki, or to update the autocompletions? I'm not sure how experiments are implemented, but I guess that when they are setup, there's probably some metadata attached to them (what they are testing, what the changes are). I think it would be nice to have a bit more transparency for the end user - to know which experiments are enabled/available, what they do, etc.
I meant it's tricky to update the wiki as it would have to be a manual sourcing process (we have experiments that are run cross-teams, so there isn't necessarily one person with the whole information to be able to update it).
I like your idea though, I'm marking this issue as "needs decision" so I can talk to the team about it 😊 thanks!
I talked to the team the overall thought was that cost to get the information of the experiments to expose it is quite high, whether it's programmatically or not, and we have many other higher priority bugs and features to address first. But I'm submitting a PR to update the link to this wiki page instead, to try to help clarify the confusion a bit, at least.
Activity
ldorigo commentedon Mar 11, 2021
Alternatively, or additionally, the page at https://github.com/microsoft/vscode-python/wiki/Experiments should make it clear what the current way is for users to opt in/out of experiments
luabud commentedon Mar 20, 2021
Thanks for bringing this up, Luca Dorigo (@ldorigo)! I agree that the current link is confusing. I'm considering either removing that line, or linking to this following page: https://github.com/microsoft/vscode-python/wiki/AB-Experiments.
The problem is that we change the experiments often enough that it would be hard to manually maintain the list of the active experiments. The idea is that the auto completions in the settings.json file should help with knowing which values are accepted or not.
ldorigo commentedon Mar 26, 2021
The new page you linked is definitely better. I'm not sure I understand your second paragraph - do you mean that it's hard to update the wiki, or to update the autocompletions? I'm not sure how experiments are implemented, but I guess that when they are setup, there's probably some metadata attached to them (what they are testing, what the changes are). I think it would be nice to have a bit more transparency for the end user - to know which experiments are enabled/available, what they do, etc.
luabud commentedon Mar 26, 2021
I meant it's tricky to update the wiki as it would have to be a manual sourcing process (we have experiments that are run cross-teams, so there isn't necessarily one person with the whole information to be able to update it).
I like your idea though, I'm marking this issue as "needs decision" so I can talk to the team about it 😊 thanks!
luabud commentedon Apr 7, 2021
I talked to the team the overall thought was that cost to get the information of the experiments to expose it is quite high, whether it's programmatically or not, and we have many other higher priority bugs and features to address first. But I'm submitting a PR to update the link to this wiki page instead, to try to help clarify the confusion a bit, at least.
Update link to A/B experiments description (#20409)
Merged PR posit-dev/positron-python#14: Merge upstream of vscode pyth…
Merged PR posit-dev/positron-python#14: Merge upstream of vscode pyth…