rospython: ability to choose python shell #24
Labels
Comments
|
Do you have any proposal how that should be done for scripts which identify Python in their shebang line? |
|
With the global scope of this ticket I don't see a technical way to achieve this. I will close the ticket for now. Please provide more information to narrow the scope or suggest ways to implement it. Then the ticket can be reopened. |
dirk-thomas
pushed a commit
that referenced
this issue
Mar 5, 2019
* enable rosrun on Windows * rosrun_fix * fix indent * revert unnecessary changes * Fix libexec path search issue. * another round of rosrun fix. * Fix File Not Found messages. * fix parameter processing * Rosrun.bat fix (#10) * Check if file exists and return correct error code * Generate toplevel forward bat script for rosrun on Windows * Fix issue that rosrun cannot handle wild char parameter (#11) * Fix typo (#12) * Fix rosrun. * fix rosrun parameter parsing issue (#14) * fix rosrun parameter parsing issue * correct file extension extraction * Fix rosrun bash script (#18) Fix rosrun bash script * update rosrun.bat to find python scripts (files with extensions) (#20) This change makes it so it does a deep search first in the rospack file, then the whole path. * fix rosrun search path pecking order. (#24) * fix. * fix. * update catkin version requirement for script.bat.in
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice to have ability to choose python shell, for example
ipythoninstead of purepython. As I understandipythonsupposed to be a drop-in replacement, thus command-line interface should be compatible.Something like
ROS_PYTHON_SHELLenvironment variable, which defaults topython, would be sufficient I guess.The text was updated successfully, but these errors were encountered: