Message210099
| Author | larry |
|---|---|
| Recipients | benjamin.peterson, eric.araujo, larry, ncoghlan, pitrou, python-dev, scoder, terry.reedy, yselivanov |
| Date | 2014-02-03.08:45:57 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1391417157.42.0.336317136734.issue17159@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> What I'm saying is that the existing function introspection API > would have provided a much better way to do these things, > and that it's good to finally have the meta data available in the > source code so that that API can be made available at some point. What "existing function introspection API"? I wasn't aware there was an existing mechanism to provide signature metadata for builtin functions. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-02-03 08:45:57 | larry | set | recipients: + larry, terry.reedy, ncoghlan, pitrou, scoder, benjamin.peterson, eric.araujo, python-dev, yselivanov |
| 2014-02-03 08:45:57 | larry | set | messageid: <1391417157.42.0.336317136734.issue17159@psf.upfronthosting.co.za> |
| 2014-02-03 08:45:57 | larry | link | issue17159 messages |
| 2014-02-03 08:45:57 | larry | create | |