Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2001-August/017061.html below:

[Python-Dev] PyObject_SetAttr - is it the only way types should set attributes?

• Previous message: [Python-Dev] PyObject_SetAttr - is it the only way types should set attributes?
• Next message: [Python-Dev] PyObject_SetAttr - is it the only way types should set attributes?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>>>>> "SM" == Skip Montanaro <skip@pobox.com> writes:

  SM> In thinking about the implementation of TRACK_GLOBAL some more,
  SM> I'm trying to figure out where object updating is going to take
  SM> place.  Is PyObject_GenericSetAttr the only way C-based objects
  SM> should set attributes?

C code can manipulate __dict__, too, right?  It's a pretty common
idiom to get a module dictionary and use PyDict_SetItem().  

I'm also curious about the new type-class unification stuff.  Is it
possible to modify a C object via something like a C struct and have
that change be visible as a modified attrbute at the Python level?

Jeremy

• Previous message: [Python-Dev] PyObject_SetAttr - is it the only way types should set attributes?
• Next message: [Python-Dev] PyObject_SetAttr - is it the only way types should set attributes?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4