Skip to content
Snippets Groups Projects
Commit a4bc8bb4 authored by Henrik tom Wörden's avatar Henrik tom Wörden
Browse files

Merge tag 'linkahead-rename-step-2' into f-linkahead-rename-tmp

parents 0062a9bc 8de757e6
No related branches found
No related tags found
1 merge request!114Helper MR
Pipeline #41719 passed
git merge linkahead-rename-step-1
# resolve potential conflicts and commit
rm -rf src/linkahead
git mv src/caosdb/ src/linkahead
rm -rf src/caosdb
python3 create_slim_linkahead_wrapper.py
git add src
git ci -m "MAINT: rename caosdb to linkahead (module)"
git merge linkahead-rename-step-2
# resolve potential conflicts and commit
git merge dev
......@@ -188,7 +188,10 @@ def setup_package():
package_data={
'linkahead': ['cert/indiscale.ca.crt', 'schema-pycaosdb-ini.yml'],
},
scripts=["src/linkahead/utils/linkahead_admin.py"]
scripts=[
"src/linkahead/utils/caosdb_admin.py",
"src/linkahead/utils/linkahead_admin.py"
]
)
try:
setup(**metadata)
......
......@@ -16,11 +16,11 @@ following. For more information on specific error types, see also the
.. note::
Starting from PyLinkAhead 0.5, the error handling has changed
Starting from PyCaosDB 0.5, the error handling has changed
significantly. New error classes have been introduced and the
behavior of ``TransactionError`` and ``EntityError`` has been
re-worked. In the following, only the "new" errors are
discussed. Please refer to the documentation of PyLinkAhead 0.4.1 and
discussed. Please refer to the documentation of PyCaosDB 0.4.1 and
earlier for the old error handling.
LinkAheadException
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment