Django-all-access

Latest version: v0.9.0

Safety actively analyzes 681881 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 3

0.5.1

------------------------------------

- Fix incompatibility with the existing South migrations and a customized User model. Thanks to Jharrod LaFon for the report and fix.

0.5.0

------------------------------------

This release adds additional hooks for changing the OAuth client behaviors. It also
adds support for Python 3.2+.

- New view hooks for customizing the OAuth client
- Fixed issue with including oauth_verifier in POST when fetching the access token
- Documented the API for :py:class:`OAuthClient` and :py:class:`OAuth2Client`
- Updated requirements to requests >= 1.0 and requests_oauthlib >= 0.3.0
- Updated requirement for PyCrypto >= 2.4

Backwards Incompatible Changes
__________________________________

- Dropped support for requests < 1.0
- Dropped support for Django < 1.4.2

0.4.1

------------------------------------

There were incompatibilty issues with requests-oauthlib (0.2) and requests which
required dropping requests 1.0 support. The requirement of oauthlib was also raised
to 0.3.4 due to similar issues. For more detail see the below issues.

- https://github.com/requests/requests-oauthlib/issues/1
- https://github.com/requests/requests-oauthlib/pull/10

0.4.0

------------------------------------

This release is largely to keep pace with features/changes to some of the
dependencies. This also helps work toward Python 3.0 support.

- Updated for compatibility with Django 1.4 timezone support
- Updated for compatibility with Django 1.5 swappable ``auth.User``
- Updated for compatibility with Requests 1.0
- Added requests_oauthlib requirement
- Updated requirement of oauthlib to 0.3 or higher

0.3.0

------------------------------------

This release added some basic logging to django-all-access. To enable this logging
in your project, you should update your ``LOGGING`` configuration to include
``allaccess`` in the ``loggers`` section. Below is an example:

.. code-block:: python

LOGGING = {
'handlers': {
'console':{
'level':'DEBUG',
'class':'logging.StreamHandler',
},
'mail_admins': {
'level': 'ERROR',
'class': 'django.utils.log.AdminEmailHandler',
'filters': ['special']
}
},
'loggers': {
'django.request': {
'handlers': ['mail_admins', ],
'level': 'ERROR',
'propagate': True,
},
'allaccess': {
'handlers': ['console', ],
'level': 'INFO',
}
}
}

For more information on logging please see the
`Django documentation <https://docs.djangoproject.com/en/1.4/topics/logging/>`_
or the `Python documentation <http://docs.python.org/library/logging.html>`_.


Features
_________________

- Added access to simple API wrapper through the ``AccountAccess`` model
- Added state parameter for OAuth 2.0 by default
- Added basic error logging to OAuth clients and views
- Added contributing guide and mailing list info

0.2.1

------------------------------------

Bug Fixes
_________________

- Fixes missing Content-Length header when requesting OAuth 2.0 access token

Page 2 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.