Update documentation

Author: jim-easterbrook

INSTALL.rst

@@ -21,7 +21,7 @@ Use installed libexiv2
 
 In the example above, pip_ installs a "binary wheel_".
 This is pre-compiled and includes a copy of the libexiv2_ library, which makes installation quick and easy.
-Wheels for `python-exiv2`_ are available for Windows, Linux, and MacOS with Python versions from 3.6 to 3.12.
+Wheels for `python-exiv2`_ are available for Windows, Linux, and MacOS with Python versions from 3.6 to 3.13.
 
 If your computer already has libexiv2_ installed (typically by your operating system's "package manager") then pip_ might be able to compile `python-exiv2`_ to use it.
 First you need to check what version of python-exiv2 you have::

README.rst

@@ -52,7 +52,7 @@ If your software is currently incompatible with libexiv2 v0.28.x you can use an
 
     $ pip install --user exiv2==0.16.2 --only-binary :all:
 
-Alternatively, if you have libexiv2 v0.27.x and its "development headers" installed, you can install python-exiv2 from source using your system libexiv2::
+Alternatively, if you have libexiv2 v0.27.x and its "development headers" installed on your computer, you can install python-exiv2 from source using your system libexiv2::
 
     $ pip install --user exiv2 --no-binary :all:
 

USAGE.rst

@@ -51,22 +51,13 @@ Some parts of the interface are deprecated and will eventually be removed.
 Please use Python's ``-Wd`` flag when testing your software to ensure it isn't using deprecated features.
 (Do let me know if I've deprecated a feature you need and can't replace with an alternative.)
 
-Enums
------
-
-The C++ libexiv2 library often uses ``enum`` classes to list related data, such as the value type identifiers stored in `Exiv2::TypeId`_.
-SWIG's default processing of such enums is to add all the values as named constants to the top level of the module, e.g. ``exiv2.asciiString``.
-In python-exiv2 most of the C++ enums are represented by Python enum_ classes, e.g. ``exiv2.TypeId.asciiString`` is a member of ``exiv2.TypeId``.
-
-Unfortunately there is no easy way to deprecate the SWIG generated top level constants, but they will eventually be removed from python-exiv2.
-Please ensure you only use the enum classes in your use of python-exiv2.
-
 Data structures
 ---------------
 
 Some parts of the Exiv2 API use structures to hold several related data items.
 For example, the `Exiv2::ExifTags`_ class has a ``tagList()`` method that returns a list of `Exiv2::TagInfo`_ structs.
-In python-exiv2 (since v0.16.2) these structs have dict_ like behaviour, so the members can be accessed more easily:
+Since python-exiv2 v0.18.0 struct member names ending with an underscore ``_`` have aliases without the underscore.
+Since v0.16.2 these structs also have dict_ like behaviour, so the members can be accessed more easily:
 
 .. code:: python
 
@@ -95,9 +86,6 @@ In python-exiv2 (since v0.16.2) these structs have dict_ like behaviour, so the
 In general it's more efficient to use attribute access (``info.title``) than dict_ access (``info['title']``).
 It is sometimes useful to be able to iterate over the members though, as shown above.
 
-Note that in the C++ API the struct member names end with an underscore.
-In the Python interface the underscore is optional for attribute names, and removed in the dict_ like interface.
-
 Reading data values
 -------------------
 
@@ -320,6 +308,8 @@ Warning: segmentation faults
 If an iterator is invalidated, e.g. by deleting the datum it points to, then your Python program may crash with a segmentation fault if you try to use the invalid iterator.
 Just as in C++, there is no way to detect that an iterator has become invalid.
 
+Since v0.18.0 python-exiv2 can invalidate iterators if the data container is resized, but you should not expect this to work in all circumstances.
+
 Segmentation faults
 -------------------