imas-python 0.1.dev1630__tar.gz → 0.1.dev1633__tar.gz

{imas_python-0.1.dev1630 → imas_python-0.1.dev1633}/.gitignore

@@ -95,10 +95,8 @@ imas/_version.py
 
 # IMAS DD
 data-dictionary
-access-layer
 containers/arch/imas/
 containers/arch/data-dictionary/
-containers/arch/access-layer/
 imas/assets/IDSDef.zip
 
 # IDS files

{imas_python-0.1.dev1630 → imas_python-0.1.dev1633}/CONTRIBUTING.md

@@ -7,36 +7,31 @@ Please first make sure you read and follow the
 [Code of Conduct](CODE_OF_CONDUCT.md).
 
 ## You think you found a bug in the code, or have a question in its use
-1. use the [issue search](https://github.com/iterorganization/
-imas-python/issues) to check if someone already created 
-a similar issue;
-2. if not, make a **new issue** to describe your problem or question. 
+1. use the [issue search](https://github.com/iterorganization/imas-python/issues)
+to check if someone already created a similar issue;
+3. if not, make a **new issue** to describe your problem or question. 
 In the case of a bug suspiscion, please try to give all the relevant 
 information to allow reproducing the error or identifying 
 its root cause (version of the imas-python, OS and relevant 
 dependencies, snippet of code);
-3. apply relevant labels to the issue.
+4. apply relevant labels to the issue.
 
 ## You want to make or ask some change to the code
-1. use the [issue search](https://github.com/iterorganization/
-imas-python/issues) to check if someone already proposed 
-a similar idea/change;
-2. if not, create a **new issue** to describe what change you would like to see 
+1. use the [issue search](https://github.com/iterorganization/imas-python/issues)
+to check if someone already proposed a similar idea/change;
+3. if not, create a **new issue** to describe what change you would like to see 
 implemented and specify it if you intend to work on it yourself or if some help 
 will be needed;
-3. wait until some kind of consensus is reached about your idea being relevant, 
+4. wait until some kind of consensus is reached about your idea being relevant, 
 at which time the issue will be assigned (to you or someone else who can work on 
 this topic);
-4. if you do the development yourself, fork the repository to your own Github 
+5. if you do the development yourself, fork the repository to your own Github 
 profile and create your own feature branch off of the latest develop commit. 
 Make sure to regularly sync your branch with the latest commits from `develop` 
 (find instructions 
-[here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/
-working-with-forks/syncing-a-fork);
-5. when your development is ready, create a pull request (find instructions 
-[here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/
-proposing-changes-to-your-work-with-pull-requests/
-creating-a-pull-request-from-a-fork)).
+[here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork));
+6. when your development is ready, create a pull request (find instructions 
+[here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)).
 
 
 While we will try to answer questions quickly and to address issues in a timely 

{imas_python-0.1.dev1630 → imas_python-0.1.dev1633}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: imas-python
-Version: 0.1.dev1630
+Version: 0.1.dev1633
 Summary: Pythonic wrappers for the IMAS Access Layer
 Author: imas-python developers
 Author-email: Olivier Hoenen <olivier.hoenen@iter.org>

{imas_python-0.1.dev1630 → imas_python-0.1.dev1633}/benchmarks/technical.py

@@ -1,5 +1,4 @@
 import imas
-import imas
 
 
 def timeraw_create_default_imas_factory():
@@ -16,12 +15,6 @@ def timeraw_import_imas():
     """
 
 
-def timeraw_import_imas():
-    return """
-    import imas
-    """
-
-
 # It would be nice if we could track these, but unfortunately it breaks things like
 # `asv compare` :(
 """

{imas_python-0.1.dev1630 → imas_python-0.1.dev1633}/benchmarks/utils.py

@@ -6,10 +6,6 @@ from pathlib import Path
 import imas
 import imas.exception
 
-# Don't directly import imas: code analyzers break on the huge code base
-imas = importlib.import_module("imas")
-
-
 # Backend constants
 HDF5 = "HDF5"
 MDSPLUS = "MDSplus"
@@ -60,13 +56,11 @@ available_slicing_backends = [
     backend for backend in available_backends if backend not in [ASCII, NETCDF]
 ]
 
-hlis = ["imas", "imas"]
+hlis = ["imas"]
 DBEntry = {
     "imas": imas.DBEntry,
-    "imas": imas.DBEntry,
 }
 factory = {
-    "imas": imas,
     "imas": imas.IDSFactory(),
 }
 available_serializers = [imas.ids_defs.ASCII_SERIALIZER_PROTOCOL]
@@ -74,9 +68,6 @@ available_serializers = [imas.ids_defs.ASCII_SERIALIZER_PROTOCOL]
 
 def create_dbentry(hli, backend):
     if backend == NETCDF:
-        if hli == "imas":
-            # Raising NotImplementedError will skip the benchmarks for this combination
-            raise NotImplementedError("AL-Python HLI doesn't implement netCDF.")
         if hli == "imas":  # check if netcdf backend is available
             try:
                 assert (

{imas_python-0.1.dev1630 → imas_python-0.1.dev1633}/imas/_version.py

@@ -12,5 +12,5 @@ __version__: str
 __version_tuple__: VERSION_TUPLE
 version_tuple: VERSION_TUPLE
 
-__version__ = version = '0.1.dev1630'
-__version_tuple__ = version_tuple = (0, 1, 'dev1630')
+__version__ = version = '0.1.dev1633'
+__version_tuple__ = version_tuple = (0, 1, 'dev1633')

{imas_python-0.1.dev1630 → imas_python-0.1.dev1633}/imas_python.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: imas-python
-Version: 0.1.dev1630
+Version: 0.1.dev1633
 Summary: Pythonic wrappers for the IMAS Access Layer
 Author: imas-python developers
 Author-email: Olivier Hoenen <olivier.hoenen@iter.org>

{imas_python-0.1.dev1630 → imas_python-0.1.dev1633}/imas_python.egg-info/SOURCES.txt

@@ -14,7 +14,7 @@ conftest.py
 pyproject.toml
 setup.cfg
 setup.py
-.github/workflows/liniting.yml
+.github/workflows/linting.yml
 .github/workflows/publish.yml
 benchmarks/__init__.py
 benchmarks/core_profiles.py