forked from auto-mat/django-import-export-celery
-
Notifications
You must be signed in to change notification settings - Fork 1
Updgrade to the latest base version #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
GergelyKovach
wants to merge
122
commits into
pulilab:master
Choose a base branch
from
auto-mat:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix TypeError: NoneType takes no arguments
Load model choices from the admin form (Fix 52)
Fix for dry_run when diff is skipped (#63)
Added pypi workflows
…kend Enabling Customization of Storage Backends
Fix: AttributeError if IMPORT_EXPORT_CELERY_STORAGE not defined
…files-upon-deleting-the-import-job delete uploaded file on import job delete
…uto-file-delete added try except for import job file delete
…e-limit Add configurable soft and hard time limits for import and export tasks
…modules instead of deprecated method In Django documentation we can see that get_storage_class is deprecated in Django 5.1 and later. https://docs.djangoproject.com/en/5.0/ref/files/storage/#django.core.files.storage.get_storage_class Recommendation of Django is to use storages instead of get_storage_class. This leads to specify this file storage backend in STORAGES config settings instead of a new config variable. This commit allows also to keep using custom storage classe from older verions (4.2 and earlier) and prevents to crash when invalid storage class is provided, using the default one. Solves #115
Manage custom storage class using django.core.files.storage.storages …
Bumps [django](https://github.com/django/django) from 3.2.18 to 3.2.19. - [Commits](django/django@3.2.18...3.2.19) --- updated-dependencies: - dependency-name: django dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [pygments](https://github.com/pygments/pygments) from 2.10.0 to 2.15.0. - [Release notes](https://github.com/pygments/pygments/releases) - [Changelog](https://github.com/pygments/pygments/blob/master/CHANGES) - [Commits](pygments/pygments@2.10.0...2.15.0) --- updated-dependencies: - dependency-name: pygments dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [django](https://github.com/django/django) from 3.2.19 to 3.2.25. - [Commits](django/django@3.2.19...3.2.25) --- updated-dependencies: - dependency-name: django dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
This reverts commit 80a1ebb.
This reverts commit 7678b58.
Handle ValidationErrors having just plain messages list
add configurable email on completion for export job
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.