2026.02.24 Weekly Meeting

Community Weekly meetings
1

Tomorrow, we will be having our next weekly hangout at 10:00 AM ET until 11:00 AM ET.

Anyone is welcome to join at this link: https://bit.ly/slicer-googlemeet-hosted-by-kitware

Agenda:

Please post to this thread to put a topic on the agenda! We will try to prioritize agenda items during the meeting.

Thanks
Sam and Ebrahim

2

I’d like to have a follow up discussion of the slicer-skill stuff.

2 Likes
3

I’d like to ask about Improve python package installation utilities by ebrahimebrahim · Pull Request #9010 · Slicer/Slicer · GitHub to see see if the naming slicer.pydeps is agreeable.

4

Notes from the meeting

slicer-skill (Steve, and everyone)

Lots of discussion on skills and other coding agent workflows.

pip_install features PR (Ebrahim)

  • Slicer#9010
  • Docstrings shortened; most examples are moved to a new script repository section.
  • Split off the slicer.util.pip_* out of slicer.util into a new package.
    • With the name slicer.packaging we run into a name conflict with the packaging module (a dependency of pip).
    • Landed on the name: slicer.pydeps. So slicer.pydeps.pip_ensure(...), etc.
      • py in the name of a python module is kind of annoying. Or is it? pydicom?
      • Maybe we should actually make slicer.util into an import package and make slicer.util.pydeps (with a better name than pydeps). Because we are importing all slicer.* things, and so if “sub-utilities” are all direclty under the slicer package then we prevent ourselves from using good package names due to this name shadowing issue. We may want to set the precedent now that “sub-utilities” should be slicer.util.*.
      • Review can proceed and when we finalize the naming and package organization we can do it at the end before merging.