Python Standardization

[Gedare Bloom]

On Sun, Mar 22, 2020 at 7:07 AM Anmol Mishra <anmol.j2020 at gmail.com> wrote:
>
> Hello,
> Since you clarified the motivation for API, I need to ask a few questions which will help me.
>
> 1. By API, Do you mean a wrapper or a common access point to test/access all the utilities? If yes, Is REST API is expected like a dashboard?
>
> 2. Is there any active API?
>
> I know this question may seem to be naive but I need to discuss it and clarification is better than any wrong interpretation. All dev members can help me, I will really appreciate it.
>
To get better participation you might want to use a more specific
subject line and provide some extra context to your question.

The project idea is about defining a uniform/consistent interface for
using different products located primarily in rtems-tools.git The
project idea ticket says:
 * A general RTEMS tool library with a standard API to handle common tasks.
 * All utilities callable as a function within the API with the tool
itself being a thin layer.
 * Testing on all API commands under both Python 2.x and 3.x.
API is taken as the original meaning of "application programming
interface" to mean how applications will use the tool library. This
has nothing to do with web services. I hope that helps with some of
your confusion.

Many of the "home-grown" RTEMS tools have relatively consistent
command line interfaces (CLI), but I can't speak to their API; a lot
of them were designed to be used on the command line, which could also
be used as an API but it is not efficient because you generally have
to invoke the tool in a subprocess in such cases.

> Regards
> Anmol