Bump django-multiselectfield from 0.1.13 to 1.0.1
Bumps django-multiselectfield from 0.1.13 to 1.0.1.
Release notes
Sourced from django-multiselectfield's releases.
v1.0.1
- Badge image worked on GitHub but was broken on PyPI — fixed it.
v1.0.0
This release introduces multiple changes that are incompatible with previous versions.
The major version number has been incremented following
Semantic Versioning (SemVer) <https://semver.org/>_, as several components of the package have changed in ways that may require updates in client code.The internal codebase has been significantly cleaned up and reorganized, making it more maintainable and consistent.
This version contains 40% fewer lines of code compared to the previous release.
Less code means fewer bugs, easier maintenance, and better long-term sustainability.
Breaking changes
Remove MSFList (01dcad230dc368b88a39bfc36f90ddd145f381a2):
- Removed: (50d3f785883e0a314f2dc89950e3fe1e88a7ede6)
- It was created to support MultiSelectFields in admin.list_display, but it never actually worked. If you add a multiselect field to list_display, Django does not call to str method of MSGList (renamed to MSFList)
- It was created for integer choices too and it is a misconception. This is explained in the README file.
Remove MSFFlatchoices (01dcad230dc368b88a39bfc36f90ddd145f381a2):
- Removed: (5638247c1d70670d4f81adf35143ef17a7d7575e)
- In list_display, labels for the choices are now shown (comma-separated) instead of the values of the choices (comma-separated).
In to_python method, value is a list or a string. (c4579138dda2833cbce26afbf57da5353aa45690)
- Remove set case and dict case
- If this breaks something, please create a test to help understand the use case.
Removing integer choices:
- It was a mistake. MultiSelectField inherits of CharField, not IntegerField.
- It is impossible knows if original choice is (1, 'Item title 2.1') or ('1', 'Item title 2.1')
Fix: Form instance generated twice since Django (#168)
Fix CSS admin:
Fix Properly Display Categorized Choices in get_FOO_display (#169)
SortMultiSelectField: (#172)
... (truncated)
Changelog
Sourced from django-multiselectfield's changelog.
1.0.1 (2025-06-12)
- Badge image worked on GitHub but was broken on PyPI — fixed it.
1.0.0 (2025-06-12)
This release introduces multiple changes that are incompatible with previous versions.
The major version number has been incremented following
Semantic Versioning (SemVer) <https://semver.org/>_, as several components of the package have changed in ways that may require updates in client code.The internal codebase has been significantly cleaned up and reorganized, making it more maintainable and consistent.
This version contains 40% fewer lines of code compared to the previous release.
Less code means fewer bugs, easier maintenance, and better long-term sustainability.
Breaking changes
Remove MSFList (
01dcad230dc368b88a39bfc36f90ddd145f381a2 <https://github.com/goinnn/django-multiselectfield/commit/01dcad230dc368b88a39bfc36f90ddd145f381a2>_):
- Removed: (
50d3f785883e0a314f2dc89950e3fe1e88a7ede6 <https://github.com/goinnn/django-multiselectfield/commit/50d3f785883e0a314f2dc89950e3fe1e88a7ede6>_)- It was created to support MultiSelectFields in admin.list_display, but it never actually worked. If you add a multiselect field to list_display, Django does not call to str method of MSGList (renamed to MSFList)
- It was created for integer choices too and it is a misconception. This is explained in the README file.
Remove MSFFlatchoices (
01dcad230dc368b88a39bfc36f90ddd145f381a2 <https://github.com/goinnn/django-multiselectfield/commit/01dcad230dc368b88a39bfc36f90ddd145f381a2>_):
- Removed: (
5638247c1d70670d4f81adf35143ef17a7d7575e <https://github.com/goinnn/django-multiselectfield/commit/5638247c1d70670d4f81adf35143ef17a7d7575e>_)- In list_display, labels for the choices are now shown (comma-separated) instead of the values of the choices (comma-separated).
In to_python method, value is a list or a string. (
c4579138dda2833cbce26afbf57da5353aa45690 <https://github.com/goinnn/django-multiselectfield/commit/c4579138dda2833cbce26afbf57da5353aa45690>_)
- Remove set case and dict case
- If this breaks something, please create a test to help understand the use case.
Removing integer choices:
- It was a mistake. MultiSelectField inherits of CharField, not IntegerField.
- It is impossible knows if original choice is (1, 'Item title 2.1') or ('1', 'Item title 2.1')
Fix: Form instance generated twice since Django (
[#168](https://github.com/goinnn/django-multiselectfield/issues/168) <https://github.com/goinnn/django-multiselectfield/pull/168>_)Fix CSS admin:
- (
[#173](https://github.com/goinnn/django-multiselectfield/issues/173) <https://github.com/goinnn/django-multiselectfield/pull/173>_)- (
7711f4aa755c81d00f07ce8a6ff0fd9240061f9c <https://github.com/goinnn/django-multiselectfield/commit/7711f4aa755c81d00f07ce8a6ff0fd9240061f9c>_)
... (truncated)
Commits
679bac6Ready to new releasebef2514Ready to new release9a564a3Add image from github (pypi broken)f2b3186Fix typo error7289469Fix another pypi errorf17a828Improve readme filed9e2b97Fix error uploading to pypia387bc6Ready to new release. The major version number has been incremented because t...4fc1369If the choices are Proxy str (i18n) patched_display_for_field gets an error8bafbdbAdd static files to package- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)