plain.oauth 0.16.0__py3-none-any.whl → 0.17.0__py3-none-any.whl

plain/oauth/README.md

@@ -15,7 +15,6 @@ There are three OAuth flows that it makes possible:
 2. Login via OAuth (existing user, existing OAuth connection)
 3. Connect/disconnect OAuth accounts to a user (existing user, new OAuth connection)
 
-
 ## Usage
 
 Install the package from PyPi:
@@ -142,7 +141,7 @@ That's pretty much it!
 The most common error you'll run into is if an existing user clicks a login button,
 but they haven't yet connected that provider to their account.
 For security reasons,
-the required flow here is that the user actually logs in with another method (however they signed up) and then *connects* the OAuth provider from a settings page.
+the required flow here is that the user actually logs in with another method (however they signed up) and then _connects_ the OAuth provider from a settings page.
 
 For this error (and a couple others),
 there is an error template that is rendered.
@@ -236,7 +235,7 @@ response = requests.get(...)
 
 ### Using the Django system check
 
-This library comes with a Django system check to ensure you don't *remove* a provider from `settings.py` that is still in use in your database.
+This library comes with a Django system check to ensure you don't _remove_ a provider from `settings.py` that is still in use in your database.
 You do need to specify the `--database` for this to run when using the check command by itself:
 
 ```sh
@@ -247,7 +246,7 @@ python manage.py check --database default
 
 ### How is this different from [Django OAuth libraries](https://djangopackages.org/grids/g/oauth/)?
 
-The short answer is that *it does less*.
+The short answer is that _it does less_.
 
 In [django-allauth](https://github.com/pennersr/django-allauth)
 (maybe the most popular alternative)
@@ -262,7 +261,7 @@ Personally, I don't like the way that your OAuth settings are stored in the data
 and the implications for doing it one way or another.
 
 The other popular OAuth libraries have similar issues,
-and I think their *weight* outweighs their usefulness for 80% of the use cases.
+and I think their _weight_ outweighs their usefulness for 80% of the use cases.
 
 ### Why aren't providers included in the library itself?
 
@@ -281,7 +280,7 @@ Just copy that code and paste it in your project.
 Tweak as necessary!
 
 This might sound strange at first.
-But in the long run we think it's actually *much* more maintainable for both us (as library authors) and you (as app author).
+But in the long run we think it's actually _much_ more maintainable for both us (as library authors) and you (as app author).
 If something breaks with a provider, you can fix it immediately!
 You don't need to try to run changes through us or wait for an upstream update.
 You're welcome to contribute an example to this repo,

plain/oauth/config.py

@@ -3,4 +3,4 @@ from plain.packages import PackageConfig, register_config
 
 @register_config
 class Config(PackageConfig):
-    label = "plainoauth"  # Primarily for migrations
+    package_label = "plainoauth"  # Primarily for migrations

{plain_oauth-0.16.0.dist-info → plain_oauth-0.17.0.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: plain.oauth
-Version: 0.16.0
+Version: 0.17.0
 Summary: OAuth login and API access for Plain.
 Author-email: Dave Gaeddert <dave.gaeddert@dropseed.dev>
 License-Expression: BSD-3-Clause
@@ -29,7 +29,6 @@ There are three OAuth flows that it makes possible:
 2. Login via OAuth (existing user, existing OAuth connection)
 3. Connect/disconnect OAuth accounts to a user (existing user, new OAuth connection)
 
-
 ## Usage
 
 Install the package from PyPi:
@@ -156,7 +155,7 @@ That's pretty much it!
 The most common error you'll run into is if an existing user clicks a login button,
 but they haven't yet connected that provider to their account.
 For security reasons,
-the required flow here is that the user actually logs in with another method (however they signed up) and then *connects* the OAuth provider from a settings page.
+the required flow here is that the user actually logs in with another method (however they signed up) and then _connects_ the OAuth provider from a settings page.
 
 For this error (and a couple others),
 there is an error template that is rendered.
@@ -250,7 +249,7 @@ response = requests.get(...)
 
 ### Using the Django system check
 
-This library comes with a Django system check to ensure you don't *remove* a provider from `settings.py` that is still in use in your database.
+This library comes with a Django system check to ensure you don't _remove_ a provider from `settings.py` that is still in use in your database.
 You do need to specify the `--database` for this to run when using the check command by itself:
 
 ```sh
