From 1a561e536c963cd802ba9b61313c22fcb5ae0c31 Mon Sep 17 00:00:00 2001
From: daira <>
Date: Sat, 31 Aug 2013 15:07:11 +0000
Subject: [PATCH] say that 'python setup.py trial' is only for backward
 compatibility

[Imported from Trac: page AdvancedInstall, version 65]
---
 AdvancedInstall.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/AdvancedInstall.md b/AdvancedInstall.md
index 2a37627..61514f8 100644
--- a/AdvancedInstall.md
+++ b/AdvancedInstall.md
@@ -240,14 +240,15 @@ There are a few other supported ways to run tests:
 * `bin/tahoe debug trial`. This will *not* rebuild (if a build was needed,
 > some tests may fail). It accepts all of the same options as Twisted's `trial`
 > script; use `bin/tahoe debug trial --help` to see help for these.
-* `python setup.py trial` does the same thing as `bin/tahoe debug trial`,
-> although it doesn't support all of the `trial` options (and the test suite
-> must be specified using `-s`). It's supported mainly for backward
-> compatibility.
 * `make test` does the same thing as `python setup.py test`.
 * `make quicktest` does the same thing as `bin/tahoe debug trial`.
 
-Running `trial` directly is not supported because it will not necessarily
+The following way of running tests is supported only for backward compatibility:
+* `python setup.py trial` does almost the same thing as `bin/tahoe debug trial`,
+> but doesn't support all of the `trial` options, and the test suite must be
+> specified using `-s`).
+
+Running `trial` directly is *not* supported, because it will not necessarily
 put the correct libraries (the same ones that would be used by `bin/tahoe`)
 on Python's `sys.path`.