PR Summary:

• Extends get_name() in query.py to support DB.Workset objects (which are not DB.Element subclasses and therefore had no .Name retrieval path).
• Replaces the if PY3: engine guard with if hasattr(element, "Name"): to detect name-capable objects dynamically.
• Updates docstring to reflect the expanded type signature.

Review Summary:

The intent of the PR is valid — DB.Workset is not a DB.Element, so the original code had a gap. However, the chosen approach introduces a regression for IronPython 2 (IPY2712), which is the primary runtime for this codebase. In IronPython 2.7, DB.Element objects do expose a .Name attribute via the .NET bridge, so hasattr(element, "Name") always returns True for standard elements — this causes the else: Element.Name.GetValue(element) branch to become permanently unreachable. That branch exists specifically to work around a well-documented IronPython 2.7 bug where direct .Name access on derived element types (e.g. WallType, FamilySymbol, Room) returns the unbound descriptor object instead of the name string. A safer fix uses an explicit isinstance(element, DB.Workset) check while restoring the original PY3 guard.

Suggestions

• Add a unit/integration test covering get_name() with a DB.Workset instance and common element types (e.g. WallType, Room) under both IronPython 2 and CPython 3 engines to prevent future regressions. Apply

Pull request overview

This PR extends pyrevit.revit.db.query.get_name() to also return a meaningful name when passed a Revit DB.Workset, making the helper more universally usable across Revit object types.

Changes:

• Updates get_name() docstring to document DB.Workset support.
• Adds an explicit DB.Workset type check so get_name() can return workset.Name (notably preventing the IronPython/PY2 fallback path from trying to treat a workset like a DB.Element).