Colanderalchemy

Latest version: v0.3.4

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

Scan your dependencies

Page 1 of 3

0.3.5.dev1

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

0.3.4

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

- no functional changes; updates to tests and supported versions

0.3.3

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

- Allow recursive schema creation (PR `81 <https://github.com/stefanofontanelli/ColanderAlchemy/pull/81>`_).
[Ademan, offlinehacker]
- Allow ``includes``, ``excludes`` and ``overrides`` to be specified in
``__colanderalchemy_config__`` and applied to the ``SchemaNode``.
[davidjb]
- Clarify documentation for quickstart.
[davidjb]

0.3.2.post1

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

- Only apply declaratively defined settings to the outer Sequence when
mapping an SQLAlchemy relationship. Previously, overrides were applied
to both the Sequence and Mapping nodes, leading to unexpected behaviour.
[davidjb]
- The order in which fields are added are now properly maintained
(`issue 45
<https://github.com/stefanofontanelli/ColanderAlchemy/issues/45>`_)
[uralbash]
- Added ability to override fields on their own (PR
`69 <https://github.com/stefanofontanelli/ColanderAlchemy/pull/69>`_,
`70 <https://github.com/stefanofontanelli/ColanderAlchemy/pull/70>`_)
[uralbash]
- Allow setting ColanderAlchemy options in sqlalchemy type. [pieterproigia]
- Make it possible to set the ``unknown`` ``colander.Mapping`` option
using ``__colanderalchemy_config__`` (PR
`78 <https://github.com/stefanofontanelli/ColanderAlchemy/pull/78>`_)
[elemoine]

0.3.1

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

- maintain the order of SQLAlchemy object attributes in the
Colander schema [tisdall]
- use Colander defaults wherever explicit settings are
not given [tisdall]
- added tests for confirming documentation examples [tisdall]
- added fix and test for `issue 35
<https://github.com/stefanofontanelli/ColanderAlchemy/issues/35>`_
(thrown exception on encountering synonym() ) [tisdall]
- made changes to accommodate SQLAlchemy >= 0.9a [tisdall]
- allows "children" override
(`issue 44
<https://github.com/stefanofontanelli/ColanderAlchemy/issues/44>`_)
[tisdall]
- no longer call callable SQLAlchemy defaults to fill in
colander default values (`issue 43
<https://github.com/stefanofontanelli/ColanderAlchemy/issues/43>`_)
[tisdall]
- fixed some minor issues with colander default and missing values
to ensure transitive relationships (such as dictify/objectify)
[tisdall]
- require colander 1.0b1 or greater to support `colander.drop`
(`issue 52
<https://github.com/stefanofontanelli/ColanderAlchemy/issues/52>`_)
[tisdall]

0.3

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

- Add ``objectify`` function on ``SQLAlchemySchemaNode`` -- use this to
recreate SQLAlchemy object instances from the configured mappers.
This new method is the opposite of ``dictify``.
[davidjb]
- Colander's ``DateTime`` now defaults to using a naive ``datetime``
when no timezone is provided, similar to SQLAlchemy.
[tisdall]
- fixed defaults for SchemaNode.default and SchemaNode.missing
[tisdall]

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.