holoviz / holoviz/param

Fate of `name`?

Open
#770 24 comments 0 reactions 0 assignees View on GitHub
type-bug
Dominant language
Python
Stars
521
Forks
86
Avg merge
1d 13h
Merged PRs (30d)
35

Description

This was certainly already suggested and discussed multiple times (e.g. https://github.com/holoviz/param/pull/740#issuecomment-1549323783 from @jlstevens) but I couldn't find a specific issue for it. `name` is a `String` Parameter included by default in every Parameterized object. At the class level it's set to the class name so `P.name == P.__name__` and at the instance level it's set to the class name plus a global Parameterized instances count of 5 digits (e.g. `P().name == "P00143"`).

The existence of `name` probably always comes as a surprise to Param users, I'm sure it had some very good reasons to exist when Param was created, however it seems to me this is no longer the case.

I'm sure `.name` is relied upon in many places in the HoloViz source codes (I definitively have code that uses `P.name` instead of `P.__name__`), removing it would certainly need to wait for Param 3.0. Until then, let's discuss how much we want to see it go away and if we do how it could be deprecated.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.