Notes from the meeting
slicer-skill (Steve, and everyone)
- New slicer-skill ai tool
- GitHub - pieper/slicer-skill: SKILLS.md style information for slicer programing and usage
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 ofslicer.utilinto a new package.- With the name
slicer.packagingwe run into a name conflict with thepackagingmodule (a dependency ofpip). - Landed on the name:
slicer.pydeps. Soslicer.pydeps.pip_ensure(...), etc.pyin the name of a python module is kind of annoying. Or is it? pydicom?- Maybe we should actually make
slicer.utilinto an import package and makeslicer.util.pydeps(with a better name thanpydeps). Because we are importing allslicer.*things, and so if “sub-utilities” are all direclty under theslicerpackage 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 beslicer.util.*. - Review can proceed and when we finalize the naming and package organization we can do it at the end before merging.
- With the name