From 85163523b6c6c53af0d3aecaf25783d7b142aa2e Mon Sep 17 00:00:00 2001
From: Mikhail Golubev <mikhail.golubev@jetbrains.com>
Date: Wed, 10 Jul 2019 22:03:04 +0300
Subject: [PATCH] PY-12516 Enable automatic renaming of generated run
 configurations on module refactoring

It didn't work because we forgot to set isGeneratedName flag for such run
configurations by initializing suggested name manually instead of using
the standard LocatableConfigurationBase#setGeneratedName() method.

GitOrigin-RevId: 6f0eb6b3e53f52e6a7647298cc143a2d0f573e93
---
 .../jetbrains/python/run/PythonRunConfigurationProducer.java    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/python/src/com/jetbrains/python/run/PythonRunConfigurationProducer.java b/python/src/com/jetbrains/python/run/PythonRunConfigurationProducer.java
index bfebef707ee5..5268fc75c687 100644
--- a/python/src/com/jetbrains/python/run/PythonRunConfigurationProducer.java
+++ b/python/src/com/jetbrains/python/run/PythonRunConfigurationProducer.java
@@ -54,7 +54,7 @@ public final class PythonRunConfigurationProducer extends LazyRunConfigurationPr
       configuration.setUseModuleSdk(true);
       configuration.setModule(module);
     }
-    configuration.setName(configuration.suggestedName());
+    configuration.setGeneratedName();
     return true;
   }