[RTEMS Project] #4037: Python script distrubution standardisation

[RTEMS trac]

#4037: Python script distrubution standardisation
--------------------------+--------------------
  Reporter:  Chris Johns  |      Owner:  (none)
      Type:  defect       |     Status:  new
  Priority:  normal       |  Milestone:  6.1
 Component:  admin        |    Version:  6
  Severity:  normal       |   Keywords:
Blocked By:               |   Blocking:
--------------------------+--------------------
 The RSB and Tools wrap python scripts in a shell script based wrapper that
 detects the installed version and uses it. Other python scripts in RTEMS
 do not. I would like to have a consistent model for all scripts.

 [[https://www.python.org/dev/peps/pep-0394/ | PEP0394]] discusses the
 issues and says a distro can decide not to provide a `python` command by
 default. It also says a `virtualenv` can be used to provide a consistent
 default environment.

 Do we assume `#! /usr/bin/env python` will always work in our script and
 we make sure we are `python2` and `python3` clean for user installed
 commands?

 If a user does not have a `python` command installed by default do we
 document how to install one or do we document using a `virtualenv`?

 A simple shebang is cleaner for us to maintain however it added an extra
 dependency we need to document.

 Note, development script and tools should follow the same model we decide
 on however they only need to support `python3`.

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