Thanks Ken, I was aware of the work these guys are doing, I have just run into some issues and solved them, but still want to make sure my fixes are working in both Python 2 and 3 so I do a lot of switching.

That brings up something else I was wondering.  If I find/fix something should I go through the proper trac ticket process or should I go through Michael Karg, Séverin Lemaignan, and Lorenz Mösenlechner so they can be rolled into broader patches like the ones on trac right now?  I guess what I am asking is whether or not the move to support Python3 is solid enough to move to bug reporting or if it is still fluid enough for patching in larger patches.

On Wed, Aug 10, 2011 at 9:44 AM, William Woodall <wjwwood@gmail.com> wrote:
> +1
> I wonder if this could also be used to control which version of Python you
> are using without changing the paths and such.  I have been working on
> making ros, ros_comm, and common_msgs more Python 2/3 portable because of
> MORSE, which uses Blender, which requires Python3.  I had considered setting
> something like env['ROS_PYTHON'] and replacing the #!/usr/bin/env python
> lines with something like ros-shebang that would select python executables
> and paths based on the environment variable.  This isn't something I see
> people doing often, but it might be a use case to consider when designing
> this tool.  There might also be a better/existing way of doing what I am
> talking about, but I am just not aware of it.
  
Michael Karg, Séverin Lemaignan, and Lorenz Mösenlechner have been
working on the above MORSE problem by making the Python code Py3k
compatible. You may want to look at:
  
https://code.ros.org/trac/ros/ticket/3166
https://code.ros.org/trac/ros/ticket/3576
https://code.ros.org/trac/ros/ticket/3627
  

Most of the patches have been merged and they have been using MORSE with ROS.
So as to not bomb this thread, please start a new thread if you wish
to discuss the above.
  
 - Ken

Thanks, 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
William Woodall
Graduate Software Engineering
Auburn University
w@auburn.edu
wjwwood@gmail.com
williamjwoodall.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~