Docassemble

Latest version: v1.6.2

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

Scan your dependencies

Page 7 of 145

1.4.96

Not secure
Fixed
- Issue with installation of SSL certificates stored on S3.

1.4.95

Not secure
Fixed
- The `small screen navigation` option under `features` could not be
overridden to `True`.
- The `nice_number()` function sometimes did not properly detect
whether a number was an integer.

1.4.94

Not secure
Added
- The `raw html` special field type under `fields` and `review`. This
is similar to `html` but allows modification of the structure of the
HTML in the list as a whole.

1.4.93

Not secure
Added
- The `current_context()` function, which is the new function to use
in place of `user_info()` for attributes that are not related to the
logged in user. The object returned by `current_context()` also has
a new attribute, `inside_of`, which can be used to detect whether
the Python code that is currently executing is executing inside of a
particular type of document assembly process.

Changed
- The `user_info()` function had previously provided much of the
information that the `current_context()` function now
provides. However, the name `user_info()` was not suitable for that
information. A deprecation warning will be logged if code accesses
the attributes of `user_info()` that do not relate to the logged-in
user. In a future version, accessing these attributes will raise an
exception.
- The behavior of the object returned from `user_info()` is different,
which might be a breaking change if you used `user_info()` in a
certain way. Previously, `user_info()` returned an object with
static attributes. Now, the attributes of the object returned by
`user_info()` are dynamic attributes (using the `property`
decorator). If you set `u = user_info()` and `u` becomes a variable
in the interview answers, `u.id` will always return the user id of
the current logged-in user, not necessarily the user who was logged
in when `u` was defined.
- The new function `current_context()` works the same way. If you set
`c = current_context()` then `c.current_section` will be the current
section at the time the attribute was accessed, not the time that
`c` was defined.
- Another difference in the way that `user_info()` operates is that if
the user is not logged in, the attributes other than `first_name`
and `last_name` will exist, but will be `None`. Previously, those
attributes did not exist, and accessing them would raise an
`AttributeError`. If you want to test whether the user is logged in,
use `user_logged_in()`.

Fixed
- A non-`required` boolean field value that was not filled out was set
to `False` instead of `None` as the documentation specified. The
default value is now `None`.
- The `words` directive was unable to load translations from
Playground packages.

1.4.92

Not secure
Fixed
- The `reconsider` and `need` modifiers were not active on all
`mandatory` blocks.
- The `depends on` and `on change` features did not work on all `code`
blocks executed during `process_action()`.
- Playground raised exception if `playground examples` is an empty
list.

1.4.91

Not secure
Changed
- Improved error messages when Python code contains errors.

Fixed
- Error when YAML parsing did not succeed.

Page 7 of 145

Links

Releases

Has known vulnerabilities

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.