Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #78803
| Path | csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail |
|---|---|
| Return-Path | <rosuav@gmail.com> |
| X-Original-To | python-list@python.org |
| Delivered-To | python-list@mail.python.org |
| X-Spam-Status | OK 0.005 |
| X-Spam-Evidence | '*H*': 0.99; '*S*': 0.00; 'builtin': 0.09; 'default;': 0.09; 'latter': 0.09; 'namespace': 0.09; 'variant': 0.09; 'cc:addr:python-list': 0.11; 'def': 0.12; "wouldn't": 0.14; '"does': 0.16; '"is': 0.16; 'bindings,': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'function"': 0.16; 'function?': 0.16; 'lambda': 0.16; 'marco': 0.16; 'namespace,': 0.16; 'language': 0.16; 'wrote:': 0.18; 'obviously': 0.18; 'wed,': 0.18; 'cc:addr:python.org': 0.22; "aren't": 0.24; 'instance,': 0.24; 'issue,': 0.24; 'cc:2**0': 0.24; 'header:In-Reply-To:1': 0.27; 'external': 0.29; 'am,': 0.29; 'thus': 0.29; 'related': 0.29; 'message-id:@mail.gmail.com': 0.30; 'that.': 0.31; 'class': 0.32; 'sense': 0.34; 'core': 0.34; 'maybe': 0.34; 'subject:the': 0.34; 'connection': 0.35; 'created': 0.35; 'something': 0.35; 'late': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'there': 0.35; 'functions.': 0.36; 'like,': 0.36; 'method': 0.36; 'changing': 0.37; 'too': 0.37; 'list': 0.37; 'subject:" ': 0.39; 'is.': 0.60; 'new': 0.61; 'name': 0.63; 'provide': 0.64; 'more': 0.64; 'different': 0.65; 'situation': 0.65; 'worth': 0.66; 'between': 0.67; 'usage;': 0.84; 'to:none': 0.92 |
| DKIM-Signature | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=/NiY7Ba5VUdTwjsMO2VMK16BYfa9mOS9fa8tO3rExbY=; b=KsCmFzfPw3sMNxio8aj8uk+TrIIMAtfBfV1V3+8QXYZ6yOLQC2hJ3ORGhGFTO3NfPp oLZR5z2YiEXcpGve+R/wASul2i7yJRToeIv21msEWydN+/kbfANMd4WR5vRa56oMai0J GchK/0F+qEitDlIj3fX68mev+qyZ/ZK6QTfcWeCLWN7Ib1CcxNTs6b4p/basJ1ILl07m onk4hnYkFQtTouG60qtHsujyVX7aSJfNRhtXlsV7oImCJIfg1wqnj5A887n955YaFO4/ 7oMUuvTL2AjSAKSJpg3gewWXcL6UqrD5po+ddeheuTUYpYq2lvMIBPsyAA7ERnFdM2Qm TEug== |
| MIME-Version | 1.0 |
| X-Received | by 10.43.94.7 with SMTP id bw7mr4843338icc.26.1412689243866; Tue, 07 Oct 2014 06:40:43 -0700 (PDT) |
| In-Reply-To | <m10pj3$82l$1@speranza.aioe.org> |
| References | <m10pj3$82l$1@speranza.aioe.org> |
| Date | Wed, 8 Oct 2014 00:40:43 +1100 |
| Subject | Re: Muddleheaded use of the "built-in" term |
| From | Chris Angelico <rosuav@gmail.com> |
| Cc | "python-list@python.org" <python-list@python.org> |
| Content-Type | text/plain; charset=UTF-8 |
| X-BeenThere | python-list@python.org |
| X-Mailman-Version | 2.1.15 |
| Precedence | list |
| List-Id | General discussion list for the Python programming language <python-list.python.org> |
| List-Unsubscribe | <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe> |
| List-Archive | <http://mail.python.org/pipermail/python-list/> |
| List-Post | <mailto:python-list@python.org> |
| List-Help | <mailto:python-list-request@python.org?subject=help> |
| List-Subscribe | <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.14660.1412689246.18130.python-list@python.org> (permalink) |
| Lines | 28 |
| NNTP-Posting-Host | 2001:888:2000:d::a6 |
| X-Trace | 1412689246 news.xs4all.nl 2920 [2001:888:2000:d::a6]:33475 |
| X-Complaints-To | abuse@xs4all.nl |
| Xref | csiph.com comp.lang.python:78803 |
Show key headers only | View raw
On Wed, Oct 8, 2014 at 12:24 AM, Marco Buttu <marco.buttu@gmail.com> wrote: > Is it too late for changing the name of the `builtin` namespace in something > like, for instance, `root` namespace, or using the name "core" > (inspect.iscore(), types.CoreFunctionType, ecc.) to indicate "written in C"? Yes, I think it's too late to change that. But it's no different from any other word that has more than one variant of meaning; you have to cope with the collisions. Is there any situation where it's ambiguous? There are builtin name bindings, and there are built-in functions. The former are provided by the language core and are thus available by default; the latter are provided by the language core and thus do not provide __code__. There's a connection between the meanings, but they aren't identical. What's a function? Obviously something created with def or lambda is. Is a class a function? Is an object with a __call__ method a function? Is a list comprehension a function? In different senses, all of them are; but maybe what you want to ask is not "is this a function" but "is this callable" (list comps aren't), or "does this create a new local scope", or "does this have __code__" or something. Yet the meanings of "function" are all related (mostly by external usage; list comps by internal functionality), so it wouldn't make sense to decry the collisions on that word. I do see your issue, but I don't think this can be changed, nor is worth changing. ChrisA
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Muddleheaded use of the "built-in" term Marco Buttu <marco.buttu@gmail.com> - 2014-10-07 15:24 +0200 Re: Muddleheaded use of the "built-in" term Chris Angelico <rosuav@gmail.com> - 2014-10-08 00:40 +1100
csiph-web