From 1906b0437e77c194543b3e549187c1989270ebd3 Mon Sep 17 00:00:00 2001 From: Jack Lloyd Date: Fri, 19 Apr 2019 05:06:04 -0400 Subject: Also deprecate Python2 with the Python wrapper Supporting both is actually kind of a pain and it would be nice to be able to drop that eventually. --- doc/manual/deprecated.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/manual/deprecated.rst b/doc/manual/deprecated.rst index 97168d9f0..cefdec7a1 100644 --- a/doc/manual/deprecated.rst +++ b/doc/manual/deprecated.rst @@ -10,11 +10,13 @@ This is in addition to specific API calls marked with BOTAN_DEPRECATED in the source. - Configuring a build (with ``configure.py``) using Python2. In a future - major release, Python3 will be required. This will not affect the Python - module, which will continue to support Python2 for the forseeable future. + major release, Python3 will be required. + +- Using the Python wrapper with Python2. - Directly using an algorithm class like ``AES_128`` or ``SHA_256``. Instead - create the objects via a ``T::create`` call. + create the objects via a ``T::create`` call. A future major release may + make such declarations private. - Directly accessing the member variables of types calendar_point, ASN1_Attribute, AlgorithmIdentifier, and BER_Object -- cgit v1.2.3