@@ -261,7 +260,7 @@ python manage.py check --database default
 
 ### How is this different from [Django OAuth libraries](https://djangopackages.org/grids/g/oauth/)?
 
-The short answer is that *it does less*.
+The short answer is that _it does less_.
 
 In [django-allauth](https://github.com/pennersr/django-allauth)
 (maybe the most popular alternative)
@@ -276,7 +275,7 @@ Personally, I don't like the way that your OAuth settings are stored in the data
 and the implications for doing it one way or another.
 
 The other popular OAuth libraries have similar issues,
-and I think their *weight* outweighs their usefulness for 80% of the use cases.
+and I think their _weight_ outweighs their usefulness for 80% of the use cases.
 
 ### Why aren't providers included in the library itself?
 
@@ -295,7 +294,7 @@ Just copy that code and paste it in your project.
 Tweak as necessary!
 
 This might sound strange at first.
-But in the long run we think it's actually *much* more maintainable for both us (as library authors) and you (as app author).
+But in the long run we think it's actually _much_ more maintainable for both us (as library authors) and you (as app author).
 If something breaks with a provider, you can fix it immediately!
 You don't need to try to run changes through us or wait for an upstream update.
 You're welcome to contribute an example to this repo,

{plain_oauth-0.16.0.dist-info → plain_oauth-0.17.0.dist-info}/RECORD

@@ -1,7 +1,7 @@
-plain/oauth/README.md,sha256=RWGb-KlcYm6etIKAgypE7qqzmgRWskAaVdKxfrXybV8,9901
+plain/oauth/README.md,sha256=9_l9lOSndGBG31mD3oteT8UJMeonuCKdBreLQhUO70E,9900
 plain/oauth/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 plain/oauth/admin.py,sha256=rqrGRRUVxOlG9wiuXtndIyQxd1VT67cvFy6qWo7LF-Q,1278
-plain/oauth/config.py,sha256=5Zc9mdpRgN3R1c9YspFrspWteqB2NAWna2p_-tgoPCc,159
+plain/oauth/config.py,sha256=0Q4IILBKQbIaxqeL9WRTH5Cka-BO3c3SOj1AdQIAJgc,167
 plain/oauth/default_settings.py,sha256=dlN1J9vSOjjxPNLp-0qe-cLTqwM4E69ZAx_8lpxMhaM,28
 plain/oauth/exceptions.py,sha256=TMGtIGkK3_J4rsEy1oPCmia7BnRSK8N8RMZm4_pNelA,189
 plain/oauth/models.py,sha256=ceSw9AKZMXffE4ZKZLxIbOlSyndTCHL22GCuSF3Hpmk,6880
@@ -17,7 +17,7 @@ plain/oauth/migrations/0006_remove_oauthconnection_unique_oauth_provider_user_id
 plain/oauth/migrations/0007_alter_oauthconnection_provider_key_and_more.py,sha256=B_LW6xG1o_uA13tqUs0KniXl1JBNbQu4wMh2pW8rq5I,675
 plain/oauth/migrations/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 plain/oauth/templates/oauth/error.html,sha256=xkkWw57sZ3fz4dDfH30SVtq3okJNnJmrSRPfGxrxjh8,108
-plain_oauth-0.16.0.dist-info/METADATA,sha256=Aezs8S0fDrIgNHJ0T9grRxq5ZF0j59a_yN9VpvMnWg0,10305
-plain_oauth-0.16.0.dist-info/WHEEL,sha256=qtCwoSJWgHk21S1Kb4ihdzI2rlJ1ZKaIurTj_ngOhyQ,87
-plain_oauth-0.16.0.dist-info/licenses/LICENSE,sha256=cvKM3OlqHx3ijD6e34zsSUkPvzl-ya3Dd63A6EHL94U,1500
-plain_oauth-0.16.0.dist-info/RECORD,,
+plain_oauth-0.17.0.dist-info/METADATA,sha256=8Vti0F7xXIyJ2yp8wkG1Ouf_ZhqtqxpujdxBqahdW14,10304
+plain_oauth-0.17.0.dist-info/WHEEL,sha256=qtCwoSJWgHk21S1Kb4ihdzI2rlJ1ZKaIurTj_ngOhyQ,87
+plain_oauth-0.17.0.dist-info/licenses/LICENSE,sha256=cvKM3OlqHx3ijD6e34zsSUkPvzl-ya3Dd63A6EHL94U,1500
+plain_oauth-0.17.0.dist-info/RECORD,,