Message266177
| Author |
ionelmc |
| Recipients |
Claudiu.Popa, belopolsky, christian.heimes, eric.snow, eryksun, ethan.furman, grahamd, ionelmc, jedwards, llllllllll, r.david.murray, rhettinger, steven.daprano, terry.reedy |
| Date |
2016年05月23日.19:49:27 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CANkHFr8-vN+LdYB-qJM_WxVLPu8n3iwymsfOg1qZzLireKhfrQ@mail.gmail.com> |
| In-reply-to |
<1464028458.4.0.426910538028.issue23990@psf.upfronthosting.co.za> |
| Content |
On Mon, May 23, 2016 at 9:34 PM, Ethan Furman <report@bugs.python.org>
wrote:
> "Add proxy support to builtins" and should address such things as
> callable, issubclass, and whatever else is is appropriate.
As previously stated this builtin is the only one not doing the right
thing. If you think otherwise, please provide proof. I provided plenty of
supporting examples.
Your "working around" is basically saying "don't use callable or don't
solve your problem". Not an option.
Let me restate the problem: I want to implement a "proxy that resolves the
target at a later time". That means I can't juggle classes ahead of time
(no `resolve_proxy` or whatever) and I can't tell users "don't use
callable" (what's the point of having a proxy then?). |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年05月23日 19:49:27 | ionelmc | set | recipients:
+ ionelmc, rhettinger, terry.reedy, belopolsky, christian.heimes, grahamd, steven.daprano, r.david.murray, Claudiu.Popa, ethan.furman, eric.snow, eryksun, llllllllll, jedwards |
| 2016年05月23日 19:49:27 | ionelmc | link | issue23990 messages |
| 2016年05月23日 19:49:27 | ionelmc | create |
|