3.6 compatibility

[pyderasn.git] / doc / features.rst

diff --git a/doc/features.rst b/doc/features.rst
index dcbd0ebcdc8b3ce6c9afdae23050a869411b0eef..fa1f3d6a90930bedcd9ecb457f151965d4f95929 100644 (file)
--- a/doc/features.rst
+++ b/doc/features.rst
@@ -1,13 +1,14 @@
 Features
 ========
 
+* BER/CER/DER decoding, DER encoding
 * Basic ASN.1 data types (X.208): BOOLEAN, INTEGER, BIT STRING, OCTET
   STRING, NULL, OBJECT IDENTIFIER, ENUMERATED, all strings, UTCTime,
   GeneralizedTime, CHOICE, ANY, SEQUENCE (OF), SET (OF)
 * Size :ref:`constraints <bounds>` checking
 * Working with sequences as high level data objects with ability to
   (un)marshall them
-* Python 2.7/3.5 compatibility
+* Python 2.7/3.5/3.6 compatibility
 
 Why yet another library? `pyasn1 <https://github.com/etingof/pyasn1>`__
 had all of this a long time ago. PyDERASN resembles it in many ways. In
@@ -25,6 +26,8 @@ practice it should be relatively easy to convert ``pyasn1``'s code to
   settable values, even when they are inherited
 * However they do not require tags matching: IMPLICIT/EXPLICIT tags will
   be set automatically in the given sequence
+* Descriptive errors, like ``pyderasn.DecodeError: UTCTime
+  (tbsCertificate.validity.notAfter.utcTime) (at 328) invalid UTCTime format``
 * ``__slots__`` friendliness
 * Could be significantly faster. For example parsing of CACert.org's CRL
   under Python 3.5.2:
@@ -39,11 +42,10 @@ practice it should be relatively easy to convert ``pyasn1``'s code to
 There are drawbacks:
 
 * No old Python versions support
-* No BER/CER support
 * PyDERASN does **not** have object recreation capable ``repr``-s::
 
     pyderasn>>> repr(algo_id)
-    AlgorithmIdentifier SEQUENCE[OBJECT IDENTIFIER 1.3.14.3.2.26, [UNIV 5] ANY 0500 OPTIONAL]
+    AlgorithmIdentifier SEQUENCE[algorithm: OBJECT IDENTIFIER 1.3.14.3.2.26; parameters: [UNIV 5] ANY 0500 OPTIONAL]
 
     pyasn1>>> repr(algo_id)
     AlgorithmIdentifier().setComponents(ObjectIdentifier('1.3.14.3.2.26'), Any(hexValue='0500'))