Roundup Tracker - Issues

Message8552

Author schlatterbeck
Recipients rouilj, schlatterbeck
Date 2026-10-12.13:29:39
Message-id <1791811780.12.0.364795757513.issue2551434@roundup-tracker.org>
In-reply-to
I've just upgraded to the latest version in mercurial.
For some re-use in the web interface I'm not just registering functions but also other objects.

I'm now getting a traceback

Traceback (most recent call last):
  File "/home/ralf/roundup/ttt_time2/utils/proplist.py", line 84, in <module>
    db      = tracker.open ('admin')
  File "/usr/local/lib/python3.13/dist-packages/roundup/instance.py", line 123, in open
    extension(self)
    ~~~~~~~~~^^^^^^
  File "./extensions/interfaces.py", line 721, in init
    reg ("ymd",                          common.ymd)
    ~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/dist-packages/roundup/instance.py", line 358, in registerUtil
    self.templating_utils[name]._registered_at = (
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'str' object has no attribute '_registered_at' and no __dict__ for setting new attributes

For one of the occasions I'm trying to register a str.

This used to work.

Why are we setting an attribute 'register_location' to an object registered with registerUtil?
Can we really assume this works for anything that is supposed to be registered there?

If registerUtil is only allowed for function objects we should say so in the docs?
History
Date User Action Args
2026-10-12 13:29:40schlatterbecksetrecipients: + schlatterbeck, rouilj
2026-10-12 13:29:40schlatterbecksetmessageid: <1791811780.12.0.364795757513.issue2551434@roundup-tracker.org>
2026-10-12 13:29:40schlatterbecklinkissue2551434 messages
2026-10-12 13:29:39schlatterbeckcreate