You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
IronPython handles descriptor replacement differently than CPython #843
If a type is patched with a descriptor, referencing the name on the type (rather than an instance) hits the descriptor's getter/setter, where it does not in CPython.
('__set__', <SomeDescriptor object at 0x000000000000006C>, None, <property object at 0x000000000000006D>)
('__get__', <SomeDescriptor object at 0x000000000000006C>, <Thing object at 0x000000000000006E>, <class '__main__.Thing'>)
<SomeDescriptor object at 0x000000000000006C>
Version info:
IronPython 2.7.12 (2.7.12.1000)
[.NETFramework,Version=v4.5 on .NET Framework 4.8.9232.0 (64-bit)]
Python 2.7.18 (v2.7.18:8d21aa21f2, Apr 20 2020, 13:25:05) [MSC v.1500 64 bit (AMD64)] on win32
Thanks. I'm working around it python-side for now. However, this prompted me to take another look at getting the project updated to use IronPython 3, but I hit some fundamental issues I don't understand. I started a new discussion over in the 3 repo: IronLanguages/ironpython3#1881
Activity
slozier commentedon Jan 22, 2025
For reference, this is fixed in ipy3. Maybe by IronLanguages/ironpython3#1272?
mickp commentedon Jan 24, 2025
Thanks. I'm working around it python-side for now. However, this prompted me to take another look at getting the project updated to use IronPython 3, but I hit some fundamental issues I don't understand. I started a new discussion over in the 3 repo: IronLanguages/ironpython3#1881