histomicsui 1.8.1.dev149__tar.gz → 1.8.1.dev153__tar.gz

{histomicsui-1.8.1.dev149 → histomicsui-1.8.1.dev153}/.circleci/config.yml

@@ -15,7 +15,7 @@ commands:
       parameters:
         node:
           type: string
-          default: v20
+          default: v22
       steps:
         - run:
             name: Use nvm
@@ -55,6 +55,7 @@ commands:
           name: Install playwright with dependencies
           command: |
             pushd histomicsui/web_client
+            # We need this version for ubuntu 26.04 base
             npx playwright install --with-deps
             popd
   tox:
@@ -118,6 +119,15 @@ jobs:
       - tox:
           env: py313
       - coverage
+  py314:
+    executor: toxandnode
+    steps:
+      - checkout
+      - use_nvm
+      - build_client
+      - tox:
+          env: py314
+      - coverage
   web_client:
     executor: toxandnode
     environment:
@@ -191,6 +201,13 @@ workflows:
             branches:
               ignore:
                 - gh-pages
+      - py314:
+          filters:
+            tags:
+              only: /^v.*/
+            branches:
+              ignore:
+                - gh-pages
       - noanalysis:
           filters:
             tags:
@@ -218,6 +235,7 @@ workflows:
             - py311
             - py312
             - py313
+            - py314
             - lint_and_docs
           filters:
             tags:

{histomicsui-1.8.1.dev149/histomicsui.egg-info → histomicsui-1.8.1.dev153}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: histomicsui
-Version: 1.8.1.dev149
+Version: 1.8.1.dev153
 Summary: Organize, visualize, and analyze histology images.
 Home-page: https://github.com/DigitalSlideArchive/histomicsui
 Author: Kitware, Inc.
@@ -136,9 +136,20 @@ The standard deployment of HistomicsUI is the `Digital Slide Archive`_.  The ass
 Development
 ===========
 
-The most convenient way to develop on HistomicsUI is to use the `devops scripts from the Digital Slide Archive <https://github.com/DigitalSlideArchive/digital_slide_archive/tree/master/devops>`_.
+The most convenient way to develop on HistomicsUI is in conjunction with the `Digital Slide Archive <https://github.com/DigitalSlideArchive/digital_slide_archive>`_.  Once both repos have been cloned locally,  mount your local HistomicsUI directory to the DSA docker container:
 
-If you are making changes to the HistomicsUI frontend, you can make Girder watch the source code and perform hot reloads on changes using the ``--watch-plugin`` argument to ``girder build``. See the `Girder docs <https://girder.readthedocs.io/en/stable/development.html#during-development>`_ for more information.
+.. code-block:: bash
+
+  # /devops/ver5/docker-compose.local.yml
+  services:
+
+    girder:
+      volumes:
+        - ../../../HistomicsUI:/opt/HistomicsUI
+
+Then use the `devops scripts from the Digital Slide Archive <https://github.com/DigitalSlideArchive/digital_slide_archive/tree/master/devops/ver5>`_.
+
+If you are making changes to the HistomicsUI frontend, you can have the Girder instance watch the local HistomicsUI source code and perform hot reloads on changes by running ``npm run build`` then ``npm run watch`` from ``histomicsui/web_client/``. See the `Girder docs <https://girder.readthedocs.io/en/stable/development.html#during-development>`_ for more information.
 
 Annotations and Metadata from Jobs
 ----------------------------------

{histomicsui-1.8.1.dev149 → histomicsui-1.8.1.dev153}/README.rst

@@ -93,9 +93,20 @@ The standard deployment of HistomicsUI is the `Digital Slide Archive`_.  The ass
 Development
 ===========
 
-The most convenient way to develop on HistomicsUI is to use the `devops scripts from the Digital Slide Archive <https://github.com/DigitalSlideArchive/digital_slide_archive/tree/master/devops>`_.
+The most convenient way to develop on HistomicsUI is in conjunction with the `Digital Slide Archive <https://github.com/DigitalSlideArchive/digital_slide_archive>`_.  Once both repos have been cloned locally,  mount your local HistomicsUI directory to the DSA docker container:
 
-If you are making changes to the HistomicsUI frontend, you can make Girder watch the source code and perform hot reloads on changes using the ``--watch-plugin`` argument to ``girder build``. See the `Girder docs <https://girder.readthedocs.io/en/stable/development.html#during-development>`_ for more information.
+.. code-block:: bash
+
+  # /devops/ver5/docker-compose.local.yml
+  services:
+
+    girder:
+      volumes:
+        - ../../../HistomicsUI:/opt/HistomicsUI
+
+Then use the `devops scripts from the Digital Slide Archive <https://github.com/DigitalSlideArchive/digital_slide_archive/tree/master/devops/ver5>`_.
+
+If you are making changes to the HistomicsUI frontend, you can have the Girder instance watch the local HistomicsUI source code and perform hot reloads on changes by running ``npm run build`` then ``npm run watch`` from ``histomicsui/web_client/``. See the `Girder docs <https://girder.readthedocs.io/en/stable/development.html#during-development>`_ for more information.
 
 Annotations and Metadata from Jobs
 ----------------------------------

{histomicsui-1.8.1.dev149 → histomicsui-1.8.1.dev153/histomicsui.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: histomicsui
-Version: 1.8.1.dev149
+Version: 1.8.1.dev153
 Summary: Organize, visualize, and analyze histology images.
 Home-page: https://github.com/DigitalSlideArchive/histomicsui
 Author: Kitware, Inc.
@@ -136,9 +136,20 @@ The standard deployment of HistomicsUI is the `Digital Slide Archive`_.  The ass
 Development
 ===========
 
-The most convenient way to develop on HistomicsUI is to use the `devops scripts from the Digital Slide Archive <https://github.com/DigitalSlideArchive/digital_slide_archive/tree/master/devops>`_.
+The most convenient way to develop on HistomicsUI is in conjunction with the `Digital Slide Archive <https://github.com/DigitalSlideArchive/digital_slide_archive>`_.  Once both repos have been cloned locally,  mount your local HistomicsUI directory to the DSA docker container:
 
-If you are making changes to the HistomicsUI frontend, you can make Girder watch the source code and perform hot reloads on changes using the ``--watch-plugin`` argument to ``girder build``. See the `Girder docs <https://girder.readthedocs.io/en/stable/development.html#during-development>`_ for more information.
+.. code-block:: bash
+
+  # /devops/ver5/docker-compose.local.yml
+  services:
+
+    girder:
+      volumes:
+        - ../../../HistomicsUI:/opt/HistomicsUI
+
+Then use the `devops scripts from the Digital Slide Archive <https://github.com/DigitalSlideArchive/digital_slide_archive/tree/master/devops/ver5>`_.
+
+If you are making changes to the HistomicsUI frontend, you can have the Girder instance watch the local HistomicsUI source code and perform hot reloads on changes by running ``npm run build`` then ``npm run watch`` from ``histomicsui/web_client/``. See the `Girder docs <https://girder.readthedocs.io/en/stable/development.html#during-development>`_ for more information.
 
 Annotations and Metadata from Jobs
 ----------------------------------