-
Notifications
You must be signed in to change notification settings - Fork 217
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Split up and then remove `aiida.orm.importexport`. Moved to `aiida.tools.importexport`. Split up into structure (relative to `aiida.tools.importexport`: ./dbexport/__init__.py ./dbexport/utils.py ./dbexport/zip.py ./dbimport/__init__.py ./dbimport/backends/utils.py ./dbimport/backends/django/__init__.py ./dbimport/backends/sqla/__init__.py ./dbimport/backends/sqla/utils.py ./config.py ./utils.py Import/export is now considered a tool, and has nothing to do with the specifics of AiiDA. It should be in a state, where it would be easy to remove it and save it in a separate repo. Import with a django or sqlalchemy backend has been split up. For export, this is not needed, since it is already backend-independent. To further reflect the split of backends, the actual import functions have been placed under `aiida.tools.importexport.dbimport.backends.[django/sqla].`. In the future, `dbimport` should reflect the situation from `dbexport` and be backend independent, creating the imported nodes through the new backend-independent ORM entities. Export to a zip-folder/file has been split up in a separate file. This should later be implemented in another place, since a ZipFolder class exists here. For example `aiida.common.folder`. See also issue #3100. Note: Be careful with wildcard imports in `__init__` files for backends specific functionality.
- Loading branch information
Showing
21 changed files
with
3,195 additions
and
3,021 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.