Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #105572 > unrolled thread
| Started by | "Sven R. Kunze" <srkunze@mail.de> |
|---|---|
| First post | 2016-03-23 23:06 +0100 |
| Last post | 2016-03-23 23:06 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: monkey patching __code__ "Sven R. Kunze" <srkunze@mail.de> - 2016-03-23 23:06 +0100
| From | "Sven R. Kunze" <srkunze@mail.de> |
|---|---|
| Date | 2016-03-23 23:06 +0100 |
| Subject | Re: monkey patching __code__ |
| Message-ID | <mailman.69.1458770767.2244.python-list@python.org> |
On 23.03.2016 09:24, dieter wrote: > But you have observed that you cannot do everything with a > code substitution: a function call does not only depend on the code > but also on other properties of the function object: e.g. the > parameter processing. Yep, that's because Python is very flexible and provides means for changing even that. So, it's not part of the __code__ object but part of the actual function. That's okay. > You might be able to change them in a similar way as "__code__" (i.e. > direct modification). Otherwise, you would need to construct a new > "function object" -- and lose the possibility to completely > change the function object in place. Exactly. Except __globals__ we are all set and I think that'll work for us. I will report once we've implemented it that way. Best, Sven
Back to top | Article view | comp.lang.python
csiph-web