From 212f4e353835b8717f99e2090286e8d68f306f42 Mon Sep 17 00:00:00 2001 From: Daniele Varrazzo Date: Sat, 22 Feb 2014 21:56:46 +0000 Subject: [PATCH] Docs wordsmithing about Range order --- doc/src/extras.rst | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/doc/src/extras.rst b/doc/src/extras.rst index 52a7056f..7fab3384 100644 --- a/doc/src/extras.rst +++ b/doc/src/extras.rst @@ -437,14 +437,17 @@ user-defined |range| types can be adapted using `register_range()`. `!Range` objects are immutable, hashable, and support the ``in`` operator (checking if an element is within the range). They can be tested for - equivalence. Empty ranges evaluate to `!False` in - boolean context, nonempty evaluate to `!True`. - - `!Range` objects can be sorted although, as on the server-side, - this ordering is not particularly meangingful. + equivalence. Empty ranges evaluate to `!False` in boolean context, + nonempty evaluate to `!True`. .. versionchanged:: 2.5.3 + `!Range` objects can be sorted although, as on the server-side, this + ordering is not particularly meangingful. It is only meant to be used + by programs assuming objects using `!Range` as primary key can be + sorted on them. In previous versions comparing `!Range`\s raises + `!TypeError`. + Although it is possible to instantiate `!Range` objects, the class doesn't have an adapter registered, so you cannot normally pass these instances as query arguments. To use range objects as query arguments you can either