Django-autocomplete-light

Latest version: v3.12.1

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

Scan your dependencies

Page 20 of 30

2.0.0a8

Not secure
- Updated pt_BR translation contributed by Fábio C. Barrionuevo da Luz (luzfcb).

2.0.0a7

- Removed a layer of complexity by trading autocomplete_js_attributes and
widget_js_attributes for attrs (for input/autocomplete object) and widget_attrs
(for widget container/widget js object).
- Fixed naming conventions issues:
- 124: css class .choiceDetail should be .choice-detail, same for
.choiceUpdate
- 97: rename .div css class to .block,
- Fixed 84: data-autocomplete-placeholder is gone in favor of the
placeholder attribute.
- Fixed 82: data-* is not parsed anymore by yourlabs.Widget, data-widget-*
is parsed for options instead.
- Fixed 81: js Autocomplete object now parses data-autocomplete-* for
options,
- Fixed 80: js maxValues is now maximumValues.
- Fixed 27: refactored selenium tests to be able to test any example app.
- Bugfix: get_autocomplete_from_arg returned wrong autocomplete in two cases

2.0.0a6

Not secure
- Simplified widget template selection.

2.0.0a5

Not secure
- Support for Django 1.6's ModelForm.Meta.fields = '__all__', generic fk
and generic m2m autocomplete fields were not created.

2.0.0a4

Not secure
- Fix 204: Restore AutocompleteModelBase as default,
- Fix 205: Support Python3 in views,
- Fixed 404 response in AutocompleteView.

2.0.0a3

Not secure
- Do not interfere with non-autocomplete-enabled form fields,
- Ported taggit support to Python3,
- Renamed TaggitTagField to TaggitField and integrated TaggitField into
autocomplete_light.ModelForm,

Page 20 of 30

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.