Django-modern-rpc

Latest version: v1.0.3

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

Scan your dependencies

Page 3 of 5

0.7.0

Not secure
**Release date: 2017-06-24**

Improvements

- Default logging behavior has changed. The library will not output any log anymore, unless `MODERNRPC_ENABLE_LOGGING`
is set to True. See [docs](https://django-modern-rpc.rtfd.io/en/latest/docs/error_handling.html) for details

0.6.0

Not secure
**Release date: 2017-05-13**

Improvements

- Django cache system was previously used to store the list of available methods in the current project.
This was useless, and caused issues with some cache systems (5). Use of cache system has been removed. The list of
RPC methods is computed when the application is started and kept in memory until it is stopped.

0.5.2

Not secure
**Release date: 2017-04-18**

Improvements

- HTTP Basic Authentication backend: User instance is now correctly stored in current request after successful
authentication (4)
- Unit testing with Django 1.11 is now performed against release version (Beta and RC are not tested anymore)
- Various Documentation improvements

0.5.1

Not secure
**Release date: 2017-03-25**

Improvements

- When RPC methods are registered, if a module file contains errors, a python warning is produced. This ensures the
message will be displayed even if the logging system is not configured in a project (2)
- Python 2 strings standardization. Allow to configure an automatic conversion of incoming strings, to ensure they have
the same type in RPC method, no matter what protocol was used to call it. Previously, due to different behavior
between JSON and XML deserializers, strings were received as `str` when method was called via XML-RPC and as `unicode`
with JSON-RPC. This standardization process is disabled by default, and can be configured for the whole project or for
specific RPC methods.
- Tests are performed against Django 1.11rc1
- `modernrpc.core.register_method()` function was deprecated since version 0.4.0 and has been removed.

0.5.0

Not secure
**Release date: 2017-02-18**

Improvements

- Typo fixes
- JSON-RPC 2.0 standard explicitly allows requests without 'params' member. This doesn't produce error anymore.
- Setting variable `MODERNRPC_XML_USE_BUILTIN_TYPES` is now deprecated in favor of `MODERNRPC_XMLRPC_USE_BUILTIN_TYPES`
- Unit tests are now performed with python 3.6 and Django 1.11 alpha, in addition to supported environment already
tested. This is a first step to full support for these environments.
- HTTP "Basic Auth" support: it is now possible to define RPC methods available only to specific users. The control can
be done on various user attributes: group, permission, superuser status, etc. Authentication backend can be extended
to support any method based on incoming request.

0.4.2

Not secure
**Release date: 2016-11-20**

Improvements

- Various performance improvements
- Better use of logging system (python builtin) to report errors & exceptions from library and RPC methods
- Rewritten docstring parser. Markdown and reStructured formatters are still supported to generate HTML documentation
for RPC methods. They now have unit tests to validate their behavior.
- rpc_method decorator can be used with or without the parenthesis (and this feature is tested)
- System methods have been documented

Page 3 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.