pipenv shell command doesn't work when installing tools #4404

Activity

1. ghost added

   triage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team

   on Feb 14, 2019
2. DonJayamanne commented on Feb 14, 2019

   

   Don Jayamanne (DonJayamanne)

   on Feb 14, 2019

   More actions

   Duplicate of #4394
3. Don Jayamanne (DonJayamanne)

   marked this as a duplicate of Revert pipenv activation to not use pipenv shell #4394 on Feb 14, 2019
4. Don Jayamanne (DonJayamanne)

   closed this as completedon Feb 14, 2019
5. ghost removed

   triage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team

   on Feb 14, 2019
6. thernstig commented on Feb 15, 2019

   

   Tobias Hernstig (thernstig)

   on Feb 15, 2019

   Author

   More actions

   Don Jayamanne (@DonJayamanne) Thanks for pointing it out. Was hard to find an issue due to the minimalistic information in the original :)

   I realize I kind of baked two questions into this issue, but what about this part:

   If you close a terminal (trashcan) and open it again and start writing quickly, the text you enter end up on the same line as "pipenv shell". E.g. I often open terminal and quickly write git ts. What happens is that it looks like: git tspipenv shell. I think this might be related in some sense.

   I am assuming that even though it is reverted to activate, this might still be a problem?
7. ericarnold-granular commented on Feb 21, 2019

   

   Eric Arnold (ericarnold-granular)

   on Feb 21, 2019

   More actions

   Is this the same thing that causes debugging to be broken when trying to launch the app directly? This is the debug def I have for our Flask app

               "name": "Flask",
               "type": "python",
               "request": "launch",
               "port": 9876,
               "module": "flask",
               "env": {
                   "FLASK_APP": "sales_aggr_svc.server",
                   "FLASK_ENV": "development",
                   "FLASK_DEBUG": "0",
                   "DEBUG": "true"
               },
               "args": [
                   "run"
               ],
               "jinja": true
   

   When I try to run it I get this:

   eric@eric-XPS-15-9560:~/sales-aggr-svc$ pipenv shell
   cd /sales-aggr-svc ; env "FLASK_APP=sales_aggr_svc.server" "FLASK_ENV=development" "FLASK_DEBUG=0" "DEBUG=true" "PYTHONIOENCODING=UTF-8" "PYTHONUNBUFFERED=1" /home/eric/.local/share/virtualenvs/sales-aggr-svc-0a-no2Bc/bin/python /home/eric/.vscode/extensions/ms-python.python-2019.1.0/pythonFiles/ptvsd_launcher.py --default --client --host localhost --port 9876 -m flask run 
   Launching subshell in virtual environment...
    . /home/eric/.local/share/virtualenvs/sales-aggr-svc-0a-no2Bc/bin/activate
   eric@eric-XPS-15-9560:~/sales-aggr-svc$  . /home/eric/.local/share/virtualenvs/sales-aggr-svc-0a-no2Bc/bin/activate
   (sales-aggr-svc) eric@eric-XPS-15-9560:~/sales-aggr-svc$ 
   

   Eventually it pops up a "Timeout waiting for debugger connection" dialog and the debugger stops.

   Oddly enough, if I point the Python interpreter at a different project, then then it sources the activate file first (which puts it in a pipenv shell) and runs the main command after that, which allows the debugger to connect. That only works if the projects have the same dependencies though.

   eric@eric-XPS-15-9560:~/sales-aggr-svc$ source /home/eric/.local/share/virtualenvs/enrollments-svc-G11ZWuBp/bin/activate
   (enrollments-svc) eric@eric-XPS-15-9560:~/sales-aggr-svc$ cd /sales-aggr-svc ; env "FLASK_APP=sales_aggr_svc.server" "FLASK_ENV=development" "FLASK_DEBUG=0" "DEBUG=true" "PYTHONIOENCODING=UTF-8" "PYTHONUNBUFFERED=1" /home/eric/.local/share/virtualenvs/enrollments-svc-G11ZWuBp/bin/python /home/eric/.vscode/extensions/ms-python.python-2019.1.0/pythonFiles/ptvsd_launcher.py --default --client --host localhost --port 9876 -m flask run
   
8. lock

   locked as resolved and limited conversation to collaborators on Mar 21, 2019
9. Kartik Raj (karrtikr)

   changed the title [-]Python install extension [/-] [+]`pipenv shell` command doesn't work when installing tools[/+] on Mar 19, 2021