https://bugs.freedesktop.org/show_bug.cgi?id=66031
Stephan Bergmann <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |NOTABUG CC| |[email protected] Summary|com.sun.star.style |PyUNO uno.getConstantByName |enumerations missing from |no longer works for enum |pyuno |members --- Comment #6 from Stephan Bergmann <[email protected]> --- (In reply to comment #2) > It looks like uno.Enum has been around a long time, so maybe > getConstantByName was always wrong for enumerations, and just worked by > luck. So this could just be a final break with what has been "don't do > that" behavior for a while. If so, it's still an incompatibility with > pre-4.1 releases, even if the earlier behavior was accidental, so perhaps it > could be mentioned in the 4.1 release notes, if only to save someone else > with similar legacy scripts some time identifying the issue. I just added <https://wiki.documentfoundation.org/index.php?title=ReleaseNotes/4.1&oldid=73013>: "Due to changes for the new type.rdb format, uno.getConstantByName no longer works for UNOIDL enum members, only for UNOIDL constants. Even though uno.getConstantByName had only been documented to work for constants, existing code might have relied on the fact that it somewhat accidentally also worked for enum members." Given the vague documentation of PyUNO, it is hard to tell whether this is a "true" regression, but lets stick to a strict reading of getConstantByName's documentation and mark this NOTABUG for now. If this causes a problem for too much existing code, we could extend the implementation of getConstantByName to also work again for enum members. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
