aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorAlex Gaynor <alex.gaynor@gmail.com>2017-11-10 23:19:05 -0500
committerPaul Kehrer <paul.l.kehrer@gmail.com>2017-11-11 12:19:05 +0800
commit270933c1a2afa0aa60409946bb7319d85fd60059 (patch)
treef5ff261a2dd5be46e812785d67f9322596b19792 /docs
parentd2d800058f93f78e46afe504b5709b865b7af35d (diff)
downloadcryptography-270933c1a2afa0aa60409946bb7319d85fd60059.tar.gz
cryptography-270933c1a2afa0aa60409946bb7319d85fd60059.tar.bz2
cryptography-270933c1a2afa0aa60409946bb7319d85fd60059.zip
Use a different warning class so users get warnings (#4014)
* Use a different warning class so users get warnings * fixed tests * do our own warning class * typo * flake8
Diffstat (limited to 'docs')
-rw-r--r--docs/api-stability.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/api-stability.rst b/docs/api-stability.rst
index 7ba1d426..2bb53841 100644
--- a/docs/api-stability.rst
+++ b/docs/api-stability.rst
@@ -42,9 +42,9 @@ entirely. In that case, here's how the process will work:
* In ``cryptography X.Y`` the feature exists.
* In ``cryptography X.Y+1`` using that feature will emit a
- ``PendingDeprecationWarning``.
+ ``UserWarning``.
* In ``cryptography X.Y+2`` using that feature will emit a
- ``DeprecationWarning``.
+ ``UserWarning``.
* In ``cryptography X.Y+3`` the feature will be removed or changed.
In short, code that runs without warnings will always continue to work for a