<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->

• VSCode Version: 1.47.3 (system setup)
• OS Version: Windows_NT x64 10.0.18362

Steps to Reproduce:

1. Create a snippet with a transformation which replaces part of the text with tabs, e.g. the following Python snippet

	"Plain object": {
		"prefix": ["class"],
		"body": [
			"class ${1:Name}:",
			"\tdef __init__(self, ${2:arg_list}):",
			"\t\t${2/ *([^:]+?) *(:[^,]+)? *(,|$)/self.${1} = ${1}\n\t\t/g}",
			"\tdef __repr__(self):",
			"\t\treturn repr(self.__dict__)",
			""
		]
	}

2. Use the snippet. The explicit tabs at the beginning of lines get replaced with spaces per the file preferences. However, the tabs that result from the transform don't overgo the same process.

Does this issue occur when all extensions are disabled?: Didn't check

I would like to add another example I just encountered -- implementing any binary operation on an immutable instance, for instance, this doesn't compile:

class Vector(tuple):
  def __add__(self, other: Vector) -> Vector:
    return tuple(sum(vals) for vals in zip(self, other))

Another issue I reported (#13042) was transitively marked as a dup of this one (via #13017) but these seem to be separate (perhaps related?) issues.

@greazer This does not seem to be a dup of #13016 , but indeed of the bug that I reported #13042. This seems to do with the window group focus (please note my workaround), and while it might be related, the functionality involved and side-effects are not similar to the upstream bug https://github.com/microsoft/vscode/issues/103200 mentioned in #13016. I would vote to re-open.

A partial workaround - put a regular code editor in the same window group. Once that is done, and the cursor is first placed in that code editor, you'll be able to copy. If you need, I can post a gif.

Thanks for the reply. Note that this only when switching between window groups. If the Python Interactive Window is in the same window group as another plain code editor, the bug doesn't happen. I'm pretty sure this bug only showed up after upgrading VS Code. I'm not sure what my previous version was.

Bug: Notebook Editor, Interactive Window, Editor cells

Steps to cause the bug to occur

1. Create a Python file with one cell that outputs some text
2. Execute the cell
3. Select and copy the text from the Python Interactive window - paste it somewhere - it copied fine
4. Change the selection in the code window (preferable to a line with some content)
5. Select and copy other text from the Python Interactive window - paste it somewhere - it copied the text from the code window rather than the Python Interactive window

Actual behavior

Sometimes, when the active window is the Python Interactive window, the text selected in the code window gets copied when I hit Ctrl + C instead of the text in the active window.

Expected behavior

Text selected in the active window will be copied when I hit Ctrl + C.

Your Jupyter and/or Python environment

• Jupyter server running: Local
• Extension version: v2020.7.94776
• VS Code version: 1.47.2 (system setup; commit: 17299e413d5590b14ab0340ea477cdd86ff13daf)
• Setting python.jediEnabled: false
• Setting python.languageServer: Microsoft
• Python and/or Anaconda version: CPython 3.7.4
• OS: Windows_NT x64 10.0.18362
• Virtual environment: none (system install)

Developer Tools Console Output

No output

Thanks for the patch, but I'm going to decline. Hash randomization has system wide effects and nothing that are specific to the random() module. The only relation is that they share the word "random" :-)

Hey, thanks for the comment. While a FAQ entry is indeed relevant, I think that so is a mention in random - a user like me expected deterministic behavior when using random.seed(), didn't get such a behavior, and consulted the docs for random for some insight. Users should be aware that there are other sources of randomness in otherwise deterministic code -- the use of the same word, random, is not happenstance.