Allow "Run Python File in Terminal" button to be configurable #11812

Activity

1. Luciana Abud (luabud)

   added

   feature-requestRequest for new features or functionalityRequest for new features or functionality

   area-terminal

   needs proposalNeed to make some design decisionsNeed to make some design decisions

   area-environmentsFeatures relating to handling interpreter environmentsFeatures relating to handling interpreter environments

   on May 14, 2020
2. Luciana Abud (luabud)

   self-assigned this

   on Aug 12, 2020
3. Inetov commented on Oct 16, 2020

   

   Inetov

   on Oct 16, 2020

   More actions

   yes, at the moment this is a completely useless button.
   we have a button close at hand, but to use launch.json we need to go to the menu ...
4. gandhis1 commented on May 12, 2022

   

   Siddhartha Gandhi (gandhis1)

   on May 12, 2022

   More actions

   I agree here, unless I'm missing something apparently there isn't any way to run a script with arguments through this button/command. One is forced to use the Debug screen launchers which is substantially less convenient.
5. diogo-rossi commented on Sep 11, 2022

   

   Diogo (diogo-rossi)

   on Sep 11, 2022

   Last edited by diogo-rossi

   More actions

   I agree here, unless I'm missing something apparently there isn't any way to run a script with arguments through this button/command. One is forced to use the Debug screen launchers which is substantially less convenient.

   Siddhartha Gandhi (@gandhis1), if you think it will be good, please, up vote this
6. diogo-rossi commented on Sep 12, 2022

   

   Diogo (diogo-rossi)

   on Sep 12, 2022

   Last edited by diogo-rossi

   More actions

   Or simply by allowing arguments to be passed to python (e.g. -i) or to the file.

   Luciana Abud (@luabud), I think we already can pass arguments to python with the setting "python.terminal.launchArgs".

   I've opened this issue to request the same for the script file.

   👍React with 👍1Reacted by Luciana Abud
7. luabud commented on Sep 14, 2022

   

   Luciana Abud (luabud)

   on Sep 14, 2022

   MemberAuthor

   More actions

   Yes, good point! And perhaps you meant to reference #19810?

   👍React with 👍1Reacted by Diogo
8. diogo-rossi commented on Sep 14, 2022

   

   Diogo (diogo-rossi)

   on Sep 14, 2022

   More actions

   Yes, good point! And perhaps you meant to reference #19810?

   Yeah, my bad. I updated the link now.
9. AntonVucinic commented on Sep 19, 2022

   

   Anton Vučinić (AntonVucinic)

   on Sep 19, 2022

   Last edited by AntonVucinic

   More actions

   Another good option would be to add the ability to run currently open file as a module. This is already referenced by #10130 in a slightly different way. Currently there is only a way to set a specific module to be ran.
   There is a workaround that works for files in the project root directory:

   {
       "name": "Python: Module",
       "type": "python",
       "request": "launch",
       "module": "${fileBasenameNoExtension}",
       "justMyCode": true
   }
   

   I think there should be an option to run the currently open file as a module and also set that to be the default behaviour for the "Run Python File" button so that it could be used without starting the debugger.

   👍React with 👍5Reacted by Simon Friedberger, Apromixately, Tom, mattviguier and ManiMatter
10. starball5 commented on Jun 21, 2023

    

    starball (starball5)

    on Jun 21, 2023

    Last edited by starball5

    More actions

    Possibly related on Stack Overflow: How can I configure the "Run" button next to the editor tabs in VS Code for Python files?
11. Apromixately commented on Nov 23, 2023

    

    Apromixately

    on Nov 23, 2023

    More actions

    I agree with Anton Vučinić (@AntonVucinic) and #10130 running files as a module would be useful. When there is a bit of folder hierarchy, the only way to import something is to use modules. This could also be solved with some search/replace in the variables.

    To give a bash example:

    folder='foo/bar/baz'
    echo ${folder//\//.}
    

    gives foo.bar.baz which is pretty much what is needed here. Then this could be solved using:

    {
        "name": "Python: Module",
        "type": "python",
        "request": "launch",
         "module": "${relativeFileDirname//\//.}.${fileBasenameNoExtension}",
        "justMyCode": true
    }
    

    Apologies if this seems like hijacking this issue but #10130 is closed.

    👍React with 👍1Reacted by Tom
12. Apromixately commented on Nov 23, 2023

    

    Apromixately

    on Nov 23, 2023

    More actions

    Actually, there might be an easier way to solve this. Afaict from https://code.visualstudio.com/docs/editor/variables-reference#_command-variables, if this extension would define a getModule function we could use ${command:getModule}.
13. starball5 commented on Dec 7, 2023

    

    starball (starball5)

    on Dec 7, 2023

    More actions

    Related: https://code.visualstudio.com/updates/v1_85#_configurable-debugging-option-under-the-run-button-menu