Run python tests without compiling TF

Bhack · June 12, 2021, 10:20pm

Theorically this activity could be part of the old approved RFC:

tensorflow/community/blob/master/rfcs/20190305-modular-tensorflow.md

# Modular TensorFlow

| Status        | Accepted                                             |
:-------------- |:---------------------------------------------------- |
| **Author(s)** | Gunhan Gulsoy (gunan@google.com)                     |
| **Sponsor**   | Martin Wicke (wicke@google.com)                      |
| **Updated**   | 2019-11-25                                           |


## Motivation

TensorFlow is a very successful open source project. Since it has been open sourced, [1800+ contributors](https://github.com/tensorflow/tensorflow) have submitted code into TF from outside Google. However, as more and more developers contribute, it becomes more and more difficult to manage contributions in the single repository.

This project aims to split the TensorFlow codebase into **smaller, more focused**, repositories that can be released and managed separately. These modules will talk to each other using **well defined APIs**. Thanks to the module APIs, these modules are now **managed/owned/released independently.**

### Problems addressed

#### Spaghetti dependencies

Everything being in a single repository encourages everyone to freely use all other code in the repository, even when this does not make sense. This ensures the library is very difficult to modify later.

This file has been truncated. show original

mihaimaruseac · June 13, 2021, 4:57pm

Yes, but that effort is no longer staffed

Bhack · June 13, 2021, 6:22pm

We have also :

github.com/tensorflow/community

RFC: Tensorflow Core as a product

tensorflow:master ← sun51:patch-2

opened 11:39PM - 20 Nov 20 UTC

sun51

+174 -0

but I don’t know if It is already on a “old branch”

mihaimaruseac · June 13, 2021, 7:12pm

Yeah, that one was abandoned too

Bhack · June 14, 2021, 5:21pm

No more ace to play

Bhack · June 14, 2021, 6:20pm

Ops we have also:

Outdated?

mihaimaruseac · June 14, 2021, 7:33pm

Oh, that’s even older. But it’s very related to this.

Bhack · June 14, 2021, 7:48pm

Sorry, but when everything is open or approved it hard to know the real status

mihaimaruseac · June 14, 2021, 7:49pm

Yes. We need a way to mark obsolete RFCs

Bhack · June 14, 2021, 7:53pm

Yes probably we need to add something to the process:

github.com

tensorflow/community/blob/master/governance/TF-RFCs.md

# TensorFlow Request for Comments (TF-RFC)

The purpose of a TensorFlow RFC is to engage the TensorFlow community in
development, by getting feedback from stakeholders and experts, and
communicating design changes broadly.

## Who is involved?

Any **community member** may help by providing feedback on whether the RFC will
meet their needs.

An **RFC author** is one or more community member who writes an RFC and is
committed to championing it through the  process.

An **RFC sponsor** is any maintainer who sponsors the RFC and will shepherd it
through the RFC review process.

A **review committee** is a group of maintainers who have the responsibility of
recommending the adoption of the RFC.

This file has been truncated. show original

And make a periodical pass (every month?) over the PR and merged RFC.

/cc @ewilderj