Message245942
| Author | martin.panter |
|---|---|
| Recipients | amaury.forgeotdarc, bgailer, docs@python, eric.araujo, eric.snow, ethan.furman, flox, georg.brandl, martin.panter, ncoghlan, nedbat, r.david.murray, techtonik, terry.reedy |
| Date | 2015-06-29.15:09:56 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1435590596.59.0.134132228015.issue17546@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I quickly scanned through the email thread from Issue 17960. I guess it makes sense to specify that locals() can be used to directly get a class’s namespace. Probably doesn’t hurt to say locals() is equivalent to globals() at module level, although this seems like a fairly redundant feature. Here is locals_doc.03.patch, which uses my wording for function namespaces, and also adds more for class and global namespaces, as suggested by Nick. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-06-29 15:09:56 | martin.panter | set | recipients: + martin.panter, georg.brandl, terry.reedy, amaury.forgeotdarc, ncoghlan, techtonik, nedbat, bgailer, eric.araujo, r.david.murray, flox, docs@python, ethan.furman, eric.snow |
| 2015-06-29 15:09:56 | martin.panter | set | messageid: <1435590596.59.0.134132228015.issue17546@psf.upfronthosting.co.za> |
| 2015-06-29 15:09:56 | martin.panter | link | issue17546 messages |
| 2015-06-29 15:09:56 | martin.panter | create | |