commit 23a6f30f67b6a26bff3d87de16a26c4cb2a6cf04
author Greg Roodt <groodt@gmail.com> Sat Nov 05 03:53:48 2022 +1100
committer GitHub <noreply@github.com> Fri Nov 04 12:53:48 2022 -0400
tree d0a293cc715989129dfe6cb22303ce4097b6041d
parent 9fae6b63cfeace2e0fb93c9c1ebdc28d3991b16f

Update README.md (#136)

Make it clearer that this project is unmaintained and considered deprecated.

README.md

diff --git a/README.md b/README.md
index 5c98910..14921ee 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-# Subpar
+# Subpar (deprecated)
 
 [![Build Status](https://travis-ci.org/google/subpar.svg?branch=master)](https://travis-ci.org/google/subpar)
 
@@ -7,9 +7,10 @@
 
 ## Status
 
-Subpar is currently owned by the maintainers of [bazelbuild/rules_python](https://github.com/bazelbuild/rules_python), which depends on it. It is not being actively developed beyond what is needed to keep compatibility with rules_python.
-
-Historically, subpar was the only way to produce a deployable Python artifact in Bazel. This is no longer quite true; `--build_python_zip` allows you to create executable Python zip artifacts with the standard `py_binary` rule. Subpar still supports some use cases `--build_python_zip` doesn't: In particular, it allows you to build archives of specific targets without using a global command-line flag, and in some cases the archives can run in-place without extraction.
+This project is unmaintained and considered deprecated.
+Historically, subpar was the only way to produce a deployable Python artifact in Bazel. 
+This is no longer true; `--build_python_zip` and the `python_zip_file` output_group allows you to create executable Python zip artifacts with the standard `py_binary` rule.
+`rules_docker` can also be used to build container images that launch `py_binary`.
 
 ## Setup