Restler

Latest version: v0.7.1

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

Scan your dependencies

Page 1 of 4

0.7.2

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

- Nothing changed yet.

0.7.1

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

- Added support for entity '*_filter' methods.
- Downgraded SQLAlchemy from 0.7.1 to 0.7.2. We want to require SA 0.7 w/o
requiring users to upgrade to point releases if they don't want/need to
(unless there's a good reason to force an upgrade).

0.7.0

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

- Upgraded SQLAlchemy from 0.6 series to 0.7 (0.6.0 => 0.7.1).
- Upgraded decorator from 3.1.2 to 3.3.1

0.6.3

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

- Moved project hosting from Google Code to Bitbucket:
https://bitbucket.org/wyatt/restler

- Don't assume a thread local database session factory is in use. Added
a `clear_db_session` API method that is now called from the `finally`
clause in the Restler controller's `__call__` instead of directly
calling the session factory's `remove` method. The default implementation
assumes a thread local session factory is in use and calls its `remove`
method just like before. The difference now is that subclasses can more
easily override this behavior by providing an alternate implemenation
(which, perhaps, does nothing).

0.6.2

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

- By default, include attributes and properties from base classes when
creating simple objects. This only applies when the set of fields to
include isn't explicitly specified (e.g., via the `fields` query
parameter).

- When creating simple objects, don't blow up when accessing an attribute
of a field that may be NULL. Previously, an AttributeError would be
raised. This comes up when a sub-attribute is requested via the `fields`
query param using dot notation--e.g., fields=["assignee.full_name"].
Assuming `assignee` could be NULL, it seems preferable to return
`"assignee": null` in the JSON representation than to blow up with an
internal server error. The client can check for `null` and raise an
error if appropriate.

- When the client specifies the URL it uses to access the WS server
utilizing Restler (via the X-Restler-Client-Request-URL header), make sure
that URL paths generated for redirection don't include the SCRIPT_NAME of
the WS server.

- Added some tests for redirection.

0.6.1

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

- Allow default filter params to be overridden when calling `set_collection`
(added `filter_params=None` keyword arg).
- Don't strip query parameter values for filter params, since whitespace
padded values and values consisting of only spaces are both valid in some
scenarios (e.g., Oracle CHAR(1) where " " is a meaningful value).
(XXX: this change might be backward incompatible)

Page 1 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.