[RTEMS Project] #4037: Python script distribution standardisation

[RTEMS trac]

#4037: Python script distribution standardisation
-------------------------+---------------------
 Reporter:  Chris Johns  |       Owner:  (none)
     Type:  defect       |      Status:  new
 Priority:  normal       |   Milestone:  6.1
Component:  admin        |     Version:  6
 Severity:  normal       |  Resolution:
 Keywords:               |  Blocked By:
 Blocking:               |
-------------------------+---------------------

Comment (by Joel Sherrill):

 Can we write a simple program as an alternative to env which answers the
 question of "which Python" in a way we want? rtems-which-python python[23]
 and let it answer the question?

 I am opposed to forcing use of virtualenv but only encouraging it. It is a
 nice feature and I am using it but I only use it because the host doesn't
 have everything in a complete (Tex packaging) or current way. If the host
 is sufficient, it shouldn't be needed.

 CentOS 7 does have a Python 3 but you have to install a "software
 collection"
 (https://developers.redhat.com/products/softwarecollections/overview for a
 description and list). This is the RedHat way of adding newer technologies
 as an option. This is what I have been doing on CentOS 7 combined with a
 virtualenv.


 {{{
 scl enable rh-python36 bash
 }}}

 I have been doing the Python 3 Software Collection plus a virtualenv for
 Sphinx to build the RTEMS documentation.

--
Ticket URL: <http://devel.rtems.org/ticket/4037#comment:12>
RTEMS Project <http://www.rtems.org/>
RTEMS Project